There is a particular kind of door problem that has nothing to do with your software and everything to do with arithmetic. A coach pulls up, forty people get off at once, and they all converge on a single scanner within the same ninety seconds. Up to that point the door was calm. Now there is a wall of people, and the scanner that handled a steady trickle is the bottleneck for a sudden flood. Single-gate venues, side entrances and back-of-house crew doors all share this shape: one point, occasional surges, and no room to add lanes.
You cannot always widen the gate. What you can do is change how the group moves through it, so a single scanner handles a surge without the queue backing up into the car park. The trick is to do the slow work before people reach the scanner, and to keep the scan itself as close to instant as the technology allows.
Why one gate stalls
A scanner is rarely the slow part. A clean QR scan is close to instant, and a smooth check-in averages around eight seconds end to end. The delay in a group arrival is everything around the scan: people fishing for phones, brightening screens, finding the right email, realising they screenshotted the wrong thing, or simply not being ready when they reach the front. With forty people, those small fumbles stack into minutes.
So the goal is not a faster scanner. It is a group that arrives at the gate already prepared, so the scanner can do the one thing it is fast at, over and over, without waiting for anyone.
Do the work before the gate
The most effective moves happen before anyone reaches the scanner. Treat the approach to the gate as part of the process, not dead space.
- Tell people what to have ready, in advance and again as they queue: pass open, screen bright, brightness up.
- Send passes that load without a connection, so nobody is reloading an email on a weak signal at the worst moment.
- Position a member of crew up the queue to spot the unready, help them find their pass, and pull aside anyone with a problem before they reach the front.
- Keep the scan point clear of clutter so the scanner reads first time, every time.
That up-the-queue role is the single biggest lever. One person walking the line, getting screens ready and lifting out the awkward cases, turns a stop-start queue into a steady feed. The scanner then never waits, and a single gate sustains a throughput that feels impossible when everyone arrives cold.
The scanner is fast. The queue is slow. Move the slowness up the line, away from the gate, and a single point handles far more than its width suggests.
Group and household passes
Some groups should not be forty individual scans at all. A household, a delegation, a corporate block booking, these can travel as a group where one scan admits the party, with the headcount handled in the record rather than at the gate. This collapses the slowest part of a group arrival into a single action.
| Approach | Scans for 40 | Best for |
|---|---|---|
| Individual passes | 40 | Mixed crowd, separate arrivals |
| Group pass, one scan | 1 | Coaches, delegations, blocks |
| Household pass | A few | Families arriving together |
CheckInHub supports group and household check-in, so a party that booked together can come through together without forty separate fumbles at the gate. We cover the registration side of this in group and household check-in, handled. The result is that the coach load that used to define your worst queue becomes one of your quickest.
When you genuinely need two devices
There is a limit to what preparation can do. If single-gate surges are a regular feature rather than an occasional one, a second device at the same point, with a member of crew working it during the rush and standing down between coaches, doubles your surge capacity without needing a second physical lane. Both devices check in against the same live list, so there is no risk of a double entry or a mismatch. The maths behind when a second device pays for itself sits in the maths behind one kiosk versus three.
Stagger the surge where you can
Not every group arrival is beyond your influence. If you control the inbound logistics, the cheapest fix of all is to spread the arrivals so they never converge on the gate at once. Two coaches timed ten minutes apart are two manageable feeds. Two coaches arriving together are one wall. The same goes for crew and contractors, who can be asked to arrive on a staggered schedule rather than all reporting at the same hour. Staggering does nothing to speed up an individual scan, but it removes the condition that makes a single gate fail in the first place, which is everyone wanting through in the same ninety seconds. Where you cannot control timing, the preparation work up the queue is doing the same job after the fact: smoothing a spike into a flow.
Keep the record honest
Moving fast through one gate is only useful if you still trust the number afterwards. Whatever shortcuts you take at the surge, the live count has to stay accurate, so security, capacity and any re-entry checks still hold. A group pass that admits a party should record the party. A second device should write to the same list as the first. The discipline is that speed at the gate never comes at the cost of a count you cannot rely on later.
A single gate is a constraint, not a sentence. Prepare the group before they reach it, let parties travel as parties, add a second device only where the surges justify it, and keep the count clean throughout. Do that and the coach of forty stops being the moment the door fell behind, and becomes ninety seconds that barely registered.
