Short answer: give every guest their own link, and let a dashboard collect the replies. That turns RSVP tracking from a transcription job into a page you glance at. What you want from it is five things: live yes / no / pending counts, adults and children as separate numbers, an opened-versus-replied signal per guest, an automatic reminder on a date you set, and a CSV export you can hand to a caterer. RSVora does all five free at any guest count.
Why the spreadsheet fails
Nothing is wrong with a spreadsheet except that it makes you the integration layer. Replies arrive by text, by email, in a group chat, and verbally at school pickup. You transcribe them. You are also the reminder system, and you have no idea who has actually seen the invitation.
Three specific failures follow from that:
- The count is people, not headcounts. "Sarah — yes" hides the fact that Sarah is bringing a partner and three children. This is the most common reason a catering order is wrong.
- There is no opened signal. A guest who has not seen the invitation and a guest who has seen it and is undecided look identical in a spreadsheet, and they need completely different follow-ups.
- Chasing is manual, so it happens late. Usually the week of, usually as a slightly apologetic group message.
What good RSVP tracking gives you
1. Per-guest links
If everyone answers through the same URL, you learn that somebody said yes. If everyone has their own link, you learn who. On RSVora each guest gets an unguessable token URL of their own, and you can still share one public link into a group chat for the people you did not list individually. Both feed the same dashboard.
2. Adults and children as separate numbers
A guest who replies yes sets two counts. That gives you the two figures you actually need — total heads for catering and seating, child count for the entertainment, the cake and whether you need high chairs. It also removes the awkward conversation, because the form asked, not you.
3. Opened versus replied
The pending list is where the work is, and it splits in two:
- Not opened. The invitation did not reach them, or it is buried. Resend it on a different channel.
- Opened, not replied. They have seen it and are deciding, or they forgot. This is a one-line message, not a resend.
4. An automatic reminder
Set the RSVP-by date when you create the event and the reminder goes out on its own. The value is not the reminder itself, it is that you are not the one sending it. Hosts consistently under-chase because chasing feels rude, and a scheduled system message does not feel rude to anybody.
5. Export
At some point a caterer, a venue or a school office wants a list. CSV export means that is a download, not an afternoon.
A workable timeline
- Send: two to three weeks out for a casual party, four to six if people need a babysitter or travel, six to eight for a wedding.
- RSVP-by date: far enough before the event that you can still act on the number. For catering, ask your supplier what their cutoff is and set yours three days earlier.
- Automatic reminder: on the RSVP-by date.
- Personal chase: two days after that, to the names still pending, one message each.
- Final count: the day after the chase.
How to word the chase
The reason "Just checking in!" does not work is that it is not a question. A closed question with the specific detail in it does:
Hi Priya — are you and Sam able to make Saturday the 12th? Just need the final number for food by Thursday.
Name, event, date, deadline, reason. It is answerable in one word, and giving the reason makes the deadline feel like logistics rather than pressure.
More on the wording in how to ask for RSVPs and actually get them and what to do when guests do not RSVP.
Doing it free
RSVora does all of the above with no paid tier, no guest cap and no advertising shown to your guests. Create the event, add guests or share one link, and the dashboard fills in as people reply. Start one — it takes about a minute.