Wedding Websites & RSVPs
Collecting Meal Choices and Dietary Needs the Easy Way
Of all the small jobs in wedding planning, collecting meal choices is the one that quietly turns into a nightmare. It starts simple. You ask people to pick chicken or fish, they reply by text, by email, by a comment on the save-the-date, and three weeks later you are cross-referencing four different threads trying to work out whether Auntie Sue is vegetarian or just doesn't eat pork. There is a calmer way to do it, and it mostly comes down to asking properly and keeping everything in one place.
Ask at the right moment
Meal choices belong with the RSVP, not before and not as a separate round of chasing. When someone confirms they are coming, that is the moment they are thinking about your wedding, so ask them to choose their courses right there. Make them do it twice and half of them will forget the second time.
Most caterers want final numbers and a meal breakdown roughly three to four weeks before the day. Work backwards from that. If your RSVP deadline is six weeks out, you have a comfortable buffer to chase the inevitable stragglers without panicking your kitchen.
Write the menu so there is nothing to guess
Vague menu wording causes most of the back-and-forth. "Chicken" tells a guest nothing. Is it spicy? Is there a creamy sauce someone with a dairy issue needs to dodge? Spell it out in plain terms, and flag the obvious allergens right on the menu so people can choose confidently.
A clear choice looks like this:
- Starter: Heritage tomato and burrata salad (v) or smoked salmon with dill crème fraîche
- Main: Roast chicken with thyme jus or wild mushroom risotto (ve)
- Dessert: Sticky toffee pudding or lemon posset
Label the vegetarian and vegan options clearly, and if you are offering a children's menu, say so. The fewer questions your guests have to ask you, the fewer messages land in your inbox.
Separate "preference" from "must avoid"
This is the bit people muddle. There is a real difference between someone who would rather not have beef and someone who will end up in hospital if there is a trace of peanut. Treat them differently.
A good dietary question has two parts: which formal option do you want, and is there anything you genuinely cannot eat. Give people a free-text box for the second part, because allergies and intolerances are too varied for tick boxes. You want to capture coeliac, severe nut allergies, shellfish, dairy, and anything religious or medical, and you want it in the guest's own words so nothing gets lost in translation.
| Type | Example | How to handle it |
|---|---|---|
| Course choice | Chicken or risotto | Tick box at RSVP |
| Dietary requirement | Coeliac, nut allergy | Free-text box, flagged to caterer |
| Preference | "Not keen on fish" | Note it, but it is lower priority |
| Children's meals | Under-12s menu | Separate option, counted apart |
Keep it all in one list
The real headache is not collecting the answers, it is collating them. If your replies arrive across texts, emails and verbal mentions at the pub, someone has to type all of that into a spreadsheet by hand, and that is where mistakes creep in. A guest gets missed. A nut allergy gets typed into the wrong row. Your caterer ends up with a list that does not match your seating plan.
This is exactly the sort of thing a wedding website with built-in RSVPs sorts out for you. Guests pick their courses and flag any dietary needs at the same time as confirming, and it all lands against their name automatically. Build The Day lets each guest choose their meal by course and add dietary requirements when they reply, so your numbers and your kitchen list stay in step without you copying anything across. When it comes to handing the caterer a final breakdown, you export one clean list rather than reconstructing it from memory.
Chase the stragglers without the stress
There will always be a handful who do not reply. Set your deadline, send one friendly reminder a week before, and then a final nudge. After that, a simple rule keeps things moving: anyone who has not chosen by the cut-off gets the most popular option or a safe vegetarian default. Tell people this gently in your reminder ("if we don't hear by the 14th, we'll pop you down for the chicken") and you will be amazed how quickly the laggards reply.
A quick checklist before you send numbers
Before you hand anything to your caterer, run through this:
- Every confirmed guest has a meal choice, including plus-ones and children
- Dietary needs are written in the guest's own words, not summarised
- Allergies are flagged separately and clearly, ideally highlighted
- Your numbers match your final seating plan
- You have noted who needs which meal at which table, so service runs smoothly
Get this right and the meal side of your day becomes one of the least stressful parts of planning. Your caterer gets exactly what they need, your guests get fed properly, and nobody ends up staring at a plate they cannot eat. That is the whole point: a tidy list now means a smooth, well-fed wedding later.
Header photo by Oksana Berko on Unsplash
Keep reading
More from the blog
Keeping Your Guests' Data Private and Secure
How to handle wedding guest addresses, emails and dietary details responsibly, from sharing photos to choosing a wedding website you can trust.
Is a Wedding Hashtag Still Worth It?
Whether a wedding hashtag still earns its place in 2026, when it actually helps, and the simpler ways to gather your guests' photos in one spot.
Collecting Guest Song Requests Online
How to gather wedding song requests from guests online, build a dance floor playlist everyone loves and brief your DJ or band without the chaos.