How Many Ticket Scanners Does Your Event Need?

Almost every door disaster starts the same way: a queue that looks fine at 19:00 and stretches around the block by 19:25. The organiser blames “slow scanning”. The real cause is arithmetic. A door is a queue, and a queue has exactly two numbers — how fast people arrive, and how fast you can process them. If the first number is bigger than the second for long enough, the line grows, and nothing about the software will save you.

So we did the arithmetic. This piece models how many scanning lanes an event actually needs at different crowd sizes, anchors the service rates against published throughput figures from access-control and screening vendors, and shows exactly where the seconds go. Every assumption is stated so you can rerun the numbers with your own.

The two numbers that decide whether you have a queue

Arrival rate is your crowd divided by the window in which they turn up. Service rate is guests per minute per lane. Access-control manufacturer Avant-Garde publishes the formula plainly in its turnstile throughput guidance:

(number of patrons ÷ time allotted) ÷ rate of throughput = number of lanes required

That single line is the whole discipline. Everything else — reader type, staff training, whether the venue Wi-Fi holds — is just an argument about what number goes in the denominator.

How long does check-in take at an event?

Per guest, far less than people assume; in aggregate, far more. Published per-lane rates give us the ceiling. Avant-Garde puts full-height turnstiles at 20–30 people per minute, waist-high at 25–40, and barrier optical models at 45–60, noting these assume a fast credential read of roughly 1–2 seconds and ideal conditions. At the security-screening end, Evolv states in its published FAQ that Express can screen up to 4,000 people per hour on a dual-lane system — roughly 33 per lane per minute — with the caveat that real throughput depends on the venue’s sensitivity settings and alarm-resolution process.

Those are engineered hardware lanes. A member of staff holding a phone is a different machine. For the model below we assume 6 seconds per guest (10/min) for phone-camera scanning and 3 seconds per guest (20/min) for a dedicated USB or Bluetooth reader. Those figures are assumptions, not measurements — they bracket the realistic band between a hardware lane’s 1–2 second read and the messy reality of finding a screenshot on a stranger’s phone.

Lanes needed by crowd size: the model

Below, the arrival rate is the full crowd spread evenly across the entry window. Lanes are the formula result rounded up to a whole scanner.

Two things jump out. First, the swing between a phone camera and a proper reader is roughly half your door staff — at 5,000 guests it is the difference between nine positions and five. Second, small events are structurally safe: below about 300 guests over half an hour, one competent scanner clears the crowd with room to spare, which is why organisers who cut their teeth on 150-person nights are so often blindsided at 1,000.

How many check-in stations do I need if everyone arrives at once?

They will not arrive evenly, and that is where the table above is optimistic. Take the 1,000-guest event and assume 40% of the crowd turns up in the busiest 15 minutes — a modelled surge, not a measured one, but a familiar shape for a headline set time. Arrivals hit 26.7 per minute. Two reader lanes at 20/min each handle it comfortably; a single reader lane does not. That single lane falls behind by 6.7 guests every minute, so after 15 minutes roughly 100 people are stacked up, and the last person in that queue waits about five extra minutes purely because of the shortfall.

Backlog is the quiet killer. A lane deficit does not cause a fixed delay — it compounds for as long as the surge lasts, then takes just as long to drain. Adding one lane before doors open is trivially cheap; adding one at 19:25 is impossible.

Where the seconds actually go

Reader speed is rarely the binding constraint. In our modelled 3-second reader lane, the scan itself is a fraction of that. The rest is human and network:

• The network round-trip. If each scan waits on a server response over congested venue Wi-Fi or a saturated cell tower, a 300ms API call can become two seconds. Multiply by 1,000 guests.
• Exceptions. A wrong name, a duplicate ticket, a guest who bought for four and arrived with three. Each exception blocks a lane for far longer than a valid scan, which is a strong argument for a separate resolution position rather than letting problems stall the main queue.
• Finding the ticket. Guests digging through email while standing at the scanner. Signage and a pre-event “have your ticket open” reminder buy back more seconds than any hardware upgrade.

The network point is the one organisers most often get wrong, and it is the reason offline capability matters more than raw scan speed. A lane that validates locally has a service rate that does not degrade when 2,000 phones hit the same mast at 19:00.

What this means for a WordPress door

If you sell through WooCommerce, the door software is where this model becomes real. The Venuera Check-in add-on is a browser PWA rather than an app-store download, which matters for the lane maths: any phone your staff already own becomes a scanning position, so adding the third lane in the table above is a staffing decision, not a hardware purchase. It scans QR codes and 1D barcodes with the device camera, and also accepts USB or Bluetooth readers — the 20/min column, not the 10/min one.

Crucially, it caches the attendee list locally and validates against the same rules offline, queueing scans and reconciling them on sync. That keeps the per-scan cost stable when the venue connection is not. Duplicate and over-limit tickets are caught at the door, with check-in rules — maximum entries, availability window, per-period limits — resolved from global settings down through the event to the individual ticket type. Underneath, each ticket carries a unique QR derived from a salted SHA-256 hash of its ticket UID, so a screenshot passed to a friend fails on the second scan rather than at the bar.

Sources & methodology

Published throughput figures are taken from Avant-Garde’s turnstile throughput guidance (full-height 20–30/min, waist-high 25–40/min, barrier optical 45–60/min, plus the lanes-required formula) and Evolv’s published FAQ (up to 4,000 people per hour, dual-lane, throughput dependent on sensitivity and resolution settings), both retrieved 28 July 2026. Vendor specifications describe ideal conditions and change over time; treat them as ceilings.

The 10/min phone-camera and 20/min handheld-reader service rates are our own stated assumptions, not measured data, chosen to bracket the range between a hardware lane’s 1–2 second credential read and real-world staffed entry. Lane counts use the Avant-Garde formula with uniform arrivals across the stated window, rounded up. The surge example assumes 40% of a 1,000-guest crowd arrives in the busiest 15 minutes; backlog is (arrival rate − service rate) × surge duration, and tail wait is backlog ÷ service rate. Venuera product behaviour described here was verified against the plugin source rather than marketing copy. Substitute your own timings and the arithmetic holds.

Related reading: QR vs barcode vs NFC ticket validation, offline box-office capability compared, and how to check guests in at the door.

Frequently asked questions

How long does check-in take at an event?

Per guest, between roughly 1 and 6 seconds depending on the method: published turnstile specifications assume a 1–2 second credential read, while a staff member scanning phones is realistically nearer 3–6 seconds. What determines your total entry time is not per-guest speed but whether your lanes collectively exceed the arrival rate — if they do not, the wait grows for as long as the surge lasts.

How many check-in stations do I need?

Divide your crowd by your entry window in minutes, then divide that by your per-lane rate per minute, and round up. A 1,000-guest event over 45 minutes needs about three lanes at 10 guests per minute or two at 20. Add a lane if a large share of guests arrive in a short surge, and a separate position for problem tickets.

Is a phone camera fast enough to scan tickets?

For most events, yes — a phone camera lane clears a few hundred guests comfortably. Above roughly 1,000 guests the difference between a camera and a dedicated USB or Bluetooth reader is worth about half your door staff, so at that scale readers usually cost less than the extra positions they replace.

What happens if the venue Wi-Fi fails during check-in?

With cloud-only scanning, every scan waits on a server response and the lane slows or stops. Check-in tools that cache the attendee list locally validate offline against the same rules and sync queued scans afterwards, which keeps the per-scan cost stable regardless of connectivity.