SchoolStackMost LMS rollouts don’t fail on the technology. They fail because every teacher uses the system differently, students can’t find anything, and by spring half the staff are back on email and shared drives. A good rollout is mostly about agreeing on a few conventions and helping teachers stick to them.
This plan assumes you have already picked a platform. If you haven’t, start with our LMS ranking and the Google Classroom vs Canvas comparison.
Before launch: set up the plumbing
Teachers lose patience fast if classes are missing or students can’t log in. Before any teacher training:
- Rostering. Connect the LMS to your student information system so classes, teachers and students sync automatically. Avoid manual CSV uploads if you can, because they go out of date within weeks.
- Single sign-on. Students should log in with the account they already use, usually Google or Microsoft.
- Integrations. Connect the tools teachers already use, such as quiz apps or a video platform, through LTI or the LMS’s built-in integrations.
- Test accounts. Create a test student in every year group and log in as them on the devices students actually use.
Agree on a few conventions
Students take six or more subjects. If each teacher organises their course differently, students spend their time hunting for work. Agree on a short list of conventions before launch:
- How courses are named, for example “8B Science 2026”.
- How content is organised, for example one module or topic per unit, with the newest at the top.
- How assignments are named and when due dates are set.
- Where homework goes, and whether it always has a due date.
- How feedback is returned.
Keep the list to one page. Build a course template that follows it, so teachers start from a working example rather than a blank page.
Term 1: start with a pilot group
Choose a group of eight to fifteen teachers from different departments, including a few who are not keen on technology. They:
- Use the LMS with their classes for the full term.
- Test the conventions and suggest changes.
- Become the people other teachers ask for help in their department.
Hold a short check-in every two weeks. Fix problems with rostering, devices and integrations quickly, because the pilot teachers will tell everyone else about them.
Term 2: train everyone in small steps
Don’t train every feature at once. Most teachers need three things in their first weeks:
- Posting materials.
- Setting an assignment with a due date.
- Returning feedback and grades.
Run short sessions, ideally led by the pilot teachers in each department. Follow up with a one-page guide and a short screen recording for each task. Advanced features such as rubrics, quizzes and analytics can wait until teachers are comfortable.
Term 3: set the expectation
By the third term, make the LMS the expected home for homework and course materials. Say so clearly, and give a date. Then:
- Check a sample of courses against the conventions, and offer help where they don’t match.
- Show families how to see their child’s work, either through a parent view or a weekly summary email.
- Retire the old tools, such as shared drive folders or a homework app the LMS replaces.
Measure whether it worked
At the end of the first year, check:
- What share of classes posted homework in the LMS each week?
- What share of assignments had a due date and were returned with feedback?
- What do students say about finding their work? A three-question survey is enough.
Use the results to update the conventions and plan the next year’s training.
Common mistakes
- Launching in the middle of the year without a pilot. If you can, start with a pilot in one term and launch fully at the start of a school year.
- Training on everything at once. Teachers remember what they use in the following week.
- No conventions. This is the most common reason students give up on an LMS.
- Keeping the old system running indefinitely. Set a date and switch it off.