Reunion RSVP form
A reunion RSVP tracks attendance and headcount — the same problem as an event registration, but the context is different. This form asks yes or no first, then who they are and how many are coming, so the organizer can plan seating and meals without chasing replies. The form captures who was at the reunion and when they responded, which creates a memory that is better than a spreadsheet kept in someone's email.
The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.
A relation field ties people to the reunion without extra context
A text field for class year or family relation makes the export self-describing — you can see that someone is a second cousin or class of 1985 without a legend. A checkbox labeled just "attending" loses that context.
Timestamps matter for reunion memory
Every RSVP carries the exact moment it arrived, which matters for reunions because it is part of the memory — who reached out first, who arrived late in the planning. That timestamp becomes a story the export tells.
No card required.
Reunion RSVP
Live previewHow to build this form
5 steps in the editor. Nothing here needs a paid plan.
- Add a text field for the attendee's name and an email field for follow-up.
- Add a text field for their relation to the group — class year for a school reunion, relation for a family reunion.
- Add a radio group asking yes or no, marking it required.
- Add a number field for number of guests, optional for quick yeses, and an optional textarea for dietary needs.
- Set a response cap in Settings once you have headcount.
Fields in this form
7 fields, using 5 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Your name | Short text | Yes |
| Yes | ||
| Class year or family relation | Short text | Yes |
| Will you attend? | Radio buttons | Yes |
| How many guests, including you? | Number | Optional |
| Any dietary restrictions? | Long text | Optional |
| What are you up to these days? (optional) | Long text | Optional |
What goes wrong with this form
Specific to a reunion rsvp form, not general advice about forms.
No relation field to explain who people are
Without a class year or relation field, an export of names tells you nothing about how those people connect — you are back to reading emails or assuming you remember everyone. A text field for relation makes the response list self-organizing.
Attendance as a checkbox instead of a radio with a no option
An unchecked box looks identical to a reply that never arrived. A required radio with a "no" option is what tells you who said no from who simply has not opened the invite yet.
Not capturing when people responded
Timestamps on every reply create a memory — who reached out early, who was the last to say they were coming. That matters more for a reunion than for a business event, because the reunion is partly made of those memories.
Questions about this form
What fields does a reunion RSVP need that a regular event form doesn't?
A relation field — class year for school reunions, family relation for family ones. That one additional field makes the response list self-describing; you can see relationships without opening individual replies.
How do I handle dietary needs for a reunion?
Add an optional textarea for dietary restrictions, which is the same approach as event-registration-form. An optional field means respondents do not have to pick a box if nothing applies, but the field is there so the answer arrives before catering is finalized.
Can I find out who is bringing a guest without asking separately?
Yes — a number field for guest count shows who is coming solo and who is bringing others. Export to CSV and you have a real column to sort by, which is simpler than reading free text or asking a follow-up question.