Skip to content

Measuring registration desk throughput per lane and per minute on show morning

Attendee analyticsUpdated 2026-08-188 min read

In short

Registration desk throughput is completed check-ins per lane per minute, calculated from the timestamps the registration system already writes. Split mean service time into lookup and badge print, because only one of those is fixable on the day. Fourteen lanes running at 3.4 check-ins a minute clear 2,856 an hour, which falls 544 short of a 3,400 arrival peak.

At 09:20 on day one somebody from the show office walks the registration hall, looks at the queue, and radios the operations lead to say it is bad. The operations lead asks how bad. Nobody has a number, so the answer is a description of a queue, and the decision that follows gets made on the description.

Registration desk throughput is the number that ends that conversation, and it is already sitting in your registration system. Completed check-ins, per lane, per minute. No stopwatch, no observer, no supplier.

The measurement, and where it comes from

Every completed check-in writes a row. That row has a completion timestamp and, in every system I have worked with, some identifier for the workstation, the scanner or the operator that produced it.

Group those rows by lane and by minute and count them. That is throughput. It takes one query and it can run live.

Two details decide whether the number means anything. The first is that you count completions and nothing else, so a lookup that was started and abandoned contributes zero, which is correct, because the person is still in the hall. The second is that you use the lane identifier consistently, since a desk where two staff share one workstation is one lane for throughput purposes no matter how many people are standing behind it.

Report the median rate across lanes and the spread. The mean hides the case that matters most, which is one lane running at half the rate of its neighbours because its printer keeps jamming.

Where does the time in a transaction actually go?

Mean service time is throughput's reciprocal, and splitting it is the whole point of doing this properly.

A check-in has two phases with different owners. The lookup phase covers everything from the attendee presenting themselves to the record being confirmed: scanning a QR code, or typing a surname, or resolving the two people with the same surname, or handling somebody who registered under a company account. The print phase covers the badge coming out of the printer and being handed over.

These are worth separating because only one of them is fixable on the morning. If lookup is slow because your search matches on exact surname and half your international attendees have their name entered differently on the badge and the passport, you can brief the team, change the search behaviour, or add a lane. If the print takes seven seconds because that is the thermal printer's cycle at that badge size, no briefing changes it, and the only levers are more printers or pre-printed badges.

Most registration systems do not stamp the two phases separately, which is a reasonable thing to ask a supplier for. Failing that, you can measure it once with a phone timer across thirty transactions at a quiet moment, get the split, and use it for the rest of the show.

What does fourteen lanes actually clear?

Here is the arithmetic worked through on one show morning.

The mean service time is 17.6 seconds, split as 10.6 seconds of lookup and 7.0 seconds of badge print. Sixty divided by 17.6 gives 3.4 completed check-ins per lane per minute. One lane therefore clears 3.4 times 60, which is 204 people an hour.

You have 14 lanes open. Fourteen times 3.4 is 47.6 check-ins a minute, or 2,856 an hour.

Your arrival peak in the 09:00 hour is 3,400 people. Subtract and the desk is 544 people an hour short. Those 544 do not disappear. They join a queue that grows for as long as the deficit persists, and if the peak hour runs at that rate for the full hour the queue is 544 people longer at 10:00 than it was at 09:00, on top of anybody already waiting.

Two ways out, and the arithmetic separates them cleanly.

Add lanes. To clear 3,400 at 204 per lane per hour you need 3,400 divided by 204, which is 16.7, so 17 lanes to break even. Break even is the wrong target, because arrivals inside the hour are uneven, so call it 19 or 20 to actually stay ahead. That is five or six more desks, five or six more staff, five or six more printers, and the floor space to put them on.

Or cut the print time. Move from a 7.0 second print to 3.5 seconds, by changing badge stock, print quality or printer model, and mean service time falls to 14.1 seconds. Sixty over 14.1 is 4.26 per lane per minute, so 255 an hour per lane. Fourteen lanes now clear 3,578 an hour, which is ahead of the 3,400 peak with the lanes you already have.

Three and a half seconds per transaction bought more capacity than five extra desks. That is the kind of finding that only appears once you split service time, and it is why the split is worth the effort of getting.

Why the average lane rate misleads you

The calculation above assumes every transaction takes 17.6 seconds. Real transactions vary enormously, and variability costs you capacity in a way that averages conceal.

Kingman showed in 1961, in the Mathematical Proceedings of the Cambridge Philosophical Society, that the mean wait in a single server queue under heavy load scales with a variability term, a utilisation term and the service time itself. The practical consequence for a registration hall is that two desks with identical mean service times behave completely differently if one has consistent transactions and the other alternates between four second scans and ninety second problem cases.

You can see this in your own data without doing any queueing theory. Pull the service time for every transaction in one hour and look at the distribution rather than the mean. If the 90th percentile is three times the median, your desk has a long tail, and the long tail is what actually produces the queue photograph.

The fix for a long tail is usually organisational. Take the slow transaction type off the main lanes and give it a dedicated desk. Groups, on-site registrations, badge reprints and anybody with a problem all belong somewhere other than the lane a pre-registered attendee with a QR code is standing in. Splitting them raises the throughput of the fast lanes and makes the mean service time on those lanes mean something.

Erlang set out the relationship between offered traffic and server count in 1917, publishing the loss and waiting formulae that telephone engineers have used ever since. The registration hall is the same problem with people instead of calls, and the uncomfortable part of Erlang's result holds here too: as you approach full utilisation of your lanes, the wait rises much faster than the load does. A desk running at 95 per cent of its capacity is in a completely different state from one running at 80 per cent, even though the difference sounds small on a slide.

Turning the number into a decision on the morning

Throughput becomes operational when somebody in the show office is watching it against a target that was set before the doors opened.

Compute the required rate per minute for the current 15 minute bin from your expected arrivals, put the actual rate beside it, and show the gap. Four numbers on a screen: arrivals so far this bin, check-ins completed this bin, lanes open, and the rate needed to hold level. When the actual rate drops below the needed rate, somebody opens a lane or moves a queue, and they do it at 09:12 rather than at 09:47.

Predicting the wait that a given queue implies is a different calculation that needs the arrival rate as well, and turning a queue length into an expected registration queue wait time is worth doing separately. Deciding how many staff should be rostered to each bin before the day starts is a planning exercise rather than a live one, and a proper registration desk staffing model works from the same service time you just measured.

Where this stops

Throughput measures the desk. It says nothing about whether the desk is the constraint.

At several shows I have looked at, the real bottleneck sat in front of the desks rather than at them. A queue that cannot physically feed lanes fast enough, because the barrier layout forces everyone through one entry point, produces idle lanes and a large queue at the same time. Your throughput number will look fine and your attendees will still be waiting twenty minutes. If lanes are idle while people wait, stop measuring the desk and go and look at the barriers.

The measurement also assumes the completion timestamp is written when the transaction completes. Some systems write it on record creation, some batch their writes, and some devices buffer while offline and stamp on sync. Any of those turns your per-minute rate into fiction, particularly during a wifi problem, which is exactly when you are relying on it. Check the behaviour of your own system against a stopwatch once, for twenty transactions, before you build a live view on it.

Self-service kiosks measure differently again, because the cycle includes the attendee's own interaction time, and self service check in throughput has its own bottleneck that is rarely the person.

The step for this week takes one query. Pull last edition's check-in records for the busiest hour, group by lane and by minute, and look at the spread across lanes. If your slowest lane ran at 60 per cent of your fastest, you already know where an hour of process work goes, and everything else in your on-site attendee analytics reporting can wait until that gap is explained.

Questions people ask about registration desk throughput

How do you measure registration desk throughput?
Take completed check-in records, group them by lane and by minute, and count. The registration system already stamps each record with a device or workstation identifier and a completion time, so the measurement needs an export rather than an observer. Report the median rate per lane per minute and the spread across lanes, since the spread is where the problem usually sits.
What is a normal check-in rate per lane?
It depends almost entirely on what happens in the transaction. A pre-registered attendee with a QR code and a pre-printed badge can clear in under 10 seconds. A lookup by name with an on-demand badge print runs 15 to 25 seconds. Measure your own, because a rate borrowed from another show carries that show's badge stock and process.
How many registration lanes do I need?
Divide your peak hour arrivals by the number of check-ins one lane completes in an hour. At a 17.6 second mean service time a lane clears about 204 people an hour, so a 3,400 person peak needs 17 lanes to break even and more than that to avoid a queue building. Halving the badge print time changes the answer more than adding staff does.

Related reading

All on-site analytics articles