For whoever keeps losing track of heads
A spreadsheet guest list starts decaying the hour you share it. Build instead from names, then let confirmations tick rows off so the list is true on the day you need the number.
Every guest list begins as one column of names, and for a week that is fine. Then replies arrive by text, two people bring partners you add from memory, one family emails three separate messages, and someone on the list has quietly moved without it being recorded. The document you trusted becomes the thing you distrust, and the final number is assembled by gut on the eve of the event.
The structural problem is that the list and the replies live apart. Every answer requires you to transcribe it, and transcription is where guest lists go wrong. The fix is not a better spreadsheet; it is making the reply and the list the same object.
So build in the opposite order: collect names first as the skeleton, then point the invitation at the list so each confirmation lands against its own row. From that point the list maintains itself, and you only ever add to it, never repair it.
One sitting per pass, each roughly ten minutes. The passes answer different questions.
Names only, no filtering. Family, friends, colleagues, neighbours, the people you feel obliged to ask. This pass exists so nothing important is forgotten in the tidy-up of pass two.
Group the names into circles — your side, their side, work, the old friendship crew. Set a budget ceiling per person for food and space, then mark which circles fit inside it. This is where tough cuts happen, and they belong here, months before any guest feels them.
Decide the invite unit: a household, a couple, an individual. Set the plus-one policy per name now, because the list is what enforces it later. Add contact details only for people you will actually message.
Small habits, borrowed from people who run events for a living, that stop the list wobbling.
Here is the part that changes everything: once your names exist in My Joyfullday's guest list, the invitation you send is wired to it. A guest opens the link, confirms, names their companion inside your limit, and adds a meal note — and all of it attaches to their row. No transcription. The replied column fills itself, the outstanding column shows exactly who still owes an answer, and the running total is honest weeks before any caterer needs it.
Declines count too, which is what makes the number trustworthy rather than optimistic. And for the handful who reply to nothing, the list hands you the reminder: one action sends a nudge through WhatsApp or email to the non-responders only. Your job shrinks to decisions, because the record-keeping is no longer a job at all.
How it works
Plausible names first, circles and limits second, households and plus-one rules third. Keep the plus-one policy as a single written line you can paste into the invitation later.
Enter the households into your event's guest list in the web app, or describe the gathering to Jitabi and add names after it drafts the page. The list is the skeleton the invitation hangs on.
Publish the page with RSVP switched on and limits set per name. Every reply now has somewhere to land instead of a thread.
Check the outstanding column weekly, remind the quiet names from inside the list, and arrive at your deadline with a total that built itself.
Questions
Settled and closed the moment invitations go out. Replies and reminders can keep moving after that, but new names should not. A list still growing during the send wave is a list that produces forgotten invitations and double counts.
Decide per household at the list stage and enter the allowance against the name. When the invitation's reply form goes out, it enforces whatever the list says, so no guest can confirm more companions than you granted.
That is the right instinct. My Joyfullday supports collaborators with different access levels on an event, so a partner or co-host can watch replies without either of you editing a private copy of the same names.
A confirmation, from anyone in the household, against a named row — including their plus-ones and meal notes. A read receipt, a vague maybe in a chat, or a verbal yes at a family dinner counts for nothing until it lands on the list.
Yes. Declines are why the total is trustworthy, and their names tell you who to inform if plans shift later. A list that only records yeses leaves you re-deriving the real headcount from memory.
Get Started
Three passes, clear household rules, and replies wired straight to names. A guest list should be a record that updates itself, not a document you repair.
