Why "are they doing a good job?" is the wrong question
Guard services are bought in hours and judged on impressions. Nothing happened last month, the officers seem professional, the invoice arrives on time — so the service must be working.
That reasoning holds right up until someone challenges it. A break-in on a night that should have been covered. An insurance adjuster asking for the patrol log. A tenant's attorney asking what security was actually provided on the property. At that point the question stops being whether the service felt adequate and becomes whether you can show what was done.
Most arrangements fail that second question, and not because anyone was dishonest. They fail because nobody ever built a record capable of answering it.
This is worth taking seriously at the scale involved. Private security is one of the largest occupations in the country — the U.S. Bureau of Labor Statistics counts roughly 157,200 openings for security guards and gambling surveillance officers each year, with a median annual wage of $38,020 as of May 2025. An enormous amount of money changes hands for work that, in most contracts, produces no independently verifiable output at all.
The assessment measures one thing: whether the work leaves evidence.
What the assessment scores
Fifteen questions, weighted, across five areas. Each question is answered Yes, Partly, or No — and "I don't know" counts as No, because from an evidentiary standpoint there is no difference between a record that does not exist and one nobody can produce.
| Area Weight What it asks about | | |
|---|
| Defined tasks | 18 pts | Whether the work is specified before the shift — checkpoints, frequency, versioned instructions |
| Patrol proof | 23 pts | Whether a completed check is tied to a place and a time by something other than a person's word |
| Missed-round visibility | 24 pts | Whether a gap surfaces on its own, and whether the client sees it too |
| Incident records | 19 pts | Whether events are captured with enough detail and kept long enough to be useful later |
| Management and client review | 16 pts | Whether anyone reads the records, and whether the buyer can reach them independently |
Missed-round visibility carries the heaviest weight, and that is deliberate. A patrol record that only contains the rounds that happened is a marketing document. A patrol record that also shows the rounds that did not happen is evidence.
The exact weights differ slightly between the client and provider versions, because the two sides have different things to prove.
The five areas, and what a strong answer looks like
Defined tasks
The baseline is a site-specific document listing every point an officer has to reach, how often, and what to check at each one. Not a service description. Not "patrol the property."
If that document does not exist yet, building it is the prerequisite for everything else on this page — our free security patrol plan generator produces one from your site type, square footage and staffing, and checks whether the route actually fits the shift.
This area also asks whether the document is dated and versioned. That sounds bureaucratic until an incident from four months ago is under review and nobody can say which version of the instructions applied that night.
Patrol proof
A checkbox confirms that somebody wrote something down. It does not confirm where they were standing.
Strong answers here mean each visit is anchored to a location or a scan at a fixed marker, with the time captured by the system rather than typed in afterwards. The distinction matters more than it sounds: rounds logged at exactly 1:00, 2:00 and 3:00, in identical handwriting, were written at the end of the shift. We cover the mechanics in more depth in why patrol verification checkpoints matter.
Missed-round visibility
A patrol record is proof only if a missed round would show up in it.
This is the single most common blind spot. Plenty of services produce a record of completed patrols. Far fewer produce a record where an incomplete shift is visible without anyone choosing to report it. And fewer still make that visible to the client rather than only to the supervisor.
The failure pattern is well documented and rarely dramatic — it is described in why security guard accountability breaks down when patrol systems fail.
Incident records
An entry in a daily activity report saying "checked rear gate, all secure" is not an incident record. A usable one carries the time, the location, a description, photographs, and the identity of whoever recorded it — captured when the thing was found, not reconstructed at the end of the shift.
Retention matters just as much as content. A record that is deleted after 30 days is unavailable exactly when a claim or a dispute reaches the stage where it would matter. The reasoning is set out in why incident reports without verification fail security audits and, for the longer-horizon view, in what a patrol audit trail actually has to contain.
Management and client review
Records nobody reads change nothing. This area asks whether a named person reviews the patrol history on a schedule, whether the client can reach it directly rather than waiting for a monthly summary, and whether the data is fed back into the assignment when the same problem keeps appearing.
For buyers there is one more question here that catches people out: can you export your own patrol and incident records and keep them after the contract ends? Records that live only inside a provider's system leave with the provider.
What your score means
| Score Band What it means | | |
|---|
| 81–100 | Verifiable | You can prove the service you are paying for. Most of what happens on site leaves a record that holds up when someone asks for it. |
| 61–80 | Mostly documented | The core of the service is recorded, but there are points where verification depends on a person rather than a record. Those are the points that fail under pressure. |
| 41–60 | Trust-based | You are buying hours and assuming they contain patrols. The assumption may well be correct — it just cannot be checked. |
| 0–40 | Unverifiable | If an incident were reviewed tomorrow, there would be no defensible record of what was or was not done. |
Most arrangements land in the middle two bands. That is not a scandal. It is what happens when a service is specified in hours and never re-specified in evidence.
Turning the score into a dollar figure
The score answers how much of your guarding is verifiable. The obvious follow-up is what the unverifiable part costs.
Each band maps to a suggested record rate — the share of required patrols that produce a record you could actually show someone:
| Band Suggested record rate | |
|---|
| Verifiable | 90–100% |
| Mostly documented | 70–90% |
| Trust-based | 40–70% |
| Unverifiable | Under 40% |
Take that percentage to the spend estimate in how to verify the guard service you are paying for, where you can put it against your monthly guarding spend. The assessment result page links straight through with the number pre-filled.
If you are earlier in the process and still working out what the service should cost, start with the security guard cost calculator, which breaks down wage, burden and margin by state.
If you provide guard services, run it on yourself first
Every buyer-side question in this assessment has a provider-side twin, and the provider version is the more commercially useful of the two.
A client who starts doubting a service almost always asks the same thing: show me last Tuesday night. Whether you can answer that within a working day — precisely, without a scramble — decides more contract renewals than any capability statement.
Running the assessment on your own operation tells you where that request would find you. It also tends to reframe the conversation with clients: a provider who arrives with a verifiability score and a plan to raise it is in a different position from one defending a monthly report.
The industry-level framing is worth reading alongside this. ASIS International, the accredited standards body for the profession, publishes standards and guidelines covering private security officer programs that address selection, training and program evaluation — the organizational layer this assessment scores from the outside.
What this assessment is not
It is not a site risk assessment. It says nothing about whether your checkpoint coverage is adequate for the threats your property faces — that is a different exercise, and it starts with a walk of the site.
It is not a judgment about honesty. A completely diligent provider with paper logs will score in the trust-based band. The score measures evidence, not integrity, and the two are not the same thing.
It is not a compliance determination. Patrol frequency and record-keeping requirements may be set by your contract, your insurance carrier, or the authority having jurisdiction, and those override anything scored here.
The underlying reasoning — why verification, transparency, context, consistency and accountability form the operational basis for all of this — is set out in the science of security patrols.
Closing the gaps the score finds
Most of the points lost in this assessment come down to one structural fact: the patrol produces no independent record. Everything downstream — the missed-round question, the incident evidence question, the client access question — follows from that.
Closing it does not require new hardware. A guard tour system records each checkpoint visit with a timestamp and a verified location from the phones officers already carry, logs incidents with photographs at the moment they are found, and makes missed rounds visible in the patrol history rather than in a conversation.
Frequently asked questions
What is a security guard audit checklist?
A security guard audit checklist is a structured set of questions used to evaluate a guarding arrangement against defined criteria rather than general impressions. Most published checklists are supervisor-facing and cover an officer's appearance and conduct on post. This one is different: it evaluates the arrangement itself — whether the work is specified, recorded, reviewed and provable — and returns a score rather than a list of ticks.
How do I audit my security guard company?
Start with what can be produced rather than what is promised. Pick a past night at random and ask for every round from it. Ask where a missed round would appear. Ask how incidents are documented and how long records are kept. Ask whether you can reach the records yourself. The 15-question assessment on this page turns those questions into a weighted score across five areas.
What should a client measure in a guard service contract?
Completed rounds against required rounds, missed and late rounds, incident count and response time, and record retention. These are measurable, and they are the figures that matter when a claim, a dispute or a renewal puts the service under review. Hours on site and headcount are inputs, not performance.
Is a paper patrol log enough?
A paper log is documentation, and it can be entirely accurate. What it generally cannot do is demonstrate that a specific check happened at a specific place and time, or reveal a round that was never walked. For contractual and insurance purposes, the gap between recording and evidencing is where most disputes are decided.
What score should I be aiming for?
Anything above 80 means the service is verifiable end to end. Between 60 and 80 the core is documented but there are single points of failure. Below 60, verification depends on trust — which may be well placed, but cannot be demonstrated to a third party.
Does this work for in-house security teams?
Yes. Use the provider version. An in-house team faces the same evidentiary questions as a contractor, usually from risk management, insurance or legal rather than from a client.
Is the assessment free?
Yes. The score, the band and the five-area breakdown appear on screen with no sign-up. The full PDF report — including every question where points were lost and what a verifiable version of it looks like — is emailed after you provide your name and work email.
A patrol verifiability assessment scores how provable a guarding arrangement is, rather than how competent the officers are. It measures five areas — defined tasks, patrol proof, missed-round visibility, incident records, and management and client review — and returns a score from 0 to 100 with a matching band: verifiable, mostly documented, trust-based, or unverifiable. The score maps to a suggested record rate, which is the share of required patrols producing evidence that could be shown to an insurer, a client, or a court. The assessment runs from either the buyer's or the provider's perspective and treats "I don't know" as a negative answer, since an unproducible record and a missing record are evidentially identical.
Gyula Györfi — Founder of Trinity Guard®
Former police commander with 26 years of security operations experience, including the protection of diplomatic facilities and 18 years in command roles. Trinity Guard® has been developed since 2022 around one principle: a patrol is only worth what its execution can prove.
Author profile →
Turn the audit result into verifiable patrol proof.
Use the gaps in your score as the starting point, then test a phone-based patrol verification workflow on a real site for 14 days.
