How to
How to roll out a menu change across QSR locations
Update every crew member on the new menu before launch day: convert the menu spec, build prep modules, assign network-wide, and verify completion site-by-site.
Step-by-step
Upload the menu spec and prep guides
From the HQ dashboard, upload the new menu spec sheet, prep guides, and any allergen/safety updates. Aristotl extracts ingredient lists, prep steps, plating standards, and allergen information into structured content. The output is a parsed module tree organized by item - burger A, side B, drink C - ready to be turned into per-item training. Confirm the parse.
Build per-item prep modules with photo references
Generate the menu-launch course. Aristotl creates a short module per new item - typical structure: ingredients → assembly steps → plating reference photo → allergen flags → quiz. For QSR contexts, scenario-based prompts work best ('A guest asks if item X is gluten-free - what's the response?'). Add real photos from the launch kit. Total course usually 20–30 minutes.
Assign network-wide with launch-day deadline
Target every crew-member role across every location with a deadline of launch-day-minus-1. Auto-translation handles each location's language mix. Aristotl sends notifications immediately and reminders midway through the window and again near the deadline. Franchise managers see live progress per location, so they can run a 10-minute pre-shift recap on the lowest-scoring items.
Verify launch-day readiness site-by-site
On launch morning, open the menu-launch dashboard. Every location should be fully complete with quiz averages above your operational threshold. Locations falling short trigger a manager flag - the location either runs a final huddle or holds the new items off the menu until staff are ready. Export the readiness report for ops leadership.