A wedding guest list template is the budget in spreadsheet form. Catering, rentals, invitations, and often the venue itself are priced per person. Treat the list as an operations file, not a sentiment file. You can be warm in the invitations and ruthless in the columns.

Build one shared sheet and keep it alive from the first draft through thank-you notes. The couples who “just know who’s coming” are the ones buying 11 extra dinners at overtime prices. 2026 invitation timelines have not changed: save-the-dates when travel is involved, invitations 8–10 weeks out, RSVP 3–4 weeks before the date, then a human follow-up—not another email blast.

Set the rules before you add names

• Confirm the seated capacity of the ceremony and the reception. Use the smaller number.
• Confirm the budget per guest (food + bar + rentals + paper). That number, not guilt, sets the cap.
• Decide the adult / child policy and write it once. “Babes in arms only,” “kids’ table for family,” or “adults only” all work. Mixing them by favorite cousin does not.
• Decide the plus-one policy: spouses and live-in partners yes; dates for people in relationships you have met; no plus-one for singles unless you owe them a social debt or they will know no one.
• Decide whether plus-ones must be named on the RSVP. Named guests are cheaper than blanks that become strangers.
• Agree who can add names. If four parents are contributing opinions, give them a capped allotment, not an open hose.
• Create list statuses: A (invited no matter what), B (invited if A declines), C (ceremony-only or weekday-lunch only, if you are using that structure), Not invited (so you do not relitigate).
• Put “how we know them” on every row. Six months later you will not remember whether this is your manager or your mother’s neighbor.

Spreadsheet columns (build these)

Use Google Sheets or similar so two people are not emailing versions named final-v3.

• Household ID (so a family of four is one invitation, four seats).
• Guest 1 full name as it should appear on the envelope.
• Guest 2 full name (spouse/partner).
• Additional household names (children, extra adults).
• Plus-one allowed? (Y/N) and plus-one name once known.
• Relationship / side (Partner A family, Partner B friends, work, etc.).
• A / B / C list status.
• Address line 1, line 2, city, state, postal code, country.
• Address verified? (Y/N) and date verified.
• Email and mobile (for RSVP chases and day-of logistics).
• Save-the-date sent (date + method).
• Invitation sent (date).
• RSVP method (card / website / text).
• RSVP received (date).
• Attending? (Y/N/unknown).
• Meal choice 1, 2, 3… and dietary notes.
• Hotel / shuttle interest.
• Table number (later).
• Gift received and thank-you sent (date).
• Notes (divorce, accessibility, “do not seat with…”).

Draft the A list

The A list is everyone you would still invite if the venue shrank tomorrow.

• Partner A immediate family.
• Partner B immediate family.
• Wedding party and their named plus-ones per your policy.
• Officiant and spouse if that is your custom.
• Grandparents and anyone whose absence would be a story you do not want to tell.
• Close friends who would be in the room if you married on a Tuesday.
• People hosting events (rehearsal dinner, welcome party) if they are not already on the list.
• Work people only if you would have dinner with them this month without a wedding attached.
• Count seated heads, not invitations. A household of five is five dinners.

Draft the B list

B-list guests are real guests. They are not leftovers. They are people you want if space opens. The only sin is inviting them so late they can tell.

• Build B at the same time as A, not the week after RSVPs.
• Keep B large enough to matter (often 15–25% of A capacity) or skip the tactic.
• Do not print B-list invitations with a later RSVP date that exposes the tier if you can avoid it. Mail them as A-list declines come in, still inside the 6–8 week window if possible.
• Track B-list mail dates separately so you do not double-invite or forget.
• Move a B guest to A only when a specific A seat is dead (decline in hand), not when you “have a feeling.”
• Never B-list immediate family or the wedding party. That is how you start a different kind of event.

Names, households, and envelopes

Envelope etiquette is just clarity. People should be able to tell who is invited.

• Use the names people use, not the names on a 2011 Christmas card. Ask if unsure.
• Married couple, same last name: traditional outer envelope can still read “Mx. and Mx. Lastname”; inner or online can list first names.
• Married different last names: list both names. Do not invent a shared one.
• Unmarried partners in one household: both names, separate lines or “and.”
• Plus-one unknown: “and Guest” only if you truly mean a nameless guest. Prefer to ask for the name before printing.
• Children: if invited, name them. If not, the envelope should not say “and family.”
• Widowed guests: use the name they use now. Do not guess from old records.
• Doctors, clergy, military: use titles if they use them in civilian life; consistency matters more than perfection.
• Kids’ last names when parents differ: write what the parents use at school.
• Collect pronouns and phonetic pronunciation for the MC list while you are at it.

Address hunt

Bad addresses waste postage and time you do not have at week eight.

• Start with your own records, then parents’ records, then a text to the household.
• For international guests, get postal codes and apartment numbers. Write the country.
• Verify a sample of addresses in USPS tools before a calligrapher writes 140 envelopes.
• Keep a “moved” flag. People relocate between save-the-date and invitation.
• Collect emails even if you are mailing paper. RSVP chases happen on phones.
• Note which households should not receive a save-the-date (late B, or people you will only invite to a post-elopement party).

Save-the-dates and the first public count

• Send to A-list (and B only if you are prepared to invite them). A save-the-date is a social contract.
• Include city, date, website. You do not need the venue street address yet.
• If the wedding is adults-only, say so here if children would otherwise be assumed. Do not surprise people at the invitation.
• Destination or holiday weekends: send 8–10 months out. Local: 6–8 months is enough.
• Log send dates. You will be asked “did we send one to…” in November.

Invitations and who is actually invited

• Mail 8–10 weeks before a local wedding; 10–12 for destination or guests who need flights.
• RSVP date 3–4 weeks before the wedding, and earlier if catering needs a long lead.
• Match the names on the invitation to the seats. “The Smith Family” with no kids named will be interpreted as kids.
• Put the wedding website on the invite or on a small card. Meal choices and shuttles live there, not on a cramped suite if you can help it.
• Number the back of RSVP cards in pencil keyed to the spreadsheet. Handwriting is not a database.
• Order 10–15% extra suites.
• International postage and hand-canceling at the post office for letterpress or wax.

RSVP tracking

• Check the website dashboard and the mailbox twice a week starting the week invites land.
• Enter responses the day they arrive. Batching is how you lose a gluten-free note.
• Treat “maybe” as incomplete. Follow up.
• The deadline is a deadline. The next day, start calling the silent households.
• Script: “We need a yes or no for catering. We hope it’s yes. Can you tell us by Friday?” Warm, short, specific.
• Call, do not only email, anyone over 60 who has not used the website.
• If a guest RSVPs for extra people, reply once, kindly, with the policy. Do not add chairs to keep the peace unless you mean to reset the policy for everyone.
• If a guest brings a plus-one you did not offer, decide in advance whether the coordinator intercepts at check-in or you eat the plate. Put the decision in writing for the coordinator.
• Keep a running headcount and a “declines that free a B seat” list.

Meals, access, and logistics fields

• Meal choice per attending adult.
• Kids’ meal or high chair.
• Allergies that are medically real vs. preferences. Both can be honored; only one should change a kitchen.
• Wheelchair seating, aisle end, hearing, translation, or a quiet room request.
• Need a hotel room or shuttle: yes/no. This is not a rooming list unless you are booking for them.
• Ceremony-only vs. full reception if you have split events (use sparingly; it reads as a tier).

Seating chart, fed by this sheet

• Do not start seating until RSVPs are mostly in. You will do it twice otherwise.
• Flag divorced parents, second marriages, and anyone who should not share a table before you place friends.
• Put accessibility needs on the chart, not in someone’s memory.
• Assign a table for vendors if they eat in the room.
• Leave two flex seats if the venue allows. Someone will add a last-minute yes you cannot refuse (or a vendor meal).
• Print a copy for the coordinator and a copy for the escort display. Digital-only dies with the venue Wi-Fi.

Day-of list uses

• Escort display / place cards pulled from the same names as the RSVP (no nicknames unless that is how they RSVP’d).
• Check-in list at welcome table if you have a large guest list or a security need.
• Meal tickets or a coded seating list for the kitchen.
• Transportation manifest if you are running shuttles by name.
• Emergency contact for any guest who needs one (elderly relatives).

After-the-yes maintenance

• Last-minute declines happen. Have a rule: after final count, a decline does not automatically pull a B guest unless catering still allows a swap.
• Log gifts as they arrive, including cash and Venmo, with dates.
• Thank-you notes key off this sheet. If the name is wrong here, it is wrong on the card.
• After the wedding, archive the sheet. You will need it for leftover favors, lost-and-found, and the “who was that?” photo captions.

Sample household rows (copy into your sheet)

Think in households, then explode to seats:

• HH-014 | Jordan Hale & Sam Hale | children: Avery Hale, Nia Hale | A | 4 seats | adults-only? N | meals TBD | table TBD
• HH-015 | Priya Shah | plus-one: Y, name pending | B | 2 seats | address verified 2026-03-12
• HH-016 | Dr. Elena Ruiz | plus-one: N | A | 1 seat | accessibility: aisle end, no stairs

Your real sheet will be wider. The point is that every seat has a name, a status, and a path to a yes or no.

Scripts worth stealing (and then sounding like yourself)

• Address request: “We’re printing invitations and want your name and address exactly as you use them. Also, any +1 we should include by name?”
• Adults-only: “We’re keeping the reception 21+ / 18+ / adults only, so we can have a late night. We hope you’ll still come and enjoy a night off.”
• No plus-one: “We’re tight on space so we can host the people we love—invitation is for you. Can’t wait to see you.”
• Missing RSVP: “Catering needs a number on Monday. Are you a yes for [date]? If yes, any meal choice and dietary notes?”
• Extra-guest attempt: “We only have a seat for the names on the invitation. If something’s changed at home, call us and we’ll be honest about space.”

What people miss

They build a names list and forget households, then under-order invitations. They send save-the-dates to people they later cut. They allow unnamed plus-ones and watch the count inflate by twelve. They put “and family” on an adults-only wedding. They never verify addresses, and the expensive suites come back weeks later. They treat the RSVP deadline as decorative, then give the caterer a guess. They seat enemies because “they’ll be fine.” They have no column for gifts, so thank-you notes stall. They B-list so late that the invitation arrives after the person’s weekend is already booked—and the person knows exactly what happened.

Fix: cap first, policies second, A list third, addresses fourth, paper last. Follow up like an operator. Kind, dated, done.