Last updated: May 14, 2026
The RSVP process is where wedding planning turns stressful. You send out invitations, and then you wait. Phone calls to relatives. Text message chains. A spreadsheet that never quite matches reality. Duplicate names. People who said yes by accident and no on purpose.
There is a better way. This guide covers what to collect, how to track it, and what to do with the data once the catering deadline looms.
Most couples only ask for a yes or no. That is not enough. Here is everything worth collecting — and why:
Attendance (yes / no / maybe)
The obvious one. 'Maybe' is worth tracking separately — it affects your buffer calculation.
Full name
You need this for seating charts and place cards. First name only creates duplicates in large families.
Meal preference
If you have multiple menu options (chicken, fish, vegetarian), collect this at RSVP time. Chasing it later is painful.
Dietary restrictions
Separate from meal preference. A vegetarian option doesn't cover nut allergies or celiac. Ask explicitly.
Plus-one details
If you allow plus-ones, collect the plus-one's name and meal preference at the same time — not as a follow-up.
Children attending
Affects catering (children's meals), seating, and entertainment considerations.
Special accommodations
Mobility requirements, hearing assistance, nursing rooms — ask once in the RSVP instead of managing ad hoc requests.
A platform like GuestCard eliminates the friction on both sides. The couple sends one link. Guests open it on their phone, tap yes or no, fill in meal preference and dietary restrictions in under 60 seconds, and close the tab. No app to download, no account required.
You see every response update in real time on your dashboard. Filters show you attending vs not attending, vegetarian vs gluten-free, guests who have not responded. When the caterer calls for a headcount, you open the dashboard and read out the numbers — or export a CSV and forward it directly.
Dietary restrictions are the most underestimated logistics challenge in wedding catering. Most couples discover the full picture too late — after the caterer has already finalized quantities.
Collect structured data, not a free-text field. "Other dietary notes" produces entries like "no shellfish" that you have to manually categorize. Instead, offer checkboxes:
Share the final categorized list with your caterer at least two weeks before the event. A good platform lets you export this as a clean spreadsheet — not a raw data dump you have to reformat yourself.
Set your RSVP deadline 3–4 weeks before the wedding date. That gives you time to follow up with non-responders and still meet the venue and caterer deadlines.
Two weeks before deadline
Send a gentle reminder to everyone who has not responded. Filter by 'pending' in your dashboard and send a WhatsApp or email blast.
Three days before deadline
Final reminder to the remaining non-responders. Be direct — you need a headcount.
At the deadline
Treat non-responders as not attending for catering purposes, but keep a small buffer (3–5%) for late confirmations.
Most venues and caterers need a firm headcount 7–10 days before the event. Here is how to calculate it from your RSVP data:
Confirmed attending — the straightforward count
+ 3–5% buffer — for last-minute confirmations from maybes and late RSVPs
= Your number to give the caterer
Round up, not down. A venue that has prepared for 165 and receives 170 will be annoyed. A venue that has prepared for 170 and receives 165 will have a small surplus — which is always preferable.
RSVP tracking that actually works
GuestCard collects attendance, meal preferences, dietary restrictions, and plus-one details in one form. Real-time dashboard, CSV export, and reminder filters included. First event free.
See pricing