Classic form
Conference registration form
A real, finished registration form for a two-day conference. Every field below is one somebody actually has to answer, so the list is short on purpose.
The form itself
A static copy of the finished form, exactly as it renders. Nothing here can be filled in or submitted, so read it as a reference and build your own from the button above.
Every field, and what it collects
The complete field list, in the order respondents meet it.
- Attendee nameNameRequired
- Email addressShort textRequired
- Your ticket and joining details go here.
- Mobile numberShort text
- Only used for day-of updates.
- OrganisationShort text
- Job titleShort text
- Ticket typeSingle choiceRequired
- Options: Standard, $490 · Team of three or more, $390 each · Speaker or sponsor · Virtual, stream only
- Which days will you attend?Multiple choice
- Options: Wednesday 14 October · Thursday 15 October · Workshop day, Friday 16 October
- Preferred breakout trackDropdown
- Options: Platform and infrastructure · Data and machine learning · Product and design · Security · Undecided
- Dietary requirementsLong text
- Written in your own words rather than a tick list, because allergies rarely fit a tick list.
- Accessibility requirementsLong text
- Tell us what you need and we will arrange it before you arrive.
- Before you finishMultiple choiceRequired
- Options: I have read and agree to the Summit code of conduct · I am happy to appear in photography and video from the event
Who is coming
Your ticket
Access and catering
What makes this form work
Ticket type comes before anything optional
The thing you need for revenue and capacity sits near the top, while attention is highest. Dietary and access questions come after, where a longer answer is fine.
Dietary needs are a text box, not a tick list
Every allergy list is missing somebody. An open box catches the coeliac who also cannot have sesame, and it takes the same three seconds to fill in.
Accessibility is asked plainly
Naming real examples, captioning, an interpreter, a seat near the front, gets far better answers than "special requirements", which most people leave blank.
Questions people ask
What fields does a conference registration form need?
Name, email and ticket type are the minimum. Add organisation and job title if you print badges, day selection if it is a multi-day event, and separate dietary and accessibility questions if you are feeding people or hosting them in person.
Should I ask for dietary requirements as a dropdown?
An open text box works better. Allergies and medical diets rarely fit a fixed list, and caterers need the detail rather than a category.
Can I take payment on the form?
This example collects the registration and the ticket type. Send the payment link in the confirmation email, or point the thank-you screen straight at your checkout.
Build your own in about a minute
The button below opens the form generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make my conference registration formOther form examples
Gym membership form
Everything a gym needs to sign somebody up in one sitting, including the health screening and the waiver signature that usually sends people back to paper.
Rental application form
One application per adult, covering everything an agent assesses. It is long because a short rental application just becomes three emails afterwards.
Job application form
A job application that collects what actually decides a shortlist, and deliberately leaves out the questions that create legal risk.
New to the builder? Start withCreate a form from scratch with AI, thencontrol who can fill it in.