Someone is going to ask you how many people are coming.

It will happen at the worst possible moment — while you're on the phone with the venue, while you're trying to finalize the catering headcount, while you're in the middle of something else entirely. And you'll need to know the answer.

Not roughly. Not "I think around forty?" Not "let me check my spreadsheet real quick, I have a few of them."

Exactly.

That's the real goal of reunion RSVP and payment tracking: not just knowing who said yes, but knowing who's confirmed, who's paid, who's bringing a guest, and what your actual revenue looks like right now. All of it, accurate, available in under ten seconds whenever someone asks.

Here's how to get there.

Why RSVPs and Payments Need to Live in the Same Place

The classic reunion tracking setup looks something like this: RSVPs collected through a Google Form, payments collected through Venmo, and a spreadsheet somewhere in the middle trying to reconcile the two.

The problem isn't any one of those tools. The problem is the gap between them.

Someone fills out the Google Form but never pays. Someone pays on Venmo but never fills out the form. Someone fills out the form with one name but pays under a different one. You spend twenty minutes cross-referencing lists trying to figure out if Chad Creamer and C. Creamer are the same person. (They are. They're always the same person.)

Every hour you spend reconciling two separate systems is an hour you're not spending on the actual reunion. And the more people you're tracking, the worse it gets. Forty people is manageable — barely. Eighty people across three spreadsheets at midnight is a different experience entirely.

The fix is simple: RSVP and payment happen in the same moment, in the same place, and feed into the same record. When someone confirms they're coming and pays in a single flow, there's nothing to reconcile. The record is complete the moment they finish.

What Good Reunion Tracking Actually Looks Like

Let's get specific about what you actually need to track, because "keep better records" is advice that helps nobody.

Names — actual names, not just headcounts.

Your venue needs a headcount. Your caterer needs a headcount. But you also need names — for name tags, for the "Who's Coming" section of your reunion page, for the seating chart if you have one, for the moment someone walks in and asks "wait, is Jennifer coming?" and you need to actually check.

Good tracking captures the attendee's name and every guest they're bringing, individually, at the moment they RSVP. Not a guest count. Names.

Which events they're attending.

Reunion weekends are rarely one event. There's usually a Friday kickoff, a Saturday main event, maybe a Sunday brunch or a tour. Someone might come to all three or just the Saturday night. Tracking needs to be per-event, not just per-person — otherwise your event-by-event headcounts are guesses.

Payment status — precisely.

Paid, pending, or comped. How much, for which event, on which date. Not "I think they paid" or "pretty sure that $60 came from them." The exact amount, tied to the exact person, visible at a glance.

Guests added after the fact.

People forget. Someone RSVPs for themselves and then remembers their spouse is coming too. They need to be able to go back, add the guest, and pay the difference — without you having to manually update anything. Good tracking handles this automatically.

The Spreadsheet Problem (And Why It Gets Worse Over Time)

Spreadsheets aren't bad tools. They're the wrong tool for this specific job — and the reason becomes clear around the 30-person mark.

Below 30 people, a spreadsheet is manageable. You can see everyone, you know most of them personally, and the manual updates are annoying but not catastrophic.

Above 30 people, everything changes. You're scrolling to find names. You're color-coding payment statuses. You're creating a second tab for event breakdown. You're naming the file "reunion payments FINAL v3" because the previous two versions had errors you can't fully account for.

And the deeper problem: spreadsheets are static. They show you what was true when you last updated them — which, at 11pm on a Tuesday when you have other things going on, might have been four days ago. Four days is a long time when tickets are still selling.

A live dashboard — one that updates the moment someone pays, the moment someone RSVPs, the moment any record changes — is a fundamentally different experience. You open it and see what's true right now. Not what was true last time you had a chance to update a spreadsheet.

How to Set Up Your Tracking System Before You Open RSVPs

The best time to set up your tracking system is before anyone has RSVPed. The second best time is right now. Here's the setup sequence:

Step one — decide on your events first.

Before you open RSVPs, know what you're collecting RSVPs for. If you have three events over a weekend, set them all up. Mark events that aren't priced yet as "pricing coming soon" — people can still RSVP and get locked in, and you collect payment once you finalize the price.

Step two — set your ticket types per event.

Some events are free (a school tour, a casual kickoff). Some are ticketed (the main Saturday night event). Some might be a flat rate per family group rather than per person — a park outing where it makes more sense to charge per family than per head. Set this up before RSVPs open so the system captures the right information from the first person who clicks.

Step three — connect your payments before you share the link.

If payments require a separate step after RSVP, you'll have a gap. Connect your payment processing before the RSVP link goes out so the first person who clicks goes through the complete flow — RSVP, guest names, payment — in one motion.

Step four — share one link, not multiple.

One link to the reunion page. Not a Venmo handle in one message, a Google Form in another, and a separate email for the hotel recommendations. One link, shared everywhere, that does everything. The fewer places people have to go, the fewer things fall through the cracks.

What to Do With the People Who Don't Pay at RSVP

Even with the best setup, you'll have some attendees who RSVP'd to a free event and now owe for an event that was previously "pricing coming soon." Or people who came in through a different channel and were added manually.

For those cases, a payment request feature — where you can send a payment link directly to unpaid RSVPs for a specific event — closes the loop without you having to track anyone down manually or send awkward personal messages. The system sends the request. The person pays. The record updates.

This is the closest thing to a "chasing payments" scenario that exists in a well-run reunion tracking system — and even here, you're not chasing. You're triggering one automated request and moving on.

The Dashboard Check You Should Do Every Week

Once your RSVP and payment tracking is live, build one habit: check the dashboard once a week, same day, same time.

Look at four things:

Total RSVPs confirmed — is the number growing? If it's been flat for two weeks, it's time to send an announcement or push on social.

Payment status breakdown — how many paid vs. pending? If pending is growing faster than paid, something in the flow needs attention.

Per-event headcounts — are your event numbers tracking toward your venue minimums and catering commitments?

Total raised — tickets plus sponsors plus any donations. Does this number cover your committed expenses with room to spare?

Those four numbers, once a week, give you complete situational awareness over your reunion finances without living inside a spreadsheet.

A Note on Cash and Manual Payments

Not everyone will pay online. Someone's grandfather will hand you an envelope. Someone will Venmo you directly because they didn't see the link. Someone will ask if they can pay at the door.

Good tracking accommodates this. The ability to manually record a cash or Venmo payment — marking the RSVP as paid with a note on how it was collected — keeps your dashboard accurate even when payment comes in through an informal channel. The goal is one source of truth, not a perfect world where everyone pays the same way.

Reunion tracking isn't glamorous. Nobody gets excited about it the way they get excited about the venue or the playlist or the photo slideshow. But the organizers who get it right — who always know exactly where things stand, who can answer any question about RSVPs or revenue in under ten seconds — those are the organizers who enjoy the planning process instead of dreading it.

Set it up right from the start. Let the system do the tracking. Save your energy for the parts that actually matter.

MyReunite tracks RSVPs, guest names, payment status, and per-event headcounts in one live dashboard — updated in real time the moment anything changes. Start planning your reunion free →

Related posts: