How to create an online registration form
A registration form looks trivial — name, email, done. Then comes the first event where half the people skip the phone number, three register twice, and the organiser cannot tell from the spreadsheet who paid. This walkthrough is about avoiding that.
Step by step
- 1
Start with the purpose, not the fields
Write one sentence about what you will do with the data. “I need an attendee list for check-in and emails to send the programme.” Every field is then measured against that sentence.
- 2
Add only necessary fields
Name and email almost always. Phone only if you genuinely call. Address only if you ship something. Anything you can collect later does not belong in registration.
- 3
Split attendee categories
If you have junior/senior, member/non-member or company/individual, use conditional logic. Each category then sees only its own follow-up questions.
- 4
Set the capacity
A response maximum closes registration once full. A per-respondent limit prevents duplicate sign-ups.
- 5
Schedule opening and closing
Registration opens at an exact time and closes itself after the deadline — no babysitting.
- 6
Write the confirmation email
A recap of what they signed up for, when and where to show up, and what happens next. If you collect a fee by transfer, the payment details belong here.
Fields that work well
- Full name — one field, not two; people split their names differently.
- Email — the only reliable channel for confirmations and changes.
- Category / attendance variant — it drives the rest of the form.
- A free-text note — one open field saves dozens of “can I arrive an hour earlier?” emails.
- A processing consent, if the registration is not performance of a contract.
The most common mistakes
Too many fields up front. A full address and company ID on a Saturday workshop sign-up delights nobody and hurts completion.
Required fields that need not be. Every required field is a point where registration can end.
Missing confirmation. If someone gets no email, within two days they will ask whether the sign-up went through — extra work for you.
Collecting data “just in case”. What you never collect, you never have to protect or delete.
FAQ
How many fields should a registration form have?
As few as the purpose requires. A typical event fits in five to seven fields; the rest can be collected later.
How do I prevent duplicate sign-ups?
With a per-respondent response limit and duplicate detection.
Do I need a processing consent?
Not always — if registration is performance of a contract (a paid event), the contract is the legal basis. Consent is typically needed for marketing emails.
Related
Try Gatherino for free
Free plan: 3 forms and 100 responses a month. No credit card, EU-hosted data.
Get started free →