Technology · 9 min read
Guard tour system buyer's guide: GPS vs QR vs NFC vs beacons
How each checkpoint verification technology actually performs in the field, what each one proves in a dispute, and how to choose per site.
Key takeaways
- NFC proves physical presence best; GPS alone is the weakest evidence.
- QR is cheapest to deploy and easiest to defeat by photograph.
- Most mature programs mix technologies by site risk level.
- What matters legally is the timestamped chain, not the scan method.
What you are actually proving
A guard tour system exists to answer one question in a dispute: was an officer physically at this location at this time? Every technology choice is a trade-off between how strongly it answers that question and how much friction it adds for the officer.
GPS
Zero hardware, works anywhere outdoors, degrades badly indoors and in urban canyons. Accuracy of 10-30 metres is often sufficient for a large open site and useless in a multi-storey building. Best as a supporting signal rather than the primary proof.
QR codes
Cheap, printable, instantly replaceable. The weakness is obvious: a photographed code can be scanned from anywhere. Combine with GPS coordinates captured at scan time to close that gap.
NFC tags
The strongest routine evidence. The phone must be within centimetres of the tag, which cannot be defeated by a photograph. Tags are inexpensive, weatherproof and passive. This is the default recommendation for high-risk and litigated sites.
Bluetooth beacons
Useful for proximity-based automatic logging on large indoor sites, at the cost of battery maintenance and more complex deployment. Worth it for hospitals and airports where hands-free logging matters.
Choosing per site
Assign verification method by risk level rather than standardising company-wide. MerlynOps supports GPS, QR and NFC on the same tour, so a single route can escalate verification strength at the checkpoints that matter.
What clients actually want to see in the report
Clients do not want raw scan logs. They want a short answer to one question: was the site patrolled as contracted last month, and what happened when it was not? Coverage percentage, missed checkpoints with reasons, and incidents in context.
If your tour system cannot produce that page automatically, your supervisors are rebuilding it by hand every month — which is both a margin leak and a credibility risk when the numbers do not match.
Failure modes to plan for
Tags get painted over, removed during renovations or stolen. Phones lose signal in stairwells and basements. Batteries die. A tour system that treats every miss as officer failure will destroy trust with your officers within weeks.
Require offline capture with sync on reconnect, a documented exception reason, and a supervisor review queue. The goal is an honest record, not a perfect one.
Rolling it out without a revolt
Introduce tours at one site with a supervisor who supports the change. Explain to officers that verified scans protect them from false allegations as much as they prove service to the client — this is the argument that lands.
Set the first month as a baseline with no penalties, publish the results openly, then set expectations from real data rather than a number invented in a sales meeting.
