Event registration form questions worth asking (and the ones to drop)

Start with the questions that let you contact the person and count heads. That is a name, an email address, and the ticket type, session or date they want. For paid events add the payment step. For in-person events that serve food, add one dietary question. That core runs to four or five questions, and for a free meetup it can be the whole form.

Name the email field for its purpose ("Where should we send your ticket?") so people type an address they actually read. Ask for a phone number only if you will text people on the day, and say so next to the field. If a company is booking several places, ask for one booker's details and then a name and email per attendee, rather than making each person fill in the full form.

Close the form automatically when capacity is reached. A capacity cap set a few places below the real room limit, plus a closed message that links to a waitlist, saves you from writing apology emails.

Ask one gate question first: "Do you have any dietary requirements?" with Yes and No. Only a Yes opens the detail question. Most attendees see one click instead of fifteen options, and your caterer gets a cleaner list.

For the detail question, use a multiple-choice list with an "Other" text box. Cover the common diets (vegetarian, vegan, halal, kosher, gluten-free) and then the allergens. Allergen lists differ by country. The US FDA names nine major allergens: milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans and sesame, the last added from 1 January 2023. UK food businesses work with 14, which adds celery, cereals containing gluten, lupin, molluscs, mustard and sulphites. Use the list your caterer works from, so the two match.

Add one more conditional question for severe allergies: "Is this a severe allergy that needs special handling (for example, a separate kitchen area)?" That is the answer your caterer most needs to see flagged, and it is easy to lose in a comma-separated list.

Ask what people need, not what their condition is. The ADA National Network's guide to accessible events suggests exactly this shape of question: which of the following will you need to take part, followed by options such as large print or electronic materials, a sign language interpreter, real-time captioning (CART), an assistive listening device, step-free seating, space for a service animal or a personal assistant, plus an "Other" box. Nobody has to disclose a diagnosis to get a ramp.

Ask early, and put a date on it: "Tell us by [date] so we can book an interpreter." Interpreters and captioners are booked in advance. Always give a contact for people who would rather explain by email or phone than in a form field.

Under Title III, businesses and nonprofits that run events open to the public must communicate effectively with disabled attendees, using auxiliary aids such as interpreters, real-time captioning, large print or Braille. The Justice Department encourages them to consult the person about which aid works. The federal regulation at 28 CFR 36.301(c) also says a public accommodation may not add a surcharge to cover those measures, so there is no extra fee for an interpreter. This is a factual summary, not legal advice. Talk to a lawyer about your own event.

In Great Britain, event organisers providing a service must make reasonable adjustments for disabled people, and the Equality and Human Rights Commission's code of practice describes that duty as anticipatory. You should think about likely barriers before anyone asks, rather than waiting for a registration to arrive. Section 20(7) of the Act also stops a service provider charging the disabled person for the cost of an adjustment. An accessibility question on the form helps you meet the duty, but it does not replace planning step-free access and hearing loops in advance.

Article 5 of the GDPR requires personal data to be "adequate, relevant and limited to what is necessary" for the purpose you collect it for, and kept no longer than needed. Even outside the EU and UK, that is a good editing rule. Each extra field costs completion time and becomes something you have to protect.

Health details and religious beliefs are special category data under Article 9. A halal or kosher meal choice can reveal religion, and an allergy or access need is health information. So make these questions optional, say why you are asking and who will see the answers (the caterer, the venue), limit access to the people who need them, and delete them after the event. Under GDPR, explicit consent is one of the lawful routes for this kind of data. Confirm your basis with whoever handles data protection in your organisation.

Zunoform handles the form side of this on every plan: conditional logic for the gate questions, branching by ticket type, a scheduler question for timed sessions, hidden fields that record UTM sources so you can drop "how did you hear about us", and closing the form automatically on a date or at a response count with a message that links to your waitlist. Payments through your own Stripe or PayPal account need Pro ($14.99 a month), as do confirmation emails sent through Zunoform's mailer. On Free, those emails go out only through your own SMTP server.

It is not an event platform. There is no ticket scanning, badge printing or check-in app, and no event discovery. For a large public ticketed event, a dedicated platform such as Eventbrite does more. If you are comparing tools rather than questions, see our separate guide to event registration form builders. And if you expect more than 500 registrations a month and want to pay nothing, Google Forms and Tally have no response cap on their free plans.