Conference registration form
A conference registration form onboards attendees for a professional event spanning multiple days and tracks — distinct from a webinar, which is one virtual session. This captures name and email, company, a ticket tier, a primary track or session interest so you can personalise pre-event communication, and optional dietary or accessibility needs so your venue can accommodate them.
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.
Track preference helps you communicate before the event
Knowing which track attendees chose means you can send track-specific reading lists and speaker bios ahead of time — personalisation done at registration, not manually later.
Dietary and accessibility needs improve the on-site experience
Asking upfront means catering and accessible seating are prepared in advance rather than scrambled at the venue.
No card required.
Conference Registration
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 full name and an email field for the agenda and updates.
- Add a text field for company or organisation.
- Add a select for ticket tier — general admission, VIP, student — so you know access level.
- Add a select for primary track interest, so you can send track-specific schedules.
- Add an optional textarea for dietary or accessibility needs so catering and venue staff can prepare.
Fields in this form
6 fields, using 4 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Full name | Short text | Yes |
| Yes | ||
| Company or organisation | Short text | Yes |
| Ticket tier | Select | Yes |
| Primary track interest | Select | Yes |
| Dietary or accessibility needs (optional) | Long text | Optional |
What goes wrong with this form
Specific to a conference registration form, not general advice about forms.
Treating track preference as binding rather than informative
Track preference is a hint for pre-event communication, not a commitment — attendees may explore other tracks on-site, so keep the full agenda visible to everyone.
Not sharing accessibility needs with your venue early
A flagged need that never reaches the venue is useless. Export and share the CSV with venue operations well ahead of the event.
Asking for dietary preferences without acting on them
If the caterer only receives a headcount, dietary answers go to waste. Export the dietary needs as their own list and send it separately.
Questions about this form
How is this different from a webinar registration form?
A webinar is one virtual session, often one-off. A conference is multi-day, in-person, with multiple tracks, so this form asks for track preference and accessibility needs that a webinar registration does not need.
Can attendees choose multiple tracks?
This form has one select for primary track preference. If you need multiple track selections, you would need a form with several checkbox-style fields instead — for most events, one primary preference is enough to personalise outreach.
What should I do with the dietary and accessibility needs?
Export the CSV and share it with your venue and catering team ahead of the event, so they can prepare vegan options, accessible seating or quiet rooms in time.