What is a guard tour?
A guard tour is a structured inspection of a site or a series of checkpoints by a security guard at defined intervals. The purpose is to deter unauthorised access, detect hazards or incidents, and provide documented evidence that the site was monitored. Guard tours are a core deliverable in most static guarding and mobile patrol contracts.
Client contracts often specify the number of tours per duty, the checkpoints to be covered, and the form of evidence required. A client paying for four tours per night is not simply paying for a guard to be present on site. They are paying for four documented inspections of agreed checkpoints at agreed times. The distinction matters when something goes wrong.
Why patrol accountability matters
Without documented evidence of patrol completion, a security company cannot prove to a client, insurer, or regulator that guards performed their contracted duties. If an incident occurs at a site during a duty period and there is no patrol log, the question “was a guard actually there and did they check the site?” cannot be answered with confidence.
This creates liability exposure for the security company and erodes client trust. Clients who cannot verify that patrols occurred have no way to distinguish a security company that delivers on its contract from one that does not. In competitive tender environments, verifiable patrol records are increasingly a differentiator.
Patrol accountability is also a welfare mechanism. When a guard is logging checkpoints in real time, supervisors know where the guard is. A guard who stops logging is detectable quickly, not discovered hours later.
Checkpoint design: where and how often
Checkpoints should cover all areas that the contract requires to be monitored: entry and exit points, high-value asset locations, vulnerable perimeter sections, and areas with prior incident history. The placement of checkpoints should be reviewed when a new client contract is set up and updated when the site risk profile changes.
The sequence and spacing of checkpoints affects guard safety. A predictable patrol pattern that exposes the guard to the same entry point at the same time each hour creates a vulnerability. Consider varying patrol routes and times where the site and contract allow, and flag to clients when a mandated sequence creates a foreseeable risk.
Tour frequency should be based on the risk profile of the site. A high-theft retail site at night needs more frequent patrols than a low-risk carpark during business hours. Document checkpoint placement and tour frequency decisions with reference to the risk assessment that supports them.
Traditional vs technology-based patrol systems
Physical logbook
The guard signs a logbook at each checkpoint. Simple and low-cost, but easy to falsify (a guard can sign all entries at the end of the duty), produces no real-time visibility for supervisors, and the paper record is vulnerable to being lost, damaged, or illegible. Retrieving a historical log from a paper system for an insurance or legal matter is time-consuming.
NFC and QR checkpoints
The guard scans a tag or QR code at each checkpoint with a mobile device, creating a timestamped digital record. This approach provides real-time patrol data and is significantly harder to falsify than a paper log: the guard must physically be at the checkpoint with their registered device. The records are stored digitally and can be retrieved immediately for client reporting or incident investigation.
GPS tracking
The guard's device location is recorded continuously or at intervals, providing a movement audit trail for the entire duty. GPS tracking combines well with checkpoint scanning: scanning proves “guard was here” at a specific point, while GPS shows how the guard moved between checkpoints. For mobile patrols covering multiple sites, GPS data can verify site-to-site travel and confirm that all contracted sites were visited.
Real-time operations visibility
A guard tour system that feeds data to a live operations dashboard gives supervisors the ability to see patrol progress in real time, not retrospectively. If a guard is overdue at a checkpoint, the supervisor can act before the tour is complete rather than reviewing a log the next morning.
Real-time visibility also supports welfare check integration. If a guard fails to log a checkpoint and then fails a welfare timer acknowledgement, the pattern is visible in one place and the escalation can begin immediately. Patrol accountability and lone-worker safety become part of the same operational picture rather than two separate systems a supervisor must monitor independently.
Incident reporting during tours
Guards conducting tours will sometimes identify hazards, suspicious activity, or incidents. A structured incident report filed at the time of observation is more reliable than a verbal handover at the end of the duty. Memory fades, details change, and a verbal account provides no independent record of the time the observation was made.
Digital incident reports attached to the patrol record, including timestamps and any relevant notes, give the client and the security company an accurate record of what was found and what action was taken. Define in advance which types of observations require an immediate notification to the client or supervisor, and which go into the end-of-duty report.
Clients often use incident reports from patrol duties to manage their own compliance obligations. A security company that delivers structured, timely incident reports is providing a service that goes beyond the patrol itself.
What to include in a client patrol report
At the end of each duty, the client should receive a record that confirms the contracted service was delivered. A complete patrol report includes:
- Guard name and duty period (start and end times)
- Each checkpoint with the scan or log time
- Any anomalies or incidents observed and the action taken
- Any access or security issues identified during the duty
- The guard's sign-off at the end of the duty
This report is the primary evidence that the contracted service was delivered. Many clients use patrol reports for insurance purposes, building management records, and compliance with their own regulatory requirements. The format should match what is specified in the client contract.
Audit-ready records for regulators and insurers
In the event of an incident or insurance claim, the patrol record becomes evidence. A record that can be questioned on its integrity (paper logs that could have been backdated, Excel sheets with no version history) provides weaker protection than a record with a verifiable chain of custody.
An audit-ready patrol record has four properties: it is timestamped at the time of the event, it cannot be retroactively altered without a trace, it is tied to a specific guard's account, and it can be accessed quickly without needing to recover a paper log from a filing cabinet.
Cloud-stored digital patrol records meet all four requirements and can be retrieved and shared with a regulator, insurer, or legal representative in minutes rather than days. They are also accessible remotely if a dispute arises while the original paper records are at another location.
Related resources
Frequently asked questions
Can clients see guard patrol records in real time?
Yes. OnDuty365 provides a live operations view where supervisors can see duty status, patrol progress, and any incidents raised during the duty. Whether clients have direct access to this view depends on the configuration the security company sets up for that client relationship.
What evidence do I need to provide clients after a patrol duty?
At a minimum: a record of who was on duty, the patrol checkpoints covered and times, any incidents or anomalies observed and the actions taken, and the guard's acknowledgement at the end of the duty. The specific format may be defined in your client contract. Digital records with timestamps are easier to retrieve and harder to dispute than paper logs.
How do I handle a checkpoint that a guard could not access during a tour?
The guard should log the inaccessible checkpoint with a note explaining why (locked door, area under maintenance, safety hazard) and the time of the attempt. This creates an accurate record rather than a gap in the patrol log. If the checkpoint is routinely inaccessible, notify the client and update the tour route documentation.