A fast check-in desk does not feel fast. It feels calm. The queue moves at a steady walking pace, nobody is hunched over a laptop squinting at a spreadsheet, and the person on the door has time to say hello. Speed at the front door is the result of removing friction, not of moving quickly. The desks that look frantic are almost always the slow ones.
Take apart any desk that genuinely shifts people, and you find the same parts arranged with care. Here is the anatomy.
The layout: entry on one side, exit on the other
A guest at a check-in desk is doing three things: presenting who they are, being confirmed, and receiving whatever they need to go in, a badge, a wristband, a nod. If those three happen in three different directions, the desk jams.
The fix is flow. Guests should approach from one clear side, be processed across the desk, and leave on the other, never doubling back into the people arriving behind them. Where badges are collected, put them at the exit end so the confirmed guest moves forward to pick one up rather than waiting at the point of scan.
For anything above a couple of hundred people, split the desk by surname or by ticket type, with clear signs at standing-read height. A single queue that branches at the desk is slower than two queues that were separated by a sign ten feet earlier. Our piece on cutting the queue covers the queue mechanics in more detail.
The kit: one scanner, one screen, one decision
The fastest desks own the smallest number of moving parts. Each guest interaction should resolve to a single decision on a single screen: are they on the list, and are they in. Everything that sits between the guest arriving and that decision is friction.
That means:
- A device that reads the guest's code on the first present, whether that is a phone, a tablet camera or a wedge scanner.
- A screen that shows a clear yes or no, large enough to read at arm's length, so the door person is not interpreting a tiny status field.
- A search box for the inevitable guest whose phone is dead or whose code will not load, fast enough to find someone by surname in seconds.
Every second you add to one check-in, you add to every person still in the queue behind them.
The enemy here is the laptop with a spreadsheet open. Scrolling a list of six hundred names, marking a cell, hoping nobody else marked it too, is the slowest possible desk and the easiest to get wrong. Moving off the spreadsheet is the single biggest speed gain most events ever make, which is why we talk about it in from spreadsheet to check-in.
The roles: greeter, scanner, problem-solver
People, not just kit, make a desk fast. The trap is to have everyone do everything, which means every small problem stops the whole line. Split the work.
- The greeter keeps the queue moving and ready: code open, name to hand, sorted into the right lane. Most of your speed lives here, before anyone reaches the desk.
- The scanner does one thing: confirm and wave through. They never leave the desk to solve a problem, because the moment they do, the queue stops.
- The problem-solver takes the awkward cases off to the side: not on the list, wrong ticket, name does not match. Pulling these out of the main line is what keeps the main line fast.
On a small door, one person can wear two of these hats. The principle holds regardless of scale: keep the confirm-and-wave function uninterrupted, and route every exception away from it.
Where the seconds actually go
It helps to see where time leaks, because the instinct is usually to optimise the wrong step. Here is roughly how a single arrival breaks down at a well-run desk versus a struggling one.
| Step | Calm desk | Struggling desk |
|---|---|---|
| Guest reaches the front with code ready | Greeter sorted them already | Guest still finding the email |
| Present and read the code | One present, instant | Camera refocusing, screen too dim |
| Confirm on screen | Clear yes or no | Scrolling a spreadsheet |
| Handle an exception | Pulled to the side | Whole queue waits |
| Hand over badge | Collected at the exit end | Searched for at the desk |
Notice that the device read is rarely where the time goes. The losses are at the edges: a guest who was not ready, an exception that blocked the line, a badge hunted for at the wrong end. A fast desk is mostly good choreography around a quick scan.
Rehearse it once, empty
The cheapest improvement you can make is to run the desk once before anyone arrives. Walk a colleague through as a guest. Scan a real record. Hand over a real badge. Force a deliberate exception, someone not on the list, and watch how it is handled. You will find the awkward angle, the dim screen, the missing pen, the lane sign nobody can read, in five minutes of quiet rather than in front of a growing queue.
Across more than 125,000 guests checked in through CheckInHub, the average sits around eight seconds per person, and almost none of that eight seconds is the technology. It is the layout, the roles and the rehearsal that turn a desk from a bottleneck into a welcome. The kit only has to get out of the way.
