Event Registration Form Guide: What to Ask, What to Skip, and How to Set One Up

Updated October 2026.

An event registration form does two jobs at once. It is the last step between someone deciding to come and actually committing, and it is the source of almost every list you will use afterwards: badges, the check-in roster, catering numbers, follow-up emails and sponsor reports. Ask too little and you scramble later. Ask too much and people leave halfway through. This guide covers what to ask, what to skip, and how to set a form up and test it before you open registration.

What an event registration form has to do

Before you add a single field, write down what you will do with the answers. Every question should map to a decision or a task. If you can't name the task, the question probably doesn't belong.

For most events, the form needs to:

• Identify the person well enough to check them in and contact them.
• Tell you how many people to plan for, and for which parts of the event.
• Capture anything you need to keep someone safe or included: dietary needs, accessibility, emergency contacts for youth or outdoor events.
• Record consent for the communications you plan to send.
• Collect payment, or send people to where payment happens.

It is worth thinking about measurement here too. Encore's report What's shaping live experiences in 2026 found that events which measure outcomes keep 71% of their sponsors, against 52% for those that don't. A single well-chosen question, such as job role or what the attendee hopes to get from the event, can give you a baseline to report against later.

The fields worth asking for

Here is a starting point. Adjust it to your event, but keep the required column short.

Fields that depend on the event

• Campus events: student ID or department, if you need to verify eligibility.
• Association meetings: membership number, if members pay a different rate.
• Multi-day conferences: which days the person is attending, so your daily headcounts are real.
• Workshops with limited seats: which session they want, so you can cap numbers.
• Youth or outdoor events: an emergency contact.

One open question, at most

A free-text question such as "What do you most want to learn?" can shape your agenda or your speaker briefings. One is useful. Three is a survey, and people will skip it or abandon the form.

What to skip

Every extra field costs you some sign-ups. These are the usual offenders:

• Full postal address, unless you are shipping something.
• Date of birth, unless there is a real age restriction. If there is, ask "Are you 18 or over?" instead.
• Gender, unless it drives a real decision such as room allocation. If you ask, make it optional and include a "prefer not to say" option.
• Company size, budget or buying timeline on a free community event. It reads like a sales form.
• Questions you can ask later. Session choices for a three-day conference can wait for a follow-up email closer to the date.
• Duplicate confirmation fields such as "confirm email", which mostly add friction on phones.

A simple test: if nobody on your team can name who will read the answers to a question, remove it.

Privacy and consent

Registration data is personal data, and your form is where you set expectations about it. Keep three things in place:

• Say what you will use the data for, next to the submit button, with a link to your privacy policy.
• Separate logistics from marketing. Event confirmations and day-of updates are part of running the event. Newsletters and partner offers need their own consent, and the box should start unticked.
• Be clear about sharing. If sponsors will receive attendee details, say so on the form, not after the event.

Rules differ by audience. US organizers often deal with state privacy laws, organizers in India with the Digital Personal Data Protection Act, and anyone registering people from Europe with GDPR. Our guide to GDPR for event organizers covers the consent side in more detail. If in doubt, collect less.

Paid events: where the form meets the ticket

For a paid event, the registration form and the checkout are two halves of the same step. Keep the questions before payment to the minimum, because every screen between "I want a ticket" and "paid" loses people. Anything that is nice to know can be asked on the confirmation page or in a follow-up email.

Decide early where the money goes. On WebMobi, WebMobi takes 0% of ticket revenue on every plan, including Free, and is never in the money path: attendees pay you, on your own payment provider. If you already sell tickets elsewhere, you can paste that ticketing link and the event button sends people there. In India, you can connect your own Razorpay account and take ticket money directly into it.

How to set up an event registration form on WebMobi

WebMobi includes native registration on the event page, so people register with you rather than with a third party and you keep the relationship. A typical setup looks like this:

1. Create the event. Start from the event workspace, or describe your event in a sentence or two in the chat planner on webmobi.com and save the plan as a real event and website.
2. Build the event website. The registration form lives on your own event page, alongside the agenda, speakers and sponsors.
3. Decide how people get in. For a public event, publish it. For a private one, attendees can enter an access code you send them, and events protected with a code or made private are never listed on the Discover page. Our page on private event registration explains the options.
4. Add people you already know. If you have an existing list, such as members, staff or invited guests, upload it as a spreadsheet with bulk attendee upload.
5. Leave email off while you set up. A new event sends no email until you turn it on, so nobody gets a half-finished confirmation while you are still testing.
6. Rehearse in test mode. Publish the event as Test, register yourself and a colleague, and check in. Test registrations and check-ins never count. When you are ready, go live.

Once registrations come in, the registration list shows who has signed up, and you can add people manually. Registration statuses use one consistent set of terms, so your attendee counts stay accurate. There is more on the registration side on our event registration platform page.

Test the form before you open it

Run through the form yourself, on a phone, as a first-time visitor. Check that:

• It works on a small screen without zooming or horizontal scrolling.
• Required fields are marked, and error messages say what to fix.
• The confirmation arrives, with the right date, time zone and venue.
• Anyone who uses a screen reader or keyboard only can complete it.
• The data lands where your team expects it, in the format they need for badges and catering.

Then ask someone who has never seen the event to register, and watch where they hesitate. That five-minute test catches most problems.

After launch: late sign-ups and the door

Plan for people who register late or not at all. Bizzabo's 2025 State of Events and Industry Benchmarks found that 59% of organizers reported an increase in late registrations, so keep the form open as long as your catering and capacity allow, and decide in advance when it closes.

The form also sets up check-in. In the same Bizzabo survey, 71% of attendees said ease of check-in could make or break their event experience. The cleaner your registration data, the faster the line moves. On WebMobi, registered attendees can be scanned in from any phone browser with web check-in, and offline check-in keeps scanning when the venue wifi drops, then syncs. When someone turns up who never registered, walk-in registration lets you add them at the desk and check them in in one step.

For more on reducing drop-off once the form is live, see our guide to event registration optimization.

Ready to build yours? Create an event free and set up your registration form on your own event page. The Free plan covers 50 participants a year.

About WebMobi: before 2020, WebMobi’s event apps ran more than 2,000 events for over 2,000,000 attendees — among them the Boston Marathon, the Tribeca Film Festival, the NSW Department of Education and Connect ERA. More case studies.

Related on WebMobi: ticketing with 0% fees

Frequently asked questions

How many fields should an event registration form have?

As few as will let you run the event. Name, email and ticket type cover most free events. Add fields only when you can name the task each answer feeds, such as badges, catering or sponsor reporting.

Should phone number be required?

Usually not. Make it optional unless you genuinely need to reach people on the day, for example for outdoor events, travel changes or audiences that rely on messaging more than email.

Can I collect registrations if I sell tickets on another platform?

Yes. On WebMobi you can paste your existing ticketing link so the event button sends people there, or use native registration on your own event page. WebMobi takes 0% of ticket revenue either way.

How do I handle people who turn up without registering?

Decide your policy before the day and brief the desk staff. On WebMobi, walk-in registration adds the person at the desk and checks them in in one step, so they still appear in your attendance records.

How can I test my form without messing up my numbers?

Publish the event in test mode on WebMobi. Test registrations and check-ins never count, and a new event sends no email until you switch it on, so you can rehearse the whole flow and then go live.