Event registration is a balance between what you need to run the event and what somebody will tolerate before they close the tab. The balance point moves a lot depending on the event, which is why one registration form copied between twelve events works badly for eleven of them.
Here are the twelve shapes, and the question each one cannot afford to leave out.
1. A paid conference
The longest acceptable registration form, because somebody paying several hundred to attend expects admin. Ticket type, dietary requirements, accessibility needs, badge name, sessions, and an invoice option for people expensing it.
Must not skip: accessibility requirements. Asking on the day is too late, and people will not volunteer it unprompted.
2. A free local meetup
Name, email, and whether they are coming. Three fields. A free meetup has a no-show rate around half whatever you register, and a longer form does not improve it.
Must not skip: a reminder the day before. It moves attendance more than anything on the form.
3. A webinar
The lowest-friction registration there is, and the highest no-show rate. Three or four fields maximum, because people are trading an email for a link and will not answer carefully.
Must not skip: one question about what they want covered. It improves the session and gives you something personal to say in the reminder email.
4. A hands-on workshop
Shorter than a conference, more substantial than a meetup. The questions that matter are about preparation rather than logistics.
Must not skip: current experience level. Two questions about what they already know will save the first half hour of the session.
5. A wedding or private celebration
Warm rather than administrative, and built for guests who are not comfortable with forms. Keep it short, make the deadline obvious, and ask about food per guest rather than per invitation.
Must not skip: dietary requirements for each named person. One household can easily have three different answers.
6. A fundraiser or charity dinner
Registration and payment in the same submission, usually with ticket tiers and an option to donate more or sponsor a table.
Must not skip: the option to give without attending. A meaningful share of people want to support you and cannot come, and most forms give them nowhere to do it.
7. A class or course with limited places
Capacity is the whole problem. Cap the form so it closes itself rather than taking a thirteenth booking for twelve places.
Must not skip: health and safety questions where the activity warrants them. These are the ones you will wish you had asked.
8. A school or community event
Usually a parent registering a child, which means two sets of details and a consent section. Make it work on a phone, because that is where it will be filled in.
Must not skip: two emergency contacts. The first is often unreachable at the exact moment they are needed.
9. A sports event or race
Waivers, categories, and a medical declaration. Longer than most registration forms and justifiably so.
Must not skip: a signature on the waiver, and an emergency contact that goes on the bib.
10. A trade show or exhibition
Two different forms wearing one name: visitors and exhibitors want completely different things. Split them rather than branching.
Must not skip: for exhibitors, the insurance certificate and power requirements. Both hold everything up if left to the final week.
11. A multi-day festival or retreat
Accommodation, travel, dietary needs, which days, and often payment in instalments. The longest form on this list.
Must not skip: save and resume. Nobody completes a form that needs travel details in one sitting.
12. A small internal meeting
Two questions: are you coming, and do you need anything. Anything longer is an imposition on colleagues who could have replied to an email.
Must not skip: nothing. This is the one case where less is unambiguously better.
A free event has a no-show rate around half whatever you register. A longer registration form does not fix that; a reminder the day before does.
What applies to all of them
Say how long the form takes. Confirm the detail back by email afterwards, with a calendar file attached so the date lands in a diary rather than an inbox. Cap the form if places are limited, so it closes itself with a message you wrote rather than overselling.
And ask about accessibility on every single one, even the short ones. It is one question, it is answered by almost nobody, and the person who needs it will remember that you asked.
The questions worth asking on every one
Whatever the event, four questions earn their place and are regularly left out.
- Accessibility requirements. One optional question. The person who needs it will remember that you asked, and arranging it a week out is trivial compared to on the day.
- Dietary requirements, if there is food. Broken out by type rather than a single free-text box, because counts are what a kitchen works from.
- An emergency contact, for anything residential, physical, or involving children.
- How they heard about it. The only reliable way to find out which of your channels actually fills a room.
Capacity, waitlists and cancellations
Most registration problems are capacity problems wearing a different hat.
Cap the form rather than counting by hand. A response limit closes it automatically with a message you wrote, which is better than discovering you are twelve over on the morning of the event.
Run the waitlist as a second form that opens when the first closes. People will give you an email to be told about a cancellation, and that list is also the best possible audience for the next event.
And ask about cancellations explicitly. A line saying "let us know if you cannot make it" with a link recovers places that would otherwise show up as empty chairs.