How Many Check-in Lanes Do You Need? A Sizing Formula by Attendee Count

The number of check-in lanes you need equals the number of attendees arriving in your peak window, multiplied by the average processing time per person, divided by the length of that window. For 2,000 attendees with 70% arriving in a 30-minute window at 15 seconds per person — a reasonable planning assumption — that works out to roughly 12 lanes.

The formula, step by step

Four inputs are enough to get a reliable estimate:

• N — total expected attendees
• P — the share arriving in your busiest window (typically 60-75% for a single-entrance conference with a fixed start time — a planning heuristic, not a measured average)
• W — the length of that peak window, in minutes
• T — average processing time per person, in seconds

The formula: Lanes = ROUNDUP( (N × P × T) / (W × 60) )

Worked example: 2,000 attendees, 70% peak share, 30-minute window, 15 seconds per person.

• Peak attendees = 2,000 × 0.70 = 1,400
• Total processing seconds needed = 1,400 × 15 = 21,000
• Window capacity per lane = 30 × 60 = 1,800 seconds
• Lanes = ROUNDUP(21,000 / 1,800) = ROUNDUP(11.67) = 12 lanes

Reference table by event size

These are planning estimates, not guarantees — treat them as a starting point for a conversation with whoever is sizing your actual operation, not a final number.

What changes the number

• Badge technology. A QR code scan typically runs 10-15 seconds per person; an NFC smart-badge tap can run 5-8 seconds; a manual name lookup against a printed list commonly runs 30-60 seconds or more. These are directional industry estimates, not measured data — treat them as planning inputs until you have your own event history. Technology choice alone can still meaningfully cut the required lane count.
• Staff experience. A trained host working a lane generally processes faster than a first-time volunteer — plan for this as a directional difference, not a fixed rate.
• Pre-registration and self-check-in. Kiosks or self-scan options can absorb a meaningful share of the "simple" cases (no changes, no questions) and free staffed lanes for exceptions.
• Group arrivals. Exhibitor teams, VIP blocks, or bus-transported delegations arrive in bursts rather than a smooth curve — plan a separate, dedicated lane for these rather than folding them into the general estimate.

beamian's own positioning around check-in speed — discussed in Why Event Check-in Guarantees Beat Software Licenses — argues for a guaranteed average tailored to each event, in the same range as the mid-range figures used above. Treat 15 seconds as a reasonable planning target until you have your own historical data, not as a fixed number beamian has published as a universal guarantee.

Why the formula is only a starting point

The math above assumes a smooth, predictable arrival curve. Real events rarely cooperate: buses arrive together, a keynote speaker's name recognition front-loads the morning rush, or a delayed flight shifts an entire delegation's arrival by twenty minutes. Building in buffer capacity — and having a plan for the failure modes described in OaaS: Why you shouldn't pay for software that fails — is what turns a sizing estimate into an operational plan.

This is also the exact calculation Arrivio's quote wizard runs automatically, adjustable in real time by slider, alongside staffing, hardware and logistics recommendations for your specific event.