Registration form: fields to keep, fields to cut, and what breaks sign-ups

A registration form is the narrowest point of whatever you are running. Everyone who wants to attend your event, join your course or use your service has to pass through it, and every field you add loses a few of them — not because the field is hard, but because each one is another moment to reconsider.

So the design question is not "what would be useful to know". It is "what do we genuinely need before they arrive, and what can we ask afterwards".

The minimum registration form

• Name — one field, not two. Splitting first and last breaks for a large share of the world's names and gains you almost nothing.
• Email — the only channel you truly need. Validate the format, and confirm it back on the success screen so typos surface immediately.
• The thing being registered for, if there is a choice: session, date, ticket type.
• Anything legally required — consent for the specific processing you will do, stated plainly rather than buried in a checkbox that also accepts marketing.

That is usually the whole list. Phone number, company, job title, dietary requirements and t-shirt size can be collected in the confirmation email, where the person has already committed and is far more willing to answer.

The most expensive optional field is the phone number. People read it as "someone will call me", and a meaningful share abandon rather than hand it over. If you do need it, say why, in one short line next to the field.

What quietly breaks registrations

• Required fields that are not marked required, so the form rejects a submission the person thought was complete.
• Validation that fires on every keystroke and shows an error before the field is finished.
• Losing entered data on a validation error. Nothing kills a registration faster than retyping.
• No confirmation screen or email, so people register twice "just in case".
• A form that is unusable on a phone, which is where most registrations now happen.
• A deadline nobody mentioned until the form was closed.

Building one that holds up

1. Start from a template rather than a blank page, then delete every field you cannot justify by naming what you will do with the answer.
2. Group into short sections with a progress indicator if you genuinely need more than one screen.
3. Use branching so a question only appears when it applies — dietary requirements after choosing the dinner session, not before.
4. Set a capacity limit or a closing date on the form itself, so it stops accepting when the event is full instead of embarrassing you later.
5. Send a confirmation the moment it is submitted, with the details they will need on the day.
6. Test it on your own phone, on a bad connection, before sharing the link.

In Ettex Forms that maps directly onto the builder: drag-and-drop question blocks, choice, scale, date and file-upload types, logic and branching, multi-step sections with progress, validation for required fields and formats, quotas and limits to close a form by date or response count, custom themes to match your brand, and publishing either as a link or embedded on your site. Submissions arrive in a searchable response inbox with a live summary and export to CSV or XLS — which is the attendee list you will actually work from on the day. Registration and feedback templates ship with the product.

After the form

Registration data ages fast. Export the list the morning of the event rather than the week before, keep one canonical copy rather than a spreadsheet per organiser, and delete what you no longer need — a registration list is personal data, and holding it indefinitely is a liability rather than an asset.

A good registration form is almost boring: two or three fields, a clear confirmation, and a limit that closes it on time. Every clever addition beyond that is paid for in people who did not finish.