Event Registration Forms That People Actually Finish

A registration form is the narrowest point of your event. Everything you spent on marketing arrives here, and every field you add loses a few of them. The question is never "what would be nice to know" — it is "what do we need before we can take their money".

Ask three things now, the rest later

To issue a ticket you need a name, an email address and what they are buying. Everything else — dietary requirements, job title, t-shirt size, which sessions they want — can be collected in a follow-up form a week later, when they are already committed.

This single change is usually worth more than any other optimisation. A fourteen-field form does not gather more data than a four-field form plus a follow-up; it gathers less, because fewer people reach the end.

Make the required fields genuinely required

Go through your form and ask, of each field: what decision or task does this answer feed? If nobody can name one, the field is a habit. "Organisation" is useful if you segment by it; "Fax" has not fed a decision since 2004.

Use conditional questions rather than long forms

Ask the dietary question only of people who selected a ticket that includes lunch. Ask for an accessibility requirement once, plainly, with a free-text box rather than a list of checkboxes that never fits. Conditional logic keeps a form short for most people while still asking the specific question of the few who need it.

The five errors that lose registrations

• Validation that fires on every keystroke. Tell people what is wrong when they leave the field, not while they are typing.
• Losing the form on an error. If a payment fails and the form is empty when they come back, most will not retype it.
• A price that appears only at the end. Show the total as it changes.
• No mobile pass. More than half will start on a phone. Test it on one.
• No confirmation. The immediate email is not a courtesy; it is the receipt that stops the support email.

Say what happens next

One line under the submit button: what they will receive, when, and what they should do if it does not arrive. It costs nothing and removes a fifth of your inbox.

Watch where people stop

If your platform reports form completion, look at where people abandon. A drop at the payment step is a pricing or method problem — see collecting event payments. A drop in the middle is a field problem. A drop at the start is usually a price expectation set wrong by the page before.

Gathervo's form builder does conditional fields, per-ticket questions and a follow-up form without a developer. Build one free, and read ticket types and pricing for what sits behind the form.