How to create an event registration form
The registration form is your event's first impression and also where you lose the most people. A long form erodes trust and gets abandoned; an incomplete one creates work on the day. This article covers the balance between the two, and the privacy limits worth respecting.
Which fields to ask for
Every extra field lowers completion somewhat. So before adding one, answer a single question: "what will I do with this?" If the answer does not attach to a concrete action, the field does not belong on the form.
Needed at almost every event
- Full name — for matching people at the door and for certificates.
- Email — confirmations, reminders, QR codes and certificates all go here. It is the one truly indispensable field.
- Phone — only if last-minute changes are plausible. A cancellation or time change announced by email gets noticed too late.
Depending on the event
- Organisation / school / department — if you are printing badges or reporting on attendee profile.
- Session or workshop choice — where parallel tracks exist, this is how you manage their capacity.
- Dietary and accessibility needs — ask if you are catering; not asking means someone arrives to find nothing they can eat.
What not to ask
The most common mistake is collecting data "in case we need it later". It lowers completion and creates an obligation, because every piece of personal data you hold is data you must protect.
- National ID numbers — unless a legal requirement genuinely applies. For most events this is an unnecessary and high-risk field.
- Date of birth — pointless unless you actually enforce an age limit.
- Postal address — meaningless unless you are physically shipping something.
- Free-text "what are your expectations?" — if you do not intend to read them, this wastes the attendee's time and fills your records. Move that question to the post-event survey.
The rule: any field you collect but never use is pure loss. It lowers sign-ups, makes you responsible for the data, and feeds into no decision.
Design that lifts completion
Two forms asking for the same fields can complete at noticeably different rates. The difference usually comes from three details:
One screen, short form
Long forms that require scrolling get abandoned. If you cannot cut fields, at least put the required ones first and mark optional ones clearly.
Clear error messages
A form that rejects a phone number without saying why loses the person. Errors must name the field and the reason.
Make it easy for returning attendees
Someone who registered before should not retype everything. One-click registration from a saved profile measurably increases repeat attendance.
Capacity and waitlists
Nearly every organisation tracking capacity by hand eventually exceeds it — and exceeded capacity cannot be undone. Turning someone away at the door is lasting reputational damage.
- Define capacity in the system. When it fills, the form should close by itself rather than needing a manual "registrations closed" note.
- Keep a waitlist open. Cancellations happen at every event; without a waitlist you cannot fill the seat that opens up.
- Make cancelling easy. If telling you they cannot come is hard, people simply do not tell you — and you plan for them anyway. Easy cancellation means accurate numbers.
- Track parallel sessions separately. A single workshop can fill long before overall capacity does.
What should happen after sign-up
Instant confirmation
A confirmation email within seconds removes the "did it go through?" question and the message traffic it would have created.
Add to calendar
Include an add-to-calendar link in the confirmation. An event that never reaches the calendar gets forgotten.
Entry method
If you use QR check-in, the code belongs in this email with a clear "show this at the door". An unclear entry method means a flood of questions on the morning.
Reminders
Agenda and location 2-3 days out, one line on the morning. More than that backfires.
Privacy: limits when collecting data
Event registration is one of the most common forms of personal data processing, and most organisations do it without noticing. This is a practical summary rather than legal advice:
- Collect only for a purpose. Ask only for what running the event requires. "It might be useful later" is not a purpose.
- Say what you collect it for. Include a short privacy notice on the form and a link to your privacy policy.
- Separate marketing consent. Registering for an event is not agreement to receive future announcements. Newsletter consent belongs in its own unticked box.
- Announce photography in advance. If you will be filming, say so at registration; mentioning it at the door is too late.
- Do not keep the list forever. Delete what you no longer need after the event; an attendance record and a marketing list are different things.
A practical check: for every field, ask "can I explain to the attendee in one sentence why I want this?" If you cannot, the field should come off the form.
Frequently asked questions
How many fields should a registration form have?
Three to five covers most events: name, email, phone and one or two event-specific questions. Since every extra field lowers completion, decide which decision the information feeds before adding it.
Should I ask for an ID number?
Not unless a legal requirement genuinely applies. It lowers sign-ups and is sensitive data you then have to protect. Name and email are enough for certificates.
What should happen when capacity fills?
Ideally the form closes itself and rolls over to a waitlist. Cancellations happen at every event, and without a waitlist you cannot fill the seat that opens.
Do I need consent to send attendees a newsletter?
Yes, and it must be separate from event registration. Signing up for an event does not imply agreement to future announcements; newsletter consent belongs in its own unticked box.