The Root Problem: Patrols That Cannot Be Verified
Traditional patrol management relies on self-reporting. A guard signs a book at each station, writing the time they say they arrived. Management then has no way to distinguish an accurate entry from a hopeful one, or from a week of entries filled in on Friday afternoon.
This is not primarily a personnel problem. It is an information problem: when the only record is created by the person being measured, the record cannot be used as evidence. Everything below follows from fixing that.
The Seven Problems It Solves
- Unverifiable patrols. Every checkpoint read is an electronic event with a timestamp, recorded on a device the guard cannot edit. Service delivery becomes provable rather than asserted.
- Invisible missed checkpoints. Software compares actual reads against the scheduled route and prints a missed-checkpoint list. A supervisor sees the gap on Monday morning instead of discovering it during an incident review.
- Falsifiable logs. A timestamp written to non-volatile memory by a real-time clock cannot be backdated. Removing this option removes the temptation and the argument.
- Liability and dispute exposure. When a client alleges a patrol was skipped, or an incident occurs on an unvisited floor, the exportable record settles the question with data instead of testimony.
- Weak insurance and compliance evidence. Insurers and auditors increasingly expect documented patrol activity. Timestamped reports demonstrate due diligence in a way a signature sheet does not.
- Blind route planning. Actual read data shows which checkpoints are always late and which sections consume the most time per shift. Routes can then be rebalanced against reality rather than guesswork.
- Missing incident history. Event tags capture what the guard found — a propped door, a water leak, a burnt-out light. Over months this builds a maintenance signal that no one was previously recording.
What Changes Look Like in Numbers
The metrics that matter are simple. Once a system is running, most sites track the same four.
| Metric | What it tells you | Typical target |
|---|---|---|
| Patrol completion rate | Share of scheduled checkpoints actually read | 98%+ per shift |
| On-time arrival rate | Share of checkpoints read within the allowed time window | 95%+ |
| Missed checkpoint count | Absolute number of skipped points per period | Trending to zero |
| Incidents logged | Problems found and recorded on route | Rising at first, then stabilising |
What It Does Not Solve
- It does not stop a determined guard who carries a removed checkpoint tag with them. Mitigate this by using concealed RFID tags, and by varying route order.
- It does not improve the quality of an inspection, only whether it happened. If a guard walks past a hazard without noticing it, the system records a completed checkpoint.
- It does not replace supervision. Reports are a management input, not a management substitute — someone still has to act on them.