A guard standing at a single gate is easy to verify โ you can see them. A guard responsible for patrolling a large campus, walking a perimeter, or checking multiple floors of a building is a different problem: how do you know they actually walked the whole route, and didn't just stay near the entrance? QR Code Patrol exists to answer exactly that question.
How a checkpoint works
An admin sets up fixed checkpoints across a site โ a QR code printed and posted at each spot a patrol route is supposed to cover: a stairwell, a back gate, a parking area, a rooftop access point. Each checkpoint's QR code is unique to that specific location and that specific site.
What happens when a guard scans
During their patrol, the guard opens the scanner in their mobile app and scans the checkpoint's QR code. The scan is validated the same way attendance punch-in already is: the guard's real GPS location at the moment of the scan is checked against that checkpoint's geofence, and a scan reporting a fake or mock GPS location is rejected outright โ never even recorded as an attempt. Only a scan that passes both checks is logged as a valid patrol visit.
Why this matters more than it sounds
Physical patrol logs โ a guard signing a logbook chained to a wall at each checkpoint โ have the exact same weaknesses as paper attendance registers: they can be filled in after the fact, or signed for a checkpoint the guard never actually reached. A QR scan validated against real-time GPS closes that gap the same way GPS attendance closes it for punch-in โ it turns "the guard says they patrolled the route" into a timestamped, location-verified record.
What the record actually shows
Every accepted scan is stored as an immutable log entry โ which guard, which checkpoint, what time. An admin or supervisor reviewing patrol logs can see exactly which checkpoints were covered during a shift, in what order, and whether any were missed โ useful both for day-to-day supervision and as evidence if a client ever asks whether a specific area was actually checked during a specific window.
Handling a lost or damaged QR sticker
A QR sticker posted outdoors can fade, peel, or get damaged. Rather than that becoming a dead checkpoint, an admin can regenerate the code for that checkpoint at any time โ a fresh sticker can be printed and posted, the old code stops working immediately, and the checkpoint's prior scan history is preserved rather than lost.
Conclusion
QR Code Patrol is a small, focused feature solving a specific, common problem โ proving a guard actually walked a patrol route, not just claims to have. By reusing the same geofence and fake-GPS validation that already protects attendance, it gives an agency owner or client a real, checkable record of patrol coverage instead of a logbook that could say anything.