Event check-in checklist: before, during, and after arrivals

Use this event check-in checklist before, during, and after arrivals. Prepare the registration form and welcome desk, then rehearse missing confirmations, duplicate scans, and walk-ins with a named exception owner. The editable worksheet and printable desk sheet give your team a practical starting point.

Download the editable check-in checklist or open the printable welcome-desk sheet. Both are free to use without an account. Replace the fictional example with your own owners, escalation contact, and reviewed arrival process.

Registration and check-in are parts of one welcome. The details collected before the event should help the team recognize participants and give them a clear next step when they arrive.

Start with the arrival process, then work backward to the form. If a field does not serve a defined purpose, question whether you need it. The example in this guide is a fictional 80-person gathering with free general admission and a separate volunteer registration option.

Decide what the welcome desk needs

Write down how a participant will identify their registration, who can resolve a missing or duplicate entry, and what happens after check-in. Keep the routine path short. Give exceptions an owner so one unusual case does not leave the rest of the welcome team guessing.

For our example, the welcome lead reviews the registration list, two volunteers handle arrivals, and one organizer handles exceptions. They agree which entrance to use and what instructions a participant receives after being checked in.

This is a staffing example, not a recommended attendee-to-staff ratio. Your venue layout, arrival pattern, accessibility needs, and registration process should shape the actual arrangement.

Review the registration form before sharing it

Make ticket choices understandable. “General admission” and “Volunteer registration” should describe the intended choice without making participants decode internal labels. Explain any important difference near the choice.

Every input needs a meaningful label. The W3C form-label tutorial explains how labels identify controls and how they should be associated with their fields. Review the form with a keyboard as well as a pointer, and check that required fields and validation messages are understandable.

For the fictional free event, test one general registration and one volunteer registration in an appropriate test environment. Confirm the intended confirmation and arrival instructions. Do not create charges or register real people merely to test a marketing example.

This is the actual registration interface with sample data. ADGEvents supports event registration and QR check-in. Paid ticket checkout requires your organization’s approved live Stripe Connect account; the existence of a registration page alone does not mean paid checkout is ready.

Event registration checklist: follow the handoffs

Avoid parallel “official” lists. If someone exports a roster for an operational need, identify when it was created and how later registrations or corrections will be reconciled. A download does not automatically contain subsequent changes.

Rehearse missing registrations, duplicate scans, and walk-ins

Give one team member responsibility for the exception queue so the routine arrival line can continue. These decisions belong to your event's approved process:

A waitlist, an incomplete checkout, and a successful check-in are different states. Avoid promising admission until the appropriate authorized person has confirmed eligibility. For paid walk-ins, use the organization's supported checkout and payment-confirmation process. A screenshot or an unverified return page alone should not substitute for payment confirmation.

Test the scanner, device, and venue connection before doors open. This guide does not promise offline QR check-in. If the connection fails, pause scanning and use the organizer's approved contingency process; record any manual action so an authorized owner can reconcile it when connectivity returns. Never assume that reconnecting will import handwritten entries automatically.

Keep personal details out of public displays and broadly shared team messages. Share the information needed for the task through the access controls appropriate to your organization.

Event check-in checklist for arrival day

• Ticket names explain the available choices.
• Form fields have meaningful labels and understandable validation.
• Confirmation and arrival instructions have been reviewed.
• A sample registration has been checked through the intended process.
• Paid ticket requirements have been verified if the event charges admission.
• The team has appropriate access to current registration records.
• Missing, duplicate, and changed records have an escalation owner.
• Printed or downloaded rosters have a clear version and reconciliation process.
• Check-in equipment and the venue connection have been tested.
• Participants receive a clear next step after arrival.

Close the desk with a handoff

Before the team leaves, give the organizer the unresolved exception list, the time of the last roster review, and any approved manual actions that still need reconciliation. Count a person as arrived using the event's actual check-in record rather than adding desk notes to the attendance total. Assign follow-up for outstanding payment, access, or registration questions through the appropriate private records.

For the fictional 80-person gathering, suppose the team has 65 confirmed check-ins, two unresolved identity matches, and one walk-in awaiting an organizer's decision. The welcome lead reports 65 confirmed arrivals and three open cases. The open cases are not three more confirmed arrivals. This is a reporting example, not an attendance result for a real event.

The CSV includes the normal handoffs and four exception rehearsals, with blank due-date and completion fields for your team. Its printable version is designed for a desk briefing. Use your browser's Print command to print or save it as a PDF. Completed rosters and exception notes can contain personal data; keep them in approved restricted storage.

Download the registration-to-check-in worksheet or print the welcome-desk sheet. See the nonprofit registration and QR check-in workflow, then use the run-of-show guide to connect arrivals with the program. The post-event follow-up guide helps assign the promises that remain after the desk closes.