How to Organize Conference Registration

Decide the structure before you build the form

The form is the last thing you build. First answer the questions that shape it, because they decide how many ticket types, fields and approvals you need.

Structure the tickets

A conference usually has more than one kind of attendee, and a single "ticket" rarely fits. Keep the list short and name each type by who it is for.

• Delegate ticket

  The standard attendee. Consider a discount for early registration if you want commitments early.

• Day pass or multi-day pass

  Useful when people can only come for part of the program. Eventdex's ticketing pages describe multi-day passes.

• Group registration

  A way for one person to register several colleagues and pay once. Eventdex's ticketing page lists group ticketing.

• Speaker, sponsor and exhibitor passes

  Free or complimentary types, kept separate so you can count them and give each its own form.

• Guest or add-on tickets

  Workshops, dinners or tours sold on top of the main ticket.

  Eventdex event ticketing software

Design the form and the sessions

Ask for what you will use and nothing else. Every field is a reason to leave the page. Split the form into steps, and keep payment for last.

1. 1

   Contact details

   Name, email, organization and role. Add a phone number only if you will call or text.

2. 2

   Ticket and sessions

   Let people pick sessions or tracks during registration if seats are limited. Eventdex describes session selection and personalized registration paths.

   Eventdex event registration software
3. 3

   Needs and preferences

   Dietary needs, accessibility needs and, where relevant, badge name. Say how the information is used.

4. 4

   Consent and policies

   Add a link to your terms, privacy notice and cancellation policy, and any consent your jurisdiction requires. Take legal advice on the wording.

5. 5

   Review and pay

   Show a summary before payment so people can fix mistakes, then confirm on screen and by email.

Payments, changes and refunds

Decide your rules before the first person registers, and write them where people can find them. Most registration complaints are about money and changes, not about the form.

• Payment methods

  Card payments for individuals and a route for invoices if employers pay. Eventdex says it integrates with leading payment gateways, including Stripe, Square and Authorize.net.

  Event payment processing

• Price steps

  If you use early bird prices, state the end date on the page and apply it automatically.

• Changes and transfers

  Say whether a ticket can be changed or passed to a colleague. Eventdex describes the ability to register, cancel, modify and refund attendees.

• Refund policy

  State the deadlines and what is refunded. A short, clear policy is easier to apply than a case-by-case one.

• Waitlist

  If you cap capacity, decide what happens next. Eventdex's pages mention waitlists for oversubscribed events in a single line and do not explain how they work, so confirm what you need in a demo.

Confirmations, reminders and the data you hold

Registration does not end when someone pays. The messages after it decide whether they show up, and the list you build decides how smooth the day is.

• Instant confirmation

  Send it on registration, with the details, the ticket or QR code and a way to change the booking.

• Reminders

  Before the event, send logistics: location, schedule, what to bring and how to check in.

  Event RSVP guide

• Attendee list

  Keep one list. Export it for sponsors or the venue only with the consent you collected.

• Reports

  Track registrations by ticket type and by day so you can adjust marketing or catering numbers. Eventdex describes reports on registrations and payments.

Registration on the day

Plan the desk as carefully as the form. The goal is a fast, calm first impression and a record of who is actually in the building.

BEFORE LAUNCH
[ ] Ticket types and prices entered and checked
[ ] Capacity set for the event and for each limited session
[ ] Form reviewed: only fields we will use
[ ] Terms, privacy notice and refund policy linked
[ ] Payment tested with a real transaction and refund
[ ] Confirmation email reviewed on a phone
[ ] Test registration appears in the attendee list
[ ] Group and speaker routes tested

BEFORE THE EVENT
[ ] Reminder sent with logistics and check-in instructions
[ ] Attendee list exported and checked for gaps
[ ] Badges designed; test print done
[ ] Names to be checked in on a backup list

ON THE DAY
[ ] Desk separated by surname, type or self-check-in
[ ] Walk-in route set up, with payment
[ ] Scanners and printers tested, spare supplies at the desk
[ ] Manual fallback if the network fails
[ ] Staff briefed on name changes and refunds

AFTER
[ ] No-shows and attendance counts recorded
[ ] Registration and attendance reports saved
[ ] Thank-you and survey sent