Every wedding starts with a spreadsheet named something like “Guest List FINAL v3 (use this one).” It has a column for RSVPs that's half emoji, a dietary column nobody updates, and a tab from an earlier draft that may or may not be load-bearing. Meanwhile the real answers live in text threads.
The guest list is not a document. It's the input every other wedding decision reads from — catering counts, table counts, bar order, place cards, hotel blocks. When it drifts, everything downstream drifts with it. So we made it the one list that can't drift.
A list with consequences.
Import once, retire the spreadsheet
Bring the existing list in via CSV — names, emails, parties, the works. Export it back out any time. The data is yours; we're just keeping it honest.
RSVPs with receipts
Attending, declined, no word yet — filter and search the list by status, and watch the headcount that every other module depends on update itself.
Dietary needs that reach the kitchen
Meal selections and restrictions live on the guest, not in a separate doc. The food & drink module aggregates them automatically — twelve vegetarian, three gluten-free, one nut allergy, counted for you.
Parties, not just people
Group households and families so invitations, plus-ones, and seating all follow the same logic. The Hendersons are one unit — the app knows that.
Guests
118 invited · 94 attending
Nora Alvarez
Attending
Sam Whitfield
Attending
June Okafor
No response
Theo Marsh
Declined
Illustrative. The real thing has search, filters, and CSV export.
One RSVP update. Four counts corrected. Zero texts asking “wait, is your cousin coming?”
The method behind it: guest list management, from draft to final headcount.