The notebook · August 5, 2026 · 6 min read
By The Reunion Fund team
Forty people said yes. Twelve meant it.
Forty people say yes and twelve mean it. How to turn enthusiasm into a number you can hand a caterer, and what to do when ticket sales fall short.
Every reunion organizer learns this the same way. You post the date, the replies come in, and the enthusiasm is genuine and enormous. Wouldn't miss it. Count me in. Finally!
Then the caterer asks for a guaranteed number, and you realize you have no idea what it is.
This is not a people problem. Saying "I'm in" in a group chat costs nothing and carries no date, no payment, and no consequence. It is a mood, not a commitment, and treating it as data is how committees end up paying for thirty empty chairs or running out of food at nine o'clock.
Here is how to get a number you can actually hand to a vendor.
Why RSVPs lie, specifically
Three distinct things go wrong, and they need different fixes.
Enthusiasm decays with distance. A yes given eleven months out is a yes to the idea of the reunion. Life has not been consulted yet. Expect meaningful attrition between a first soft yes and the event, and expect it to be worst for people who answered fastest.
A chat thread has no schema. "I'm in" from someone who then adds "maybe, depends on my sister's wedding" is now what? A yes? Your list has to hold that nuance and it cannot, so somebody makes a judgment call and forgets they made it.
Plus-ones are invisible. People count themselves. They do not count their spouse, their adult kid who also went to the school, or the friend they are bringing. Headcounts routinely run 15–30% above the number of named individuals who replied, and catering is per body.
The fix: three tiers of commitment, not one
Stop asking "are you coming?" It is a single question doing three jobs badly. Split it.
| Tier | The question | What it is worth |
|---|---|---|
| Interested | "Would you want to come to something in July?" | Planning signal only. Never cater to this number. |
| RSVP | "Yes, put me down for the 18th, me plus one" | A real number, still soft. Discount it. |
| Paid | Money has changed hands | The only number that is real. |
The discipline is this: you may only make financial commitments against the paid tier. Book venues, sign catering contracts and order anything per-head off money that has actually arrived, not off a list of intentions.
That single rule prevents the most common catastrophic outcome, which is a committee personally liable for a catering minimum built on optimism.
What the conversion actually looks like
Rough working figures for a class reunion, useful for planning before you have your own data:
- Interested → RSVP: roughly half
- RSVP → Paid: roughly two-thirds, and it clusters hard around deadlines
- Paid → Attended: high, usually 90%+. People who paid show up
So 200 people expressing interest is not 200 guests. It is closer to 65. Plan the room, and the budget, for the number at the bottom of that funnel. Pricing the ticket so that number still covers the event is its own problem.
The catering guarantee, and the date that actually matters
Most venues want a guaranteed count 7–14 days before the event. That number is a floor you pay for regardless of who turns up, and it is usually the largest single financial commitment you will make.
Work backwards from it:
| When | What happens |
|---|---|
| Guarantee date minus 14 days | Payment deadline closes. This is the real deadline. |
| Guarantee date minus 7 days | Final chase to anyone RSVP'd but unpaid |
| Guarantee date | Submit paid count, plus a small buffer if the venue allows |
| Day of | Expect roughly 90–95% of paid guests |
Set your payment deadline at least two weeks before the guarantee date. Committees that set them on the same day end up guessing, because the payments that arrive on deadline day have not cleared into anything you can count yet.
Ask the venue two questions early, in writing: how far above the guarantee they can accommodate on the day, and whether the guarantee can be revised upward after submission. Many can flex up by 5–10%. Almost none will let you revise down.
When ticket sales fall short
This is the moment that decides whether the reunion happens, and it arrives more often than anybody admits. A committee sets a threshold (we need 80 to make this work) and three weeks out they are at 52.
There are four moves, roughly in order of preference.
1. Extend once, publicly, with a number. Not "we're extending the deadline." Instead: "We're 28 tickets short of the minimum. The new deadline is the 19th. If we don't get there we'll refund everyone and try again next year." Specificity converts. Vagueness reads as a soft deadline that can be ignored again.
2. Cut the per-head cost, not the event. Move from plated dinner to buffet, from open bar to cash bar, from hotel ballroom to the American Legion hall. Most reunions are over-specified in month two by people imagining a wedding. Re-scoping to hit a lower guarantee is almost always better than cancelling.
3. Shrink the format. A cocktail reception with no seated meal removes the catering guarantee almost entirely and can be run at a fraction of the commitment. Attendance often goes up, because a lower ticket price removes the barrier that was suppressing sales.
4. Cancel and refund cleanly. Sometimes the number is not there. If you cancel, do it before you are personally liable for a deposit, refund everyone promptly and completely, and say plainly why. Reunions have been cancelled for exactly this reason (not enough people paid in time), and the ones that recover are the ones where the organizer refunded fast and kept the group intact for a second attempt.
The thing that makes all four of these possible is knowing your real number early enough to act on it. A committee tracking paid guests weekly sees the shortfall at eight weeks and re-scopes. A committee tracking enthusiasm finds out at ten days and cancels.
Chasing the gap between RSVP'd and paid
The people who RSVP'd but have not paid are your highest-yield group. They have already decided to come. They just have not done the transaction, usually because they read the message on their phone while walking somewhere.
What works:
- Public updates with numbers, private messages with names. "We're at 61 of 80" in the group. "Hey Dana, you're on the list but I don't have your payment yet. Here's the link" in a DM.
- A standing weekly rhythm. Same day each week, so it reads as an update rather than nagging.
- One link, everywhere, unchanged. Every time the payment link changes, some fraction of people give up permanently.
- A named deadline with a stated consequence. "After the 19th we submit the catering count and can't add anyone" is true and it works.
What does not work: reply-all threads asking people to confirm again, and any message that requires someone to scroll up to find out how much they owe.
The short version
- "I'm in" in a group chat is a mood, not a headcount.
- Split it into three tiers: interested, RSVP'd, paid. Only the paid tier is real.
- Never make a financial commitment against a number that has not paid.
- Set your payment deadline at least two weeks before the venue's guarantee date.
- Expect roughly half of interest to RSVP, two-thirds of RSVPs to pay, and 90%+ of payers to attend.
- Count plus-ones separately. Headcounts run well above the number of people who replied.
- If you are short, extend once with a specific number, then re-scope rather than cancel.
If tracking that funnel by hand is the problem: Reunion Fund keeps RSVPs and the guest list live in one place, so the headcount updates itself instead of being reconciled out of a chat thread, and the list exports in one click when the caterer asks. If your event needs money, contributions are charged straight to the organizer's own Stripe account (Reunion Fund never holds them), and releasing anything from a shared fund takes two committee approvals, with the person who asked barred from casting one. The shared fund is off by default. The free plan covers two active events with up to 30 guests each and three co-organizers. Start planning at reunionfund.com.