RSVP Templates
Class Reunion RSVP Templates and Best Practices
An RSVP form is the moment alumni go from "maybe" to "yes." If the form is too long, too short, badly structured, or asks for the wrong things at the wrong time, you lose them. Here are 8 RSVP form structures - with the exact fields, field types, and which to mark required - plus payment timing, follow-up cadence, and the rules that govern conversion.
The 5 Rules of a Class Reunion RSVP
Before form-building: the rules that decide whether alumni complete or bounce.
✓ Step 1 captures interest. Step 2 captures money.
Two-step flow. The first screen asks 'yes/no/maybe' and an email. The second screen asks for everything else. Front-loading payment kills 30-50% of would-be RSVPs.
✓ Required fields are the minimum. Everything else is optional.
Mark only what you genuinely cannot run the event without. Most form-builders over-mark required - which is the single most common cause of abandoned RSVPs.
✓ Charge at RSVP, not at the door.
Door payment rates collapse. People say they'll show up and don't. Card-at-RSVP commitment increases attendance follow-through by 20-40%.
✓ Use conditional logic for plus-ones.
Plus-one fields should appear only if 'yes, bringing one.' Otherwise the form looks 50% longer than it actually is - and alumni bounce on visual length alone.
✓ Confirm everything by email immediately.
Auto-send a confirmation with name, ticket count, meal choice, plus-one info, payment receipt, hotel block info, and the date the RSVP closes. The committee should not be the receipt machine.
✅ With Reunly
Reunly enforces every one of these rules by default
Two-step RSVP, payment-at-RSVP, conditional plus-one logic, auto-confirmation emails - built into Reunly's class-reunion flow.
8 templates
8 RSVP Form Structures (Field-by-Field)
Eight forms covering every common class reunion use case - from the soft save-the-date check-in to the full ticketed RSVP with plus-ones, dietary needs, and committee volunteers. Each form lists every field, its type, and whether to mark it required.
📄 With Reunly
Build any of these in 10 minutes
Reunly ships with all 8 RSVP templates as starting points. Pick one, customize the fields, hit send.
Money in
Payment Timing: When to Charge
When you collect payment matters as much as how. Here's what works.
At RSVP (recommended default)
What: Charge the full ticket price (plus plus-one fee) at the moment the alumni clicks 'Confirm RSVP.'
Why: Highest commitment, lowest no-show. Refundable up to 30 days before the event, then non-refundable. Door rate is 15-25% higher and cash-only.
Use this for 90% of reunions.
Deposit at RSVP, balance later
What: Charge a $25-50 deposit at RSVP. Charge the balance 60 days before the event from the saved card.
Why: Useful for very high-ticket reunions ($200+) where alumni want time to commit. Modest lift in early RSVPs, modest drop in final attendance.
Use only if your tickets exceed $200 and you need to ease the upfront commitment.
At the door
What: Free RSVP. Pay cash or card at the door.
Why: No-show rate is 30-60%. Cash handling is a logistical nightmare. Hard to budget against. Don't.
Avoid except for genuinely free events where you only need a count.
Free event
What: No payment at all. Pure RSVP for headcount.
Why: Used for happy-hour-style 10-year reunions, alumni gatherings, or sponsor-funded events. Higher RSVP rate, lower attendance follow-through.
Acceptable for casual events under 50 people. Be prepared for 30-40% no-show.
💰 With Reunly
Reunly handles payment at RSVP natively
Stripe-powered ticket payments, deposit splits, refund logic, and plus-one fees - all reconciled per attendee in your committee dashboard.
Follow-up cadence
The 4-Touch Follow-Up Schedule
No matter how good the invitation, single-send campaigns top out at 40-45% response rates. Committees that send 4 well-paced touches hit 65-75%.
Touch 1: Initial invitation
4-6 months out · Full list
The main invitation with full details. RSVP link in 3 places (top, middle, bottom).
Channel: Email primary, Facebook secondary
Touch 2: 'We're filling up' nudge
2-3 months out · Non-responders only
Social proof + specific names. 'We're at 80 confirmed - including [4-6 recognizable names]. Are you in?'
Channel: Email + Facebook comment in pinned post
Touch 3: Specific-hook nudge
6 weeks out · Non-responders + people who clicked but didn't RSVP
Lead with a specific draw: confirmed teacher, surprise guest, classmate flying in from far away. Hotel block deadline reminder.
Channel: Email + targeted text to known phone numbers
Touch 4: Final push
7-10 days before RSVP closes · Everyone who hasn't responded
Hard deadline. 'RSVPs close Friday. Walk-up rate is $X cash only after that.' Keep under 75 words.
Channel: Email + text + Facebook post
📅 With Reunly
Reunly auto-sends the reminder cadence
Set the dates once. Reunly emails non-responders on your schedule and tracks every open, click, and RSVP back to the source.
The RSVP Confirmation Email
Auto-send within seconds of a successful RSVP. Include everything alumni need so the committee doesn't have to answer questions later.
Frequently Asked Questions
How many fields should a class reunion RSVP form have?
For the main paid RSVP, 8-12 fields is the sweet spot - spread across 2 steps. Front-load identity (name, email, attending y/n) on step 1. Put payment, meal choice, plus-one details, and notes on step 2. Forms longer than 15 fields lose 30-50% of completions. Forms shorter than 5 fields don't collect enough information for the committee to actually plan. The exception is the soft save-the-date RSVP, which can be 2 fields total.
When should I collect ticket payment - at RSVP or at the door?
Always at RSVP. Door collection rates collapse - even with a clear policy, you'll see 30-60% no-shows on door payments. Charging at RSVP serves two purposes: it locks in commitment (people who paid actually attend) and it solves the cash-handling problem for the committee. Use a payment processor that handles refunds cleanly (Stripe, Square) so the rare legitimate cancellation isn't a logistical disaster. Reunly's class-reunion product handles this natively.
Should RSVPs be on one page or split across multiple steps?
Split, almost always. Two steps is ideal: step 1 captures the soft commitment (yes, you're attending; here's your email) before showing payment. Step 2 captures the payment, meal choice, plus-one details, and dietary notes. This 'commit before pay' structure increases overall conversion 15-30% compared to a single long form. The reason: alumni who psychologically commit to attending on step 1 follow through on step 2, even with friction. Front-loading payment scares off the fence-sitters.
How do I follow up with people who haven't RSVPed?
On a 4-touch cadence: full invitation (4-6 months out), first reminder (4-6 weeks later), second reminder (6 weeks before deadline), final push (7-10 days before deadline). Each reminder should use a different angle: confirmed attendees, hotel block expiration, dress code question, deadline pressure. Vary the channel: email for the first two, email + text for the final push. The committees that hit 70%+ response rates send all four touches. The single biggest miss in reunion planning is treating RSVPs as one-and-done.
What's the best platform for collecting class reunion RSVPs?
Whatever lets you collect RSVPs, payment, plus-ones, and meal counts in one link with a dashboard the committee can see. Reunly's class-reunion product is built specifically for this case - one link captures all of it and feeds a real-time committee dashboard. Generic alternatives like Google Forms + Venmo + Eventbrite + a Google Sheet work but create reconciliation problems: who paid, who didn't, who's bringing a plus-one, who chose chicken. The simpler the stack, the cleaner the night-of headcount.
Should plus-ones be allowed to RSVP separately?
No - bundle them under the primary alumni's RSVP. Separate RSVPs for plus-ones double the data-entry burden, create matching problems ('which Sarah is this'), and complicate payment reconciliation. The cleanest workflow: the primary alumni RSVPs and adds their plus-one's name + meal choice + dietary notes in the same form. The plus-one gets a confirmation email automatically. Reunly's RSVP flow handles this with one transaction and one record per couple.
What information should I NOT collect on a reunion RSVP?
Don't collect: home address (you don't need it, and asking creates privacy concerns), job title or income level (irrelevant), social security number (never - even for tax-receipt events), personal stories you intend to publish without consent, full medical information beyond food allergies, or any information you don't have a plan to use. Every extra field is an excuse for alumni to bounce. The rule: if the committee can't articulate a concrete use for the data, don't ask for it.
How long should I leave the RSVP open?
Open the main RSVP 4-6 months before the event. Close it 2-3 weeks before the event so the venue has time for meal counts. After the close, accept walk-ups at a 15-25% premium and cash-only - this preserves the committee's budget while not turning anyone away. Don't leave RSVPs open until the day of - the venue will need a hard count, and a flexible deadline produces a chaotic one. Reunly auto-closes the RSVP on the date you set and switches to a walk-up only page after.
Collect Every RSVP. Track Every Payment. One Link.
Reunly handles RSVPs, ticket payments, plus-ones, meal counts, dietary needs, and your committee dashboard - in one class reunion link.