The guest list looks like the easy part — write down everyone you love, done. In practice it's the wedding's master variable: it drives roughly half the budget, dictates the venue, feeds the seating chart, and generates more family diplomacy than any other document. It's also not a list. It's a pipeline, from a hopeful first draft to a final headcount your caterer will hold you to, and managing the pipeline well is what keeps the last month calm.
The list is a pipeline with stages
A name on the guest list moves through states: drafted → invited → responded (yes/no) → confirmed in the final count. The failure mode is treating the list as one static document and tracking the states in your head. The fix is boring: every guest carries a status, and the counts you quote to vendors always come from statuses, never from memory.
Three numbers matter at any moment:
- Invited — invitations physically sent.
- Attending — RSVP'd yes.
- Projected final — attending, plus a realistic haircut of the no-responses.
That last one is what vendors actually need, and it's the one couples most often guess.
Expect the decline rate; plan with it
Industry rule of thumb: 10–20% of invited guests decline — closer to 10% for a local list, 20–30% when much of the list travels or the date is a holiday weekend. This isn't a sad fact; it's a planning tool.
| Invited | Expected attendance (80–90%) | Plan catering for |
|---|---|---|
| 100 | 80–90 | ~88 |
| 150 | 120–135 | ~130 |
| 200 | 160–180 | ~172 |
Two consequences. First, you can invite modestly past your venue cap — a 150-cap room can usually absorb a 165-person invite list. Do the arithmetic with the decline rate you honestly expect, not the one you hope for, and know what you'll do in the awkward miracle where everyone says yes. Second, the projected final is a moving average, not a fixed number — recompute it as RSVPs land, and the final count you owe the caterer at two weeks out becomes a reading, not a scramble.
A-list, B-list, and doing it without getting caught
The two-tier list is standard practice and slightly radioactive, so here is the mechanism, judgment-free: the A-list gets invitations at 10–12 weeks out; as declines arrive, B-list invitations go out to fill the space — but no B-list invitation ships later than six weeks out. A "we'd love you to come" that arrives three weeks before the date reads exactly like what it is. If you run a B-list, run it early, run it in one or two waves, and keep the tiers somewhere your future in-laws will not browse.
Parties, not people
Guests don't arrive as individuals — they arrive as households: couples, families with kids, the college roommate plus a partner you haven't met. Track the list by party and the hard things get easier: invitations are addressed per party, plus-ones are a party attribute instead of a philosophical debate, kids-or-no-kids becomes a per-party decision, and the seating chart later inherits coherent units instead of 140 loose names.
On plus-ones, pick a policy once and apply it uniformly — the standard tiers are: everyone married/engaged/cohabiting gets their partner invited by name; relationships past some duration get a named invite; single guests who'd know nobody get a courtesy plus-one. Any policy survives scrutiny except an inconsistent one.
Track the data you'll need later, now
At RSVP time, every attending guest should end up with: meal choice (if you're offering choices), dietary restrictions, and any access needs. This feels like over-collection in month three and feels like genius in the final month, when the caterer asks for "final count with dietary breakdown" and the answer is a report, not a group text archaeology project. The dietary tally in particular — 4 vegetarian, 2 gluten-free, 1 severe nut allergy at table 6 — is exactly the kind of number that must come from the list itself. The food & drink math guide picks up from there.
Chasing the stragglers
Every wedding has 10–15% of the list that simply does not respond by the deadline. Standard protocol: RSVP deadline four weeks out; 48 hours after it passes, one warm text ("we need final counts — are you in?"); one week after, a phone call from whichever of you knows them; after that, they're a no and the projected final updates. You are not being rude. You are being someone with a catering deadline.
How this works in ringbearer
ringbearer's guest list is the pipeline described above: statuses, parties, meals, dietary tags, and plus-ones on every entry, with CSV import to bring the draft in and export whenever you want it back. The counts feed everything downstream automatically — seating capacity, the dietary summary, the drink math — so the number you quote a vendor is always the number that's true. The guest list tour is here. When RSVPs start landing, the next document is the seating chart.
The diplomatic footnote
Someone — a parent, usually one financing something — will produce a list of names you've never heard. The operational answer: additions are welcome as long as the total respects the venue cap and the per-guest budget line, both of which are visible numbers you can share. Turning "we can't invite them" into "here's the constraint we're all working inside" won't make the conversation fun. It makes it short.
See how this works in the app: the product tour.