An HR lead at a 60-person company gets the task: roll out an LMS by the end of the quarter. They buy a licence, upload PDFs, and two weeks later nobody is logging in. The product is not the problem. The problem is that an LMS rollout without a timeline looks like a purchase, but it is a project with parallel workstreams.
This guide splits the rollout into eight weeks with milestones, owners and two worked examples. It targets teams under 100 people, where one HR lead runs it alongside normal work.
Why eight weeks and not two
Vendors often promise "live in a week". The account is open and content is uploaded — technically true. But rollout is not only the technical setup. It covers three parallel workstreams:
- Technology. SSO, user import, roles, integrations with HRIS or e-signing.
- Content. Which modules go first, who approves them, how completion is measured.
- Behaviour change. Who is mandated, what happens after 30 days of inactivity, how success is shown.
Two weeks cover only the first stream. The others fall on HR three months later, when employees still do not open the modules. Eight weeks keeps all three streams aligned inside one quarter.
Week 0: ownership and inventory
Before the first vendor call, decide three things:
- Project owner. One person, not a committee. Usually the HR director or an L&D specialist.
- Executive sponsor. The CEO or COO who signs off on mandatory status and frees IT hours.
- Inventory of existing content. PDFs, PowerPoints, recordings and third-party courses, with the last-update date.
The inventory usually shows 20 to 40 existing items, about half outdated. That is not a problem — it is the starting point. In the first two months you import 8 to 12 modules, not all of them. The rest wait for the second iteration.
Weeks 1 and 2: vendor selection and the pilot module
Shortlist three vendors. Each gets the same question and the same demo task. Example task: "Show how an employee completes a 5-minute GDPR refresher and how HR gets a completion report by department."
Three signals that separate an SMB-friendly vendor from an enterprise tool:
- Fast setup without vendor-side implementation weeks. Three calls before the first user session means hidden implementation cost.
- Transparent per-user pricing. Ask for a written quote with every add-on (SSO, API, SCORM import).
- Local-language interface and support in the EU time zone. A team under 100 has no budget for 24-hour enterprise support.
In parallel with selection, write the pilot module that will go first. The ideal choice is an annual mandatory module (compliance, workplace safety, GDPR refresh) with a clear audience and a measurable outcome.
Weeks 3 and 4: technical setup
Once the contract is signed, the first four weeks are technical. Milestones:
- Week 3, days 1 to 3. SSO integration (Google Workspace or Microsoft 365). Without SSO, people forget passwords and completion drops.
- Week 3, days 4 to 5. Import users from HRIS or CSV. Each user needs the correct department — reporting depends on it.
- Week 4, days 1 to 3. Role setup: HR admin, manager, learner. The manager sees completion for their own team, not others.
- Week 4, days 4 to 5. Import the pilot module and test. HR walks the full path as a learner.
Most SMBs stall at the user import step. If the HRIS has no department-level export, clean the CSV manually — a one-off task of 2 to 3 hours.
Weeks 5 and 6: pilot with a small cohort
A pilot is not a demo. It is a hand-off test with 10 to 15 people from two departments. Target: 85 % completion in 10 days and at least three written notes on what went wrong.
Pilot structure:
- Week 5, Monday. Launch email with a short video on what the LMS is and why they are first.
- Week 5, Thursday. First check: how many logged in, how many started the module.
- Week 6, Monday. Reminder to anyone under 50 % progress.
- Week 6, Friday. A 15-minute interview with three participants. Record it, do not take notes live.
Pilot feedback is worth more than vendor documentation. Usual result: two click-blockers (wrong redirect after login, a quiz that does not save answers) and three content questions to rewrite before full rollout.
Weeks 7 and 8: full rollout
With click-blockers fixed, go into full rollout. Milestones:
- Week 7, Monday. The CEO or COO sends an internal note. Mandatory status, 21-day deadline for the first module.
- Week 7, Wednesday. Managers get dashboard access and a 15-minute briefing on how to read completion.
- Week 8, Tuesday. Automated reminders to anyone without progress, not manual.
- Week 8, Friday. First sponsor report: completion rate, average time, three learner quotes.
After eight weeks you have the first module in production and a template for the second. The second rolls out in three weeks, not eight.
Example 1: Accounting firm, 45 people
Twelve clients, an annual GDPR obligation, an internal code of conduct. The prior year the firm used PDFs by email with an Excel log. Paper completion 100 %, actual reading rate about 30 %.
Eight-week rollout:
- Weeks 0 to 2. Project owner: finance manager. Sponsor: managing director. Shortlist of three vendors, choice driven by local-language support and SSO.
- Weeks 3 to 4. Google Workspace SSO, import of 45 users from Workspace Admin, three departments.
- Weeks 5 to 6. Pilot with 10 people from two departments. One click-blocker (progress lost on page refresh), vendor fixed it in 48 hours.
- Weeks 7 to 8. Full rollout. GDPR refresher in three 5-minute modules. 42 of 45 completed in 14 days. The other three were on leave.
Total: 48 hours of finance-manager time over eight weeks. The old system took 20 hours a year for the Excel log plus 15 for checks.
Example 2: Manufacturing company, 90 people
Three sites, mixed workforce — 25 office and 65 production staff without a work computer. The annual workplace-safety refresher was a two-hour classroom session.
Eight-week rollout:
- Weeks 0 to 2. HR lead as owner, operations director as sponsor. Extra constraint: production staff need a personal phone or shared tablet during breaks.
- Weeks 3 to 4. Microsoft 365 SSO for office, a QR code with an individual code for production. Import of 90 users across five departments.
- Weeks 5 to 6. Pilot with 12 people (6 office, 6 production). Biggest issue: the production module ran 12 minutes, too long for a break. Split into three 4-minute parts.
- Weeks 7 to 8. Full rollout. 84 of 90 completed in 21 days. Four absent, two on parental leave.
Three months in, the operations director compares: 6 hours of classroom time versus 12 minutes per employee. An inspection audit shows comparable retention at a lower production-downtime cost.
For a deeper view on importing existing content, see SCORM import guide.
Common timeline mistakes
- Skipping week 0. Without an owner and sponsor, the project stalls by week 5. Put two names on the kickoff email.
- Full catalogue in month one. Forty modules at once dilute focus. One module in month one, three in month two, full catalogue by quarter four.
- Pilot without interviews. Completion alone will not explain why three dropped out. A 15-minute call shows more than a chart.
- No dashboard for department managers. If only HR sees completion, no one pushes. A manager with their own number behaves differently.
- Manual reminders. By week 10 the HR lead gives up. Automate them in week 4.
The last point is the most common. An automatic reminder after 7 days of inactivity lifts completion by 10 to 15 percentage points with no extra work.
What to do this week
Write a one-page document: owner, sponsor, list of 8 to 12 existing items, and the target date for the first pilot module. That is week 0. Without it, every vendor contract starts on shifting ground.
Rolling out an LMS like Mentor in a sub-100-person company is a habits project, not a tech project. The eight-week timeline works because it runs tech, content and adoption in parallel. Once the pilot shows the first numbers, the second module rolls out three times faster than the first.