What to ask on an event registration form, and what to cut

Every field on a registration form has a cost, and the cost is paid by the people you most want at your event: the senior ones, filling it in on a phone, between meetings.

Nobody ever regrets a form that was too short. Plenty of organisers have watched a director give up on one that was too long, then had to be chased personally by the client.

The test for every field

Before a field goes on the form, answer one question: what decision does this change?

If the answer is "we might want it later", cut it. Later is not a decision. If the answer is "the caterer needs it", keep it and put it where the caterer's deadline needs it. If the answer is a shrug, you have found a field that exists because a previous form had it.

Applied honestly, this test removes about a third of most corporate registration forms.

What almost every corporate event actually needs

That is usually the whole form. Five fields, one screen, no scrolling on a phone.

The fields worth adding, when they earn it

• Dietary requirements. Only for events with a seated meal, and only in the form that the caterer's deadline actually needs. On a stand-up cocktail event it is noise.
• Session or workshop choice. Genuinely valuable, because it drives room capacity. If your sessions have real limits, set them with a waitlist behind each one rather than letting the form accept more than the room holds.
• Accessibility needs. A short, open, optional field. Always worth asking, never worth a dropdown.
• How did you hear about this. Only if someone has committed to reading the answers. In practice, almost nobody does.

The fields to cut, and where they should go instead

• Postal address. Unless you are physically posting something, delete it. If you are, collect it after registration from the people who qualify, not from everyone up front.
• Company size, industry, budget, buying timeline. This is a sales qualification form wearing a registration form's clothes. It converts worse and it annoys people who were invited by name. Ask afterwards, or ask nobody.
• Anything you already know. If the client supplied the guest list, do not make invited guests re-type their own company. Pre-fill it or drop it.
• Confirm your email address. A second field to catch a typo in the first one. Show the address back to them on the confirmation screen instead. That catches the same mistake and costs nothing to fill in.
• Free-text "any other comments". It generates work and reliably contains nothing you will act on before the event.

Two structural decisions that matter more than field count

Does registration need approval?

For restricted guest lists, yes. Someone reviews the registration and a ticket is only issued once it is approved. This is common for client events, launches with a curated room, and anything where the client's brand sits on the invitation.

Decide this before you build the form, not after. Retrofitting an approval step onto a form that has already issued tickets means re-issuing, re-explaining, and a day you will not get back.

One form, or one per audience?

If VIPs, media and general delegates need genuinely different questions, use separate forms rather than one form with conditional branches. Two short forms are easier to fill in, easier to check, and far easier to explain to the client than one clever one.

Make it work on a phone, because that is where it will be filled in

• One column. Always.
• Inputs at 16px or larger. Anything smaller and iOS zooms on focus, which feels broken even though it is not.
• The right keyboard for each field: email keyboard for email, number pad for phone.
• No date pickers for anything you could ask as a simple choice.
• Test it on a real phone, on mobile data, not on your laptop at the desk.

What happens after submit is part of the form

The confirmation is where most registrations quietly fail, because a form that submits successfully still leaves the guest with nothing if the email never lands.

• Show the confirmation on screen, not only by email. Their ticket and QR code should be visible immediately.
• Send the email as well, and expect a share of them to be eaten by corporate filters. That is a real, common failure with its own fixes.
• Send the ticket again closer to the day. A meaningful share of guests will have lost the first one.

The short version

Five fields, one screen, one column. Every additional field has to name a decision it changes. Decide approval before you build, not after. And treat the confirmation screen as part of the form, because for a guest whose corporate mail filter ate your email, it is the only part they will ever see.