Post Orders: The Document Your Security Team Runs On
For a client, good post orders reduce inconsistency. They help the regular officer, relief officer, supervisor, and account manager work from the same understanding of the site.
The short version
The short version
Post orders are the site-specific instructions that tell a security team what the assignment requires, how routine duties should be performed, who must be contacted, and when an officer should escalate instead of deciding alone.
A Contract Is Not Enough Instruction
A contract defines the business agreement. It may describe coverage hours, general duties, price, and legal terms.
It usually does not tell an officer:
Those details belong in post orders and related site instructions.
Without them, officers fill gaps with memory, habit, or personal judgment. Even capable people can make different choices because they were given different information.
Good Post Orders Answer Routine Questions
An officer should be able to use the document during the shift, not only sign it during orientation.
The Purpose of the Post
Begin with the reason the post exists. An officer who understands the purpose can make better decisions when conditions do not match the script. For example, a lobby post may exist to control access, assist approved visitors, observe the entrance, and give the client a professional point of contact. The purpose is broader than “sit at the desk.”
Duties and Priorities
List the regular duties in a useful order. That may include:
Separate critical duties from secondary tasks. If two needs compete, the officer should know which takes priority.
Schedule and Sequence
State when time-sensitive duties occur and how they fit together. A patrol instruction should explain more than “conduct patrols.” It may need to identify areas, frequency, checkpoints, conditions to observe, and what requires a report or notification. Avoid creating a schedule so rigid that it makes patrols predictable or prevents the officer from responding to real conditions. Give enough structure for consistency and enough judgment for the assignment.
Contacts and Escalation
The document should identify:
Officers should know who to call first, what information to provide, and what to do if the first contact does not respond.
Reporting Requirements
Explain what must be documented, where it is documented, and when the report is due.
Include expectations for:
The reporting section should help the officer understand what the client and provider need to know, not merely which button to press.
Write for the Relief Officer
The regular officer may know the site so well that weak post orders appear adequate. They remember the client’s preferences, recognize employees, and know which door sticks in wet weather.
The real test is the qualified relief officer arriving for the first time.
Can that person find:
If the post can only function when one person is present, the instructions are not carrying enough of the service.
Keep Authority and Boundaries Clear
Post orders should tell officers what they may decide and what must be escalated.
For example, an officer may be authorized to deny entry when a visitor lacks required approval. The officer may not be authorized to create an exception because the visitor is persistent or says the meeting is important.
Clear boundaries help officers remain professional under pressure. They also protect the client from different rules being invented on different shifts.
Instructions must remain within the law, the contract, company policy, and the authority the client can properly give. If a requested duty appears unsafe, unlawful, or outside scope, the officer should know how to pause and contact leadership.
Use Scenarios Where a Rule Is Not Enough
Some duties are better explained through short examples.
An access section might include:
The example should show the decision boundary, required contact, and reporting step. It should not try to predict every possible conversation.
The goal is consistent judgment, not a script for every human interaction.
Make the Document Usable on Shift
Strong content can still fail if the document is difficult to use.
Make post orders:
Use headings, short paragraphs, tables, and bullets where they improve scanning. Put urgent contacts and immediate actions where an officer can find them quickly.
Do not bury a critical instruction inside a long history of the account.
Treat Changes as Controlled Information
Clients and site conditions change. Post orders should change with them.
A useful update process includes:
Identify the requested or observed change.
Confirm that it is safe, lawful, within scope, and approved by the right person.
Update the controlled document.
Brief every affected officer and supervisor.
Confirm understanding when the change is important.
Record the effective date and owner.
Remove or archive the outdated instruction.
A message sent to one officer is not a complete post-order update.
Review the Document Against the Real Site
Do not wait for an annual review if the post is changing every month.
Review post orders after:
Supervisors should also compare the written instructions with what officers are doing. The document may be outdated, or the practice may have drifted away from it.
Use This Client Review
Ask the provider to review the post orders with you and answer:
0 of 8 checked. Anything left unchecked is where to start.
Post orders should not remove the need for trained people or active supervision. They give those people a common operating picture.
When the document is clear, current, and used, the client receives a more consistent service, officers receive better support, and supervisors have a real standard to inspect and improve.
Written by the People
Who Do the Work.
ARDENT Protection
ARDENT Protection. A Florida security and protection company, licensed since 2020, Florida Security Agency License #B1900411. Guard Services, Fire Watch, Event Security, Executive Protection and Workplace Violence Prevention, statewide.
Would Your Post Orders Hold Up Tonight?
Tell us what your officers are working from and where the instructions run out, and we will tell you what the post is likely missing. Sometimes the answer is a documentation fix, not a bigger contract.