Post orders: the document that runs your post when you’re not there
Search for security guard post orders examples and you’ll find plenty of templates — but a template isn’t the problem most companies have. The problem is post orders that are outdated, vague, buried in a binder nobody opens, or written like legal contracts instead of instructions a guard can act on at 3 AM. Post orders are the single document that defines what “doing the job” means at each site. When they’re bad, every guard improvises differently, and the client experiences an inconsistent service they can’t quite name but definitely notices.
Here’s how to write post orders that actually get read and followed.
What post orders must cover
Think of post orders as answering four questions: what is this post, what do I do routinely, what do I do when something happens, and who do I call. A complete set covers:
- Post identification — site name, address, post name/number, client contact, hours of coverage.
- Mission statement — one or two sentences on why this post exists (“Control vehicle access to the distribution center and protect the loading dock during overnight hours”).
- Duties by time block — what happens at shift start, hourly, and at shift end. Specific, not aspirational.
- Access control rules — who gets in, with what credentials, and what to do with everyone else. Include after-hours rules separately; they’re usually different.
- Patrol requirements — routes, checkpoints, frequency, and what to inspect at each stop.
- Emergency procedures — one page per scenario: fire, medical, intrusion, weapon on site, bomb threat, severe weather, power failure.
- Prohibited actions — what the guard must NOT do (pursue off property, accept packages, open doors for “forgotten badge” claims — whatever applies).
- Contact roster — dispatch, supervisor, client contacts, emergency services, in escalation order with hours of availability.
- Reporting requirements — what gets logged, what triggers an incident report, what gets called in immediately.
Real examples: vague vs. usable
The difference between orders that work and orders that decorate a binder is specificity. Compare:
| Vague (useless) | Specific (usable) |
|---|---|
| “Conduct regular patrols of the property." | "Complete a full perimeter patrol at least once per hour, scanning all 8 checkpoints. Vary the route and timing." |
| "Monitor visitors and vehicles." | "All visitors after 6 PM: verify ID, confirm host by phone, log entry with photo, issue visitor badge #." |
| "Respond appropriately to alarms." | "On any door alarm: 1) note zone, 2) notify dispatch before responding, 3) approach and observe — do not enter if signs of forced entry; hold for police." |
| "Keep the client informed." | "Call the facility manager (list hours) for: any injury, any forced entry, water/fire damage. Everything else goes in the daily activity report.” |
Example — an emergency section done right (medical):
MEDICAL EMERGENCY
- Call 911 first. Give address: [full address], gate 2 entrance.
- Notify dispatch on channel 1.
- Do not move the person unless in immediate danger.
- Send the second officer (if staffed) to gate 2 to guide EMS.
- Complete an incident report before end of shift; photograph the scene only after care is underway.
Numbered steps, in order, with the decision points removed wherever possible. At 3 AM under stress, nobody wants to interpret — they want step 1.
Writing rules that keep orders usable
- Write at task level, in plain language. Short sentences. Active voice. “Lock gate 3 at 22:00” beats “Gate 3 should be secured at the appropriate time.”
- One scenario per page. In an emergency, the guard should flip (or tap) directly to FIRE and see only fire steps.
- Distinguish must / must not / may. Guards need to know where their discretion starts and ends. Ambiguity here is how lawsuits happen.
- Date and version every page. “Which version was in force that night?” is a question you’ll eventually be asked under oath.
- Have a guard read the draft. If a new officer can’t execute the orders on their first shift without calling for clarification, rewrite. The author always overestimates clarity.
- Get client sign-off. Post orders are also your protection: when the client’s expectations and your orders match in writing, “your guard should have done X” disputes get short.
The maintenance problem (where paper post orders die)
Almost every guard company has decent post orders somewhere. Almost none keep them current. The client changes a gate procedure by email, the account manager forwards it to a supervisor, two guards hear about it verbally, and six months later the binder still says the old thing. Now three shifts run three different procedures.
This is the strongest argument for digital post orders:
- One live version per post, updated centrally, effective instantly for every shift.
- In the guard’s pocket. Orders live in the same mobile app the guard already uses to clock in and run patrols — not in a binder under old newspapers in the guard shack.
- Read receipts. You can see which guards have opened and acknowledged the current version — which converts “nobody told me” from an excuse into a records question.
- Onboarding speed. A guard covering an unfamiliar post for one night can read the orders on the drive over (not while driving) and arrive functional.
Post orders also connect naturally to the rest of your operation: patrol requirements defined in orders should match the checkpoints in your guard tour system, so compliance is measured, not assumed.
A realistic writing plan
Don’t announce a company-wide post orders rewrite — those stall. Instead: pick your three biggest accounts, write or rewrite one set per week using the structure above, get client sign-off, load them digitally, and require acknowledgment from every guard on those posts. Nine weeks later your top accounts are covered, and you have a house style for every new contract’s orders — which, by the way, look excellent attached to an RFP response.
Want post orders, patrols, attendance, and reporting living in one app your guards already carry? Get a demo and bring your messiest binder — we’ll digitize it with you.