Test your event
Run a controlled booking and check-in rehearsal before you promote the event.
In this article, you'll run an internal end-to-end test of the attendee journey, the staff check-in tools, and the launch assets you plan to use on the day.
Test before public promotion
Some event checks only become meaningful on the real attendee entry point, such as the ticket QR code and the Scanner App. If needed, publish to a controlled internal audience first, then test before you share the event widely.
Prerequisites
- Your event build is complete enough to validate and stage for internal testing.
- You have one staff device for the Scanner App and one attendee device for the public event flow.
- You know whether the activity uses Self check-in, Scan check-in, or a mix across different activities in the campaign.
Run one end-to-end rehearsal
Create an internal test booking
Use the same entry point you plan to promote after launch: the direct event URL, a venue QR code, or the landing page link. Complete one real booking with an internal email address so you can follow the full attendee journey.
Check the attendee confirmation
Verify the attendee receives the expected confirmation email, can open the booking confirmation, and can access the final ticket asset you plan to rely on on the day.
If your setup includes a ticket file or PDF, open that exact file as well. The QR code the attendee presents to staff must match the booking you just created.
Walk through the check-in path
Test the attendee state that matches your configuration, then confirm the host flow on the Scanner App.
Open the attendee flow during the active check-in window and confirm the attendee can start check-in successfully.
Also test the time-based states around it:
- before the window opens, the attendee should see the countdown to check-in
- during the window, the attendee should be able to complete check-in
- after the window ends, the attendee should see the check-in ended state
Open the attendee ticket and confirm the attendee can see the ticket QR code and any Add to Calendar option your experience shows.
Then open the Scanner App on a staff device, authenticate, choose the activity, and test the main host paths:
Scan QR CodeFind by EmailFind by SlotSlots Availability
When the scan succeeds, confirm the attendee state updates from waiting-for-scan to checked in.
Test the early and late windows
Use a slot with a known start time and compare the visible behavior with your check-in settings.
Example: if a slot starts at 14:00, the early window is 15 minutes, and the late window is 10 minutes, the attendee or host should be able to check in from 13:45 until 14:10, but not before or after that range.
Review the notifications
Read every message the attendee receives during the rehearsal, especially booking confirmation, reminder, and cancellation flows when those are enabled.
Check that dates, times, venue details, links, and brand wording are correct, and make sure the attendee can understand what to do next without extra explanation from your team.
What good looks like
Before launch, your internal rehearsal should confirm all of the following:
- the public event entry point opens the expected activity
- the booking confirmation matches the selected slot and attendee details
- the attendee QR code works from the real device or file you plan to use on site
- the check-in window behaves correctly before, during, and after the slot
- the Scanner App can handle scan, email search, and slot-based checks for staff
- notification copy is clear, accurate, and brand-safe