How to organize a wedding guest list

Organise the list by household, not by person. Give every household a side, a tier, and one row that holds the address, the email, and a mobile number. Then cut with rules instead of judgement calls, and expect 75 to 85 percent of local invitees to say yes.

Step 1: One list, one row per household

The single most common mistake is a list of names. Invitations, RSVPs, seating, and thank-you notes all work at the household level: the Okonkwos, not Ada and then Chidi in two separate rows. Give each household a display name, the guests inside it, one postal address, one email, and one mobile number.

Columns worth having from the start: household name, guests, side, tier, email, mobile, address, children yes or no, dietary notes, and travelling from. You will use every one of them later.

Step 2: Tier before you argue

Sort every household into three tiers before anyone debates a specific name.

• Tier A: you would move the date for them. Immediate family, the people standing up with you, your closest friends.
• Tier B: you genuinely want them there and the budget decides.
• Tier C: invited out of habit, obligation, or a parent's request.

Tiers make the hard conversation abstract. It is much easier to agree that Tier C is out than to say a specific colleague is.

Step 3: Split the allocation up front

If both families are contributing, agree the split before names get written down. A common shape is a third to each family and a third to the couple. Then each side fills their own allocation and nobody audits anyone else's choices.

Step 4: Do the maths on attendance

Local weddings land around 75 to 85 percent acceptance. Destination weddings run 55 to 65 percent. Weekday and long-weekend weddings sit lower again. Multiply your list by the right rate before you panic about the venue capacity: 180 invitations to a local wedding is roughly a room of 140.

A word of caution: those rates are averages, not a promise. If your list is mostly local family, expect the high end and plan the room for it. The rates by guest type are broken down in how many invited wedding guests come.

Step 5: Cut with rules, never with names

When you need to lose thirty people, pick a rule and apply it to everybody: no coworkers, no children, nobody you have not spoken to in three years, no plus-ones for guests who will know five other people in the room. One rule removes a block of households and gives you the same sentence for anyone who asks. Judging households individually produces thirty separate arguments and at least one lasting grudge.

For the plus-one version of that conversation, we wrote three scripts for a no-plus-ones note.

Step 6: Run a B-list honestly or not at all

A B-list only works with a time gap. Send the first wave eight weeks out with an RSVP deadline four weeks later, then release the second wave as declines arrive. Anything tighter and the second group receives an invitation three weeks before the wedding, which tells them exactly what happened. If you cannot build that gap into your timeline, invite fewer people and keep the list clean.

Step 7: Collect contact details while you build

The list stalls on missing addresses, not on names. Chase them in the same week you build the list, before enthusiasm fades. Mobile numbers matter more than most couples expect: a text reminder recovers RSVPs that email never will, and you cannot collect numbers retroactively from the people who have gone quiet.

Step 8: Keep one source of truth

Two spreadsheets and a group chat is how a household gets invited twice and another gets missed. Pick one place, keep it there, and let RSVPs write back into the same rows. On Simplyweds the guest list, the invitation send, the RSVPs, and the reminder texts all read from one table, so the count you see is the count the caterer gets.

FAQ

Once the list is settled, the next job is the room. Our free seating chart planner takes a pasted guest list and turns it into tables you can export for the venue, and the seating rules guide covers the pairs everyone worries about.