Designing conference registration

Registration is the first part of the event

For most attendees, registration is their first real experience of your conference. If it is confusing, slow or full of surprises at the payment step, they arrive already a little sceptical. If it is clear and quick, and the confirmation tells them exactly what happens next, they arrive ready to engage.

Good registration design is mostly about decisions you make before you open a form builder: what people can buy, how sessions fill, what you need to know about each attendee and why. The form itself is the easy part.

Build ticket classes around access

A common mistake is creating a separate ticket for every combination of person and access: "speaker two-day", "student one-day with workshop", and so on. The list grows quickly and becomes impossible to change.

Instead, separate two ideas. The first is who someone is: attendee, student, speaker, sponsor guest, staff. The second is what they can access: the full conference, a single day, the workshop day, the evening reception, the online stream. Each ticket class combines one of each, and you can add or remove access items without rebuilding everything.

• Full conference pass, in person
• Single-day pass, with the day chosen at registration
• Online pass with live stream and replays
• Workshop add-on, limited by room capacity
• Complimentary passes for speakers and sponsor guests
• Concession or student pass, with any eligibility check stated up front

Price clearly, including the fees

Attendees should be able to see the full price before they start entering details. If a service fee, a payment fee or a tax will be added, show it on the ticket selection page or at least before the payment step, itemised. People rarely object to a fee they were told about; they object strongly to one that appears at the end.

Plan your pricing windows in advance and publish their dates. An early rate that ends on a stated date is fair and creates a natural moment to register. A price that changes without notice, or an "only a few left" message that is not true, damages trust quickly and is not worth the short-term bump.

Session capacity and waitlists

Multi-track conferences often have popular sessions in small rooms. If you let attendees choose sessions at registration, enforce room capacity, because a workshop with forty registrations and twenty-five chairs is a poor experience for everyone in it.

Run a waitlist for full sessions and decide in advance how it works. When a place opens, is it offered to the next person for a limited time, or assigned automatically? Tell people how long they have to accept an offered place and what happens if they do not. Release unconfirmed places promptly, especially in the final days, when plans change most.

Consider a worked example. A workshop room holds 30. You open registrations for 30 and close the session. Over the next month, four attendees switch to another session. Without a waitlist, those four seats sit empty on the day while people who wanted them chose something else. With one, they go to the next four people automatically, with an email asking each to confirm.

Every limited session needs three things decided before registration opens: its real capacity, what happens when it fills, and how freed places are offered.

Ask only what you will use

Registration forms tend to grow by committee. Marketing wants job titles, sponsors want company size, catering wants dietary needs, and someone adds a question about how attendees heard about the event. Each question reduces completion a little.

Ask what you need to deliver the event first: name, contact details, the ticket and sessions chosen, dietary requirements for any meals, and access needs. Then add business questions only if someone will act on the answers. Use conditional questions so that a speaker or sponsor sees their own extra fields and ordinary attendees do not.

Group registrations

Companies and universities often register several people at once. Let a group booker buy multiple passes in one transaction, but collect each attendee’s own details, ideally by inviting them to complete their registration themselves. A badge printed with "Guest 3 of Acme" helps nobody, and dietary and access needs belong to individuals, not to the booker.

Decide whether group bookers can reassign passes and until when. Name changes are common as travel budgets shift, and a clear policy saves a stream of emails.

Refunds, transfers and changes

Publish your refund and transfer policy on the registration page and in the confirmation email. State the dates plainly: full refund until a certain date, transfer to a colleague allowed until another, no refunds after a final date. Tell attendees how to request a change and how long it takes.

When a pass is refunded or transferred, make sure everything attached to it follows: session places released, badge reissued under the new name, any dietary or access request moved to the new person or removed.

Accessibility at registration

Ask every attendee what would help them take part, in terms of what they need: step-free access, captions, a sign language interpreter, a seat near the front, a quiet room, an accompanying carer. Make it easy to say yes to a carer pass without a separate process.

Then route the answers to the people who arrange rooms, sessions and catering, and confirm back to the attendee what has been arranged. An access request that disappears into a spreadsheet is worse than not asking.

Consent: operations, marketing and sponsors

Attendees agree to different things for different purposes. Operational messages, such as their ticket, room changes and safety notices, go to everyone who registers. Marketing about future events is a separate choice. Sharing details with sponsors or exhibitors, for example when a badge is scanned at a booth, is another separate choice.

Keep these choices distinct on the form, unticked by default where the law requires it, and record them per attendee. When a sponsor asks for "the attendee list", the honest answer is the list of attendees who agreed to share their details with sponsors, and no more.

Badges and confirmation

The confirmation email is the most-read message you will send. Include the pass or QR code, the dates and venue with a map, the sessions chosen, what to bring, how to change the registration, and who to contact. For online passes, include how and when access will be sent.

Badges should show what staff and other attendees need to see: name, organisation if the attendee wishes, and any access colour or ribbon that controls entry to areas. Keep personal details such as email addresses off the printed badge and inside the code, which only authorised scanners can read.

1. Send the confirmation with the pass the moment payment is confirmed.
2. Send a reminder a week before with travel and venue details.
3. Send the final details two or three days out, including check-in times.
4. Print or prepare badges from the final list, not an earlier export.
5. Test the full journey with real test registrations of every ticket type.

Hybrid and online attendees

If part of your audience joins online, design for them deliberately. Show session times in each attendee’s own time zone, make it clear which sessions are streamed and which are in-room only, and explain how replays work and for how long they are available.

An online pass should come with its own confirmation and reminder flow, timed to the attendee’s time zone rather than the venue’s. Attergo handles ticket classes, session capacity, waitlists and online passes from one inventory, but the design questions above are the work that matters, whatever system you choose.