What Makes a Good Post Order (And Why Most Are Terrible)

Every security post should have a post order. Most do, in theory. The problem is that most post orders are so generic, outdated, or poorly written that they're nearly useless as actual operational guidance. I've seen post orders for major Memphis facilities that were three pages of boilerplate, last updated four years ago, with no site-specific information whatsoever. An officer arriving for their first shift at that property would learn exactly nothing from reading it.

That's a training failure, an operations failure, and a liability failure all at once.

What a Post Order Actually Is

A post order is a written document that tells a security officer precisely what they are responsible for at a specific property during a specific shift. It's not a general handbook. It's not a list of company policies. It's a site-specific, role-specific operational guide that answers the questions an officer will actually face: Where do I park? Who do I call if there's a fire? What do I do if someone refuses to leave? Which doors do I check and in what order? Who has after-hours access authorization?

A good post order is a decision tree built for that exact location. A bad post order is a generic document with the client's name typed at the top.

The Anatomy of a Useful Post Order

The document should open with property-specific information: the address, the key contacts list with current phone numbers, the alarm company information, and a brief description of the facility layout. Officers who've never been to a property before need to understand its geography quickly.

The body should address, by scenario: access control procedures for employees and visitors, vehicle patrol routes and checkpoint sequences, lock-up and open-up procedures, emergency response procedures broken down by type (fire, medical, active threat, severe weather), and escalation protocols for various categories of incident. Each section should be specific enough that an officer with no prior knowledge of the property can follow it without improvising.

The document should also include clear statements of authority: what actions the officer is authorized to take independently, and what requires supervisor or management notification before acting. This boundary-setting is where many post orders fail, because they're either too vague ("use judgment") or so rigid they don't account for real-world variables.

Post Orders for Event Security

Event security is where post order quality is most immediately visible. A well-run event like a corporate function in Downtown Memphis, a fundraiser at a venue near Beale Street, or a large gathering at FedExForum requires officers to have clear, specific guidance about their assignment before they arrive. What's the perimeter? What credentials authorize entry? Who's the event coordinator to contact if there's a problem? What's the crowd capacity threshold that triggers a call to management?

Officers who show up to events without specific post orders improvise, and improvised security is inconsistent security. Some officers will be too aggressive about access control and create friction with legitimate guests. Others will be too passive and miss genuine threats. The post order is what creates consistency across a team of officers who may have never worked together before. Our security officer program includes event-specific post order development as standard practice.

Updating Post Orders: When and Why

A post order should be reviewed and updated whenever: a significant change is made to the facility (new entrance, renovated floor, updated alarm system), there's a change in tenant or operational schedule, an incident occurs that revealed a gap in existing procedures, or it's been more than six months since the last review.

We treat post orders as living documents and review them with clients at least semi-annually, more frequently for high-activity properties or those with complex operations. If your current security provider has never shown you your post order or asked for your input in updating it, that's a conversation worth starting.

Making the Investment

Developing a strong post order takes two to four hours of collaborative work between the security provider and the client. That investment pays back immediately in officer performance and continues paying back every time an officer handles a difficult situation correctly because they knew exactly what to do. It also pays back legally, because documented procedures create defensible standards when incidents are litigated.

We build site-specific post orders for every client we serve across Memphis and Shelby County. Call us at (202) 222-2225 or reach out here to discuss your security operations. You can also learn more about how we serve the Memphis area.