For the day you stop asking is she coming
The list moves the second a guest answers. Names, replies and meals update live from any screen, and on the day a QR check-in at the door keeps the count honest while the party is already on.
Write the names into a document on Tuesday and by Thursday it is a period piece. A guest added a partner, another answered no after a work trip was announced, and none of that told your file. The document is not wrong yet; it is simply no longer the event.
What a host actually needs is a document that edits itself while you sleep. A list fed directly by replies, visible from wherever you are, and trusted by everyone who has to act on the numbers, is not a fancy version of a guest list. It is the only version that can do the job.
Anna Lindqvist and her fiancé each checked replies from a different city during the planning. Two screens, one truth, no comparison of notes at midnight.
Add collaborators with access levels and the list can extend to a sister chasing suppliers or the parent confirming the cake, without sharing the whole account.
On the day the QR check-in means arrivals land on the same list, so a host mid-hairdo can still see that Grandmother made it through before the speeches.
Trust in a record comes from where its data enters. Here there is exactly one door: the reply button on the invitation page. No message history is mined, no bot lurks in a group chat extracting maybes, no contacts get imported from anywhere. A guest exists on the list because that guest answered, which is why the count survives a call from the caterer.
Everything the day needs hangs off that single record: the number, the meals, the seating worked from arrangements on the same list, the reminders aimed at gaps, the arrivals at the door. One list, and the whole evening agrees with it.
How it works
The event page goes out across your chats as a single address, so replies from every chat feed the one list rather than several.
Every tap writes a name with its party and plate. Opening the list is reading the event, not auditing old messages.
Add a collaborator at an access level you set, and the two of you plan against one record instead of trading screenshots.
Set up the QR check-in for the day and arrivals tick against the same names, completing the list from invitation to final guest.
Questions
It does exactly that. Replies are recorded against your event the moment guests tap, whether or not you have the page open, so nothing is waiting for you to refresh your memory. When you next look, the list is current to the last answer.
No. Guests open your invitation page and reply there. The list, with everyone's answers and meals, is what you and your collaborators see, and the event can be password-protected so only invited guests even reach the page.
Arrival, against a name on the list. On the day it separates the replied from the present, so the record answers both questions the morning after depends on: who confirmed, and who is actually inside.
Yes. Collaborators join with access levels you choose, which is how one partner, one family member and one helper all work from the live list without three versions of the evening existing.
It is a web page you sign into from any browser. There is no app to install; the phone in your pocket and the laptop at home open the same live record, which is rather the point.
Get Started
Start free and let replies, meals and arrivals write one record everyone trusts, readable from any screen you happen to be holding.
