Publishing a menu is a starting point. The ongoing work is making sure the guest-facing information keeps pace with the restaurant. Give that work an owner and connect it to changes your team already tracks.
Define what triggers a review.
Make a menu review part of a recipe change, supplier substitution, new garnish, or preparation-method change. A familiar dish name does not mean the ingredient and preparation information has stayed the same.
Give updates a clear owner.
Decide who gathers the details, who checks them with the kitchen, and who updates the digital menu. In a small restaurant, one person may hold multiple responsibilities. In a restaurant group, make location-level differences explicit.
Use a short, repeatable checklist.
- Identify the dishes affected by the change.
- Collect the current recipe and ingredient information.
- Review allergen details, possible modifications, and preparation notes.
- Update the menu and tell the service team what changed.
- Open the guest-facing menu to check the published information.
Check what guests actually see.
Use the same link or QR code your guests use. Look at the dish details and selected-allergy experience on a phone. Do not assume an update is complete until the public information reflects the intended change.
Keep questions connected to people.
Make it easy for guests to talk with staff. When the team is uncertain about an ingredient or preparation detail, investigate it rather than relying on an old digital record.
Software can organize the information. Your restaurant’s team must verify it and maintain its own allergen procedures.
See how allergen management in MyMealMenus supports dish-level information, or start with the digital allergy menu setup guide.