Multi-location SOP rollout playbook

## The four phases of a rollout A structured SOP rollout has four phases: (1) authoring at HQ — the new or updated SOP is finalized and signed off, (2) deployment — the SOP is converted to training and pushed to every location, (3) location-level training — frontliners complete the training during their shift schedule, and (4) verification — HQ confirms completion and intervenes on laggards. Most franchise systems have phase 1 dialed in. Phases 2, 3, and 4 are where time and quality leak. ## Phase 2: from document to training The gap between 'we have a new SOP' and 'every frontliner is trained on it' is usually a manual content-build cycle. Someone in L&D takes the SOP and rebuilds it as a slide deck or an Articulate course, which takes 2–4 weeks. By the time the training is ready, HQ has already issued the next SOP update, and the L&D team is one rollout behind permanently. The fix is automated transformation: SOP document in, training course out, in hours not weeks. This is the core wedge Aristotl was built around — your existing SOP doc becomes a learner-ready course automatically. The rollout cycle compresses from a quarter to a week, and HQ stops being content-bound. ## Phase 3: location-level training Deployment is the easy half of phase 2. Phase 3 is the hard part: getting every frontliner across every location to actually do the training. The friction at this stage is real and predictable: managers don't prioritize the training during a busy shift, frontliners forget, and the rota schedule doesn't have built-in training time. The answer is mobile-first delivery and shift-by-shift assignment. Each frontliner gets the training in 6–10 minute chunks they can complete on shift during a slow moment, on their commute, or on their break. Push notifications and manager-level dashboards keep the assignment visible. The training is done before the next shift if the location has built it into their rhythm. This is also where franchise-manager dashboards earn their weight. Each franchise manager sees their location's completion in real time, knows who's behind, and can reassign a frontliner to a slow shift to catch up. HQ doesn't have to chase the manager — the manager has the same data HQ does. ## Phase 4: verification The verification phase is where most rollouts die quietly. HQ assumes the rollout is done because nobody is reporting problems. The reality is: half the locations are at 80% completion, a quarter are at 50%, and a few are below 30%. The bottom-quartile locations are failure points if an audit, an incident, or a regulator visits. A real verification dashboard shows completion rate per location, days-since-deployment, and a red flag on locations below threshold. HQ can intervene specifically on the lagging locations — a regional manager call, an extra shift assignment, an escalation to the franchisee. This is operational follow-through that turns a rollout from 'we issued it' into 'every location did it'. ## The cycle-time benchmark A well-run multi-location rollout completes in 14 calendar days from SOP authoring complete to 95%+ completion across all locations. That's the benchmark. Most franchise systems we've audited run 60–90 days for the same outcome. The 14-day target is achievable when (a) authoring-to-training is hours not weeks, (b) deployment is push-not-pull, (c) location-level dashboards exist for franchise managers, and (d) HQ has visibility to intervene on laggards. ## What to measure Three numbers, weekly: median time-from-authoring-to-95%-completion, percentage of rollouts completed within 14-day window, and number of locations consistently in the bottom quartile. The first two measure the system; the third identifies which franchisees need a different conversation. All three are uncollectable without real tooling — and that's why most franchise systems don't track them.

Ready to put this into practice?