Wedding invitations and food allergies: ask without a quiz

Three weeks before the wedding, one line lands in the group chat: “Heads up, Marta can’t have dairy.” By then forty people have already replied “fine” to a message about parking. Her line sits four screens up, you mean to write it down, and it slips.

Food allergies at a wedding are not a paperwork problem. They are a message to the kitchen, and the kitchen needs one thing from you: a number of plates. The question is how you get that number without handing eighty guests a medical form.

Where food allergies belong on your wedding invitations

Put the menu in the dinner scene of your invitation and keep the allergy question out of the shared confirmation list. Not because it is a secret, but because that list is communal reading, and nobody wants their medical history sitting in it. Your invitation is built from scenes — the doorway, the ceremony, the long dinner, the last dance — and the dinner scene is where the dishes go: starter, main, dessert. Guests read it while they are thinking about food, which is the moment they remember what they cannot eat. Then ask by message, household by household, and keep the answers in one note. Your RSVP questions are yours to write, and the replies land in a single ordered list inside the invitation instead of across three chats. Use that list for logistics, not for medical details.

• “Anything you can’t eat? We’ll sort it out with the kitchen.”
• “If we don’t hear back, we’ll assume you eat everything.”
• “Just tell us the plate: gluten-free, dairy-free, no nuts.”
• “Anything different for the children sitting with you?”

Ask for the plate, not the diagnosis

“Gluten-free” tells the kitchen what to cook. “Coeliac, diagnosed at nine” does not change a single dish, and it asks your guest to explain themselves in a thread full of people. You are ordering plates, so ask about plates.

Name the three things in your own menu that trip people up. If the main is finished with butter, the starter is dressed with walnuts and the dessert is a cream tart, write exactly that: dairy in the sauce, nuts in the dressing, egg in the dessert. Three specifics get read; a general appeal gets skimmed. Count the children too. If two kids at table six eat dairy-free, the kitchen is cooking two separate plates that night, and it needs to know before the shopping is done.

An allergy question is not a form. It is one line, to one person, at the moment they are reading the menu.

What you hear on Thursday does not get reprinted

Someone tells you on Thursday that their daughter can’t have dairy. You open the editor, reword the dinner scene, add a line beside the menu and publish. The link you already sent is the same link, so guests who open it see the current version — no correction message, no fresh card, no envelope. The same applies if the time moves or dinner shifts indoors. Change it once, in one place, and the invitation catches up by itself.

When your guest does not read your language

Family flying in read the invitation in their own language. The content can be configured per language — English, Spanish, Catalan, French, Italian, Portuguese and German — so the question about dinner arrives in the words they would use themselves, not a literal translation of “food intolerances”.

Start with the menu, not the form. Write the dishes into the dinner scene, pick the three details that matter, and send one line to the households you need an answer from. Keep those answers in a single note and hand that note to the kitchen. Then use your confirmation list for the easy things: who is coming, who is bringing a plus-one, what time they will arrive. That is how everyone eats well without anyone explaining their gut in a group chat.