For whoever signs the caterer's form
The gap between a good guess and a confirmed list is where the replies land. On the page, under names, with plus-ones and food notes — before the cake order closes, not after the doors open.
Every birthday has a moment when a number must be real. The cake order, the caterer's cut-off, the venue's final count. Hosts usually meet that moment with an estimate built from read receipts and optimism, then discover the truth at the door. Thirty expected in your head, forty in the room — or the reverse, with a table of ten sitting empty in full view of the guest of honour.
An RSVP page moves the number earlier. Guests confirm on the invitation, their answer recorded against their name, and the count grows while there is still time to act on it. The caterer gets a list of names instead of a hopeful round number.
When a family is invited, each member counts — not one line for 'the Kowalskis'. The reply shows exactly who is coming, which matters most at kids' parties, where children plus staying parents are two very different numbers.
Guests bring someone only inside the limit you set, and every plus-one appears on the list attached to the guest who invited them. The budget survives the open invitation.
Meal choices and allergies arrive as part of the yes, so the vegetarian count is data rather than a guess made in the hallway.
Set a reply date, and the quiet guests get a nudge by WhatsApp or email. The list shows who has not answered before you need to know their name — and a reminder is a plain message from the host, not a confrontation.
Late replies are normal, so plan for them: a deadline with a week of slack, one round of reminders, and a list that stays open until the catering cut-off rather than the pretty date on the invitation. A slightly untidy count you can still act on beats a tidy one that arrived too late to use. The point is not perfection — it is that the cake decision gets made from the best real number you have, not from the loudest guess in the family chat.
How it works
Publish the birthday page with RSVP switched on, plus-one limits set, and the deadline chosen around the catering cut-off rather than around the party.
Add the members you expect to each entry, or invite the household and let the reply specify who is actually coming. Either way, names end up on the list instead of heads.
When the deadline passes, one button reaches the non-responders. The list updates as answers come back in.
Export the confirmed count when the caterer calls, and on the night the QR check-in at the door shows who actually arrived against what was ordered.
Questions
No. They open the link, say yes or no, name their plus-one inside your limit, add any food note, and that is the whole task. Accounts exist only for the people managing the event.
That is the gap between confirmed and actual, and every party has some. Door check-in by QR marks arrivals as they happen, so the list matches the room rather than the replies.
Yes — they reopen the page and update it. The latest answer is the one on your list, so no reconciliation work falls to you.
It is kinder than the alternative. Guests prefer one clear date to an open question, and a deadline with slack gives you time to remind quietly before the numbers must be final.
Add the members to the entry when you invite, or leave the reply to specify. Either route, the list holds names rather than an unexplained heads-count, which is what cake and favours are actually ordered from.
Get Started
Turn birthday replies into a list you can hand to the caterer with a straight face, and let the reminders handle the chasing.
