How to Track Wedding RSVPs

Every wedding has the same third act: the RSVP deadline passes and a fifth of the list has said nothing. Not yes, not no, just silence, while the caterer wants numbers and the seating chart waits. RSVP tracking is really two skills: keeping clean data as answers arrive, and chasing the silent minority without souring relationships. Both are learnable.

The Data to Track Per Guest

A guest list entry earns its keep when it answers questions during planning. Track, per invited unit (a household, not just a person):

Full names of every invited individual, including children
Party size: invited count versus confirmed count
RSVP status: pending, attending, declined
Meal choices and dietary restrictions
Invitation status: not sent, sent
Group: family side, friends, colleagues (this powers the seating chart later)
Notes: gift received, song request, accessibility needs

Spreadsheets can hold all this, and they work until the fourth device edit conflict or the column someone sorted without sorting its neighbors. Purpose-built tools survive family collaboration better: an app like Vernans keeps party sizes, RSVP status, and dietary notes on each guest card, shows a live confirmed headcount, and (with sharing) lets both families update the same list instead of emailing versions around.

The Math of Declines

Plan with realistic decline rates instead of hoping:

Local guests: 10 to 15 percent decline
Out-of-town guests: 20 to 30 percent decline
Destination weddings: 30 to 45 percent decline

Blended, most weddings land at 15 to 20 percent regrets. This matters in both directions: for budgets (you likely need fewer meals than invitations) and for A/B list planning (declines free seats earlier than you think).

The Chase: Scripts That Work

Silence rarely means rudeness; it means a card under a fridge magnet. Escalate gently:

Day after the deadline, text: "Hi Aunt Rosa! Finalizing numbers for the caterer this week. Can you let me know if you four can make it on June 20? So hope you can!"

Three days later, call. Calls resolve what texts cannot, especially for older guests, and most conversion happens here.

A week later, the closing message: "Hi Marcus, we need to give final numbers tomorrow. I will have to mark you as unable to attend unless I hear from you today. We would love to celebrate with you!"

Firm, warm, deadline-anchored. Nobody reasonable resents it.

Three Rules for a Clean Count

One source of truth. The moment two lists exist, the count is wrong somewhere. All updates go to one place, whoever receives the reply.
Count seats, not rows. "The Nguyens, party of 5, confirmed 4" is the level of detail catering actually bills at.
Freeze the list on a date. After the final-numbers date, changes go through one person only. Late chaos is manageable when it has a gatekeeper.

Frequently Asked Questions

What percentage of guests will not respond at all without chasing?

Typically 10 to 20 percent need at least one follow-up. Build a two-week chase window between RSVP deadline and final vendor numbers.

Someone replied yes verbally at a party. Does that count?

Record it immediately yourself and confirm the details (party size, meals) by message. Verbal yeses evaporate.

Can we uninvite a non-responder?

After a documented deadline and multiple contact attempts, marking someone as not attending is legitimate and standard. The closing script above makes it explicit and fair.

How do we track RSVPs for multiple events (rehearsal dinner, brunch)?

Per-event status on the same master list, never separate lists. Every guest card should show which events they are invited to and which they confirmed.