Free Security Patrol Plan Generator

What a security patrol plan has to contain

A patrol plan that holds up under review — from a client, an insurance carrier, or opposing counsel — contains seven elements. Anything less is a wish list.

The seventh element is the one almost every template omits — and it is the one that decides whether the other six survive contact with a real shift.

How many checkpoints does a site actually need?

There is no fixed ratio, but there is a workable starting point. Checkpoint count is driven by three things: the property's floor area, the number of separate structures and levels, and the fixed assets that have to be inspected regardless of size.

Typical starting density by property type:

Add one checkpoint per additional floor, and two per additional building. Then add the mandatory points for the property type — those are not negotiable against square footage, because a sprinkler valve does not care how big the warehouse is.

Below five checkpoints, a patrol plan stops being verifiable. Above roughly forty, officers start scanning to satisfy the system rather than inspecting to protect the site.

How often should officers patrol?

Patrol frequency is set by risk exposure and occupancy, not by habit. Properties in their high-risk window commonly run rounds every 30 to 60 minutes. Low-risk areas and occupied daytime hours are often covered every two to four hours.

Typical round counts per shift:

These are medium-risk figures. A low-risk site runs roughly a quarter fewer rounds; a high-risk site runs about 40% more. The generator applies the same adjustment, so the plan it builds will match this table for your inputs.

Your contract

If the client bought hourly rounds, hourly rounds is the requirement, whether or not the risk profile justifies it.

Your insurance carrier

Some policies condition coverage on documented patrol frequency. A denied claim traced to a missing patrol log is an expensive way to learn this.

The authority having jurisdiction

Fire watch assignments are the clearest case: the interval comes from the fire marshal's order, your impairment plan, or the ILSM program governing that building — not from an industry rule of thumb.

Why fixed patrol times defeat the patrol

A patrol that runs at 10:00, 11:00, and 12:00 teaches anyone watching exactly when the property is unobserved. After three nights of observation, the schedule becomes a map of your blind spots.

Every serious patrol plan is built to be unpredictable within a defined coverage guarantee. Three mechanisms do the work:

Time windows instead of clock times

The round starts somewhere between 10:05 and 10:35. The interval is maintained, the exact moment is not.

Alternating direction

Running the same route in reverse changes which points are checked early and which are checked late — without adding a single minute to the route.

Mandatory versus rotating checkpoints

Critical points are checked on every round. Secondary points rotate, with a guarantee that each one is covered at least once per shift. Coverage stays complete; the pattern does not.

The discipline here is that unpredictability cannot come at the cost of coverage. Randomizing without a coverage guarantee produces gaps rather than deterrence. The generator enforces both: it varies the schedule, then verifies that every selected checkpoint appears in the shift.

This is where most downloadable templates end and real patrol planning begins. A static spreadsheet cannot vary a schedule, and it cannot prove that the variation still covers the site.

Can the route actually be walked?

This is the question that separates a plan from a document.

The math is straightforward. Compare the time it takes to complete one round against the interval between rounds. If a single round takes 52 minutes and the plan calls for rounds every 45 minutes, one officer cannot hold that cycle. The plan either needs a second officer splitting the route, fewer checkpoints, or a revised interval.

Round time is the sum of four things:

• Travel time between checkpoints, estimated from site area and checkpoint count
• Inspection time at each point — 30 seconds for a door check, up to two and a half minutes for a mechanical room
• Vertical movement — roughly two minutes per floor transition on stairs
• Shift overhead — briefing, breaks, handover, and report time come out of patrol capacity before the first round starts

A twelve-hour shift does not contain twelve hours of patrol time. After briefing, meal and rest breaks, handover, and administrative time, the realistic figure is closer to nine and a half hours. Plans built against the raw shift length are over-scheduled by roughly twenty percent from the first day.

The generator calculates all four and returns one of four verdicts:

The middle band is the target. A plan running at 95% capacity has no room for the thing patrols exist to handle.

QR or GPS — choosing the verification method for each checkpoint

Checkpoints are only useful if the visit is provable. Two methods cover almost every site, and the choice is decided by the checkpoint's location rather than by preference.

GPS suits outdoor checkpoints with open sky: perimeter gates, yard areas, parking lots, fuel tanks, fence lines. The officer's coordinates at the moment of the check are the proof.

QR suits everything indoors and anything under a roof or structure: mechanical rooms, stairwells, server rooms, covered loading docks, parking structures. Where satellite signal is unreliable, a scan at a fixed physical marker is more trustworthy than a coordinate.

Both methods work from a standard smartphone. No proprietary wand, no reader hardware, no tags to replace when someone repaints the corridor — which also means the plan can be deployed the same day it is written.

For the operational side of verification, see our guard tour system guide.

Patrol plans by property type

Every property type carries risks the others do not, and the checkpoint list should reflect that. Open the generator pre-filled for your site:

From a written plan to a verified patrol

A patrol plan on paper documents intent. It does not document performance. The gap between the two is where most liability sits: when an incident is reviewed, the question is never whether a plan existed — it is whether the patrol described in the plan actually happened.

Running the plan digitally closes that gap. Each checkpoint visit carries a timestamp and a verified location. Incidents are logged with photos and a description at the moment they are found. The result is a patrol record that stands on its own in a client review, an insurance claim, or a deposition.

The plan you generate here can be recreated in Trinity Guard® using the same checkpoints, route logic, and QR/GPS verification methods, so the operational plan and the digital patrol record stay aligned.

Assumptions and limits

This generator produces a suggested starting plan based on the information you provide. It is not a site risk assessment, and it does not replace a walk of the property.

Travel times are estimated from area and checkpoint count, not from a floor plan — real routes are affected by internal walls, one-way circulation, locked zones, and terrain. Verify the timings on site before you adopt the plan. Patrol frequency and scope may be governed by your contract, your insurance carrier, or the authority having jurisdiction, and those requirements take precedence over anything calculated here.

Frequently asked questions