The shift-by-shift SOP rollout method

## Why shift-by-shift The one-time-blast approach assumes every frontliner has the same calendar, the same shift availability, and the same urgency. None of that is true at most franchise operations. Some frontliners work 30 hours a week across 5 shifts; others work 12 hours across 2. Some are at the location daily; others are only there twice a month for catch-up shifts. A blast assignment hits everyone with the same deadline, and the part-timers always lag. Shift-by-shift assignment instead targets each frontliner with the training right before their next scheduled shift. The 12-hour-a-week part-timer who works Saturday gets the training assigned Friday morning. The 5-shift-a-week regular gets it the day before their next shift. Everyone has the same effective lead time relative to their work. ## How it works in practice The operating mechanism: HQ uploads the new SOP, the training course is generated, and the rollout is configured with a 'before next shift' assignment rule. Every frontliner who has a shift in the next 14 days gets the assignment, with a deadline of 'completed before that shift starts'. Frontliners with a shift tomorrow get a tomorrow deadline; frontliners with a shift in 10 days get a 10-day deadline. Managers see a per-shift readiness view: looking at tomorrow's shift, here are the 6 frontliners scheduled and which of them have completed the new SOP training. If anyone hasn't, the manager knows before the shift starts and can either push them to complete it during pre-shift, swap them off, or run a 5-minute team huddle on the new SOP at the start of the shift. ## Mobile delivery is non-negotiable Shift-by-shift only works if frontliners can complete the training on their phone. Most frontliner training has to happen on the commute, in pre-shift, on a break, or just after a shift ends. Pulling them into a back-office to sit at a laptop doesn't fit the shift rhythm. Aristotl's mobile-first delivery is built around exactly this — courses run on any phone browser, no install, no app store. ## What you can train shift-by-shift Not everything fits the shift-by-shift method. Quick procedural updates (new menu item, new POS button, new check-in step) work great. New brand standards or significant policy changes work fine. Multi-hour foundational training (full new-hire onboarding, comprehensive compliance) doesn't — these need a different cadence with dedicated training time. The rule of thumb: if the training is under 15 minutes per frontliner, shift-by-shift works. If it's over 30 minutes, you need a different deployment. ## Tracking shift-by-shift The HQ-level reporting changes shape with this method. Instead of a system-wide completion percentage, the relevant number is 'shift readiness' — for the next 7 days of scheduled shifts, what percentage of scheduled frontliners are training-complete? This is a forward-looking metric that tells HQ if the rollout is on track to complete by deadline. A franchise manager seeing 92% shift-readiness for tomorrow's shifts can plan their day. The same manager seeing 60% knows they have a problem and can intervene. ## What good looks like A well-run shift-by-shift rollout has 95%+ shift readiness across every store within 7 days of rollout start, has zero shifts where a frontliner encountered the new procedure without training, and has the rollout fully completed within 14 days of HQ deployment. This is the cadence that scales for franchise systems with irregular-hour frontliners — and it's much harder to run with PowerPoint and a Sheets file than with a real training platform.

Ready to put this into practice?