Give the door team responsibilities, not a shared owner password
Read the guide →Guide preview
Assign scanning, exception handling and administration separately, then verify each person can do their actual job.
Assign roles, prepare the correct devices and dates, define the offline fallback and rehearse the critical cases before accepting readiness.
Assign roles, prepare the correct devices and dates, define the offline fallback and rehearse the critical cases before accepting readiness.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Assign scanning, exception handling and administration separately, then verify each person can do their actual job.
Check the real device, event and operator together; installing an app alone is not readiness.
An event name is not enough when tickets belong to different dates or time slots.
Offline scanning can use prepared data; it cannot make disconnected devices share new decisions.
A printed list is a snapshot; show when it was made and how later changes reach the door.
A filter can deliberately reject a valid ticket at the wrong station; brief operators on that distinction.
Put the event scope, ordinary action and exception route before background information.
Test ordinary and awkward cases with the actual roles; record observations, not a blanket pass.
Transfer the current scope, device state and outstanding decisions—not merely the scanner.