A security patrol report is the record that proves a guard actually walked the site. It documents where they went, when they got there, and what they found along the way. Without it, a patrol is just a claim. With it, you have verifiable evidence that the checkpoints were covered, the round was completed, and any issue was seen and logged.
The value of the report depends entirely on what it records. A report that says “all clear, 10pm” proves nothing; the guard could have written it from the gatehouse. A report that ties each checkpoint to a GPS location, a scan time and a photo is evidence. This guide sets out the seven things every security patrol report must record, and how a digital patrol makes each one verifiable.
Why the security patrol report matters
A patrol report answers three questions that clients and courts both ask. Did the guard cover the whole site, or just the easy parts? When exactly were they at each point? And what did they do about anything they found?
The report matters most when something goes wrong. If a break-in happens between two checkpoints, the report shows whether the round was on schedule or whether a section was skipped. If a client disputes that the site was patrolled at all, the report is the proof. This is why proof of patrol is a real requirement, not a formality: it is the difference between a defensible service and a guard’s unverified word.
The 7 things every security patrol report must record
- Guard and shift – who patrolled and on which shift, so the round is attributable.
- Date and start and end times – when the patrol began and finished, from the waypoint start and end times, not a figure written afterwards.
- Checkpoints visited – each checkpoint on the route, confirmed by a QR scan so the guard had to be physically present to log it.
- Time at each checkpoint – the scan time at each point, which shows the round was walked in sequence and on schedule.
- GPS location – the location captured at each scan, tying the guard to the place, not just the time.
- Verification media – a selfie or photo where required, adding a further layer of proof.
- Observations and issues – anything found on the round: an unlocked door, a hazard, a suspicious person, with the action taken.
AVES patrols capture exactly these: checkpoints visited with GPS location and scan time, a QR code at each point, an optional required selfie, waypoint start and end times, and the total distance covered. That last figure, total distance, is a quiet but powerful check: a full round covers a known distance, and a short one shows on the record.
How a digital patrol report is verified
A paper patrol log can be written anywhere, which is precisely its weakness. A digital patrol removes the ability to fake it. The guard must scan a QR code fixed at each checkpoint to log it, and the scan captures the GPS location and the exact time automatically. Where a selfie is required, the guard cannot log a point without it.
The result is a report that is verifiable rather than merely claimed. A supervisor can see the route as it was actually walked, the time spent, the distance covered and any gaps. For the full patrol and checkpoint workflow, see the AVES guard tour system. For why unverified patrols are a genuine liability, see missed patrol verification.
Common security patrol report mistakes
Written from the gatehouse. A report completed without walking the round proves nothing. QR scans at fixed points remove this.
No time per checkpoint. A single end-of-round timestamp hides whether the patrol was on schedule. Each checkpoint needs its own scan time.
No location. A time with no place does not prove the guard was where they should have been.
Skipped checkpoints not flagged. A report that silently omits a missed point is worse than one that records the gap.
Vague observations. “All fine” is not an observation. Note what was checked and anything found.
Security patrol report checklist
- Guard and shift recorded.
- Patrol start and end times captured automatically.
- Every checkpoint confirmed by a scan at the point.
- A time recorded at each checkpoint, not just at the end.
- GPS location captured at each scan.
- Selfie or photo verification where required.
- Observations and actions logged.
- Total distance or route completeness visible, so gaps show.
Frequently asked questions
What is a security patrol report?
A security patrol report is a record proving a guard patrolled a site, documenting the checkpoints visited, the time and location of each, and any issues found. It is used as proof of patrol for clients, insurers and investigations.
What should a security patrol report include?
The guard and shift, start and end times, each checkpoint with its scan time and GPS location, verification media where required, and observations with actions taken.
How do you prove a patrol actually happened?
By tying each checkpoint to a QR scan that captures the GPS location and time automatically, so the guard must be physically present to log it. A single written “all clear” does not prove a patrol.
What is the difference between a patrol report and a daily activity report?
A patrol report covers a specific round and its checkpoints. A daily activity report summarises everything across a shift. The patrol report feeds the wider activity record.
Can a digital patrol report be faked?
It is far harder. Because a checkpoint is only logged when the guard scans a fixed QR code, and the scan captures location, time and often a selfie, a report cannot be completed without being at the points.
Give your patrols proof, not just a signature
If your patrol reports are still handwritten logs, you cannot prove the round was walked. AVES patrols log each checkpoint by QR scan with GPS, time, an optional selfie and the total distance covered, so every report is verifiable.
Book a 30-minute demo and we will show you the actual patrol and checkpoint screens: Book a demo.
Prefer to explore first? Start a free account.
Follow AVES on Instagram.