Class Reunion Registration Form Setup

Q: What should a reunion registration form include?

Capture name, contact info, guest count, meal or dietary choices, ticket type, and payment. Keep it short so people finish it in one sitting.

Q: Should registration and payment be combined?

Yes. Combining RSVP and payment on one form boosts completion and gives you an accurate paid headcount instead of guesses.

Q: How do I collect meal choices?

Add a simple dropdown for entree or dietary needs on the form so your caterer gets exact counts from your RSVP totals.

The form is your headcount, so treat it that way

Everything downstream, catering counts, name tags, seating, the final budget, flows from your registration form. If the form is long or splits RSVP from payment, people start it and never finish, and you are left calling classmates a week before the event. The goal is a form someone can complete on their phone in under two minutes, in a single sitting, with money already collected. Keep it short, ask only what you will actually use, and put payment on the same screen.

< 2 min

target time to complete

1 page

RSVP + payment together

6–8

fields is the sweet spot

Fields fill in one by one, then the completed form drops into your live attendee list.

What to put on the form (and what to cut)

Identity and contact

Full name (and maiden or former name for a class), email, and mobile number. Email confirms the ticket and receipt, the phone number lets you send a day-of text reminder. Skip mailing address unless you are shipping something.

Guest count and names

A simple number for guests, plus a name field for each so your check-in list and name tags are ready. This one field prevents the classic day-of scramble of unlabeled plus-ones the caterer never counted.

Meal or dietary choice

A single dropdown, entree A, entree B, vegetarian, or 'no dietary needs', gives your caterer exact counts straight from the RSVP totals. Add a short free-text box for allergies. Do not over-engineer it with ten options.

Ticket type and payment

Show your ticket tiers (early-bird, standard, single vs. couple) and collect payment on the same screen by card. A paid registration is a confirmed guest; an unpaid RSVP is a hope. Combining the two is the single biggest lever on completion and headcount accuracy.

“An unpaid RSVP is a hope. A paid registration is a guest.”

Design choices that lift completion

Small friction points quietly cost you registrations. The form should default to mobile-friendly, remember nothing sensitive, and confirm instantly. A few specifics that consistently move the needle:

Put payment on the same page as the RSVP, never a separate follow-up email
Make guest names required so name tags and check-in are ready without extra work
Send an automatic confirmation with the date, time, address, and what they paid
Show a live 'X classmates registered' count to nudge fence-sitters with social proof

Frequently asked questions

What should a reunion registration form include?

Capture name, contact info, guest count, meal or dietary choices, ticket type, and payment. Keep it short so people finish it in one sitting.

Should registration and payment be combined?

Yes. Combining RSVP and payment on one form boosts completion and gives you an accurate paid headcount instead of guesses.

How do I collect meal choices?