How to Write Security Post Orders That Actually Work

Post orders are the most important document in any security program. They're also the one most businesses pay the least attention to.

I've spent years consulting on security programs across Memphis and the Mid-South, and reviewing post orders is usually one of the first things I do when a new client brings me in. What I find almost every time: a two-page generic document that lists broad duties, doesn't account for the specific property, and would leave any officer guessing during an actual incident. Those aren't post orders. They're liability in paper form.

This guide covers what effective post orders contain, how to structure them, and the mistakes that make most of them useless.

What Post Orders Actually Are

A post order is a written instruction set specific to a single security post. Not a company policy manual. Not a generic job description. A document that tells an officer, for this location, on this shift, under these conditions: what to watch, what to do, who to call, and how to document it.

The purpose is to replace guesswork with clear protocol. Good post orders mean that if your regular officer calls in sick and a substitute walks the post for the first time, they can operate at roughly the same level as the person they're replacing. Bad post orders mean that substitute is improvising from the moment they arrive, which is exactly when mistakes happen.

The Five Sections That Matter

Effective post orders cover five things, in this order.

1. Site overview. Property address, physical layout, and any relevant context about the location. Square footage, number of buildings, parking configuration, neighboring properties, known access points including unofficial ones. If the property sits near a high-activity corridor like Summer Avenue or is adjacent to a transit stop, note that. Officers working your post should understand the environment before they start their first tour.

2. Officer duties by time block. What the officer is expected to do during each portion of their shift. Not "conduct regular patrols." That's useless. "Complete exterior patrol every 45 minutes using route A, including north and south parking lots, loading dock, and rear fence line. Log each tour completion in the incident report." Time-blocked duties create accountability and make it possible to verify whether work was actually done.

3. Access control procedures. Who is authorized to be on the property and under what conditions. Vendor hours, visitor check-in process, after-hours access protocols, and what to do when someone shows up who doesn't meet those criteria. This section should be specific enough that an officer can make a decision without calling a supervisor for every edge case.

4. Emergency and incident response protocols. Numbered steps for each major scenario: fire, medical emergency, break-in in progress, trespasser, vehicle accident on property, altercation. Each protocol lists what the officer does first, when to call 911, when to contact the property manager or on-call supervisor, and how to document it. For Memphis properties near busy corridors or areas with known activity patterns, these protocols need to reflect the actual situations officers encounter, not theoretical ones.

5. Contact list. Every relevant contact, in priority order. Emergency services come first. Then the property's on-call manager. Then the security company's supervisor line. Then any tenant contacts relevant to after-hours access. The list should have names and direct phone numbers, not department titles and general lines. An officer dealing with an incident at 3 AM doesn't have time to navigate an automated phone tree.

Three Mistakes That Make Post Orders Useless

Most post orders fail for the same reasons.

The first is writing them at the company level instead of the post level. A security company that hands every client the same template with the property name swapped in hasn't written post orders. They've given you a form. Officers working a warehouse in Frayser need different instructions than officers working a medical office off Poplar. The document needs to be specific to the site it covers.

The second mistake is not updating them. Security post orders should be reviewed whenever something significant changes at the property: a tenant moves in or out, new access points get added, the crime pattern in the surrounding area shifts, or a serious incident occurs on site. Reviewing post orders once a year is a minimum professional standard. A lot of clients I've worked with have post orders that were written when the contract started and haven't been touched since, even when the property has changed substantially.

The third mistake is confusing detail with length. Long post orders that bury the important procedures inside paragraphs of background material are almost as bad as short ones that leave everything out. Officers under stress during an incident don't read narratives. They need numbered steps they can follow in sequence. Structure matters more than volume.

Memphis-Specific Considerations

Properties in Shelby County have some consistent characteristics worth addressing in post orders.

Shift relief coordination matters more than most businesses realize. Memphis traffic on Lamar Avenue, Airways Boulevard, and around the I-240 interchange can affect officer arrival times. Post orders should include a specific protocol for what to do if shift relief is more than 15 minutes late, including who to call and whether the officer is expected to hold the post until a replacement arrives.

Properties near the medical district, the hospital corridors on Union and Madison, and the areas around the airport face a different mix of late-night foot traffic than a commercial strip in Collierville or a business park in Bartlett. Officers need site-specific guidance about what's normal for their location versus what warrants a closer look and a log entry.

If your property borders a residential neighborhood, noise escalation and neighbor disputes that spill onto your lot are a common scenario. A good post order addresses whether officers engage, how they document it, and when to call Memphis Police rather than handle it as a simple access issue.

How to Handle Review and Sign-Off

Post orders should be a two-way document. Your security company writes them based on a site walk and intake conversation with your team. You review them before any officer starts. That review meeting matters because your staff knows things about the property that won't come up in a walk-through: the vendor who shows up without notice at 5 AM, the tenant with a history of lockout calls, the corner of the lot where unauthorized parking is a chronic problem.

Once finalized, post orders should be signed by both the property contact and the security company's account manager. That creates shared accountability for what's in the document and gives both sides a clear reference point if questions come up later about what an officer was supposed to do in a given situation.

Keep a copy on-site, accessible to officers at the post. A post order document that's only in the company's file doesn't help anyone at 2 AM on a Tuesday.

What Good Post Orders Actually Change

The practical difference between solid post orders and generic ones shows up in two situations: routine audits and actual incidents.

During a routine audit, specific time-blocked duties with GPS-verified patrol logs give you real data on whether your security program is being executed as designed. You can see if tours are running on schedule, whether incidents are being documented completely, and whether the officer coverage you're paying for is actually happening.

During an actual incident, clear protocols mean officers act faster and make fewer mistakes. They don't freeze up trying to figure out who to call first. They don't skip documentation steps because no one told them what to capture. And if the incident ever becomes a legal matter, well-documented post orders with an officer who followed them is a much better position to be in than one where the response was improvised.

Our security officers at Shield of Steel receive post-specific training before starting at any new location, and that training is built around the post orders for that site. Our commercial patrol teams use GPS-verified tour tracking tied directly to the checkpoint requirements written into each post order, so clients can see exactly what got covered on any given shift.

For clients across Memphis and Shelby County, we build property-specific post orders as part of our standard contract onboarding. If you have a current security provider and you're not sure your post orders are doing what they should, that's worth a look before you need them to hold up under pressure.

Call (202) 222-2225 or reach out here. A post orders review takes about an hour and usually surfaces things that surprise even clients who think their program is in good shape.