Most chains change the menu four to six times a year. Each change touches product, supply chain, signage, POS, marketing and training at once, and of those six the training strand quietly decides how launch week reads. Everything else can be right and the launch still shows up as complaints in week one, because at store thirty-four nobody was shown how the item is built.
This is a deliberately sector-specific guide, written with foodservice constraints in it: a crew that turns over, shifts that never contain the same people twice, a counter that has to answer questions the moment the item goes live, and a launch date set by marketing that will not move.
Counting backwards from the first order, not forwards from the brief
The rollout window is fourteen days, counted backwards. Marketing owns the launch date and everything else is derived from it, which is a different habit from the one most operations teams have, where a project starts when the brief lands and finishes when it finishes.
Four blocks fit inside those fourteen days: HQ finalises, training gets built, stores complete it, and readiness gets checked with time left to act on a store that is behind. Compress any one and the compression lands on the last block, because the launch date does not move. That is why the gate check gets skipped by exactly the chains that most need it.
Days fourteen to ten: the spec has to stop moving
In the first block, HQ finalises the recipe cards, the assembly and plating standards, the allergen and nutrition information, and the POS flow including any upsell prompt.
The rule here is not that the work has to be good, which everyone agrees on. It is that it has to be frozen. Training built on a spec still being adjusted has to be rebuilt, and rebuilding it consumes the block that belonged to the stores. If a supplier substitution is still open on day ten, close it or accept that the item launches with a change to be pushed separately.
Most chains author late and compress everything downstream. The fix is not a faster training team. It is moving authoring earlier and treating the day ten freeze as a real deadline with a named owner.
Days ten to seven: turning a spec into something finishable on a shift
The second block converts the spec into training. What comes out of it should not be one course about the new item. It should be a small set of short modules that match the moments in a shift where they will actually be used.
Typically four things. An ingredients and assembly module from the recipe card, with the plating reference photo from the launch kit in it rather than described in words. An allergen module, discussed separately below because it behaves differently. A POS module covering how the item is rung up, short and dull, which prevents a surprising amount of queue time. And an upsell or service module if the item comes with a script.
Two design points carry the weight. Keep each module to a few minutes, because crew complete these between rushes, not in a training room. And write the questions as situations rather than recall: is the sauce on the side by default, what comes with it, can it be made without the cheese. Situations tell you afterwards what a store cannot handle. Recall questions tell you who read the card.
The allergen gate is a dependency, not one of the four modules
Treat this differently from the rest, because it is the one part of a menu change with a legal edge on it.
A new item is not only a new recipe. It is a new allergen answer that whoever is standing at the counter has to be able to give correctly, from the moment the item is orderable. Under Regulation (EU) 1169/2011 art. 44(1)(a) and its Belgian and Dutch implementations, allergen information for non-prepacked food is mandatory, and where it is given orally the person giving it has to be able to give it correctly. Our allergen guide sets out what those national rules require and what they do not; the point for a rollout is narrower.
Three things follow operationally. The written allergen file at each site is updated on the launch date, not after it, because that file is what an inspection asks for and what the oral answer derives from. The counter is trained on the new answer before the item is sellable, not during launch week. And if a supplier specification for a bought-in component is still outstanding on day seven, the item is not ready, however well the assembly training went.
That last one is what makes it a gate rather than a module. Treat an unresolved allergen specification the same way you would treat undelivered stock: the item does not go on the menu at that site.
Days seven to three: fifty stores, on shift, on their own phones
The third block is where the training reaches people, and it works only under two conditions.
First, crew can actually complete it: on a phone, in the browser, in short pieces, in the language each person reads, inside paid time. A network with a mixed crew and three shifts has no other route that reaches everyone. Second, the person who can act on a store being behind can see that it is behind, on the day, without asking head office for a report.
Sequence the assignment to the work rather than to the course catalogue. Assembly before anyone touches the item. Allergen before anyone takes an order for it. POS before anyone rings it up. On a rota where the same person does all three within one shift, that ordering is mostly notional, but it is exactly right for a store that is phasing crew in.
Days three to one: the check that most chains cannot run
Three days out, someone has to look at the network and answer one question: which stores are not going to be ready.
The answer is not a network percentage. A network at ninety-something tells you nothing about whether store thirty-four is at zero, and store thirty-four is the whole problem. Read it per store, per required module, ideally per shift, because a store with two shifts trained and one untrained looks fine on the average and fails on a Tuesday morning.
Then act, with three responses ranked. A call from the area manager for a store that is close. An extra pre-shift huddle on the weak item for a store behind on one module. And for a store genuinely not ready, holding the item off that store's menu. Chains find the third unthinkable until the first time they use it, and then it becomes normal, because it is cheaper than a wrong allergen answer at a site nobody checked.
Launch day and the fortnight after
On launch day, watch three things per store rather than in aggregate: remaining completions, customer complaints, and any allergen question the crew could not answer. The first is your training metric. The other two are the early signal that something did not land.
Run the fortnight afterwards as a correction loop rather than a post mortem. Complaints clustered at one store about assembly means a short refresh at that store, not a network email. The same complaint at fifteen stores means the module is wrong, and the fix is to rewrite it. An allergen near miss anywhere is the one case that justifies going network-wide, as a short refresher rather than a re-run.
Getting a launch through Aristotl
The documents you produce for the launch anyway, the recipe cards, the plating standards, the allergen sheet and the POS note, are the input. Aristotl turns them into the short modules described above, with scenario questions, which is what removes the build block as the bottleneck rather than adding people to it.
Assignment runs by role and location with a deadline of the day before launch, and each person receives the content in their own language.
The dashboard reports completion and knowledge check results per site, role and version. That makes the readiness check a short exercise instead of an impossible one, and the version dimension tells you, when the recipe changes again in eight weeks, who is trained on which version. Corrections after launch go to a single site, shift or role, and the record of who received them sits next to what triggered it.
Walk us through the launch that went wrong last year
Bring the item, the documents you shipped with it, and the stores that struggled. In a demo we build that launch as it should have run and show what the readiness view would have looked like on day three, which is usually the moment the conversation stops being about training.