Wedding Dietary Requirements: How to Collect Them Properly and Safely

Wedding dietary requirements are a collection problem before they are a catering problem, and the couple own that half of it. On a list of 90 guests there is usually 1 person for whom the wrong plate means an ambulance, 3 or 4 for whom it means a wretched night, and a dozen with preferences that matter socially. A single free-text box flattens all three into one unusable heap.

Nearly every dietary disaster starts months before a kitchen is involved. It starts with a line on a reply card reading any dietaries, and a guest answering nothing major. What follows is the distinction that governs everything, the questions to ask word for word, what UK law asks of a caterer, and how an answer reaches the right chair.

Wedding dietary requirements are three problems wearing one label

A preference is a choice. An intolerance is dose-dependent and makes someone unwell. An allergy is an immune response that can be life-threatening from a trace, and coeliac disease, which is autoimmune rather than allergic, demands the same strictness about cross-contamination. Kitchens handle each differently, so the distinction has to survive the journey from guest to chef intact.

The consequence is about timing. A preference can be handled during service, whereas an allergy has to be designed into the menu weeks earlier: a named dish for a named guest, separate boards, a separate plating area. Ask late and the honest answer is plain grilled chicken and steamed vegetables.

Why does asking for any dietaries fail?

Because the question is vague in four distinct ways, and none of them is the guest’s fault.

• It is vague about scope. Some read it as allergies only, while others list every food they dislike. Anaphylactic to peanut and hates coriander then arrive in the same column.
• British guests minimise. People with genuine allergies downgrade themselves in writing rather than be a nuisance. A bit funny with shellfish has arrived from someone who carries an adrenaline auto-injector.
• It is asked of a household. One card, one box, four people. The Ahmeds, no pork tells a chef nothing about which two are also vegetarian.
• Free text cannot be sorted. Somebody retypes gf if poss and veggie, not vegan into a spreadsheet at midnight, and transcription is where errors enter.

So the fix is not a better-worded single question. It is several questions, each with fixed answers, asked of every named guest individually.

The questions to ask, word for word

Ask these per person rather than per invitation, and copy them as they stand.

• Do you have a food allergy that could cause a serious reaction? Yes or no.
• Which allergen? Tick all that apply, from the 14 allergens UK law requires to be declared: celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, peanuts, sesame, soya, sulphur dioxide and sulphites, and tree nuts. Add other, please specify.
• Do you carry an adrenaline auto-injector? Yes or no.
• Is there a medical dietary condition the kitchen should know about, such as coeliac disease or lactose intolerance? Yes or no, then a short text field.
• Do you follow a diet for religious or ethical reasons? Vegetarian, vegan, pescatarian, halal, kosher, Jain or other.
• Please choose your starter, main course and dessert, from fixed options on the menu.
• Is there anything you would simply rather not be served? Optional, and deliberately the last question on the form.

That last question earns its place by keeping dislikes out of the allergy field. Give people somewhere harmless to put a dislike of beetroot and they stop putting it where it does damage.

Two drafting notes that save an argument later

Never label a course entrée, which means the main course in America and the starter in Australia and in older British usage. And ask for a plus-one by name rather than accepting and guest, because a nameless guest cannot be asked anything and turns up with a diet nobody recorded.

Fixed answers beat free text, field by field

Collect wedding dietary requirements with the RSVP, not afterwards

Asking separately, later, is the common mistake and the expensive one. A reply is a single moment of attention: the invitation is open, the decision is made, questions are already being answered. A second round weeks later reaches perhaps half the list, and the half it misses is not random.

The dates come off the catering contract rather than off etiquette. Most UK venues want final numbers 7 to 14 days out, and some contracts say 21. Invitations go out 10 to 12 weeks ahead, so set the reply date three to four weeks before the wedding, leave a clear fortnight to chase, and put the dietary questions inside that same reply. Numbers and dietary schedule then reach the caterer together.

Both tiers need asking, which couples forget. Evening guests miss the wedding breakfast, the seated meal whatever hour it lands, but a hog roast is pork and a buffet is a cross-contamination event with shared tongs. So collect wedding dietary requirements from the evening list too.

Changes in the last fortnight

They will come: a plus-one confirmed late, a pregnancy, a diagnosis, a substitute for a guest who dropped out. Nominate one person to receive them, whether a planner, the venue coordinator or a member of the wedding party, and put that name and number on the reply page. Anything landing after the caterer’s cut-off is a telephone call rather than an email, with confirmation back in writing.

Natasha’s Law and what your caterer is obliged to do

UK food businesses must give accurate information about the 14 regulated allergens in what they serve. For food plated to order, as at most weddings, that can be given verbally or in writing, but it has to be available on request. Nobody is permitted to guess.

Natasha’s Law has been in force since October 2021. It is named after a teenager who died after eating a sandwich whose label did not declare the allergen that killed her. According to that legislation, food prepacked for direct sale needs a full ingredients list with allergens emphasised. That covers much of an evening reception: pre-wrapped rolls, boxed canapés, a grazing station made up in advance. Equivalent regulations apply across the UK.

What a caterer is not obliged to do matters just as much. They need not invent a separate allergen-free menu, and they cannot honestly certify a kitchen that handles nuts as nut-free. A chef who says “I will cook this without sesame, but I will not call the kitchen sesame-free” is showing competence rather than obstruction.

Three questions for the tasting

Is there an allergen matrix for this menu? Who is the allergen lead on the day? And what happens if a guest raises something at the table? A caterer who answers all three without hesitating has done this before, and a caterer who waves the questions away has told you something useful for free.

How do wedding dietary requirements reach the kitchen?

As a schedule, not as a paragraph. The handover fails far more often than the cooking does, and the failure is nearly always a format problem rather than a skill problem.

A chef wants one row per affected guest, with surname, table, seat number, allergen or diet, meal choices and notes. Sort it alphabetically, date it, and give it a version number, because there will be a second version. Send it in the same week the final numbers go in.

Put the serious cases in the covering note as well as in the attachment. Three lines at the top of an email get read, whereas row 12 of a spreadsheet does not. Then ask for the schedule back with a dish named against each person. There will be a vegan option is not an answer, while Ms Shah is having the aubergine, plated separately, is one.

Digital reply tools exist partly to delete the transcription step. TislitEvent collects wedding dietary requirements per named guest and exports them in that form, which is one fewer place for a hand-copied no nuts to lose its meaning.

Marking dietary restrictions on the day

A place card is a useful signal and a terrible last line of defence. Guests move seats, cards get shuffled during the drinks reception, and children rearrange them for sport.

Marking systems that work

One discreet mark meaning this guest has a specific plate, check the list, beats a code with a symbol per allergen. Staff remember one symbol under pressure, and they do not remember seven. A printed dot in the bottom corner, a different card stock or a coloured edge all work. What does not work is the word allergy across the front in red, because the guest reads it before the waiter does and it announces a private medical matter to the table.

What the waiting staff need

A printed table plan with seat numbers and the affected names circled, one copy per section, plus a verbal briefing before service. Special plates go by name, out loud: “Is one of you Priya Shah? This one is yours”. Never at a chair simply because a card sits there. Brief the evening supplier too, since hog roasts and food trucks are booked separately and routinely forgotten.

The guest who declared nothing and cannot eat the main

Plan for this one, because it happens at most weddings. Someone else filled in their reply. The plus-one was confirmed after the form closed. They did not think it counted, or they assumed they would manage.

Ask the caterer in advance for two spare covers of the most restrictive dish already in production, often the vegan main, which is frequently free of dairy and egg as well. Agree the cost at the same time. Agree, too, who fields it on the day, because the guest should raise it with the venue coordinator or a nominated friend rather than with the couple.

What must not happen is a waiter improvising. A plate assembled on the fly by someone who does not know what is in the dressing is exactly how reactions occur. If the kitchen cannot verify a dish for a guest with a serious allergy, the correct answer is that it cannot safely be served, followed by something plain and known: fruit, plain rice, an undressed salad of named ingredients.

Frequently asked questions

When should you ask guests about wedding dietary requirements?

On the reply itself, at the same moment they confirm they are coming. That is typically three to four weeks before the wedding for a hotel, and six weeks for a marquee. Asking earlier produces answers that change; asking later means a second round of messages that reaches roughly half the list, and the missing half is not random.

How many guests will have a dietary requirement?

There is no reliable published figure, so treat any percentage you are quoted with suspicion. What I can say from practice is that on an average list, and Bridebook’s UK Wedding Report puts the average ceremony at roughly 74 guests, you should expect a handful of medical cases and a larger group of preferences. Budget kitchen attention for the first group only.

Do evening guests need to be asked about dietary restrictions?

Yes. Evening food carries most of the cross-contamination risk at a British wedding: a hog roast is pork, a buffet is served with shared tongs, and a food truck rarely has an allergen matrix to hand. Ask the evening list the same questions, then send the evening supplier its own copy of the schedule rather than assuming the main caterer passes it on.

What does getting it wrong actually cost?

A wasted cover, at minimum. According to Hitched, the average UK cost per guest reached £272, up 4% from £261, across a survey of 2,020 couples, so a guest who cannot eat the plate in front of them is that much spent on nothing. The real cost is not the money. It is a guest in the car park at nine o’clock on a 2026 summer evening, waiting for an ambulance.

Sources: Hitched · Bridebook · Wikipedia · Text My Wedding

Read next: How to Make a Wedding Guest List: The Method That Ends the Argument · Chasing Wedding RSVPs: When to Start, Who Asks, When to Stop · Wedding RSVP Deadline: How to Set a Date That Actually Holds