A guard tour system (also called a guard tour patrol system or watchman clock system) is the technology a security company uses to prove patrols actually happened. At its core it answers three questions: did the guard go where they were supposed to go, when were they there, and what did they find? Everything else — dashboards, reports, alerts — is built on those three answers.

From watchclocks to smartphones

The original guard tour system was the mechanical watchclock: a guard carried a clock on a strap and turned keys chained to checkpoints around the property, punching a paper tape. The concept hasn't changed in a century — only the proof has. Keys became iButtons, then barcodes, then QR codes and NFC tags, and the paper tape became a cloud timeline with GPS coordinates attached. Modern systems run entirely on the guard's smartphone, which matters because hardware-free deployment is what makes the technology affordable for small and mid-size operators, not just enterprise contracts.

How checkpoint verification works

Checkpoints are fixed verification points placed along a patrol route — stairwell doors, parking levels, fence lines, server rooms. The guard scans each one as they pass, and each scan records who scanned, where, and at what time. Three technologies dominate:

QR code checkpoints

A printed QR sticker at each point, scanned with the phone camera. Cheapest to deploy — print and stick — and easy to replace. The main criticism is that a photo of the code could be scanned from anywhere, which is why a serious system pairs every scan with the phone's GPS position: a QR scan that happens 400 meters from the checkpoint gets flagged, not counted.

NFC tag checkpoints

A small contactless tag the guard taps with their phone. Tags can't be photographed or photocopied, survive weather better than stickers, and the tap requires physical presence within a few centimeters. Slightly higher cost per point, and the guard's phone needs NFC — which virtually every modern smartphone has.

GPS verification

The phone's location stream itself, used two ways: geofencing (confirming the guard is on-site when they clock in or scan) and breadcrumb trails (recording the patrol path between checkpoints). GPS alone can drift indoors, which is why the strongest setups combine GPS for the route with QR/NFC for the fixed points — each covers the other's weakness.

Bottom line: QR is the cheapest to roll out, NFC is the hardest to fake, and GPS ties the whole patrol together. Most operators end up using all three.

What a guard tour system actually gets you

  • Proof of service — time-stamped, location-stamped patrol records you can hand to a client instead of asking them to take your word for it.
  • Missed-patrol detection — the system flags a skipped checkpoint or an overdue round while the shift is still running, not in next week's review.
  • Liability protection — when something goes wrong at a property, the patrol record establishes what your guards did and when. Negligence claims live or die on this.
  • Guard accountability and safety — supervisors can see that a lone guard on an overnight is moving and checking in, and act when they aren't.
  • Contract retention — transparent reporting is the difference between a client who trusts the invoice and one who shops competitors at renewal.

Beyond live tracking: shift replay

Live maps tell you what's happening now. The newer capability worth asking about is shift replay — the ability to scrub back through a completed shift and watch the route play out: where the guard was at 3:12 AM, how long they spent at the loading dock, which checkpoints were scanned in what order. For incident investigations and client disputes, replay turns an argument about what happened into a recording of what happened. (This is a core feature of ShiftsGo's telemetry.)

How to choose a system

  1. Phone-based, not proprietary hardware. Dedicated patrol wands still exist, but they're an extra device to lose and a cost that phone-based systems eliminated.
  2. GPS-validated scans. Ask specifically whether checkpoint scans are cross-checked against location. If not, the proof is weak.
  3. Real-time exceptions, not just reports. A missed checkpoint should generate an alert tonight, not a line in a monthly PDF.
  4. Reporting your clients will actually read. Look at the client-facing output before you buy. If it takes a training session to interpret, it won't build trust.
  5. Integrated with scheduling and attendance. Patrol data is most useful when it lives next to who was scheduled, who clocked in, and what they logged — one system, one timeline, one source of truth.
  6. Honest pricing. Per-guard pricing punishes growth; flat tiers with usage quotas are easier to forecast against a contract's margin.

Rollout advice from the field

Don't deploy to every site at once. Pick one contract, map its patrol route, place checkpoints at the spots that matter to the client (not just the easy ones), and run it for two weeks. Use the first client report as a sales asset for the next site. Guards adapt quickly when the system replaces paperwork instead of adding to it — the resistance comes when scanning feels like surveillance on top of existing busywork, so retire the old forms the same day the scans go live.