Rolling out a menu change across 50 QSR stores

## Day -14 to -10: HQ authoring The rollout window opens 14 days before launch day. In days -14 to -10, HQ finalizes the new-item recipe cards, the assembly procedures, the allergen-and-nutrition information, and the upsell flow on POS. This is HQ's job and the training cannot start until these are stable. Most chains run their authoring late and compress the rest of the rollout — the fix is moving authoring earlier in the cycle. ## Day -10 to -7: training content built Days -10 to -7 are when the training content gets built. With document-to-course AI, this is hours not weeks. The recipe cards become an ingredient-and-assembly course. The allergen sheet becomes an allergen-update course with scenario questions ('A guest just told you their child has a milk allergy and they're asking about the new chicken sandwich — what do you do?'). The POS-flow update becomes a 4-minute walkthrough. The upsell-flow update becomes a 6-minute scenario module. This is where most operators historically get stuck — the L&D team can't build training fast enough, and the rollout extends beyond the 14-day window. Aristotl's content-from-document workflow is designed to compress this build. ## Day -7 to -3: store-level training Days -7 to -3 are when the training rolls to every store. Each crew member gets the courses assigned, with completion gates: ingredient-and-assembly course before they touch the new item, allergen course before they handle a guest order, POS-flow course before they ring up a transaction with the new item. This works only if (a) the courses are mobile-accessible and crew members can complete them on shift breaks or commute, and (b) franchise managers have a per-store dashboard so they know who's behind. Aristotl's HQ-to-franchise dashboard hierarchy is built for exactly this — HQ sees the rollup, each franchise manager sees their own store. ## Day -3 to -1: the gate check Days -3 to -1 are the gate-check window. HQ pulls a report: which stores are below 90% completion on each of the three required courses? Those stores get a regional-manager call, an extra training shift, or in extreme cases a launch-delay flag. This is the difference between a launch that goes well and a launch where store #34 is making the new sandwich wrong on day one because nobody at that store completed the assembly course. The gate check is impossible without HQ-level dashboards. Most chains skip it because they can't actually see who's behind. Aristotl's dashboard makes the gate check a 5-minute exercise. ## Launch day: live monitoring Launch day, HQ should be tracking three things: completion rate at each store (residual training to be finished), customer complaints by store (early indicator of training gaps showing up live), and allergen incidents (any store reporting an allergen-related concern). The first one is your training-side metric. The second two are leading indicators that some training didn't land. ## Day +1 to +14: post-launch retraining Days +1 to +14 are the post-launch loop. Customer complaints and allergen near-misses should trigger targeted retraining at specific stores or for specific crew members. If five customers complain about wrong assembly at store #19, that store gets a refresh of the assembly course pushed to every crew member, and a manager-level note. If an allergen near-miss happens anywhere, the allergen course gets re-pushed system-wide as a 5-minute refresher. ## What good looks like A well-run QSR menu rollout has every store at 100% required-course completion 24 hours before launch, has zero allergen incidents in the first month, and has customer-complaint rate within 10% of the chain's baseline. The 14-day cadence is the delta between operators who run rollouts as a competence and operators who treat each rollout as an emergency.

Ready to put this into practice?