Event form templates
Registration is only the first form an event needs. These templates run the whole arc: ticketing attendees, enrolling students and campers, taking vendor and volunteer applications, and collecting feedback once the doors close.
Building this from scratch instead? See Registrations & RSVPs.
Collections
Smaller, hand-picked sets built around one job, with a line on each template explaining when to reach for it.
The templates fall into four groups. Attendee sign-ups cover conferences, festivals, races, galas, golf days, hackathons, reunions, weddings and webinars. Enrolment forms handle the longer commitments of classes, courses, summer camps, schools and daycare. Supplier-side forms take vendor applications and briefs from catering, photography and corporate clients, and plan volunteer rotas. Two more run afterwards: attendee feedback and an internal debrief.
The answers are operational: a registration is a badge to print, a meal to count, a shirt to order and an emergency contact on file before anyone arrives. Each template is built backwards from what the organiser does with the data.
What is an event registration form?
An event registration form collects what an organiser needs from someone who plans to turn up: who they are, which ticket, session, distance or division they want, how to reach them, and the details that shape the day, from dietary requirements and accessibility needs to sizes, emergency contacts and a rules acknowledgement.
Two things often share the name. An RSVP asks a short question, yes, no or maybe, plus a head count and a meal choice, and suits parties and weddings where the guest list is already known. A registration is for open sign-ups from people you have never met, so it usually carries ticket tiers, a waiver and more than one attendee type. This category also covers forms pointing the other way, filled in by vendors, caterers, photographers and volunteers.
What these forms usually ask for
The questions that appear most often across our 41 event form templates.
- Email Address28 of 41
- Phone Number25 of 41
- Full Name15 of 41
- Emergency Contact Phone9 of 41
- Date of Birth8 of 41
- Emergency Contact Name8 of 41
- Event Date8 of 41
- Event Name7 of 41
Why use event form templates
Conferences run in-person, virtual and hybrid; festivals sell day, weekend, VIP and camping passes; galas sell single seats, half tables and full tables; fundraisers separate team captains from team members. Conditional logic branches on that first answer, so a virtual attendee never sees the parking question and a solo golfer is never asked for four names.
Shirt and wristband sizes, meal counts, badge names, jersey sizes and corral assignments all come out of registration, and each carries its own supplier deadline. Kept in structured fields, they filter, search and export as one clean list for the printer, the caterer or the timing company.
Camps, leagues, races and remote retreats need emergency contacts, allergies, medication notes, swim levels and authorised pickup lists, and every event is better for an explicit accessibility field than for hoping someone speaks up. Where a form carries children's medical details or custody arrangements, end-to-end encryption and EU-only hosting are both on the table; confirm what your own licensing body requires.
Embed the form on the event page or wedding website in two lines of HTML, put a QR code on the door sign at an open house, and send the same form as a plain link in the invitation email. One response list, however people arrived at it.
Real-time webhooks and 60+ app integrations let a new registration trigger what follows: a note in the team channel, a row on the run sheet, an address on the announcement list, an invoice raised in whatever tool already handles your ticket money. Nobody rekeys an attendee twice.
How to create your own
- 1
Put the event itself at the top — name, date, venue and registration deadline — before name, email and phone, so people confirm they are in the right place before typing anything.
- 2
Ask what they are registering for next: ticket tier, camp week, race distance, division, table size, or in-person versus virtual. Nearly every later question depends on this one.
- 3
Branch the rest with conditional logic, showing dietary and meal fields only to people attending in person, camping and parking add-ons only to weekend pass holders, and guardian sections only when the registrant is a child.
- 4
Add what you cannot collect on the day: emergency contact name and number, allergies and medication, accessibility requirements, shirt or wristband size, and a badge name kept separate from the legal name.
- 5
Close with acknowledgements and terms: a waiver or code-of-conduct tick box, a photo release, a short text field for insurance certificates or immunisation records kept in a cloud folder, then the ticket price and hosted checkout through Stripe, PayPal, or Square, and a confirmation message saying what happens next.
Getting better responses
The first question should be the one the attendee already has an answer to: which day, which class, which distance, which table. Emergency contacts, dietary notes and sizes belong lower down, once someone has committed. Registrations that open with a block of admin lose people who arrived ready to sign up.
Conference, trade show and gala guests often want a shortened name, post-nominals, or something different from their email signature. One extra field prevents badge reprints on site, where every correction is slow and visible.
Emergency contacts, medication notes and authorised pickup lists should be required: a parent typing 'none' costs nothing, a missing allergy costs a great deal. Learning goals, fundraising targets and 'where are you now' updates work better optional but visible, since the people who fill them in write your programme copy for you.
Dietary plans, sizes, meal choices and skill levels belong in dropdowns, since no chef can cater for 'vegan-ish' and no printer can order 'medium-ish'. Save free text for wording that has to be exact: sponsor recognition lines, roommate requests, dedications, and maiden or former names.
Ask how people heard about the event on the registration form, then put a feedback QR code at the exits and send the survey within a day or two, before attendees move on. Have the team file an internal debrief the same week, while everyone remembers which supplier let them down.
Who uses these forms
Frequently asked questions
What should an event registration form ask for?
At minimum, name, email, phone and what the person is registering for: ticket tier, session, camp week, distance or division. Then add the operational fields your event actually needs, which vary more than people expect. Dietary requirements and meal choices where there is catering, shirt or wristband sizes where there is merchandise, emergency contacts and medical notes for anything physical or residential, and a badge name where badges get printed. Anything you would otherwise chase in the final week belongs on the form.
What is the difference between an RSVP form and an event registration form?
An RSVP confirms attendance for people you have already invited: yes, no or maybe, how many are coming, and a meal choice. A registration form opens sign-ups to people you do not know, so it also handles ticket types, waivers, sizes and safety details. Weddings, galas and parties often want both, a short RSVP for the invited guest list and a fuller registration for the ticketed parts.
When should event registration open and close?
Work backwards from your suppliers' deadlines rather than from the event date. Merchandise printers generally need final sizes two to three weeks out, caterers need firm meal counts around the same point, and recruiting and briefing volunteers realistically takes a couple of months. Set the registration deadline before the earliest of those, state it in the opening paragraph of the form, and keep a shorter late or waitlist form for anything that arrives afterwards.
Can I take payment for tickets and entry fees on the form?
Yes. Add a Stripe-powered payment field to collect ticket prices, entry fees, add-ons such as parking or mulligans, and fixed deposits inside the registration itself. For allocated seating or inventory managed elsewhere, keep your ticketing tool in the flow.
Is a tick-box waiver or code of conduct acknowledgement enough?
A tick box records that the participant saw the text and agreed to it, stored with a timestamped submission you can search later, which is how many casual races, recreational leagues and hackathons handle acknowledgement. It is not the same as a signed document, and higher-risk events are often expected to hold one. Check what your insurer, venue or governing body requires before relying on the form alone.
How do I cap numbers or run a waiting list?
Watch the count as registrations come in, since responses can be filtered and searched, and a webhook on every submission can alert your team as you approach capacity. When you hit the cap, swap the shared link or embed for a short waitlist form that asks only for name, email and the session they wanted. Workshops, camps and small classes are usually easier to run this way than with a hard cut-off, because you keep the option of releasing a few extra places.
Related templates and guides
Start from scratch and build exactly the form you want.
Start building