Patrol procedures protocol template for guards

Anyone can walk a building. Patrol procedures are different: a repeatable sequence, a set of things you are looking for, a record of what you found, and a rule for what happens next. Adapt what follows into your own post orders.

What are patrol procedures for?

To make one guard's patrol look like every other guard's patrol. Consistent coverage, observation, documentation and response. A client who gets different service on Tuesday nights than on Saturdays does not have a security program. They have five people with different habits.

What has to happen before the patrol starts?

Five minutes at the top of the shift saves an hour later. Complete all of this before leaving the post.

1. Equipment check. Radio, flashlight, spare batteries, keys, phone, and any PPE the site requires. Test them, do not just locate them.
2. Post orders review. Confirm the current route and any special instruction for this shift. Instructions change without anyone announcing it.
3. Comms check. A live test with dispatch or base. A radio that powers on is not a radio that reaches anyone.
4. Recent activity review. Read the last two shifts of logs. Anything ongoing, anything the previous officer flagged, anything the client called about.
5. Conditions check. Weather that changes the walk: ice on the dock ramp, a wet lobby floor, fog that takes out your camera coverage.

Step four is where most sites leak information. If the previous officer's observations are on a clipboard in a drawer, nobody is reading them. Getting the handoff into a record the next officer opens is the subject of the shift handoff SOP.

How much should a patrol route vary?

Enough that nobody can set a watch by it. A route walked in the same direction at the same minute every hour is a published timetable for anyone who watches the property for a week.

The tension is real, though. Checkpoint sequence is often fixed by the client's requirements or by the building itself. So vary what you can and leave the rest alone.

• Alternate the starting point where the post orders permit it
• Move the timing inside the acceptable window instead of hitting the hour exactly
• Reverse direction occasionally
• Take a different path between the same two checkpoints

Frequency is the other half of the design, and it comes off the site's risk profile rather than off a template. The figures below are ranges operators commonly write into post orders, not a standard. Set yours from the site's incident history and the contract.

Where the checkpoints sit matters more than how many there are. Choosing checkpoint locations covers picking points that force the officer past the things that actually go wrong, and building routes that repeat on schedule covers wiring the sequence together.

How do you observe instead of just walking?

Four moves, in order, at every stop. Call it whatever helps you remember it. The sequence is the part that matters.

Comparison is what separates an experienced officer from a new one, and it is the one step no software does for you. The officer who noticed the same vehicle in the same corner of the deck three nights running is doing the actual work.

Security concerns

• Doors or windows unsecured that should be locked
• Signs of forced entry or tampering at frames, strikes and locks
• People in restricted areas, including staff who wandered
• Vehicles and packages that do not belong where they are
• Alarm panel status that changed since the last round
• Cameras moved, turned, obstructed or fogged

Safety hazards

Two items on this list are federal requirements rather than housekeeping, and it is worth knowing which. Under OSHA 1910.37, exit routes must be free and unobstructed, with no materials or equipment placed in them permanently or temporarily, and fire doors and other emergency safeguards must be in working order at all times. Under OSHA 1910.157, extinguishers must be readily accessible, fully charged, kept in their designated places, and visually inspected monthly.

• Wet floors, spills, trip hazards
• A pallet, cart or box parked in an exit route, even "just for tonight"
• A blocked extinguisher, or one missing from its bracket
• Burned-out lights in stairwells and parking areas
• Propped fire doors
• Damaged railings, treads or walkways
• Unusual odors: gas, smoke, chemical, hot electrical

Facility conditions

• Water leaks, standing water, active flooding
• HVAC running wrong or not at all, especially where it protects equipment
• Machinery running that should be off
• Overflowing trash or sanitation problems
• Vandalism and fresh graffiti

Facility conditions are the category guards under-report, because it feels like somebody else's job. It is also the category clients notice, since a leak found at 0300 costs a fraction of a leak found at 0800.

How do you prove the patrol happened?

The client will ask, and "I walked it" is not an answer that renews a contract. Each method proves something slightly different, so pick for what you need to demonstrate.

Most operations end up pairing two: a tap for the timestamp, a photo for the condition. There is more on the tradeoffs in using NFC checkpoints to prove the patrol happened.

What does a usable log entry look like?

Every entry carries five things: the exact time, the specific location, what you observed in factual terms, what you did about it, and what still needs doing.

The second one is worse than nothing. It creates a record that the stairwell was fine at 0230. If the door was propped and nobody wrote it down, that entry is now evidence against you.

The same standard applies to anything that escalates into a formal report. Writing incident reports people actually read covers the longer form, and the daily activity report template covers where routine entries land.

What do you do about what you found?

This is the part that turns observation into security. Every finding gets a priority, and the priority sets the response before the officer has to decide anything.

Who gets called at each level, and how long before it moves up a rung, belongs in a written escalation matrix rather than in anyone's memory.

If you discover a breach in progress

1. Stop and assess from distance. Do not close.
2. Do not enter if the threat may still be inside.
3. Radio for backup and law enforcement before anything else.
4. Keep eyes on the area if you can do it from cover.
5. Record descriptions: people, clothing, vehicles, plates, direction of travel.
6. Preserve the scene. Do not touch the point of entry.

What changes at night, and what changes in a vehicle?

The protocol is the same. The conditions are not.

On foot at night: use the flashlight deliberately rather than constantly, let your eyes adapt before entering a dark area, check behind and above rather than only ahead, stay conscious of your silhouette against a lit doorway, listen for what daytime noise normally hides, and slow down at blind corners and stairwell landings. Fatigue is its own hazard on a night rotation, and staying sharp on night patrol covers managing it.

In a vehicle: walk around it before and after the patrol, get out at every secured area rather than driving past, park so you can observe while writing, record start and end mileage, and report any mechanical issue the same shift. The drive-by is the single most common way a mobile patrol contract quietly stops being worth what the client pays for it. Fleet standards and inspection routines sit in mobile patrol fleet management.