Event Registration:
From Sign-Ups to Attendance

Event registration is the process of signing up for an event and providing the information needed to reserve or request a place. It can include ticket selection and payment, as shown in Eventbrite’s event setup guide, or approval before access is granted, as described in Zoom’s webinar registration documentation. The process connects the event page and registration form with confirmation, joining instructions, and attendance records.

For organizers, the practical work is deciding what admission includes, what information to collect, when a place becomes confirmed, and how to record attendance. For attendees, the essential questions are whether the booking is complete and what is needed to enter the venue or join online.

How event registration works#

Start by defining the admission process. An open registration can confirm a place immediately; an application process needs a review step. In Zoom, automatic and manual approval are separate registration settings, and manually approved registrants receive joining information after approval. Use wording on the form and confirmation that reflects the selected process.

For a process with limited capacity, distinguish a confirmed place from a waitlist entry. Eventbrite’s waitlist documentation describes a waitlist that can activate when a ticket type sells out or the event reaches capacity; a released ticket then has a deadline for claiming it. Joining that waitlist and claiming a ticket are separate steps.

Use a small set of booking labels that matches the actual workflow:

This is a suggested naming scheme, rather than a list of statuses used by every platform. Keep the labels consistent across the registration page, email, and attendee list.

Build the event page and registration form#

Explain the event before collecting details#

Eventbrite’s event creation workflow includes a title and summary, date and time, location, event overview, and an optional agenda. Use those elements to make the registration decision clear. State the subject, intended audience, format, start and end time with time zone, venue or online access arrangement, and what admission includes.

Place eligibility conditions and registration deadlines beside the booking information. For online events, state whether registration covers a live session, a recording, or both. For events with several sessions, identify which sessions each booking includes. Before publishing, check that the invitation, event page, ticket description, and confirmation use the same dates and admission terms.

Decide whether the form describes a buyer or each attendee#

Choose the unit of information collection before building the form. Eventbrite’s order form settings allow details to be collected from the ticket buyer only or from each ticket holder. With buyer-only collection, a multi-ticket order records the buyer’s name and email rather than a separate identity for every attendee. Choose per-attendee collection when named tickets or individual attendance records are needed.

Start with name, contact email, and the selected ticket or session. Add fields only when they serve a defined task, such as allocating a session or preparing requested event materials. Mark questions as required or optional. Eventbrite’s order form guide also explains that questions can appear before or after checkout, and unanswered required questions can prevent ticket access. Review that setting before treating a completed payment as the end of the attendee’s registration work.

Make the form accessible and limit personal data#

The W3C Web Accessibility Initiative’s forms tutorial recommends asking only for information needed to complete the process, labeling controls, providing instructions, and explaining errors and successful completion. Keep the form focused on those tasks. Check that fields, choices, and the submit button remain usable on a small screen and with a keyboard.

Use visible labels for each field and explain required inputs. W3C’s form instructions guidance states that placeholder text does not replace labels and recommends identifying required and optional information and expected formats. Put help beside the field that needs it, and show a clear message after submission.

Where UK GDPR applies, the Information Commissioner’s Office describes principles of purpose limitation, data minimisation, accuracy, and storage limitation. Apply them to registration by stating why information is collected, requesting only what that purpose requires, providing a correction route, and setting retention periods tied to the purpose. Use a private contact route for accessibility or dietary requests rather than encouraging unnecessary personal detail in a general comment box.

Set ticket, payment, and capacity rules#

Registration does not have to involve a purchase: Eventbrite supports free, paid, and donation ticket types. Choose the admission arrangement first, then configure the relevant ticket quantities, sales window, and checkout steps. For paid admission, display the ticket price and any additional charges before asking the attendee to complete payment.

State when a booking becomes confirmed and how payment problems will be handled. Provide a contact route for a missing receipt or an incomplete order. Keep cancellation and refund instructions distinct: one concerns attendance, while the other concerns money already paid.

Make the refund policy visible before purchase. Eventbrite’s refund policy guide says attendees can see the policy on the event listing and order confirmation, and that the policy determines when they can request a refund through their account. Publish the actual terms for the event, including the request deadline and any treatment of ticketing fees.

For a waitlist, explain how offers are sent and how long a person has to respond. Eventbrite allows organizers to set a claim time limit and customize the release message; its documented waitlist feature is unavailable for reserved seating. Check those restrictions before promising a waitlist for a particular ticket arrangement.

Send confirmations that explain how to attend#

Write the confirmation as attendance instructions. Include the event name, booking status, selected ticket or session, date and time with time zone, venue or joining route, preparation requirements, and a contact for booking problems. Add a calendar option when available and check that its details match the confirmation.

Eventbrite’s confirmation settings let organizers add information to the confirmation page, email, and PDF ticket, change the reply-to address, and provide messages for particular ticket types. Use those settings for arrival details, parking, items to bring, and the appropriate booking contact.

For a webinar, verify how the joining information is delivered. Zoom’s registration guide says joining links are normally sent in the confirmation email, with certain settings allowing joining information on the confirmation page close to the start. Make the instructions match the event’s settings.

Configure reminders after checking the confirmation. Zoom’s webinar email settings support reminders before the session and separate follow-up emails for attendees and absentees. Keep reminders focused on the start time and access route. In the follow-up, provide the recording or materials actually promised in the event description.

Record attendance at the event#

For an in-person event, decide how the booking will be matched to arrival. The Eventbrite Organizer app supports QR-code scanning and manual ticket check-in. Set up the correct event and ticket types, confirm staff have check-in permission, and test the process before doors open.

Check the scanner’s mode. Eventbrite distinguishes check-in, check-out, and validation-only scanning; validation-only scanning checks whether a ticket is valid without recording entry. Use a mode that produces the attendance record the event needs, and provide a manual lookup route for tickets that cannot be scanned.

For a webinar, specify whether the report will count live attendance, replay viewing, or both. In eWebinar’s reporting definitions, attendees are registrants who joined at least once, live or by replay. A combined count therefore answers a different question from the number present during the live session. Label the report accordingly.

Measure registration and attendance separately#

Use rates with explicit populations. The eWebinar KPI glossary defines registration rate as registered people divided by registration-page visitors, and attendance rate as attendees divided by registrants. Expressed as percentages:

• Registration rate: registered people ÷ registration-page visitors × 100.
• Attendance rate: attendees ÷ registrants assigned to the relevant session × 100.

Record the event, counting unit, date range, and attendance window beside the figures. eWebinar distinguishes the registration date from the date of the assigned session, so a list of people who signed up during a week may describe a different population from that week’s session registrants. Match the relevant groups before comparing the rates.

For group orders, use attendee or ticket counts when planning admission, and keep order counts separately. For recurring events, state whether the report counts unique people across the series or places booked for each session. Use registration figures to review the page and form, and attendance figures to review confirmations, access instructions, and check-in. Inspect those steps before assigning a cause to a change in the rate.

Choose registration software and test the complete process#

Compare event registration software against the tasks the event requires. Check ticket types, payment methods and fees, capacity controls, approval and waitlist options, confirmation editing, accessible forms, check-in, attendee exports, and cancellation handling. Confirm the relevant features in current documentation and the plan being considered. The platform-specific settings described above provide a starting point for that review.

Before opening registration, complete a test booking from the public page through confirmation and access. Check:

• The ticket or session selected is the one shown on the confirmation.
• Required fields, error messages, and successful submission are clear.
• Checkout displays the intended total and policy.
• Pending approval and waitlist messages accurately describe the next step.
• Confirmation links, calendar details, and booking contacts work.
• The resulting ticket can be checked in, or the webinar link can be used under the event’s access requirements.
• Corrections, cancellation, and any refund request route are available as described.

Use only the checks that apply to the event. Repeat the affected checks after changing ticket rules, form questions, or access settings.

How to register and manage a booking#

Read the event details and admission terms, choose the ticket or session, enter the requested information, and complete any payment step. Save the confirmation and check whether it confirms admission, requests further action, or places the booking on a waitlist.

For an Eventbrite booking, required order form questions may still need completion after checkout before tickets become accessible. For a Zoom webinar with manual approval, joining information follows approval. Follow the instructions for the actual booking status.

For missing access details, check the email address entered and the spam folder, then contact the listed organizer. Provide the event name and booking reference if available. To change details or cancel, use the route described in the confirmation. For paid tickets, read the event’s refund policy before submitting a request.