Employers
A complete rollout in ninety days
Ninety days are enough to go from a decision to a scheme that runs itself: thirty days to scope and open, thirty to run the first group, thirty to extend and industrialise. Here is the detailed calendar, week by week, with what each milestone produces.
The three phases, milestone by milestone
Each phase closes on an identifiable deliverable, which makes the calendar checkable: on day thirty, a pathway is open or it is not. It also lets your leadership follow progress without an extra meeting.
| Period | What happens | Your decision | Milestone deliverable |
|---|---|---|---|
| Days 1 to 15 | Scoping, mapping, module selection | The pilot population and the deadline | The map of target skills |
| Days 16 to 30 | Setup, importing people, opening | Roles and permissions | The first pathway open |
| Days 31 to 60 | Running the pilot group, assessments | The pass threshold applied | The first dated export |
| Days 61 to 90 | Extending to other departments, automation | The scope of the second wave | The scheme in steady state |
What is decided in the first thirty days
The quality of the whole scheme is decided in the first month, on three choices. Once set, they hold: revisiting them mid-course costs more than spending an extra hour on them at the start.
Choosing the pilot population
A willing department, led by a committed manager. An imposed pilot measures constraint, not the scheme.
Distributing permissions
Department managers enrol their own teams. That is what avoids the week-two bottleneck.
The internal announcement
What is required, why, and the time released to do it. An announcement that names the released time changes participation.
The scheduling markers that hold
- of initial scoping
- 40 min
- to the first pathway open
- 30 j
- to steady state
- 90 j
On a real case, with the decision-maker. It is the only meeting required before opening.
For a need covered by the existing base. Bespoke production adds to this calendar.
The scheme then runs on your internal roles, with a monthly review.
Scheduling questions
Can we start during a peak period?
Yes, by calibrating the window rather than the content. Short modules run in a few minutes at a time, offline if needed, which makes them compatible with a production peak. A long programme, by contrast, benefits from opening just after the peak: the first week is the one that sets attendance.
What if the pilot falls behind?
A late pilot is information, and it is the scheme's first useful measurement. It usually points to a window that is too tight or time that was not released. The window widens for the second wave, backed by a figure rather than an impression.
Should we wait for the pilot before launching wave two?
It is better to wait for its first export, on day sixty. It brings three quantified lessons: actual time spent, the modules that raise questions, and the populations needing a wider window. Wave two then costs less and runs faster.
Explore next
- Multi-siteRolling out consistent training across several sites: identical content, framed local adaptation, reporting consolidated by site, region and department.
- Field and offlineField training on phones and offline: module downloads, running without a network, timestamped syncing, short formats and materials for occasional readers.
- OnboardingCorporate onboarding pathway: triggered on arrival, common base, role risks, a dated record per person and a history that follows the employee.
- SubcontractorsTracking subcontractor training: dedicated access per contracting firm, results feeding your dashboard, distinction in the export and a recorded common induction.
- ComplianceBuilding a training file that stands up to inspection: export contents, procedure versions, refresher deadlines and the professional titles of compliance.
- Site HSETraining the HSE line of an industrial site: 140 modules available, four professional titles from officer to risk manager, recorded induction and a defensible register.