If you have already decided the guest list is going digital rather than living in a notebook, the question left is not "spreadsheet or paper" but which fields you actually need and how to stop RSVPs turning into a three-month WhatsApp thread. Here is what actually holds up, and where it breaks.
The short version
An online wedding guest list needs five things to not fall apart: fixed fields from day one, one row per plus one, an RSVP form the guest fills in rather than you, allergies as a required field rather than a follow-up question, and a way to export everything the day before you talk to your caterer. Miss any one of the five and the problem always shows up in the same place: the month before the wedding, when there is no room left to fix it.
The fields every guest needs
Twelve columns cover nearly every case, and dropping any of them shows the moment replies start coming in:
| Field | What it is for |
|---|---|
| Full name | Unambiguous identification, especially with repeated surnames in the family |
| Group | Bride's family, groom's family, friends, work — for filtering without searching by hand |
| Contact | Phone or email, for reminders to non-responders |
| Invitation sent | Distinguishes who has already been invited from who has not |
| RSVP status | Yes / No / Pending — the field the final headcount is built on |
| Plus one | Whether they bring a partner or extra guest, with their own row |
| Meal choice | The dish selection, if your wedding offers more than one |
| Allergies | Required, not optional — this is the field that arrives late and wrong if it is not |
| Child | For the kids' menu and the highchair count |
| Transport | If you organise a shuttle, who needs it |
| Table | Filled in last, once RSVPs are closed |
| Notes | Everything that does not fit a column: accommodation, who arrives late, who leaves early |
The column that most quickly-built lists skip is allergies as its own field. It usually gets folded into "notes", which is exactly where it gets lost right before you hand the list to your caterer.
One plus one, one row
The most common mistake is not about fields, it is about structure: adding the plus one as a note inside the main guest's row — "Sarah (+1: John)" — instead of giving them their own row.
As a note, John cannot RSVP on his own, cannot pick a meal, cannot declare an allergy. Everything routes through Sarah, who has to remember to ask John and transcribe his answer. With his own row, John confirms, chooses and declares allergies like any other guest, and your headcount comes from counting rows, not reading parentheses.
How to automate RSVPs without chasing anyone
This is where an online guest list stops being just a nice-looking sheet and starts actually saving work.
Without automation, an RSVP looks like this: you message or call every guest, wait for a reply, and copy the result into your sheet by hand. With 150 guests that is 150 conversations and 150 manual entries, and every single one is a chance to type "Yes" where it should say "No" or forget to update the row.
With an RSVP form — whether Google Forms, an embedded form, or the RSVP built into your own wedding website — the guest fills it in whenever suits them, and the reply arrives already structured: name, RSVP status, meal choice and allergies in the same row, with nothing for you to transcribe. Your job shifts from "chase and copy" to "review and chase only the ones still missing", which is a much smaller job.
The difference between a standalone form and an RSVP built into the wedding website is context: on a standalone form the guest has to remember the date, venue and dress code on their own; on a website with a built-in RSVP, they confirm on the same page that already shows all of that.
Meals and allergies: the field your caterer's headcount depends on
Your caterer does not ask for your guest list. They ask for a number: how many vegetarians, how many kids' meals, how many shellfish or nut allergies. If that information is scattered across WhatsApp threads, loose notes and memory, rebuilding it the week before the wedding is the last thing you want on your plate alongside fifteen other things.
The fix is boring but it holds: put meal choice and the allergy question inside the same RSVP form, as required fields, not as a separate message you send "when you get a chance". If the guest fills it in while confirming, the data is already where you need it. Leave it for later and half of guests never answer the follow-up, and you end up calling them one by one.
Deadlines: when to send and when to close
Send invitations 8 to 12 weeks before the wedding — earlier if some guests need to travel. Set the RSVP deadline 3 to 4 weeks before, not the week before: you need room to chase non-responders without eating into the lead time your caterer needs for the final count.
Closing the list late is not really your problem, it is the caterer's: every caterer has their own cutoff for the final headcount, and it usually sits closer to the wedding date than people expect, not further.
Spreadsheet, Google Forms or a wedding website with RSVP: the three real options
There is no single right answer, there are three different tools for three different wedding sizes.
| Tool | Best for | Where it breaks |
|---|---|---|
| Excel / Google Sheets shared with your partner | Small lists (up to 40-50 guests), full control over the columns | RSVPs stay manual: you message each guest and copy the reply in yourself |
| Google Forms + response sheet | Automating RSVPs without switching wedding website | The guest confirms out of context, without seeing the date, venue or dress code at the same time |
| Wedding website with built-in RSVP | Confirming, picking a meal and declaring allergies in the same place the guest already checks for details | Requires setting up the website, even if just for this |
For a short list and a simple wedding, a shared spreadsheet is enough and costs nothing. Automating RSVPs starts paying off around 80-100 guests, which is where chasing replies one by one starts eating real hours.
What we do
We build wedding websites with a built-in RSVP form, for €49, paid once. Guests confirm on the same page where they see the date, venue and schedule, pick their meal and declare allergies in the same form, and you export the headcount whenever you need it for the caterer. You can build the whole thing and see it before paying anything.
Frequently asked questions
How do I create a wedding guest list online?
Start with fixed fields — full name, group (bride's family, groom's family, friends, work), contact, and whether they bring a plus one — then add the fields that fill themselves in over time: RSVP status, meal choice, allergies and table. You can run it in a shared spreadsheet or in a wedding website with a built-in RSVP form; the real difference is who updates each field.
What information should each guest have in the list?
At minimum: full name, group, whether they have a plus one, whether that plus one has confirmed, meal choice, allergies or dietary restrictions, and whether children are attending. Adding the assigned table at the end saves you from redoing the seating chart by hand in the last month.
How do I automate RSVPs without chasing everyone on WhatsApp?
With an online RSVP form — Google Forms or the one built into your own wedding website — each guest responds whenever suits them and the data arrives already structured. Without that, the alternative is messaging every guest individually and copying each answer into your sheet by hand, which is where most errors creep in.
How do I manage plus ones on a wedding guest list?
Give every plus one their own row instead of a note inside the main guest's row. That way the plus one confirms, picks a meal and declares allergies on their own, and your headcount comes from counting rows instead of interpreting notes.
How do I track allergies and dietary restrictions across guests?
As a required field inside the RSVP form itself, not as a separate question you send later. If the guest fills it in while confirming, the data is already where you need it; leave it for a follow-up message and half of guests never answer, so you find out at the catering headcount instead.
Can I export the guest list to send to my caterer?
Yes, and that is the main reason to run it digitally from day one. A spreadsheet exports to CSV or Excel in one click; a wedding website with RSVP should offer the same, because the caterer needs the final headcount by meal, not access to your website.
When should I close the guest list and send invitations?
Send invitations 8 to 12 weeks before the wedding. Set the RSVP deadline 3 to 4 weeks before, not the week before, so you have room to chase non-responders before handing the final number to your caterer. Closing the list later than that eats into the caterer's margin, not yours.
Written by the Wedding30s team. If something here is out of date, email support@wedding30s.com and we will correct it.