For the number the caterer asks for
Final numbers for the caterer and the venue stop being a guess. Yeses, plus-ones and meals counted on one live page you can open anywhere, moving the second an answer arrives.
The number is never one number with one deadline. The caterer needs heads and meal splits days before the party to buy in the right shape. The venue needs a count to set tables, and seating needs to know who sits with whom. You need it on the morning, for the toast, for the favours, for whether the hall feels full.
A total dragged out of a chat scroll serves none of them, because it has no way to be current. What a number with deadlines needs is something that counts on its own, continuously, against names, with the party size and the plate already resolved.
Every yes plus its plus-ones, inside the limit you set per reply. The total moves when answers move, which is the definition of live.
Guests choose their meal as they reply, and allergies ride on the same entry, so the kitchen gets a per-choice count rather than a hope.
Seating arrangements exist for the table plan, so the count and the layout are worked from the same living list rather than two notes.
On the day, a QR check-in at the door marks who has actually arrived, giving the evening its final, true number.
For Marta's fortieth at the hall, the moment everyone dreads is the caterer's call: final numbers, by Friday, and the old version of that call meant an evening of reconstruction. The tracked way is smaller. The list is current because replies have nowhere else to go, so you open it on your phone between the flowers and the playlist and read the number across the table.
Collaborators with access see the same count from their own screens, which means the person chasing suppliers and the person chasing the cake are reading one truth. On the night itself, arrivals tick off at the door, and the kitchen's final count matches the room you are standing in.
How it works
Build the event page, write the reply question, set plus-one limits and meal choices, and publish the deadline guests will see. The count's shape is decided here.
WhatsApp carries the invitation; every tap adds a named party to the list with meals and allergies attached, no typing required from you.
When the caterer calls, open the live list and read heads and meals off it. The number is current to the last reply rather than to your memory.
QR check-in updates arrivals as guests come through, so the evening's true figure grows alongside the evening itself.
Questions
Yes, within the limit you set. Each reply carries the party through the button, and the tracker counts the whole household against your rule, so the figure cannot drift upward through quiet additions after the fact.
Yes. Meal choices are recorded with each reply, allergies noted alongside, so the caterer receives counts per choice with the dietary flags attached, pulled from the same list as the heads.
The answer still lands on the list, because replies happen whenever a person taps. What the deadline does is tell every guest when the number was needed; after that, hosts treat late yeses as spare-seat conversations, on the record.
Most hosts abandon the copy once they trust the list. The count updates itself, holds meals and allergies per guest, and tracks arrivals on the day, which is the spreadsheet's whole job done properly.
Yes. Add a collaborator with the access level you choose, and both of you see one live figure from different screens, which is how the caterer and the cake stop receiving two different numbers.
Get Started
Start free, send the invitation, and let heads, meals and arrivals count themselves on one list the whole day agrees on.
