Wedding Guest List: Template, Tiers, and RSVP Tracking

Your guest count sets your budget, not the other way around

Every guest costs money in at least six places: catering, bar, rentals, invitations, favours, and venue capacity. At a typical $200 per guest, cutting 25 people saves $5,000 — more than switching photographers, downgrading florals, and dropping videography combined.

Decide the maximum number your budget supports before anyone starts writing names. Divide your available food-and-venue budget by your per-guest figure, and treat the result as a hard cap.

The A/B tier method

Build three lists. The A list is everyone who must be there — immediate family, closest friends, and the people whose absence would genuinely change the day. The B list is people you would love to have if space allows. The C list is colleagues, distant relatives, and courtesy invites.

Invite the A list first. As regrets come in — expect 10 to 20% for a local wedding and 20 to 30% for a destination one — send B list invitations in waves. Anything mailed six or more weeks before the wedding reads as a first-round invitation.

• Each partner builds their own A list independently before comparing, so neither anchors the other.
• Apply the same rule to both families. If one set of parents gets 20 invites, so does the other.
• Use a 'have we spoken in two years?' test for the C list.
• Cap parent invites as a fixed number rather than a category, then let them choose.
• Track which wave each invitation went out in so you never double-send.

The columns your guest list needs

A guest list is a database, not a list of names. These are the fields you will actually use — anything else is noise.

Plus-one rules that hold up

Pick one rule and apply it to everyone. Inconsistency is what causes hurt feelings, not the rule itself.

• Married, engaged, or living together: always invited as a couple, and both names go on the invitation.
• In a relationship over one year: invite the partner by name if you know it.
• Wedding party: always get a plus-one.
• Guests who will not know anyone else: give a plus-one so they are not stranded.
• Address the envelope to named people only — 'and guest' invites ambiguity as well as a stranger.
• State the number of seats on the RSVP card ('We have reserved 2 seats in your honour') to stop guests adding names.

How to chase RSVPs without being awkward

Set your RSVP deadline three to four weeks before the wedding — roughly one week before your caterer's final headcount deadline. That gap is your chasing window, and you will need it: 20 to 30% of guests miss the deadline on any wedding.

• One week before the deadline: a friendly group message or website reminder.
• Day after the deadline: individual texts. Texts get replies; emails do not.
• Three days later: a phone call from whichever partner knows them better.
• Do not mark silence as a yes. Confirm every head explicitly before you pay per plate.
• Log the answer the moment you get it, including meal choice, so you never have to ask twice.
• Make online RSVP the default and paper the exception — response rates are consistently higher and the data lands clean.

Make online RSVPs match your guest list exactly

The biggest headache with online RSVPs is name drift: 'Katie' RSVPs but the list says 'Kathryn Reynolds', so you end up with two records and an inflated headcount. Solve it at input time by asking guests to select their name from your list rather than typing a new one.

If you must accept free-text names, require first and last name, match case-insensitively against your list, and flag anything unmatched for manual review instead of silently creating a new guest.