Wedding guest list: what to track, and what to drop
The columns a guest list really needs, the ones that just make work, how to keep households together, and how to stop retyping replies into a spreadsheet.
The short version
- Track households, not just people: one row per invitation, with every invited name on it.
- The columns that matter: names, side, tier, contact, invited plus ones and children, reply, dietary needs, table.
- Drop the columns you will never sort by. A guest list is a working tool, not an archive.
- Let replies fill the list themselves instead of copying them from messages.
A wedding guest list needs one row per invitation (a household), with the names of everyone invited on that row, and a short set of columns you will actually use: who they are, how to reach them, who is invited with them, their reply, their dietary needs and their table. Everything else tends to become a column nobody updates.
The columns that matter
- Household name, as you would address the invitation
- Every invited person by name, adults and children
- Side (yours, theirs, both) and tier (must, would love, nice to have)
- How to reach them: phone for a message, email if that is what they use
- Plus one allowed: yes or no, and the name if you know it
- Reply: coming, not coming, waiting
- Number coming, adults and children separately
- Dietary needs, in their own words
- Table, once the seating chart is done
The columns that usually just make work
- Postal addresses, if you are not mailing anything
- Separate columns for every event, if most guests are invited to only one
- Gift tracking before the wedding (keep that for the thank-you list)
- Notes nobody reads
Why households, not people?
Because you send one invitation per household, and you receive one reply. A list of individuals makes it easy to invite a couple twice or forget a child; a list of households, with each person named inside it, matches how invitations actually work and turns into a seating chart without retyping.
How do you stop retyping replies?
Collect them in a form that writes to the list. With an online RSVP, every reply lands in your guest list with the names, the numbers and the dietary needs already filled in, and the people who have not replied are a list of their own. Export it when the caterer or the DJ asks for it, rather than maintaining a second copy.
When should the list be final?
Before the save the dates go out, at least for the people you are certain of. Nobody who receives a save the date can be quietly dropped, so the list has to be settled first, even if a few tier-three names are still undecided.
A guest list is not a record of everyone you know. It is the plan for one evening, and every column should earn its place in it.
Common questions
What should a wedding guest list include?
One row per household with every invited person named, their side and priority tier, contact details, plus-one allowance, reply status, number of adults and children coming, dietary needs and, later, their table.
Should a wedding guest list be by person or by household?
By household, with each invited person named inside it. Invitations and replies happen per household, and it prevents inviting someone twice or forgetting a child.
Do I need guests' postal addresses?
Only if you are mailing something, such as printed invitations or thank-you cards. For digital invitations, a phone number or email is enough.
Ready to make your own invitation?
Build a digital invitation, open your RSVP and plan the whole wedding in one place.
Get started →
