A registration form builder for events, courses and classes
A registration form has a harder job than a signup form: it has to identify the person, capture what they're registering for, often take money, sometimes book a specific time, and send them away confident it worked. Most tools handle the first two and leave the rest to a second product. Here is what a complete registration flow needs and how to build one.
What makes registration different
A newsletter signup asks for an email. A registration commits somebody to being in a particular place at a particular time, which means it has to be right — and it means the failure modes are expensive. Someone registered for the wrong session, an attendee with no dietary note, a paid seat with no payment attached, two people booked into the same one-to-one slot: each of these takes a human to unpick afterwards.
The consequence is that registration forms need to do more at submission than store a row. They need to compute the right price if the price varies by ticket type. They need to hold a specific slot if the thing being registered for has slots. They need to record consent where consent is required — a photo release, a liability waiver, a parent's permission. And they need to confirm all of it back to the registrant, because a registration nobody got a confirmation for will generate an email asking whether it worked.
That's the shape to design against. Everything below assumes the goal is a single submission that leaves nothing outstanding.
What every registration form has to capture
Work down this list and mark each one as needed or not. The ones you skip should be deliberate skips.
- Identity — name and a contact method that actually reaches them on the day
- What they're registering for, expressed unambiguously (session name and date, not "the morning one")
- Quantity or party size, if more than one person can come per registration
- Anything that has to be arranged in advance: dietary needs, accessibility requirements, equipment
- Payment, where a seat isn't free — attached to the same submission, not a separate link
- A specific time slot, where the thing being registered for is one-to-one or scheduled
- Consent and waivers where they're legally required, recorded with the registration
- Emergency contact details, for anything physical or involving minors
- How they heard about it — the one marketing question worth its space on the form
Three shapes of registration form
Most registrations are one of these. Each has a different hard part.
Free event or RSVP
The simplest case, and the one where over-asking does the most damage. Name, email, and whether they're bringing anyone. Add a dietary or accessibility field behind conditional logic so it only appears for people who say they have requirements. The hard part is turnout, not data collection — so keep the form to under a minute and put the date, time and location above the first question.
Paid event or ticketed registration
Now the amount depends on the ticket type, which is where price-by-answer earns its keep: one form covering early bird, standard, and student pricing rather than three forms. The critical detail is that the total is recomputed on the server at checkout and re-verified at submission, so the amount charged is decided by your form definition rather than by whatever the browser submitted. Payments run through your own Stripe or PayPal keys with no platform cut, on Pro at $14.99/mo.
Course, class, or one-to-one session
Here the registrant isn't just signing up, they're taking a specific slot. This is the case that normally spans two tools — a form for the details and a booking link for the time — with people falling out of the gap between them. The scheduler is a native question type here, so a course registration and a session booking are one submission. Availability comes from real free/busy on the connected Google or Outlook calendar, and a unique database constraint makes double-booking impossible.
From form to a list you can work from
Three things to set up before you publish, not after registrations start arriving.
Get the data where it's needed
Decide now whether the attendee list lives in a spreadsheet, a CRM, or your own system, and connect it before launch. Google Sheets, Zoho CRM, Zapier, webhooks, and email notifications are all on the free plan; Slack, Notion, HubSpot, Mailchimp, Airtable, and Excel are on Pro. Retrofitting this after fifty registrations means a manual export and a reconciliation.
Sort registrants as they arrive
Tag rules label a response at submission based on what was answered — ticket type, session, dietary requirement, first-timer or returning — with a fallback tag when nothing matches. That turns the export into something you can filter rather than something you have to read, which matters a great deal at two hundred registrations and not at all at ten.
Test the whole path, including payment
Register yourself, end to end, with a real card and the smallest amount you can charge. Check the calendar event appeared on the right calendar, the payment description is recognisable on a statement, and the confirmation says what you think it says. Every path through the logic needs this once — most registration disasters are a branch nobody walked before launch.
Registration requirements across the tools
The specific things registration needs, and where each tool puts them. Verified August 2026.
| Registration needs | Elsewhere | Zunoform |
|---|---|---|
| Take a ticket payment | Typeform on a $91/mo tier; Google Forms cannot do it natively; Tally includes Stripe free | Pro $14.99/mo, your own Stripe or PayPal keys, no platform cut |
| Vary the price by ticket type | Often means a separate form per price, or a manual invoice | Price by answer, recomputed server-side |
| Book a specific time slot in the form | A second tool and a second link; Calendly free gives one event type and puts screening questions on a $16/seat/mo tier | Free, native scheduler with Google and Outlook sync |
| Only ask questions that apply | Google Forms can jump between sections but can't hide a single question | Free, per-question logic |
| Collect a signed waiver | Frequently a separate e-signature product | E-signature question type, paid plan to publish |
| Run it under your own branding | Never on Google Forms; $56/mo at Typeform; from $39/mo at Jotform; $29/mo at Tally | Pro $14.99/mo, custom domain on Business |
Registration templates
Four starting points covering the common registration shapes.
Attendee details, ticket type, guests, and dietary needs.
Pick a course, pick a schedule, and pay the fee in one sitting.
Ticket tiers with live pricing, track picks, and checkout in one flow.
Session choice, role, and audience questions for live online events.
Questions people ask
Can one form handle registration and payment together?
Yes, and it should. Splitting registration and payment across two steps loses people in the gap and leaves you reconciling a list of registrants against a list of payments. A payment question in the same form means the seat and the money arrive in one submission. Payments are a Pro feature at $14.99/mo, running on your own Stripe or PayPal keys.
Can a registration form book a specific time slot?
Yes — the scheduler is a native question type, so someone can register and pick their slot in the same submission. Availability is drawn from real free/busy on your connected Google or Outlook calendar, bookings sync back to it, and a unique database constraint prevents two people taking the same slot. The scheduler is on the free plan.
How do I stop people registering for the wrong session?
Label sessions unambiguously — full date, start time, and time zone, never "morning" or "session two" — and use conditional logic so the questions that follow depend on the session chosen. Then confirm the choice back to them in the wording of the ending page, where a mistake is still cheap to fix.
What should a registration confirmation include?
The date, time and time zone, the location or join link, what they registered for, what they paid if anything, and who to contact to change it. Missing any of those generates an email you then have to answer. Where the registration includes a scheduled slot, the calendar sync does part of this job by putting the event directly on the calendar.
Is a registration form builder free?
The free plan covers unlimited forms, 500 responses a month, conditional logic, file uploads, and the scheduler — enough to run a free event or a course signup end to end. Taking payment for tickets requires Pro at $14.99/mo, as does removing Zunoform branding.
Keep reading
Better forms.
Better data.
Build your first form in under 60 seconds. Free forever for personal use, no credit card required.