Blog · Access control
Offline event check-in: when the venue has no signal
Basements, marquees and networks that die the moment doors open: what "offline mode" really means in access control, how local validation works, and what to demand from any system before trusting it with your event.
There are three venues where the network ALWAYS fails: the basement (car parks, below-grade halls, clubs), the marquee on an open field, and the historic building with metre-thick walls. And there is a fourth, more treacherous case, because it gives no warning: the venue with perfect coverage… until eight hundred people walk in with eight hundred phones and the cell saturates exactly at your entry peak.
Access control is the one part of an event that cannot wait "until the network comes back". The door either validates or it doesn't; if it doesn't, the queue grows by the second, and the emergency fix — waving people through unchecked — is precisely what the system was there to prevent.
"The venue has Wi-Fi" is not a plan
We hear it at every site visit. Three realities to test before relying on it:
Guest Wi-Fi has a captive portal. That "accept the terms" screen that costs a human one tap can leave an app with no route to the internet. A venue's corporate Wi-Fi is rarely provisioned for an outside vendor's door devices.
Access points saturate too. A consumer-grade AP handles a few dozen clients comfortably; arriving attendees pile onto the same Wi-Fi and crowd out your scanners at the worst possible moment.
4G/5G is shared with the crowd. The cell that gave you 80 Mbps on Tuesday morning's site visit divides its capacity on Saturday night between every phone on the premises. Coverage doesn't disappear — it becomes unusable in bursts, which is worse, because the system "almost" works.
What "offline mode" really means
Nearly every system in this industry claims "offline mode" on its marketing page. The difference is what exactly happens at the door, and it comes down to four pieces — if one is missing, it is not an offline mode, it is a checkbox:
1. Local download BEFORE doors open. The event data — the full list, not a summary — travels to the device while there is still a network.
2. Local validation. Every QR is accepted or rejected against the device's own copy, without asking any server for permission. Without this piece, "offline" is just a screen that doesn't show an error.
3. A local log of every scan. Each read is stored on the device with its timestamp, so the history has no holes.
4. Automatic sync. The moment the network peeks through — even for a minute — scans upload to the dashboard on their own. No button somebody has to remember to press.
And a fifth, the one that separates the proven from the theoretical: tolerance to a mid-event drop. Starting without a network (you planned for it) is not the same as losing it with half the audience inside. The system has to keep validating without blinking, and reconcile afterwards.
A real case: the fair in the marquee
A regional fair, a 1,200-square-metre marquee on an open field, no fixed line, one 4G cell shared with the whole fairground. With QRACCESS the setup is the usual one, with one extra step the day before:
In the dashboard, the event is set to offline mode (the scan mode is decided in the dashboard, not on each phone). The day before, every scanner opens the app AT THE PHYSICAL DOOR and downloads the event data: the complete list lives on the device. Then the acid test, right there: airplane mode on, scan the test QR. If it validates like that, Saturday holds no surprises — it is point 4 of our day-of checklist.
During the event, every scan validates and logs locally. When the cell breathes, the app syncs on its own; when it saturates, nobody at the door notices.
In August we published what happened when we stress-tested this piece properly: 50,000 offline scans uploaded without losing a single one in the sync. That is the number to ask any vendor for: not "do you have offline mode?" but "how many offline scans have you reconciled, and how many did you lose?".
What offline mode does NOT do (and how to manage it)
Technical honesty is a specification too. Without a network, each device validates against ITS local copy: the live occupancy counter and duplicate warnings ACROSS different doors consolidate when the devices sync, not before. In practice you manage it like this:
One door, one list where possible: if each entrance serves its own zone or session, cross-door overlap never comes up.
Sync whenever the network peeks through, even in bursts: every upload shortens the reconciliation window.
Size the risk. At an open-day event, the chance of one QR slipping through two different doors inside the same window is irrelevant; at a final with active ticket resale, put the riskier gates where coverage is best or give them a dedicated network point.
Everything else — how many scanners you need, the duplicate policy, scanner accounts — works the same with or without coverage.
The buyer's checklist
If you are evaluating any access-control system (ours included), demand a demonstration of these five, on site and not in the office:
1. Local download of the complete list before the event.
2. Validation with the device in airplane mode.
3. A local, timestamped log of every scan.
4. Automatic sync when the network returns, no intervention.
5. A real figure of offline scans reconciled without losses.
The venue's network is not yours and you don't control it. The door is, and you do.