Retreat centres in the hills, basement halls and festival fields all have the same problem at the same moment: two hundred people arrive, everyone's phone reaches for the same tower, and the connection goes. A door that stops working when the network does is not a door.
Offline check-in on BrightStar keeps the line moving. The scanner holds the guest list on the device, validates against it while the connection is gone, and queues each scan locally instead of throwing it away.
How offline check-in keeps the line moving
When two hundred people are standing in a field or a stairwell waiting to get in, the worst thing a check-in system can do is stop and think. Because the BrightStar scanner already has a copy of the guest list sitting on the device, it doesn't need to reach a server to tell a valid ticket from an invalid one. It checks the name, admits the guest, and moves on.
The scan itself doesn't vanish just because the connection has. It's held on the device, waiting its turn to be sent along once a signal comes back. That's the whole point of building it this way: the moment your Wi-Fi drops shouldn't be the moment your door stops.
What happens once you're back online
Once the device reconnects, the catch-up happens without anyone at the door doing anything extra:
- 1The scanner detects the connection has returned
- 2Every queued scan is sent to BrightStar
- 3Each scan is applied to the ticket it belongs to
- 4It's recorded as having come in through the offline path
- 5The timestamp used is the moment the guest actually scanned in, not the moment it synced
Why the timeline still tells the truth
It would be easy for a system like this to record scans as happening whenever they finally reach the server, but that would quietly rewrite your night. If forty people came through during a ten-minute dead zone and their scans all landed at once when the signal returned, your check-in timeline would show a crowd arriving that never actually gathered at once.
BrightStar avoids that by keeping the real scan time attached to the scan itself. So when you look back at when people actually walked in, whether that's for your own sense of how the door ran or just to understand your arrival pattern, the timeline reflects what really happened at the door, not what happened to your Wi-Fi.
Knowing what your scanner is doing
An operator standing at a door with a device that's gone quiet needs to know two things: is it still working, and is anything piling up behind it. The scanner tells you both. It shows when it's working from its local, offline copy rather than checking live, and it shows how many scans are still waiting to go out.
That visibility is the difference between confidence and guessing. You're not wondering whether the tap you just felt actually registered — the device tells you it did, and tells you it's holding onto it until it can send it home.