How to prove patrols actually happened

Every security company says its officers patrol the site. The ones that keep the contract can prove it. As clients get more sophisticated — and as their own auditors, insurers and boards ask harder questions — the burden of proof has quietly shifted from the buyer to the provider. If you can't show the patrol happened, in the client's eyes it may as well not have.

This guide walks through why the traditional proof no longer convinces anyone, what genuinely credible evidence looks like, and how to package it so it becomes a reason clients renew rather than a box they tick.

Why "we were there" isn't enough any more

For years, patrol assurance meant a signed paper log in a folder by the door, or a line on an invoice. Both are trivially easy to fill in from the mess room at the end of a shift, and everybody knows it. A client who has been burned once — an incident on a night the log says was patrolled, an empty guardroom caught on their own CCTV — stops trusting the paperwork entirely.

Three things have changed the expectation at the same time:

• Clients have their own scrutiny. Facilities directors answer to auditors, insurers and boards who want evidence, not assurances. Your proof becomes their proof.
• Everyone has a camera and a clock. When a smartphone can timestamp and geo-tag a photo in seconds, an unverifiable tick-box looks careless by comparison.
• Price alone stopped being the whole story. When two providers cost roughly the same, the one who can show the work done wins on trust — and trust is what survives a bad month.

The problem with NFC and QR tags

The common upgrade from paper is to stick NFC or QR tags around the site and have officers scan them on their rounds. It's a step forward — it timestamps a scan — but it's important to be honest about what a scan actually proves, because a sharp client will be.

A tag scan tells you a phone was held near a tag at a moment in time. It does not tell you:

• That a person was genuinely present and alert — a tag can be scanned in five seconds on the way past, or scanned from a photo of the tag taken earlier.
• What the area was actually like — whether the fire door was propped, the stockroom was secure, the tap was left running, the car park was clear.
• That anything was checked at all — the scan is a location ping, not an observation.

Tags also fail in the real world: they get painted over, ripped off, go missing, or sit in a spot with no signal. When the one piece of evidence you have is a scan that didn't register, you're back to "trust us". Scanning has its place as a lightweight prompt, but built as the whole proof it's a thin story.

What good evidence actually looks like

Credible proof puts a person, in a place, at a time, seeing a specific thing. The strongest single artefact for that is a watermarked photo — a picture of the checkpoint or the condition, stamped with the context that makes it hard to fake and easy to trust:

• The officer — who took it, so it's attributable.
• The site and checkpoint — where exactly it was taken.
• GPS coordinates — confirming the device was physically at that location.
• A precise timestamp — the date and time burned into the image, not editable after the fact.
• The state of the area — the actual thing observed: the secured door, the clear loading bay, the fault that needs reporting.

Photos like this do something a scan never can: they carry the content of the patrol, not just its footprint. They show the client the fire exit was clear, the leak was spotted, the shutter was down. Stack a run of them across a shift and you have a timeline that's genuinely difficult to fabricate and immediately convincing.

Round it out with the supporting record — the route covered, patrols delivered against what the contract calls for, incidents with the time they were raised and resolved — and the picture is complete: not "we say we did it", but "here it is".

How to present it to clients

Evidence the client can't easily see is evidence that doesn't count. The mistake is to sit on a rich pile of proof and email a PDF once a month. The providers who win on transparency do the opposite — they hand the client the window and let them look whenever they like:

• A portal they log into. Their own login, ideally under your brand, where they can see the operation without booking a call or waiting for a report.
• Delivered vs contract, honestly. Show patrols delivered against what was agreed — and when a period is short, show that too. A portal that always reads 100% is one nobody believes.
• Photo evidence on demand. Let them open the checkpoint photo timeline themselves rather than requesting it. Self-service proof is worth more than any assurance you give in a meeting.
• Incidents in plain English. What happened, when it was raised, how fast it was dealt with — no jargon, no defensiveness.

Counter-intuitively, showing the client everything — including the imperfect bits — builds more trust than a polished summary. When they can see you're not hiding the misses, they believe the hits.

A checklist for tightening up your patrol proof

Whether or not you use a platform yet, you can raise the standard of your evidence with a few deliberate moves:

1. Decide what "proof" means per site and write it into the assignment instructions, so every officer knows the standard expected.
2. Make photos the backbone of each patrol, not an afterthought — a required shot at key checkpoints and of any issue found.
3. Watermark every photo with officer, site, checkpoint, GPS and timestamp, so each image stands on its own.
4. Capture the state, not just the scan — record the condition of the area, so evidence carries observation, not only attendance.
5. Log patrols against the contract so delivered-vs-required is always visible, not reconstructed at month end.
6. Record incidents with times — raised and resolved — so response performance is provable.
7. Give the client a live window into it, rather than a monthly PDF they have to chase.
8. Be honest about gaps. Show the misses and what you did about them; it's the fastest way to earn the benefit of the doubt.

How this wins — and keeps — contracts

Strong patrol proof stops being an operational detail and becomes a commercial weapon. In a tender, it's the thing you can demonstrate that the incumbent can't. In a renewal conversation, it's the reason a client who's being undercut on price stays anyway — they can see what they're paying for, and they don't want to go back to guessing. And when something does go wrong on site, verifiable evidence is what protects you: it shows what your team actually did, rather than leaving you to argue it after the fact.

This is exactly the ground Pulse is built for. Officers capture watermarked photo evidence at each checkpoint from the app; the operation is measured as delivered-vs-contract; and clients get a portal — under your brand — where they can open the proof themselves. The result is the quiet confidence that keeps contracts: the client stops asking whether the patrols happened, because they can already see that they did.

This guide is general operational guidance based on common practice in the UK security and facilities sector. Contractual, evidential and data-protection requirements vary — agree what evidence you capture and share with each client, and handle any personal data in line with your obligations.