A guard can be on time every shift, never miss a patrol scan, never draw a complaint, and still be doing the job badly. A security post inspection is where the paper version of your service meets the real one.

A post inspection checks four things: the guard, the post, the equipment, and the paperwork. Run both kinds. Announced visits set the standard and give you time to coach. Unannounced visits tell you what the 3am version of the post looks like. Write down what you found and what you did about it, or the whole exercise is theater.

Why run both announced and surprise inspections?

They answer different questions, and neither one substitutes for the other.

An announced visit measures the ceiling. The guard knows you are coming, so uniform, kit and log book should all be right. If they are not right on a day the guard was warned, you have found something serious in ten seconds.

Announced visits are also the only ones with room in them for real training. You can walk the route together, work through a scenario, review the post orders line by line, and let the guard raise the things they have been putting up with for six months.

A surprise visit measures the floor. Is the guard at the post. Are they awake. Is the phone in a pocket or in their hand. It also does something an announced visit cannot: it makes every shift a possible inspection, which is the actual mechanism by which standards hold.

How often?

New guards and problem sites: weekly, until performance settles
Stable sites, established guards: announced every two to four weeks
Every site, including the good ones: unannounced at random intervals, including nights and weekends

That last line is the one operators skip. A high-performing site left alone for a year quietly becomes a site where nobody checks, and the guards work it out faster than you do. If your night posts never get visited, read what actually happens on an overnight before you assume they are fine.

What do you check on the guard?

The inspection starts before you get out of the car. Did the guard notice you arrive? A guard who clocks an unfamiliar vehicle entering the lot is demonstrating exactly the awareness you are there to measure.

At post. Actually there, actually in the position the post orders describe.

Appearance. Full uniform, correct components, clean, ID visible. Measured against a written standard, not your mood.

Equipment. Flashlight works. Radio charged and on the right channel. Keys accounted for. PPE present.

Knowledge. Ask, do not assume. Who do they call for a medical? Where is the fire panel? What is the route and how often?

Engagement. Positioned to see what they are supposed to see. Not parked behind a monitor showing something else.

Grade appearance against your written uniform standard and knowledge against the post orders as written. If the guard cannot answer a question and the post orders do not answer it either, that is your finding, not theirs.

One caveat on alertness. A guard who is sharp while you are standing there may be asleep at four. Unannounced visits are the only real evidence, and a lone overnight post also deserves a welfare check-in schedule rather than just an occasional pop-in.

What do you check on the site?

Half of what limits a guard's performance is not the guard. It is the post they were handed.

The post itself

Clean and organized, or accumulating the clutter of six months of nobody caring
Lighting good enough to observe the area and write a report
Heat, cooling, and somewhere to sit that is not a milk crate
Log books, report forms, first aid kit stocked and reachable

The security equipment

Infrastructure fails quietly. Nobody gets an alert when a camera stops recording.

Cameras: pull up a live view and confirm the recorder is actually writing
Access control: test a card, test a denied card
Alarms and panic buttons: test them on a schedule the client agreed to
Radios and chargers: check the ones in the cradle, not just the one in the guard's hand

The building

Doors that do not latch. Lights burned out along the route. A fire exit with a pallet in front of it. None of these are your guard's fault, and all of them are your liability once you have seen them and said nothing. Photograph, report to the client in writing, track to resolution. If the site needs a broader look than a post visit gives you, run a full physical security audit.

What do you check in the paperwork?

Documentation is the version of the shift that survives. When a claim lands eight months later, the log entry is the whole case.

The log

Read the last seven days, not the last hour. Look for the four-hour gap with nothing in it, the entries all written in the same pen at the same slant, and the handoff notes that say "all quiet" every single shift. A DAR with a defined format makes this reviewable in two minutes instead of twenty.

Patrol records

Were the required tours done, at roughly the intervals the post orders call for, and do they show observations rather than just completions? A tour with perfect scan timing and zero observations is usually a guard walking a route without looking at anything. Checkpoint scans prove presence. They do not prove attention, and where the checkpoints sit decides how much they are worth.

Incident reports

Every incident actually written up, including the ones that resolved themselves
Submitted the same shift, not three days later from memory
Notifications made to whoever the escalation path names
Follow-up actions closed out rather than left open forever

Weak incident reports do not hurt on the day. They hurt in a deposition. What a report needs to contain is worth training against directly.

What do you do with what you find?

An inspection with no follow-up teaches the site that inspections do not matter. Sort findings into three buckets before you leave.

Fix it now

Untidy post, radio on the wrong channel, log entries in the wrong format, a supply that ran out. Correct it on the spot, explain why the standard exists, note it, and check it next visit. Do not escalate a charging cable into a disciplinary file.

Act immediately

Asleep on duty. Absent from post. Falsified patrol records. Impaired. These are not coaching moments.

Document with photographs and specific, timed observations before you say anything.
Take the corrective action your policy requires, up to removing the guard from post that hour.
Arrange coverage before you remove anyone. The post does not go dark because you found a problem.
Notify the client where the contract or the severity requires it.
Apply the same consequence you applied the last time. Inconsistency here is how you lose a wrongful termination claim.

Send it to the client

Client-side deficiencies go out in writing, promptly, and in a tone that reads as help rather than blame. Photograph, describe, track, record the response. When a client repeatedly ignores a safety or infrastructure failure, keep escalating in writing. That paper trail is what separates "we told them" from "we should have told them."

Run the same inspection form at every site so findings roll up into a pattern instead of a pile. One guard with a scruffy uniform is a coaching conversation. Six sites under the same supervisor with scruffy uniforms is a supervision problem, and you will only see it if the data is comparable. The same logic applies at shift handoff, which is the other moment where standards either transfer or quietly do not.

Key Takeaways

Announced visits measure the ceiling and buy time to train. Unannounced visits measure the floor.
Inspect every site unannounced, including the ones that never give you trouble.
Check the guard, the post, the equipment and the paperwork. Half of what limits a guard is the post.
Read a week of the log, not the last entry. Gaps and identical handoff notes are the tells.
Sort every finding into fix-now, act-now or send-to-client, and use one form everywhere.