Skip to content
All posts

· 7 min read

How to run event check-in without a queue

Guests forgive a lot, but they remember the queue. The good news is that a fast gate is mostly planning, not technology. Here is the playbook.

Do the queue maths first

A practiced volunteer with a phone scanner handles roughly one guest every 5 to 8 seconds when tickets are ready on screens, so about 8 to 10 a minute. ID checks or bag checks can triple that time. Now look at your arrival peak: if 1,500 of your 3,000 guests arrive in the hour before the headliner, you need to admit 25 a minute, so three scanning lanes at a minimum, and four to be safe.

Peak arrivals per hourLanes (tickets only)Lanes (with ID check)
30012
80024
1,50047
3,000712+

Spread the arrival peak

  • Open the gates earlier than you think, and give people a reason to come early: an opening act, food stalls, the first 200 get something.
  • Put the gate time on the ticket and in the reminder email, not just the show time.
  • For multi-day events, let day passes collect wristbands on day one so day two is a glance, not a scan.

Design the lanes

  • A separate lane for problems (lost tickets, wrong names, upgrades) set back from the main gate. The main lanes never stop for one person.
  • Signs 50 metres before the gate: "Have your ticket open". Phones out early saves more time than any scanner.
  • If you check IDs, check them in the same lane as the ticket, not in a second queue.

Scanners and network

  • Use phones volunteers already know. A web scanner that runs in the browser means no app install on the day.
  • Test the network at the gate at the same time of day as the event. Crowds kill mobile data; bring a dedicated hotspot or ask the venue for Wi-Fi.
  • Keep two spare phones charged and logged in, plus power banks.
  • Make sure two volunteers scanning the same ticket at the same moment cannot both let someone in.

Brief volunteers in five minutes

Every volunteer needs to know exactly three outcomes and what to do with each:

  1. Valid: let them in, say welcome.
  2. Already used: look at the time of the first scan, then send them to the help desk. Do not argue at the gate.
  3. Not valid or not found: send them to the help desk.

Give the help desk a laptop with the organiser dashboard to look up tickets by name or email and resend them.

After the doors close

Look at the check-in log: when did people actually arrive, which lane was slow, how many duplicates were caught. That is your plan for next time.

Run your next event on Morbin.

Booking rules that keep the wrong people out, a gate that keeps moving, and payouts when you need them.

Request access

Keep reading