Post orders translate a security contract into the officer's actual job. Weak post orders produce inconsistent service even when the officer is capable.
A useful post order should answer
- Where must the officer be and when?
- What entrances, areas, or systems are the officer responsible for?
- What recurring patrols or checks are required?
- What must be documented?
- Who is contacted for routine, urgent, and emergency issues?
- What actions are outside the officer's authority?
- What changes during nights, weekends, holidays, or special events?
Keep them operational
Post orders should be readable during a shift. Long policy language belongs in policy documents; the post order should focus on the decisions and duties the officer must execute correctly.
Review them after launch
A new assignment usually reveals details that were not obvious during the proposal stage. Review and revise the post orders as the site teaches the security team how it really operates.
Hammerhead's operating model treats post orders as a living part of service management.