Event registration form: what to ask and how to build it

A good event registration form asks only what you will actually use to produce the event, shows each guest only the questions that apply to them and is clear about what happens to their data. The landing page sells the event in ten seconds (what, when, where, who it is for) and the form collects just enough for catering, transport and the door to work. Then come the emails: instant confirmation, a reminder before the event and a personal link for anyone with details missing.

It looks like admin, but almost everything else comes out of it: catering numbers, the allergy list, the coach, the rooming list and the door. Get the form wrong and you pay for it in every one of those lists.

Before you open the editor: three questions for the client

1. Open or invitation only? If it is by invitation, each guest should have their own link or at least some validation (company email, a code). If it is open, you need a cap and a waitlist from minute one.
2. Which decisions depend on the answers? Meal, coach, T-shirt size, afternoon activity, room. Each decision is a question. Anything that changes no decision goes.
3. Who will see the answers, and when? The client will want numbers. Decide now what they see (sign-ups, places left, specific answers) and what they do not (everyone’s email, internal notes).

What to ask and what to skip

What almost always goes in

Block	Questions	Why
Identity	First name, last name, email, company, job title	Badges, door, communication
Attendance	Are you coming? Yes / No	A real headcount; the no’s are information too
Food	Meal choice, allergies and intolerances	Catering and the venue list
Logistics	Transport, arrival time, plus-one	Coach, welcome desk, capacity
Activities	Workshop, tour or capped activity	Per-activity capacity
Consent	Privacy and image, separately	GDPR and use of photos

What to leave out (or ask later)

• ID or passport numbers for a dinner. If there is no travel, hotel or access control that requires it, do not ask.
• Date of birth just in case. Only for flights, hotels or an activity with an age limit.
• Mandatory phone number when nobody is going to call.
• T-shirt size when there is no T-shirt. It happens more than you would think: someone duplicates last year’s form.
• Health data beyond allergies and diets. If you really need it (a mountain activity, say), ask only the people doing that activity and explain why.

Our rule of thumb: every extra question lowers your response rate and raises your responsibility for that data. Travel and check-in details belong in a second form for confirmed guests only.

Conditional logic: everyone sees only what applies

Conditional logic shows a question only when an earlier answer calls for it. Examples we use at almost every event:

• Not attending ends the form there. No meal, no coach.
• Bringing a plus-one reveals the guest’s name and meal choice.
• Coach reveals the pick-up point. Making my own way: nothing.
• I have allergies opens the text field. Otherwise, do not make them read it.
• Signing up for the afternoon activity reveals its own questions (size, level, footwear).

Watch out for two traps: chained conditions nobody tests (run the whole form with every combination before going live) and hidden required questions that block submission without the guest knowing why.

In Forms we start from MICE templates (conference, incentive trip, gala, kick-off, team building or RSVP) that already include conditional questions, capacity per activity, coach, sizes and dietary needs. You adjust them, but you do not start from a blank page.

Capacity, caps and waitlist

There are three kinds of limit and it pays to keep them apart:

1. Event capacity. The total the venue holds or the client pays for.
2. Per-activity places. Cooking workshop for 20, tour for 30. Someone can fit in the event and not in the workshop.
3. Places per guest type, when the client splits them (for example 50 for clients and 30 for internal staff).

Example: a gala dinner for 200 with two pre-dinner activities, a wine tasting (40 places) and a boat trip (60). Open registration without per-activity caps and two hours later you have 90 people in the tasting.

The waitlist is not decoration. Once a cap is reached, late sign-ups wait and, if someone cancels or you remove them, the next person moves up. Agree with the client whether freed places are assigned automatically or reviewed first (with VIP guests, review them).

Log the people who tell you they are not coming, too. A recorded “not attending” takes no place and gets no emails, but it stops you chasing them and gives you a true count of replies.

The landing page: ten seconds to make the case

• What it is and who it is for, in one sentence.
• Date, time and place, with the address and how to get there.
• A short programme (three or four blocks, not the whole run of show).
• Registration deadline, visible.
• The button, near the top, not three screens down.

In the client’s brand: their cover image, colours and fonts. A link carrying the client and event name builds more trust than a generic one, and if the client wants it on their own site, embed it there. Forms offers a classic layout or a step-by-step one; step by step works better on mobile when there are lots of questions.

Show the landing page to the client before it goes live. A review link where they can comment saves you the chain of screenshots with red arrows on WhatsApp.

GDPR and image rights

This is not legal advice, but these are the basics we see fail most often:

• Who is who. Usually the client is the data controller (the guests and the event are theirs) and you, agency or planner, are the data processor: you handle the data on their behalf. That is signed in a data processing agreement.
• Clear information in the form: who processes the data, why, for how long and how to exercise rights. A short notice plus a link to the full policy is standard.
• Separate boxes: one for privacy, another for image rights (photos and video, and where they will be published). Neither ticked by default.
• Sensitive data: allergies and diets are health data. Ask for the minimum, share them only with those who need them (catering, venue) and in a list that carries nothing else.
• Deletion: agree with the client when responses are deleted after the event.

Forms includes privacy and image consent boxes, a data processing agreement your client signs and a dietary and allergen list for the venue as PDF or CSV, with totals at the top. If you are unsure about your own case, ask your adviser.

Several languages without duplicate forms

For conferences and international events, one form per language is the perfect recipe for two lists that never match. The right approach is one form with several language versions and every answer in the same list.

Forms publishes in Spanish, English, Catalan, French, Portuguese, Italian and German; the AI translates missing text and you review it. Check the legal wording, meal names and dates in particular, which is where machine translation trips up.

Emails: confirmation, reminder and personal link

Confirmation. Sent automatically on submission, with a summary of their answers, date, time and place, directions and how to change their details. If there is QR check-in, the QR goes here.

Reminder. A few days before the event, with the practical bits: arrival time, access, dress code, parking, who to call if something goes wrong. If the programme changes, this is the email.

Personal link to complete details. When something is missing (meal, flight number, size), instead of asking people to fill everything in again, each person gets their own link with their answers already there and only completes what is missing.

Forms shows the status of every email: delivered, opened, visited, replied. That column is gold for the next section.

Chasing the people who never reply

There is always a chunk of the list that leaves it to the last day. Our system:

1. Segment by email status. “Never arrived” (check the address or spam) is different from “opened but did not visit” (needs a nudge) or “visited but did not finish” (something in the form stopped them).
2. First nudge halfway through, short, with their personal link and the deadline.
3. Second nudge a few days before closing, with a concrete reason: places running out, the coach being confirmed, catering needing numbers.
4. Last resort, the client. For the guests who matter, a call or message from their contact at the client beats any email.
5. Record the no’s. Whoever says they are not coming drops out of the chase.

And do not send the same reminder to the whole list: someone already registered who gets “don’t forget to sign up” assumes it failed and registers twice.

Common mistakes

• Opening registration without per-activity caps.
• Asking everyone for ID and date of birth “in case there is a hotel”.
• An image consent box glued to the privacy box, or pre-ticked.
• One form per language and two spreadsheets that never match.
• Sending catering the allergy list with everyone’s email and phone number.
• Never testing the conditional logic on a phone.
• Giving the client the full spreadsheet “so they can see how it is going” instead of a live tracking view with the figures they need.

What I would check tomorrow before going live

• Every question changes a production decision.
• Logic tested with every combination, on phone and desktop.
• Capacity, per-activity places and waitlist set up.
• Privacy and image consent in separate, unticked boxes.
• Data processing agreement signed with the client.
• Text reviewed in every language, especially the legal part.
• Confirmation email with summary, venue, directions and QR if needed.
• Reminder date and registration deadline in the calendar.
• Client has reviewed the landing page and knows what their tracking view shows.

To build it this way without wrestling spreadsheets, start from the Forms template closest to your event and trim it down; it is faster than building from scratch. And if there is a hotel involved, carry on with the rooming list guide.