For the host who keeps refreshing the chat
One question keeps a host up at night: who is actually coming. An RSVP tracker answers it in a single live view, where every reply changes the picture the second it lands.
A reply spreadsheet is a snapshot that starts going stale the moment you save it. The messages land in three different places, you copy them across when you remember, and the file is never quite current. Meanwhile the real question, who is coming, still has to be answered, and now it lives in a document no one trusts.
An RSVP tracker is the opposite: a live list that fills itself in. Each guest who replies moves their own name, so you are always looking at the current answer rather than one you transcribed last week. No copying, no second file, no "did someone already say yes in the group chat?".
The tracker splits the room into the three states that actually tell you where you stand.
A few properties separate a live list from a file you maintain by hand.
A confirmation moves the count immediately, so you are reading what is true now, not a version from your last edit.
Every yes, decline, and plus-one belongs to a real name, so the headcount has a person behind every number if someone questions it.
A guest who edits their answer changes the same record, so the total stays right to the end instead of needing a manual correction.
A tracker shows replies; it is not a forecasting tool and not a dashboard of anything else. You see who has said yes, who has not, and who is coming with a guest, which is the whole subject. On supported events the same list carries meal notes and, on the day, arrival check-ins, but the point is that this one live view is the answer to who is coming, and it does not reach past that.
The reason a group chat is a poor tracker is that it records everything except the thing you need. The count. A list attached to the invitation records replies as they happen, so the number you quote to a caterer, a venue, or a worried parent is one the replies themselves have been quietly building since the first confirmation. That reliability, a live answer you did not have to fight for, is the entire job of the tracker.
How it works
Start the list with everyone you are asking, so there is a known total to measure replies against rather than an open-ended pile.
Guests confirm from the invitation page, and each answer ties to their name on the tracker.
Yes, not yet, and with-a-guest update on their own as replies land, including plus-ones and meal notes coming in with them.
Open the tracker for a current answer to who is coming, and send a reminder to the still-silent names without leaving the page.
Questions
No. They open your link and reply in a couple of taps, and their answer appears against their name on the tracker. Nothing to install.
It updates the same moment the guest confirms, so the view you have at any point is the current one, not a snapshot you saved earlier.
Yes, and it edits the same record rather than adding a duplicate. So a changed plan moves the count instead of needing a manual fix by you.
That is one of its main jobs. The not-yet column holds the outstanding names, so you can see who is still owed a reminder and send it from the event page.
Each event keeps its own live guest list, so a wedding and a birthday do not blur into one pile of names. You open the list that belongs to the day you are planning.
Get Started
Replace the reply spreadsheet with a view that updates itself: who said yes, who has not, who is with a guest, current to the second a reply lands.
