All guides
Guest list

How to build a wedding guest list that actually holds up

Most guest-list stress is not about who to invite. It is that the list exists in four places at once. Here is how to build one you can actually trust.

6 min readNovember 2026

Almost every couple hits the same wall about six weeks in: a spreadsheet from a parent, a note on someone's phone, a list in an app, and a rough count in an email to the caterer that nobody can quite reproduce. The fix is not a better spreadsheet. It is deciding that one list is the real one, and that everything else feeds it.

Decide the shape of the list before the names

Before you type a single name, agree on three things: the number you can afford to feed, whether children are invited, and whether single guests may bring someone. Those three answers decide how long the list can be, and changing them later is what forces you to cut people you have already told about the wedding.

  • A comfortable number and a hard ceiling: the head count your venue and your budget can carry, and the point at which you stop adding.
  • Children: all, none, or only family. Pick a rule rather than deciding case by case, because every exception gets compared with someone else's exception.
  • Plus-ones: everyone single, only established couples, or none. Whatever you choose, write it down so the two of you give the same answer to the same question.

Two lists, not one

Keep an A list of people you would be sad not to see, and a B list of people you would love to invite if space appears. A B list is not rude; it is how you avoid cutting a friend three weeks out when four people decline. The one rule: never send a save-the-date to a B-list guest.

Separate the household from the person

Most guest-list errors come from mixing the two. A household (the Alvarez family, four seats) is not the same as the person you email (Maria Alvarez). When you record a party, record the number of seats with it, and give the invitation to one named person who can answer for the whole group. Collect plus-one names later, at RSVP time, and you get the real name instead of "Guest + 1" on the seating chart.

Collect the fields you need later, but not all at once

The list has to answer questions you have not asked yet: who is coming to which part of the day, what they eat, who they should sit near. Collect the boring contact fields now, and let the RSVP collect the rest. Asking for dietary restrictions on a save-the-date in March gives you answers that are stale by September.

  • Name, with the party size kept in its own field rather than written into the name.
  • Email and phone. The email is what actually gets you an answer.
  • Group, so you can filter by family, friends or work when seating starts.
  • Which parts of the day each guest is invited to, if it is not the whole wedding.

Give every guest one way in

The quietest big improvement to an RSVP process is a personalized link: one address per guest or household, opening a form that already knows who they are. No "please reply to this email with your name", no matching replies to people by hand, and nobody answering on behalf of a party they were not invited with. The answers land on the same list the seating chart reads from.

Make the list the source of truth, not a copy of one

Once the list behaves like a database instead of a document, three jobs stop taking effort: the head count, the meal totals for your caterer, and the seating chart. If you find yourself copying numbers from one place into another, that is the sign the list has already split in two.

The test of a good guest list has nothing to do with how tidy it looks. It is whether you can answer, in one place, how many of these people are coming, what they eat, and where they are sitting.

Invitation paper and blush bouquet

Start with the guest list

Import your guest list, send your first RSVP link, and see the head count update itself.

Free for 14 days, then $29/month. Cancel anytime before then and pay nothing.