How to Retrain 19 Locations on a Menu Change in One Day

It's Thursday, 2pm. The new menu is final: two items out, one item in at $16.95, three price changes, one new allergen note that legal actually cares about. It goes live tomorrow at open — across nineteen locations, three of which have a GM who started this quarter.

Every multi-unit operator has lived this day. Here is the playbook for surviving it — first the manual version, honed by people who did it with group chats and laminators, then the version where software does the sprinting. The manual version works. It just costs a day nobody billed for.

First, the standard: what “trained” means

Before any plan, define done. A location is trained on a menu change when every scheduled front-of-house person can, without looking: name the new item and its price, describe it in one guest-ready sentence, flag its allergens, and knows what to say when a guest orders something that's gone. Anything less is “we sent an email,” and emails don't sell chicken.

The manual playbook, hour by hour

2:00pm — Freeze the facts

One document, one owner. Item names, exact prices, one-sentence descriptions, allergens, 86'd replacements (“if a guest asks for the Smokehouse, offer the Nashville Hot”). Every downstream mistake tomorrow will trace back to ambiguity here, so write it like a recipe, not a memo.

2:30pm — Rewrite the training, ruthlessly small

Do not update the 40-page handbook today. Build a one-page cheat sheet and a five-question quiz. What changed, what to say, what it costs, what's in it. If you have an LMS, this is where you discover how many separate lessons mention the old burger — budget an hour of clicking per course that touches the menu, and don't forget the Spanish versions.

4:00pm — Push it through people, not channels

A message blast is not a training plan; it's a hope plan. Send the sheet to all nineteen GMs, then require a human acknowledgment from each — a reply, not a read receipt. The three new GMs get a phone call. Regional managers own chasing the silent.

Friday, pre-shift — Verify at the line

Pre-shift is the exam. Each manager runs the five questions out loud and spot-checks the two riskiest facts: the allergen and the price. Whoever misses gets the cheat sheet again and a re-ask before their first table, said kindly — the goal is a confident answer at table six, not a gotcha at the host stand.

Friday, 10am — Close the loop

Every GM reports done or not-done. No dashboard, so this is nineteen threads to reconcile — and honestly, it's where manual versions die. Most groups skip verification because collecting it is more work than the training was. The stores that quietly skipped pre-shift are the ones a guest will find for you.

Where the day actually goes

Walk the timeline and notice what consumed it. Deciding the facts took thirty minutes and genuinely required leadership. Everything after — finding each affected lesson, rewriting slides, re-doing the Spanish, chasing acknowledgments, tallying who finished — was administration. Call it six hours of skilled people doing clerical sprints, times every menu change, seasonal rollout, and price adjustment in a year. The work wasn't hard. It was long, and long is what gets skipped the third time it happens in a quarter — which is exactly how training drifts out of sync with the menu for good.

The same day, with the sprinting automated

This is the day we built PlateSpec around. The same Thursday, with software carrying the clerical weight:

• 2:00pm: You type: “86 the Smokehouse Burger. Add the Nashville Hot Chicken at $16.95 — fried chicken, cayenne butter, pickles. Contains dairy and gluten.”
• 2:01pm: The AI returns one ticket: every lesson, card, and quiz question the change touches, shown as red for removed, green for added, amber for edited. You read it in a minute, fix a word if you want, and approve.
• 2:05pm: One tap fires it to all nineteen locations. Spanish versions update themselves. Crew get the new cards on their phones — the same phones they already log into with a QR code and no password.
• Friday pre-shift: managers still run the five questions out loud — software shouldn't replace pre-shift, just arm it. But now the Command board already shows completion moving, store by store, live.
• Friday 10am: nobody collects anything. The board is the loop, closed: eighteen green, one amber, and you know which GM gets the friendly call.

Same standard, same human judgment at the decision points — minus the six hours of sprinting. Which means it actually happens, every time, including the small Tuesday price change that today doesn't feel worth the ceremony. That's the whole trick of keeping training current: making the update cheaper than the drift.