How Many Check-in Stations Does Your Event Need? The Throughput Maths

Ask an organiser what can go wrong on event day and the list gets long quickly. Speakers run late, badges go missing, catering falls behind and the AV decides not to cooperate.

A few people arrive early. Then twenty more show up. A coach pulls in. Someone can't find their confirmation email. A volunteer starts scrolling through a spreadsheet looking for a name that was registered under a colleague's account.

Five minutes later, the entrance is backed up.

It may look like a staffing problem, but it is usually a throughput problem. If people are arriving faster than your check-in process can handle them, the queue has nowhere to go but backwards.

The short answer. Take the number of guests you expect during your busiest arrival window, divide by the length of that window in hours, then divide by what one check-in station can realistically process in an hour. For QR scanning, use 150 an hour per station as a safe planning figure. A thousand guests arriving in 45 minutes needs nine stations. The rest of this article shows where those numbers come from.

This article covers:

• Why event check-in queues form

• What long check-in waits actually cost

• The throughput maths behind a busy entrance

• How many check-in stations an event really needs

• Why adding more manual desks only goes so far

• How SOURems spreads check-in across more entry points

• Common questions about event check-in speed

Why event check-in queues form

The basic problem is simple: arrivals happen in bursts, while check-in happens one person at a time.

A staffed desk using a printed attendee list or manual lookup typically takes around 45 to 90 seconds per person, according to event check-in benchmarking published by Nunify, based on deployment data from more than 200 events. That gives one manual station a practical throughput of roughly 40 to 80 attendees per hour.

Speed isn't the only issue. The same benchmarking reports manual check-in error rates of around 15 to 20%: misspelled names, incorrect registrations and badges assigned to the wrong session.

Scanning changes the equation. Benchmarks from VenueSight put staff-assisted QR check-in at roughly 5 to 15 seconds per attendee, while self-service check-in typically takes around 10 to 30 seconds.

Ranges compiled from throughput benchmarks published by Nunify and VenueSight.

At 60 manual check-ins per hour, one desk needs a full minute for every attendee. If 100 people walk through the door within ten minutes, that station hasn't suddenly become slower. It is still processing people at the same rate. It simply cannot keep up with the rush, so a queue begins to build.

What a long check-in wait actually costs

A queue at the entrance affects everything that comes after it.

Attendees miss the beginning of sessions. Staff who should be handling other jobs get pulled into registration. Speakers start in front of half-filled rooms. People arrive at the desk already irritated, which makes exceptions and registration problems harder to resolve.

QueueAway's collection of hospitality and venue queue statistics reports peak entry waits in the 20- to 40-minute range, with significant drop-off as queues get longer. A 2022 Waitwhile consumer survey also found that nearly three-quarters of respondents sometimes leave a physical line before reaching the front.

Not every attendee in a 20-minute event queue will turn around and leave. Even so, the wait has consequences. Some miss the opening session, which shows up later as a gap in your session attendance numbers. Others reach the entrance annoyed. Others will not complain at all. They may simply decide that next year's event is not worth the trouble.

That makes check-in unusually easy to underestimate. The immediate symptom is a queue. The real cost shows up later in attendee satisfaction, session attendance, staff workload and the overall experience of the event.

The event check-in maths

Consider a mid-sized event with 2,500 pre-registered attendees. Most of them are expected to arrive during the 75 minutes before the programme begins.

To get everyone inside during that window, your check-in operation needs to process:

2,500 attendees ÷ 1.25 hours = 2,000 attendees per hour

That is the number that matters more than total attendance or the number of tables that fit in the lobby. You need enough combined throughput to handle roughly 2,000 people an hour during the arrival peak.

Scenario 1: Six manual check-in stations

Assume each staffed desk can process around 70 attendees per hour. Six desks give you:

6 × 70 = 420 attendees per hour

At that rate, checking in all 2,500 attendees would take:

2,500 ÷ 420 = about 5.95 hours

That is almost six hours. Even if arrivals were spread perfectly evenly, which they rarely are, six manual desks would not come close to the throughput required for a 75-minute window. The volunteers are not working too slowly. The system simply does not have enough capacity.

Scenario 2: Six QR check-in stations

Now replace manual lookup with six scanning stations.

The benchmarks above say a staff-assisted scan takes 5 to 15 seconds, which would be 240 to 400 an hour. For planning, we use 150 attendees per hour per station, deliberately well under that range, because real check-ins include badge printing, a question or two, and the occasional phone with a dead battery. Plan on 150 and the benchmark speed becomes your margin rather than your assumption.

Combined throughput becomes:

6 × 150 = 900 attendees per hour

Clearing 2,500 attendees takes:

2,500 ÷ 900 = about 2.8 hours

That is a major improvement, but it is still more than twice the available 75-minute window. This is why changing the technology without thinking about the number of entry points only solves half the problem.

Scenario 3: Enough check-in stations for the actual arrival window

To process 2,500 people in 75 minutes, you need approximately 2,000 check-ins per hour.

At 150 attendees per hour per station:

2,000 ÷ 150 = 13.3 stations

So you would need roughly 14 check-in stations to comfortably match the expected arrival rate. If your scanning setup consistently runs closer to the benchmark speed, you may need fewer. If bag checks or registration problems slow each interaction down, you will need more.

So instead of asking "how many registration desks should we have?", ask "how many people will arrive during our busiest window, and how quickly can each check-in station process them?" Once you know those two numbers, the staffing decision becomes much easier.

Arrival concentration matters more than event size

Event size alone does not create a long check-in queue. A concentrated arrival window does.

Imagine an event with just 300 attendees. If they arrive gradually over two hours, the entrance may never feel busy. But if all 300 are told to arrive between 8:40 and 9:00 for a 9:00 start, you are suddenly trying to process 300 people in 20 minutes. That is the equivalent of 900 attendees per hour. With one manual desk at the entrance, a queue is inevitable. The event is not too large. The arrival rate is too high for the available check-in capacity.

This is also why organisers get caught off guard. A setup that worked perfectly for yesterday's networking session can fail badly at this morning's keynote, with roughly the same number of attendees. What changed was when people showed up.

And a simple average check-in time never captures the whole picture. On a real Monday morning, one person registered with a work email they can't open on their phone, another's badge is filed under their company name, a group of five stops at the same desk, and a volunteer leaves the table to find someone who can approve a change. Nothing catastrophic has happened. The process simply has no spare capacity to absorb normal exceptions while hundreds of people keep arriving behind them.

Why adding more manual desks only goes so far

The obvious response to a long queue is to add more tables and more people. Mathematically, that works. If one manual desk processes 70 people per hour, ten desks can process around 700 and twenty around 1,400.

But every extra manual desk usually needs:

• Another staff member or volunteer

• Another copy of the attendee data

• More physical space

• A clear way to divide attendees between queues

• A process for handling duplicate or inconsistent updates

• More coordination when something changes

At some point, you are spending a lot of people and floor space to scale a slow interaction.

Faster check-in changes both sides of the equation. You reduce the time required for each attendee while also making it easier to open additional entry points when they are needed. That is much more flexible than trying to predict exactly how many folding tables you will need before the doors open.

How SOURems handles busy check-in periods

The throughput numbers above are the reason SOURems check-in runs from staff phones rather than a fixed desk. Any team member with the SOURapp mobile app is a check-in station.

If the main entrance starts backing up, staff can open another scanning point. If attendees naturally split between two entrances, check-in can split with them. If one queue slows because several people need help, other scanners keep processing straightforward arrivals instead of forcing everyone through the same bottleneck.

Because every scan lands in the same live dashboard the moment it happens, each station works from the same attendance data rather than creating separate lists that need to be reconciled later. And when a guest scans, the screen shows their table or seat and any notes on their record, so staff can point them in the right direction without a second lookup.

The goal is not simply to make one desk faster.

It is to avoid designing the whole entrance around a single desk.

How to estimate how many check-in stations you need

You can get a useful first estimate with three numbers:

1. Expected attendance during the peak arrival window

2. Length of that arrival window

3. Average throughput of each check-in station

For example, you expect 1,000 attendees to arrive within 45 minutes. That means you need to handle:

1,000 ÷ 0.75 = about 1,333 attendees per hour

If each check-in station comfortably handles 150 people per hour:

1,333 ÷ 150 = 8.9

Based on throughput alone, you would want at least nine check-in stations.

In practice, build in some spare capacity. Real check-ins are not perfectly uniform. Phones run out of battery. Badges need reprinting. Someone always arrives who is not on the list. A little extra capacity gives those exceptions somewhere to go without slowing down everyone else.

FAQ

How long should event check-in take?

For the attendee, under five minutes of waiting is a reasonable target for most events. The actual scan or lookup should take far less. The five-minute target gives your setup room to handle temporary arrival spikes and attendees who need help without a large queue building. The more important metric is whether your combined check-in capacity can keep up with the number of people arriving during your busiest period.

Are QR codes really faster than a printed attendee list?

Usually, yes. Manual list lookup takes around 45 to 90 seconds per attendee, while QR-based check-in takes roughly 5 to 30 seconds depending on whether the scan is staff-assisted, self-service, or includes badge printing. That is several times the throughput per station.

How many check-in stations do I need?

It depends on your peak arrival rate, not your total attendance. Divide the number of attendees expected during the busiest arrival window by the length of that window in hours. That gives the hourly throughput your entrance needs. Then divide by the realistic hourly capacity of one station. For example, 1,000 attendees arriving in 45 minutes requires roughly 1,333 check-ins per hour. At 150 per station, that is nine stations before adding any safety margin.

Is check-in congestion only a problem at large events?

No. A 300-person event can produce a serious queue if most attendees arrive within the same 15 or 20 minutes. A 3,000-person event may have little congestion if arrivals are spread across several hours and there are enough entry points. Arrival concentration is the more useful number to watch.

Can't I just add more staff?

You can, and additional staff will increase throughput. The problem is that manual check-in scales slowly. Every extra desk requires another person, more space and more coordination. Combining faster scanning with multiple flexible entry points gives you more capacity without scaling staffing at the same rate.

What happens if someone can't find their QR code?

Keep a separate path for them so they do not hold up the scanning queue. In SOURems, staff search the guest list by name and check the person in manually, and a walk-up who was never registered can be issued a ticket on the spot. If one attendee needs two minutes of help, the hundreds behind them should not also wait two minutes.

Conclusion

A long event check-in queue is rarely the result of one volunteer moving too slowly. It happens when people arrive faster than the entrance can process them.

Once you look at check-in as a throughput problem, the solution becomes much easier to plan. Work out how many attendees are likely to arrive during the busiest part of the day. Estimate how quickly each check-in station can realistically process them. Then give yourself enough stations and separate entry points to stay ahead of that arrival rate.

Faster check-in technology helps, but speed alone is not the whole answer. Its bigger advantage is flexibility: you can add another station where the crowd is, when it is needed. The door is one part of a wider attendee management system, and it is the part your guests remember. The best check-in queue is one they barely notice.