How to write post orders guards actually use

Post orders are what a guard has instead of a supervisor at 0300. They are also the first document a plaintiff's attorney asks for. Write them so someone who has never seen the site can work a shift from them.

Who actually reads post orders?

Four audiences, and they want different things from the same document.

• The guard, who needs to act on it in the dark, one-handed, under stress.
• The supervisor, who needs to check compliance against something objective.
• The client, who needs to see the service they are paying for described accurately.
• A lawyer, possibly years later, who will read it as a statement of the standard you set for yourself.

Most bad post orders fail because they were written for the third audience only. They read like a proposal.

What has to be in a set of post orders?

The basics, complete

Obvious, and routinely half missing. A guard arriving for a first shift should be able to find the post, reach a human, and know when they can leave.

• Client name and the full site address, including the gate or entrance to use
• Key client personnel with names, titles and current phone numbers
• After-hours emergency contacts, in call order
• The exact physical location of the post
• Shift hours and the coverage schedule, including who relieves whom

Duties, in priority order

Not a flat list. A ranked one. Guards can rarely do everything at once, and the document has to say what gives.

• The two or three responsibilities that define this post
• Recurring tasks with their frequency
• Patrol routes, with checkpoint sequence and timing windows
• Access control procedure for each entry point
• Visitor handling
• What to drop first when something urgent lands

The patrol section is the one that gets copy-pasted between sites and should not be. A patrol protocol gives you the reusable skeleton; the routes, timings and checkpoints on top of it belong to this site alone.

Site-specific procedures

This is the section that justifies the document existing. Anything that would be identical at every site belongs in your company handbook instead.

• Opening and closing, step by step, including what gets armed, unarmed, locked and checked
• Key and access card protocol, including what happens when one goes missing
• Alarm system operation, with the passcode handling rule and the false alarm procedure
• Equipment specific to the site: gate controls, dock levelers, freight elevators
• Anything about this property that has surprised somebody before

Key handling in particular deserves its own written rule rather than a line in a paragraph. See the key control policy template.

Emergency procedures

The section people write last and need most. It is also the section where your instructions have to line up with somebody else's legal obligations.

A client site subject to 29 CFR 1910.38 already holds a written emergency action plan covering how to report an emergency, evacuation and exit route assignments, who shuts down critical operations, how people are accounted for, and who to ask about the plan. Point at that plan rather than inventing a second one that contradicts it.

California adds a layer. Under Labor Code section 6401.9, in force since July 1, 2024, covered employers must maintain a written Workplace Violence Prevention Plan covering emergency response, hazard correction, reporting without retaliation, post-incident investigation and training. If you employ guards in California that plan is yours too, and the post orders are where it meets the actual post.

Emergency content also needs a version a guard can reach in eight seconds. The full document is the reference; the quick reference card is what gets used.

What makes an instruction usable?

Specificity, and nothing else comes close. "Patrol the building regularly" tells a guard nothing. How often is regularly? Which floors? Looking for what? Recorded where?

Compare it to this: "Complete an interior patrol of floors 1 to 3 every two hours starting at 1800. Check every stairwell door, restroom and emergency exit. Log completion with the time and any observations."

That version can be followed, checked and defended. The first cannot be any of the three, which makes it the version that gets a company sued, because nobody can show it was met.

Three more rules on top of specificity.

1. Write in verbs. Check. Verify. Log. Contact. Secure. A post order is a set of instructions, not a description.
2. Cut the jargon or define it. A new guard does not know what your company calls a Code 4, and the shift they learn it on is not the one where it should come up.
3. Give the reason. One clause is usually enough: "check the rear dock door hourly, there is no camera coverage on that side." A guard who knows why will handle the situation the document did not anticipate.

Which situations must post orders cover explicitly?

The predictable ones, because those are where inconsistency is most visible to the client.

Visitors. Who gets in without an escort, what identification is required, how sign-in works, whether a badge is issued, and how to refuse entry. Every one of those is a potential argument in a lobby. A full visitor management SOP is worth attaching where the volume justifies it.

Deliveries. Which entrances accept them, what verification happens before signing, where packages go, and what happens at 2200 when a driver appears with a pallet. Guards with no instruction here either invent a procedure or refuse everything.

Incidents. Which categories get which response, when 911 is called, the client notification threshold, what report is filed, and who inside your company has to know before morning.

Exceptions. Post orders cannot cover everything, so name who the guard calls when the document runs out, and what they may decide alone. That path belongs in an escalation matrix with names and numbers on it.

How should post orders be formatted so guards use them?

A binder nobody opens is not a control. Format is not cosmetic here.

• Table of contents on anything over a few pages
• Numbered sections, so training and corrections can reference "4.2" instead of "the bit about deliveries"
• Ordered by frequency of use, not by how the writer thought about it
• A one-page summary at the front: emergency contacts, the critical procedures, the three things never to do
• Available at the post in both digital and paper form, because each fails differently
• Readable in bad light, at a glance, one-handed
• Version number and date on every page

The digital copy is what makes updating tractable. A paper binder at twelve sites means twelve reprints and twelve chances one of them stays stale.

How do you keep post orders current?

Outdated post orders are worse than none. A document naming a manager who left two years ago teaches guards the whole binder is fiction, and they stop consulting the parts that are still true.

1. A scheduled review, quarterly at minimum, that someone owns by name.
2. Change triggers. New client contact, changed procedure, new equipment, or a lesson out of an incident updates the document that week, not at the next review.
3. Controlled distribution. Date and version every change, push it to every guard who works the post, confirm they read it, and destroy the superseded copies.
4. Guard input. The officers working the post know which instruction is unrealistic. Ask them and act on it, or they stop telling you.

New instructions only land if they are trained, not just distributed. A substantive change belongs in the shift briefing and in the training program, not in an email nobody opens.

What happens when post orders reach a courtroom?

Which gives the one rule that overrides everything else here: never write an instruction that cannot be followed on the shift as staffed. Aspirational post orders are a signed admission of the standard you did not meet.

So audit the document against reality once a year. Walk the post at the busiest hour with the orders in hand and check whether one person could do all of it. Where they could not, change the instruction or change the staffing.