How to Write Post Orders Your Security Guards Will Actually Follow

I've audited over 200 security programs across the Mid-South in the last eight years. And I can tell you the single document that predicts whether a security team will perform well or fall apart: the post orders.

Post orders are the written instructions that tell your security officers exactly what to do at your property. When to patrol. What doors to check. How to handle a trespasser. Who to call at 2am when the fire alarm trips. They're the operating manual for every shift.

The problem? About 70% of the post orders I review are either too vague to be useful, too long to be read, or so outdated they reference employees who left three years ago. If your security isn't performing the way you expected, there's a good chance the post orders are the root cause.

Why Bad Post Orders Create Bad Security

Here's what happens when post orders are poorly written. A new guard shows up for their first shift at your property. They open the binder or pull up the PDF on their phone. They see 14 pages of dense text that reads like it was copied from a corporate policy manual. Half of it is boilerplate about the security company's values. The actual instructions, the things that matter, are buried somewhere on page 9.

So the guard does what any reasonable person would do. They skim it, pick up the basics from the outgoing officer during shift change, and figure out the rest on their own. Now you've got someone protecting your property based on a five-minute verbal summary and their best guess. That's not a security program. That's a liability.

I worked with a property manager in Cordova last fall who was furious that guards kept letting delivery trucks through the wrong gate. Turns out the post orders said "all deliveries should be directed to the appropriate entrance." Which entrance? Appropriate by whose definition? The guard didn't know, so they picked whichever gate was closest. The post orders failed before the guard did.

The Five Parts Every Post Order Needs

After years of refining this, I've landed on a framework that works. Every set of post orders should cover five areas, in this order.

1. Property overview and your role. One paragraph. What is this property? Who works here? What are the operating hours? What's the guard's primary purpose on site? For a warehouse on the Memphis I-40 corridor, that might read: "This is a 120,000 sq ft distribution warehouse operating Monday through Saturday, 6am to 10pm. Your primary role is controlling vehicle and pedestrian access at the front gate and conducting interior and exterior patrols between vehicle checks."

Short. Specific. The guard now knows where they are and what they're supposed to be doing.

2. Scheduled tasks with exact times. This is where most post orders fall apart. Vague language like "patrol regularly" or "check doors periodically" gives the guard nothing to work with. Pin down the schedule. Use a table or a numbered timeline.

For example: 6:00 PM, lock the south employee entrance and verify the deadbolt engages. 7:00 PM, begin first exterior patrol, covering the loading dock, dumpster area, and parking lot perimeter. 8:30 PM, interior walkthrough of all three warehouse bays, check for open doors and running equipment. 10:00 PM, second exterior patrol. Midnight, perimeter check with emphasis on the fence line along Lamar Avenue.

When a guard knows that at 7:00 PM they walk a specific route and check specific things, there's no ambiguity. And when you're using patrol verification technology, those checkpoints become auditable proof that the work got done.

3. Access control rules. Who gets in, who doesn't, and what to do when it's not clear. This section needs names, titles, and phone numbers. List every person authorized to enter after hours by name. List every regular vendor and their expected delivery window. Then write one clear rule for everyone else: "Any person not on the authorized list must wait at the gate while you call the on-site manager at (901) 555-XXXX. Do not grant access until you receive verbal confirmation."

Update this section monthly. People leave companies. Vendors change schedules. A guard working from an outdated access list is either going to let in someone who shouldn't be there or block someone who should. Both are problems.

4. Emergency procedures. Keep this to one page. Cover the five situations most likely to happen at that specific property. For most Memphis commercial properties, that's: fire alarm activation, medical emergency, active intruder, severe weather, and power outage. For each one, write three to five numbered steps. Not paragraphs. Steps.

Fire alarm example: 1. Call 911 and report the alarm, give the property address. 2. Notify the property manager at (901) 555-XXXX. 3. Direct all occupants to the east parking lot assembly area. 4. Meet fire department at the Poplar Avenue entrance and provide access. 5. Do not silence the alarm unless directed by the fire department.

A guard who just heard a fire alarm and has adrenaline pumping isn't going to read a paragraph. They need a checklist they can follow step by step.

5. Reporting and communication. Tell the guard exactly what to report, when, and to whom. Daily activity reports should have a set format, not a blank notebook where they write whatever they feel like. Specify: log the time and result of every patrol, record every visitor's name and time of entry, document anything unusual even if it seems minor.

Name the people who receive reports. "Email the shift report to john@company.com and security@sosguards.com before the end of your shift." Don't leave the guard guessing whether anyone is actually reading what they write. When they know a real person reviews their reports, the quality goes up immediately.

Three Mistakes That Undermine Good Post Orders

Even well-structured post orders fail when these mistakes creep in.

Writing them once and forgetting them. Your property changes. Tenants move out, construction starts next door, a new parking structure opens. Post orders should be reviewed every 90 days at minimum. At Shield of Steel, we build quarterly reviews into every client contract. The guard supervisor walks the property with the client, notes what's changed, and updates the orders that same week.

Making them too long. If your post orders run past six pages, the guard won't read them cover to cover. For most single-site assignments, three to four pages is the right length. If you have a complex property with multiple buildings or high-security areas, break the orders into sections. Core duties on the first two pages. Building-specific details in an appendix the guard can reference when needed.

Skipping the "why." Guards perform better when they understand the reason behind an instruction. "Lock gate 3 at 8pm" is fine. "Lock gate 3 at 8pm because this entrance faces an unlit alley and we've had two attempted break-ins through this gate in the past year" is better. It tells the guard this isn't just a checkbox. It matters. They'll check the lock twice.

How to Test Whether Your Post Orders Work

There's a simple test. Hand your post orders to someone who has never been to your property and ask them to tell you, based only on what they read, exactly what they'd do during a shift. If they can describe the patrol route, name the emergency contacts, and explain the access rules without asking a question, your post orders work. If they can't, you've got rewriting to do.

I ran this exercise with a Germantown retail center last month. The property manager handed the orders to a new assistant and asked her to summarize the guard's duties. She got through half the document and said, "I'm not sure which entrance is the main one." That one sentence triggered a rewrite that made the whole program sharper.

Start With What You Have

You don't need to build post orders from scratch if you already have a security team in place. Pull out whatever written instructions exist today. Compare them against the five-part framework above. Identify the gaps. Most of the time, the scheduled tasks section is too vague and the emergency procedures are out of date. Fix those two things and you'll see improvement within a week.

If you're starting a new security program or switching providers, make post order quality part of your evaluation. Ask the security company to show you a sample set of post orders from a comparable property. If they hand you something generic, that tells you how they'll manage your account. If they ask to do a site walk before writing anything, that tells you something better.

We build custom post orders for every property we protect. That process starts with a site assessment, not a template. If you want to see what that looks like for your location, call us at (202) 222-2225 or reach out through our website. We'll walk the property with you and put together a set of orders that your team can actually execute.