USE CASE
Event registration forms
Collecting RSVPs by email means counting heads by hand, chasing dietary needs the week of, and discovering you oversold the room only when the eighty-first person walks in.
A virtual attendee and a VIP need different things from the same event, but a flat form gives them the same twelve boxes and hopes they read the small print.
LIVE DEMO · READ-ONLY
Try it right here — this is the real thing.
The Event Registrationtemplate, live. Flip between page and guided mode — it’s a preview, so nothing you enter is recorded.
Question 1 of 7. Full name. Read-only preview — nothing is recorded.
Full name *
WHAT MAKES IT WORK
The parts that carry this use case
STEP BY STEP
How you’d run it in FormNest
- 01
Sell the right ticket tier
The ticket-type field puts general admission, VIP, student, and virtual in front of the attendee as a single choice, so each registration is priced and categorised the moment it arrives.
- 02
Ask only what the tier needs
A conditional rule shows the student its ID upload and the virtual attendee its streaming email, while hiding the venue and dietary questions that only matter to people in the room.
- 03
Count guests and diets before the day, not on it
The guest count and the dietary checkboxes roll straight into the responses view, so the caterer's numbers and the headcount are a summary you read, not a spreadsheet you rebuild the night before.
- 04
Cap the room, waitlist the overflow
The event module holds the capacity at two hundred and flips new registrations onto a waitlist once it is full — so the form stops overselling for you instead of you watching the count.