Memorra
Collecting wedding meal choices means gathering each guest's dinner selection at the same time they confirm attendance, so your caterer receives an exact count for every dish. The cleanest approach uses one system where guests RSVP and pick a meal in a single step, a firm deadline set 3 to 4 weeks before the wedding, and 3 to 4 meal options that include at least one vegetarian dish. Most caterers need final numbers 10 to 14 days out, so working backwards from that date keeps you from scrambling. Expect roughly 10 to 20 percent of guests to ignore the first request, which is normal and fixable with a couple of reminders. Track everything in one place, whether that is a spreadsheet with five columns or a dedicated RSVP tool, and add a notes field for allergies. Done right, this takes an afternoon to set up and saves days of chasing.
Why meal choices get messy so fast
Meal choices sound simple until you are juggling responses from over 100 people, tracking who is vegetarian, and trying to hand accurate numbers to your caterer. One guest replies to your email. Another texts your partner. A third tells your mum at a family dinner and assumes that counts. By week two you have three versions of the truth and no idea which one to trust.
The cost of getting this wrong is real. Caterers usually bill per head, and most charge for the count you confirm, not the count who actually eat. If you over-order by 15 plates because your tracking was sloppy, that is money gone. Under-order and you have hungry guests and a stressed kitchen. The whole point of a good system is to make the final number boring and correct.
The good news is that this does not have to be chaotic. Set it up properly at the start, and you get clean data and guests who feel looked after.
What is the best way to collect meal choices?
You need one place where guests confirm they are coming and select their meal. The single biggest mistake couples make is splitting this across email, text, and a website, then trying to stitch the answers together later. Pick one channel and route everything through it.
Email invitations work if your guests are reliable with email. You will still chase a handful of people, but the flow is straightforward. The weakness is that replies scatter across your inbox and you end up copying answers into a spreadsheet by hand.
Online RSVP platforms are cleaner. A guest confirms attendance and picks a meal in one action, every response lands in one dashboard, and you can see at a glance who is still pending. No copying, no cross-checking two lists.
Text RSVPs work well for casual weddings or a younger crowd. Send a link, the guest taps to confirm and choose, and you watch responses arrive in real time. Response rates over text tend to be quick because people read texts within minutes, while an email can sit unopened for days.
The method matters less than consistency. Whatever you choose, use it for every single guest, including the ones who prefer to phone you. If Aunt Carol calls to RSVP, take her answer and enter it into the same system yourself. One source of truth, no exceptions.
When should you set the RSVP deadline?
Your caterer needs final numbers roughly 10 to 14 days before the wedding. That is your fixed point. Everything else works backwards from it.
Tell your guests to respond 3 to 4 weeks out. This gap is deliberate. It gives you a full week or two to chase the people who forget before you have to lock the count. If you set the guest deadline and the caterer deadline on the same day, you leave yourself zero room to follow up, and you will regret it.
Put the date directly in your invitation: "RSVP and select your meal by [date]." Then plan two reminders:
- •One about a week before the deadline
- •One 2 to 3 days before the deadline
After the deadline passes, you can still accept responses, but say clearly that late changes might not be possible. "We're finalising numbers with our caterer on [date], so please let us know before then." That creates urgency without being rude, and it gives you cover if someone shows up expecting a meal they never confirmed.
A quick word on timing the invitations themselves. Send them 6 to 8 weeks before the wedding for a local celebration, and 8 to 12 weeks out if guests need to travel or book accommodation. Send too early and people set it aside and forget. Send too late and you are chasing from day one.
How many meal options should you offer?
Stick to 3 to 4. More options complicate the kitchen, slow down service, and make your tracking harder for no real benefit. Pick meals your caterer can actually execute well at scale.
A solid default set:
- •One vegetarian dish
- •One fish or poultry dish
- •One beef or other hearty meat dish, if you are serving meat
- •One vegan or allergen-friendly option, or a "tell us your needs" field
Describe the meals so people know what they are choosing. "Pan-seared salmon with herb butter and roasted new potatoes" beats "fish" every time. People commit faster when they can picture the plate, and vague labels generate follow-up questions you then have to answer one by one.
Always include a free-text notes field for allergies and dietary restrictions. Your four main options will not cover everyone. Someone will be coeliac, someone will be pregnant and avoiding certain foods, someone will have a nut allergy serious enough that the kitchen needs to know. As a rough guide, plan for around 1 in 10 guests to have some dietary requirement worth flagging, sometimes more depending on your crowd. That field is where those details land.
If you are offering a children's option, treat it as a separate category rather than a fifth adult meal, and count kids' plates on their own line. Caterers price and portion them differently.
How do you track meal responses without losing your mind?
You need a system that does not require detective work every time a reply comes in. The failure mode here is scrolling back through a month of messages trying to remember whether someone said chicken or beef.
If you are collecting by email, a simple spreadsheet does the job. Five columns are enough:
| Column | What it holds |
|---|---|
| Guest name | Full name, one row per person |
| RSVP status | Coming, not coming, or pending |
| Meal choice | The exact dish they picked |
| Dietary notes | Allergies, restrictions, requests |
| Date responded | So you can spot the latest change |
Update it the moment each reply arrives. The discipline of entering answers same-day is what keeps the spreadsheet trustworthy.
A dedicated RSVP tool removes most of that manual work. You see who has confirmed and what they chose without touching a spreadsheet, you can filter by meal type to get an instant count for your caterer, and you can spot missing responses in seconds instead of scrolling. Memorra ties this to your guest list, RSVP tracking, and seating chart, so a meal choice logged once shows up everywhere it is needed. If you are already tracking your budget and vendors in the same place, the meal count is just another view of data you already have.
Two to three weeks before the wedding, pull a preliminary count and sanity-check it. Do the total meals match the number of confirmed guests? If you have 96 confirmed guests and only 89 meals selected, seven people RSVP'd yes without choosing a dish, and you need to chase them specifically. Flag any special dietary needs that require extra prep so your caterer has time to plan.
What do you do about guests who don't respond?
Some people will not RSVP no matter how clear your invitation is. Expect it and build it into your plan rather than taking it personally.
About a week before your caterer deadline, list everyone still marked pending. Then reach out directly. A personal text or phone call works far better than another mass email, because the mass email is exactly what they have been ignoring. Ask them to confirm and pick a meal in the same message. Most of them simply forgot, and a nudge from you sorts it in under a minute.
For the small number who blow past the final deadline, make the call for them. A vegetarian dish is usually the safest default because most people can eat it and it sidesteps the common allergens. Note that you chose on their behalf so you remember. On the day, if they turn up and want something else, a good caterer can often swap a plate, but you should never count on that in advance.
Can guests change their meal after they've responded?
Yes, and you should let them. Someone will decide they want the beef instead of the salmon, or a dietary situation will change. Include your contact details in the invitation so people know exactly how to reach you rather than guessing.
When a change request comes in, update your system the same day and note the date of the request. That timestamp matters if two changes come from the same person and you need to know which is current. A few days before the wedding, send your caterer one final update with any last-minute swaps rolled together, so they get a single clean message rather than a trickle of edits.
Set a hard cutoff for changes that matches your caterer's own deadline, and tell guests what it is. "We can accommodate changes up to [date]" is fair to everyone, including the kitchen team who have to shop and prep against your final count.
A clear collection method, a deadline set 3 to 4 weeks out, 3 to 4 well-described options, and same-day tracking are the whole job. Get those four right and the meal count stops being a source of dread. Your caterer gets numbers they can trust, guests with allergies know they were heard, and on the day you are eating dinner instead of counting plates.