Where menu changes get lost
Picture a familiar kind of week. On Tuesday the chef switched the house pesto from a sunflower-seed base to cashews because the usual supplier was short. The kitchen knew. On Thursday night a guest mentioned a tree-nut allergy and asked about the pasta. The server checked the allergen sheet taped by the host stand, and it still listed sunflower seeds and no tree nuts. A cook caught it when the order came in. Nobody was careless. The change had simply reached half the restaurant.
That gap is a communication problem, not a cooking problem. Your trained staff and your published allergen policy decide what is safe to serve and what to tell a guest. Software cannot guarantee that a dish is free of an allergen, and it should never pretend to. What it can do is make sure that when something changes, everyone who answers guests sees the same current information at the same time, and that you can tell who has seen it. TwoQM develops automation, custom software, and connected systems for restaurants and food businesses that need that kind of record.
Here is an original example, not a TwoQM client and not a measured result. A neighborhood café with a busy weekend brunch changes three things in one week: a gluten-free bread from a different bakery, a seasonal soup made with cream instead of coconut milk, and a sauce removed from the online menu but still printed on the brunch insert. The changes travel by group text, a sticky note on the expo printer, and a Friday lineup the Sunday servers never heard.
The leaks are usually the same:
The kitchen's prep sheets change, but the server-facing allergen sheet does not.
Online ordering, the printed menu, and the POS item descriptions drift apart.
Evening and weekend staff miss the lineup where the change was announced.
A mid-week supplier substitution is never written down at all.
Afterward, no one can say which version of the information a server was looking at.
One change, one notice, two audiences
Treat every menu change as a record, not a conversation. When the chef or kitchen manager changes a recipe, an ingredient, or a supplier, they log it once:
What changed. The dish, the ingredient, and the old and new versions.
Why and since when. Supplier substitution, seasonal swap, new item, or removal, with the effective date and shift.
Allergen information affected. Which items on your restaurant's own allergen list are added or removed, as your trained staff determine them. The system records their decision; it does not make one.
Who approved it. The person your policy holds responsible for allergen information.
What guests should be told. Your approved wording for servers, so nobody improvises.
From that single entry, the same notice goes to the kitchen and the front of house together. The kitchen sees it on the prep or station view. Servers, hosts, and bartenders see it in their shift notes. The server-facing allergen reference updates from the same record, so a taped sheet stops being the source of truth.
Ask for acknowledgment, not just delivery
A notice that was sent is not a notice that was read. Ask each staff member to tap to acknowledge a change before or at the start of their next shift. Then a manager can see, before doors open, who missed Tuesday's pesto change.
Keep the rules short:
Changes that touch allergen information require acknowledgment; a new garnish can be informational only.
Staff who were off see pending notices when they clock in or open their shift view.
Managers get a list of who has not acknowledged by a time you choose.
Old versions stay on file with dates, so you can see what was posted on any given night.
That history helps with training and with reviewing a guest concern. It is a record of communication, not a compliance program. Your own policies, your local health department's requirements, and professional food-safety guidance still govern how you handle allergens.
Keep every published menu in step
Many restaurants run a POS, online ordering, delivery apps, a website menu, and printed menus. When a change reaches only some of them, guests read different descriptions in different places. Keeping them aligned is connected systems work: one approved change creating updates or tasks for each place the item appears. Whether your POS or ordering platform accepts a clean connection is confirmed during scoping. When it does not, the right answer may be a checklist task such as "reprint the brunch insert" assigned to a person and closed on the same record.
Automation first, then AI drafts a person reviews
Conventional business automation covers most of this: sending the notice to both teams, collecting acknowledgments, reminding staff who have not read it, alerting a manager before service, and opening menu-update tasks.
AI can help with wording, under review. It can turn a chef's quick note into a clear draft notice for servers, or draft a Spanish version for a bilingual crew, which a manager checks before it goes out. It should not decide what contains an allergen, answer guest allergy questions on its own, or publish menu changes. A person approves every word.
Where to start this week
Pick the last five menu changes you made and trace each one: where it was announced, who heard it, which menus and sheets were updated, and how long the old information stayed posted. Then decide who in your restaurant approves changes that touch allergen information, and how servers will confirm they have seen them.
If you want menu and allergen notices on one record that the kitchen and the floor see together, TwoQM can scope it around your menus, your policy, and the tools you already use. Pricing explains how business apps, systems, and custom software are scoped.
Describe Your Menu-Change Workflow · Explore TwoQM business automation