When a guest asks about an allergen, identify the exact item, variation, location and service first. Share only information confirmed by the current recipe or trained food-safety contact; otherwise say it is not confirmed, escalate the question and correct the public menu if verified information has changed.

This is a service-time decision guide, not medical or legal advice. It does not tell a restaurant that a dish is safe for a particular person. It gives the team a repeatable way to avoid a worse failure: turning an incomplete menu label, a past recipe or a colleague’s memory into a confident promise.

The U.S. Food and Drug Administration’s food-allergy guidance explains why a food-allergy question deserves specific, current information. A restaurant should define its own food-safety process, trained contacts and preparation controls for each location.

Start with the exact question, not a general label

“Does this contain nuts?” is not yet enough to answer. The team needs to know which menu item, which version, which service and which location the guest means. A lunch preparation, a dinner variation or a seasonal garnish can change what must be checked.

Confirm before answering Why it matters Useful response
Item and variation A base item and its add-on can differ “Which dish and option are you considering?”
Location and service Recipes and availability can vary “Let me check the current preparation for this service.”
The question’s scope “Contains” and “can you guarantee” are different requests “I can confirm only what our current source covers.”
Current source A menu page is not a substitute for verification “I will check with the kitchen contact before I answer.”

Do not ask the guest to explain their medical history. The only information needed for this operational handoff is the food question they chose to ask. If staff need to speak to a kitchen contact, pass the item and question, not the guest’s name, phone number or order history.

The digital menu accessibility guide covers how a guest finds and reads a current menu. This guide begins after that point: when the written information still needs a confirmed, person-to-person answer.

Use a five-step escalation path

The path should be short enough to use in a rush. It should also make uncertainty visible instead of hiding it behind friendly language.

  1. Pause the promise. Do not say “it should be fine,” “we usually make it without that,” or “the kitchen is careful.” Those phrases can sound like confirmation when they are not.
  2. Identify the menu choice. Capture the exact item, variant, modifier, location and service period. Use the modifier guide to make choices clear before the guest reaches this step.
  3. Check the approved current source. That may be a current recipe, ingredient record or the restaurant’s trained food-safety contact. A prior menu, an old screenshot and an unverified verbal answer are not enough.
  4. Say only what the source confirms. If the source does not answer the question, say that plainly. Do not translate “not confirmed” into a claim that the guest can safely eat the dish.
  5. Repair the public information when necessary. If the check finds that a current menu statement is unclear or wrong, assign an owner, update the source and test the public page before the next service.

This path is distinct from marking an item unavailable. The sold-out item process helps a restaurant remove a dish or availability promise. An allergen question may reveal a content problem even when the item remains available.

Give staff language that keeps the choice with the guest

Staff do not need clinical vocabulary to be clear. They need language that separates a confirmed fact from an unknown.

Avoid Use instead
“It should be okay.” “I need to confirm the current preparation before I answer.”
“Just skip the sauce.” “I can ask whether that change is available and what the current source confirms.”
“There are no nuts in it.” “Our current recipe lists these ingredients. I will have the kitchen confirm the question you asked.”
“We cannot guarantee anything.” “This information is not confirmed for your question, so I do not want to guess.”

The goal is not to force a guest to accept an alternative. It is to give them a truthful status and time to decide. If the restaurant can confirm a different menu item, describe the information it actually verified rather than comparing risk between dishes.

Keep one current menu source, then test it

A public menu should not split the team between a QR page, a PDF, a printed card and a group chat. Multiple copies make it easier for a past description to survive after a recipe or availability change.

Use this release check whenever a verified answer exposes a content gap:

  1. State exactly what needs correction: item, variation, location and service.
  2. Assign the menu owner and the approved source for the change.
  3. Update the current menu statement in clear words; do not add an icon that requires a separate explanation.
  4. Open the guest-facing page on a phone and read the corrected item in context.
  5. Tell the next shift what changed and where the approved answer now lives.

The digital-menu audit checklist is useful for the full publishing review. If the change affects a translated menu, use the menu translation checklist to keep the decision and its limitation intact in every language.

Record the correction, not the guest

An incident note can help the next shift, but it should stay operational. Record the menu item, variation, location, service, source checked, result, owner and time of the correction. Do not turn a shared menu note into a record of a guest’s health information.

Situation Immediate action Handoff record
Published wording is clear and current Share the confirmed scope No change needed
Kitchen source confirms a different fact Escalate, then update and test the menu Item, correction owner and test
Source is incomplete or unavailable Say it is not confirmed Item, source gap and owner
A guest asks about an unavailable choice Use the current availability process Item status and next update

For teams evaluating how to keep a guest-facing menu current, review restaurant digital menu software and the pricing page. Whatever system a restaurant uses, a menu answer is only as reliable as the current source and escalation path behind it.

Train the handoff before a busy service

Run one short scenario with the host, server and kitchen contact before service. Pick an item with a variation, ask a realistic allergen question and confirm that everyone can find the same current source. Then test what happens if that source does not answer the question.

This rehearsal reveals whether the team has a useful next step or only a vague instruction to “be careful.” The result to measure is simple: staff can say what is confirmed, what is not confirmed and who owns the correction without collecting personal guest information or making a safety promise.