Event registration form: which questions to ask and which to avoid

Every field has a cost, even when it looks harmless

The registration form is where interest in an event turns into attendance. The person has read the programme, decided to come and opened the form. From that moment, every question asks something of them: time, attention, sometimes a document to look for or information they do not have to hand. If the requests are too many or unclear, the temptation to postpone is strong, and people who postpone often do not come back.

The opposite problem is less visible but just as real. An event registration form that is too bare gets everyone signed up quickly, and then the secretariat spends the following weeks emailing people to ask for train times, dietary requirements or a companion's name. Every missing piece of data becomes a reminder, a reply to transcribe, information that reaches the caterer or the hotel too late.

This is why the right question when designing a form is not "what might we need?" but "what will we do with this answer, and who will use it?". If a question has no precise use, it can probably go. If an answer is needed by a supplier, a department or an organisational step, ask for it straight away, as simply as possible.

Which data you really need: start from how it will be used

A practical way to build the form is to start from the end. Picture the event already over and ask yourself which information was needed to make it work: who had to get in, who stayed at the hotel, who attended the dinner, who needed assistance. Each of these needs corresponds to a group of questions.

Some data is needed almost always: first and last name, a reliable email address for communications, and the company or organisation when the event is professional. Then there is data tied to the event format. A half-day conference in town needs little more than the essentials; a three-day congress with overnight stays, dinners and workshops needs information on arrivals, departures, rooms and chosen activities.

It also matters how the person reaches the form. If guests are invited from an existing list, much of their data is already known. In webRay®, the guest management platform by I.T.S. Planet, guest records can be imported from Excel and each invitee receives a personal link: they open the event website, check the data the secretariat already holds and fill in only what is missing. Asking again for information the organisation already has is one of the quickest ways to make the form feel like a pointless formality.

When registration is open to the public, the form is the first contact with the person and has to collect more. The same rule still applies: ask for what you need, when you need it. Data that is only useful close to the event, such as arrival time, can also be collected in a second step, as long as that step is planned from the start.

The questions worth asking, and why

Some questions are often forgotten and then recovered with difficulty. They are the ones linked to logistics and hospitality, which the person filling in the form does not think about until they become a problem in the room or at the hotel.

Dietary requirements are the classic example: asking for them in the form, with clear options and a space for notes, avoids handling requests the day before the dinner. The same goes for assistance needs, which let you arrange access, seating and support in advance. If the event has parallel sessions or limited-capacity workshops, the choice of activities belongs in the form, so places are counted in real time rather than on a separate sheet. Events with hospitality need travel information and accommodation preferences, while companion details should only be asked of people who say they are bringing one.

The table sums up the most useful questions and when they make sense.

If the event includes fees or paid services, such as accommodation or a gala dinner, the purchase can also happen within the same flow. We covered this in Paid registrations: how to collect event fees and services without chasing bank transfers.

Questions to avoid (or to rewrite)

The questions to remove are not only the useless ones. Often they are legitimate questions asked in the wrong way or at the wrong time.

The first category is data collected "just in case": a fax number, a second email address, a date of birth when it serves no purpose. Every piece of personal data collected without a precise purpose is also data you have to protect and justify. The second category concerns mandatory fields: making a field mandatory when it is not essential forces people to invent an answer just to move on, and invented data is worse than missing data.

Then there are ambiguous questions. "Will you attend the dinner?" may mean the gala dinner, the informal one or both; "Arrival" does not say whether you mean the date, the time or the means of transport. A slightly longer question that cannot be misunderstood is better. Finally, free text where a choice would work better: if you ask for "dietary requirements" in an open field, you will get answers that are hard to count. A few predefined options, with space for notes, make the data usable for whoever receives it.

Many of these problems arise when the form lives apart from the rest of the event management, perhaps as a generic form whose data ends up in a spreadsheet. It is one of the warning signs we described in Registrations, payments and check-in on Excel? When it is time to change.

Fields that change based on the answers

The most effective way to keep a form short without losing information is to show each person only the questions that concern them. This is the principle of conditional fields: one answer opens or closes the questions that follow.

A few examples make the idea clear. People who say they are not staying overnight do not see questions on dates and room type. Those who declare a companion see fields for that person's details appear, while everyone else moves on. Someone arriving by train can enter time and station, someone arriving by car can request parking. For the person filling it in, the form feels short and relevant; for the secretariat, the information arrives complete.

In webRay® form fields can be dynamic and conditioned by previous answers, so each guest sees only the relevant questions. Companions are linked to the main guest's record, with each person's data kept separate: this makes it possible to handle rooms, activities and check-in correctly. For international events, forms and communications can be managed in several languages, including Arabic with right-to-left display.

The form is not an isolated element: it has to sit inside a website that leads people to the registration button. We explained how to build that path in Your congress website: what it needs to get people to register.

Guests, speakers and sponsors: one form for each profile

A speaker does not have the same needs as an attendee, and a sponsor has different ones again. A speaker needs to provide information on their talk, technical requirements or a biography; a sponsor needs to list the staff at the stand; a VIP guest needs a dedicated welcome path. Asking everything of everyone produces endless forms in which each person has to work out alone which sections to skip.

The solution is to profile participants before they even fill in the form. In webRay® each person can be assigned a profile, such as guest, VIP, speaker, sponsor, exhibitor, press or staff, and each profile can see different questions, content and services. The same profiling then lets you send targeted communications and produce dedicated reports, for example the list of guests whose data is still missing.

The benefit also shows after registration. The data collected feeds logistics, communications and check-in without manual steps: lists can go straight to the goAhead check-in systems and the content reserved for each profile to the eventMe web app. Why it is worth managing registrants in a dedicated tool is explained in Event registration tool: why manage it separately. If the data also has to flow into your CRM or company management system, you will find the points to clarify in Integrating the event secretariat with business systems: how to do it well.

Consents and privacy: ask for the right things, in plain words

The form is also where consents are collected: consent to process data for registration, any consent for promotional communications, the release for photos and video. In practical terms it is best to keep them separate, with short and understandable wording, and to ask only for the consents truly linked to what you will do with the data.

Some information, such as dietary requirements or assistance needs, can be particularly sensitive. It makes sense to ask for it as optional, explain what it is for and limit its visibility to the people who actually need to use it. Privacy notices, legal bases and retention periods should be defined with your privacy advisor: the form should reflect those choices, not replace them.

How to build the registration form in 5 steps

These steps help turn the list of information you need into a form that is easy to fill in.

1. List who will use the dataInvolve the secretariat, hotel, caterer, check-in team and whoever prepares the reports, and note which information each of them needs and when.
2. Remove what has no useFor each field, ask who will use it and for what. If the answer is unclear, delete it; if the data is already known from the guest list, do not ask for it again.
3. Define profiles and conditionsDecide which profiles exist, such as guests, speakers and sponsors, and which questions appear only after certain answers, for example accommodation or a companion.
4. Write clear questionsPrefer predefined options to free text, make fields mandatory only where truly needed and keep consents separate with short wording agreed with your privacy advisor.
5. Test the form as a guestFill in the form on a phone for each profile, check that the conditions work and that the confirmation correctly summarises the choices made.

Checklist before opening registrations

Before publishing the form, check these points with the people who will handle the data.

Frequently asked questions