Zero Impulse
Insights

Ideas for your next move

Digital systems & AI

What your event registration system must do before ticket sales open

Build an event registration brief covering tickets, payments, attendee data, confirmations, check-in, refunds, access and reporting.

Delegates listening attentively during a conference
Delegates listening attentively during a conference · Stock photograph: Wiseboy Wissebo / Pexels.

The registration desk is a poor place to discover that a company booking cannot be split between ten delegates, or that a paid ticket has no matching confirmation. These are requirements to settle before tickets go on sale.

Walk through the event from the buyer's first visit to the final attendance report. A workshop may need a modest setup; a conference with sponsors, paid tickets and several sessions needs more coordination. This checklist will help you brief either system without paying for features you will never use.

Separate the buyer from the attendee

Sometimes the person paying is not the person attending. An administrator may register colleagues, a sponsor may receive allocated passes or a parent may complete a booking. Decide which details belong to the order and which belong to each attendee.

For group bookings, specify how names are supplied later, how substitutions work and who receives receipts and joining instructions. Test a booking with several people. One payment should not accidentally create one admission pass when the buyer purchased five.

Write clear ticket and access rules

List ticket types, capacities, availability periods and any eligibility conditions. Decide whether a ticket grants access to the whole event, particular days or selected sessions. Make inclusions visible before payment so delegates do not discover restrictions at check-in.

Define the process for complimentary passes, discounts and exhausted allocations. Assign someone to approve exceptions. Avoid sharing a permanent discount code widely if its intended use is limited to a particular group. The system should make exceptions traceable.

Design payment confirmation and reconciliation

Payment methods must fit the audience, but the important operational question is how a successful payment becomes a confirmed booking. Agree how pending, failed, duplicate and manually verified transactions are handled. A screenshot from a buyer should not be your only reconciliation record.

Identify the order reference that connects the booking to the payment record. Test the process from the buyer's device through to the finance team's report. Confirm fees, settlement arrangements and support responsibilities with the chosen payment provider before launch.

Collect only information the event needs

Every field creates work for the attendee and a responsibility for the organiser. Ask why you need each item, who will use it and how long it will be retained. Dietary or accessibility requests may need a restricted handling process because the information can be sensitive.

Explain the purpose of data collection and separate event administration from optional future marketing. Do not make a general promotional opt-in look like a requirement for receiving essential event updates. Review the ODPC's data protection guidance and obtain qualified advice where the event's processing needs it.

Prepare useful confirmations and updates

A confirmation should state the event, ticket type, date, venue or joining method, booking reference and next step. Tell the attendee how to correct a mistake and where to get help. If a QR code is required, explain whether a phone display is acceptable.

Schedule joining instructions and material changes as operational messages. Check that staff can contact the right attendees without exporting the entire database into an uncontrolled mailing list. Test delivery to several common email services and check the mobile view.

Plan the entrance as carefully as the form

Decide how staff validate a pass, prevent duplicate admission and handle someone whose name is missing. Check the equipment, charging, connectivity and staff permissions. Prepare a controlled fallback attendance list and a reconciliation process if the live connection fails.

Rehearse with ordinary front-desk staff using realistic examples. Include a transferred ticket, a spelling error, an unpaid booking and a delegate who cannot find their confirmation. The system should support a calm resolution rather than require a developer at the door.

Agree changes, refunds and reporting

Publish the event's cancellation and transfer terms before purchase, then configure a process that can apply them consistently. Name who authorises changes and how the attendee is notified. Ensure refunded or cancelled passes cannot remain valid by accident.

Define the reports you need: bookings, confirmed payments, attendance, no-shows and ticket-type totals. Keep payment status separate from check-in status. A count of form submissions is not the same as a count of paid attendees.

Run an acceptance rehearsal

Before advertising the registration link, complete an end-to-end test covering purchase, confirmation, support, check-in and reporting. Record the expected result and the person approving each stage. Keep a short launch checklist and an escalation contact for event day.

Plan your registration system with Zero Impulse. We can turn your attendee journey into a practical brief and build the registration, ticketing and check-in tools that support it.

More useful reading

Explore Digital systems & AI