The menu can be perfect and the conversation can still fail. A guest explains an allergy in a language the server does not speak, or hands over a notes-app paragraph while the pass is shouting. The information was there. It did not arrive in a form the kitchen could use.
Food Passport is the guest's card: they record what they cannot eat once, then show your team a version written in the language your staff read.
What the guest sets up once
A diner picks allergens and how severe they are, dietary needs, and whether cross-contact is a concern. They can note that they carry an adrenaline auto-injector. They choose the language your team speaks. The next Quiteful venue does not start that form from zero.
That is a different job from the menu itself. The menu says what is in the dish. The passport says what this person needs you to know before you cook it. Both should be on the table. The path from scan to plate is mapped in designing an allergy-friendly guest journey.
What your team sees
The staff side is pre-translated into English, German, French, Spanish, Portuguese, Italian, Czech, Greek, Dutch and Polish. Nobody installs an app. The card is high contrast and flips between the guest's language and yours, so you can confirm you are talking about the same thing.
Severity, auto-injector status and cross-contact warnings are written out. They are not collapsed into a single green badge. A badge can hide the difference between "I avoid cheese" and "milk will send me to hospital". If you need the language for that difference, cross-contact versus ingredients is the briefing to give the floor.
Guests can also share a time-limited link, so the card is on a screen in the kitchen rather than waved across a noisy bar.
Confirming that you understood
Staff can mark the discussion and the intended order as confirmed. That is a shared note that the allergy was heard, not a guarantee that the plate is safe. The kitchen still cooks against the recipe record. The confirmation is the handoff: we read this, we agreed this order.
Tone still matters. A card is not a reason to become cold or theatrical. Communicating allergies without scaring guests off is about keeping the facts clear and the welcome intact.
Where translation of the menu fits
A passport does not translate your dish descriptions. If guests are browsing in French, that copy still needs a reviewed translation — see translating menus with DeepL. Use both: the menu in their language, the card in yours.
A practical next step
Tell the floor the card exists and where a guest can open it. Agree the sentence you use when you have read it: what you will check with the kitchen, and what you will not promise. Then point guests who want to filter the card themselves at the live menu, where dietary tags and allergen flags already sit on each dish.
See Food Passport, or walk the wider journey in from QR code to plate.