Guard patrols that cannot be proven did not happen: how to evidence patrols
A patrol is only evidence if it records who, where and when independently of the guard's own word: a scanned checkpoint tag (QR or NFC) at each point, an automatic timestamp, and photos of anything found. Paper logs signed at the end of a shift do not survive a client dispute or an inspector; a checkpoint record does.
The problem with paper
Paper patrol sheets are filled in at the desk, in a block, often by the supervisor. They prove the sheet exists, not that the patrol happened. When a client asks whether the loading dock was checked at 2am on the night of the theft, a signature at 6am answers nothing.
What defensible evidence looks like
Checkpoint tags fixed at the points that matter (plant rooms, back gates, car park corners). The guard scans each one; the system records the tag, the guard, the time and the order. Missed points show as missed. Anything unusual is photographed on the spot and attached. The record is written once and cannot be edited afterwards.
Sealed records
The audit trail must be tamper-evident: each entry chained to the one before, held on a server the guard cannot reach. If a record could be deleted, it is not evidence. This is the difference between a logbook and a system.
Doing it without new hardware
Guards' phones are the scanners; printed QR tags cost pennies. WolfGuard prints the tags, records the scans, shows missed checkpoints on the command centre and keeps the sealed audit trail, with no devices to buy.
Related: ISO 23601 evacuation plans | How to make a fire evacuation map for a school or office in one day | Fair overtime allocation for security and shift staff | Security guard management software in Kuwait and the GCC