A security guard post orders template turns a contract into instructions that an officer can use on the property. The contract defines the purchased service. Post orders explain the site-specific responsibilities, decision limits, contacts and procedures needed to deliver it.
A copied binder can look complete while leaving the important questions unanswered: who approves an unexpected contractor, who covers a post during a break, and what happens if the manager does not answer? Use the framework below to prepare instructions with your security provider. It is a planning template, not a substitute for training, an emergency plan or legal advice.
Define the assignment in one page
Start with the property name, the covered areas, service hours, responsible manager and security supervisor. Describe the purpose of each post in plain language. “Control the designated visitor entrance according to the approved authorization process” is more useful than “maintain security at all times.”
List tasks that belong to somebody else. Maintenance repairs, tenant disputes, medical treatment and commercial decisions should not silently become security duties. If an officer has multiple assignments, explain which task takes priority and how coverage is maintained when the officer must leave a position.
Use these sections in your post orders template
- Document control: property, post name, version, effective date, approver and review owner.
- Scope: areas and hours covered, required duties, exclusions and priorities.
- Start-of-shift handoff: equipment receipt, open issues, authorized changes and confirmation that the officer is ready for the assignment.
- Access decisions: approved authorization methods, visitor or contractor exceptions and who can approve a change.
- Routine tasks: what must be checked, how completion is recorded and what to do if a check cannot be completed safely.
- Communications: the primary and backup contacts, escalation sequence and expected acknowledgment process.
- Emergencies: reference the property’s current emergency procedures and identify the officer’s trained role.
- Reporting: routine records, urgent notifications, incident references and authorized recipients.
- Relief and end of shift: transfer of equipment, unresolved issues and responsibility for accepting the handoff.
- Training and revisions: briefing record, acknowledgment and how superseded copies are withdrawn.
Write decisions rather than vague instructions
Compare “verify all visitors” with a more usable rule: “Match the visitor to a current authorization using the approved process. If the authorization cannot be confirmed, contact the designated approver and follow the waiting-area procedure. Record the unresolved request.” The second version explains what happens when the routine fails.
Keep names, phone numbers and sensitive operational details in a controlled appendix. A public template should not contain real access codes, patrol timings, camera gaps or personal schedules. The FTC’s Start with Security guide supports limiting sensitive information and restricting access to people who need it.
Make escalation possible when the first person is unavailable
List the backup decision-maker and specify which matters require immediate emergency assistance. A routine permission request should not be confused with an urgent threat. Do not make employees wait through a management call tree before seeking emergency help when immediate danger exists.
Test the business contact chain during setup with an agreed exercise. Confirm that the person answering understands what they are authorized to decide. Keep a record of changes in ownership or staffing so an old employee’s number does not remain the only contact in the binder.
Use a simple sample instruction
Illustrative scenario: a contractor arrives outside the approved visit window. The officer checks the current authorization, contacts the named property representative and follows the site’s waiting procedure. The officer records the arrival, the person contacted, the decision and any unresolved issue. The officer does not invent permission because the contractor visited last week.
This example concerns an access decision, not the design of a complete visitor system. If the property is a residential community, use our gated-community visitor management checklist to define that wider process before writing the post-specific instructions.
Brief the officer and test understanding
Signing a document does not prove that the instructions are usable. Walk the site, identify the relevant equipment and ask the officer to explain a routine scenario and an exception. Resolve contradictory directions before the first independent shift.
Keep the exercise within the assigned role. Do not create a surprise emergency or stage a confrontation to test staff. A tabletop discussion can reveal missing contacts, unclear priorities or a task that cannot be completed without abandoning another post.
Keep one current version and connect it to reporting
Give every revision a date, approver and short change summary. Brief affected staff and replace old copies. Temporary directions should identify who approved them and when they expire. Avoid relying on informal messages that the next shift cannot find.
When reviewing performance, compare the report with the applicable instructions. Our patrol report guide covers that separate review step. Post orders define the expected work; the report records what happened.
Prepare site-specific post orders with your provider
Bring the property layout, operating hours, current access process and unresolved concerns to the setup meeting. Ask the provider to identify conflicting tasks and agree on supervision and relief. Contact FSO Guard to discuss an assignment with clear written responsibilities. For evaluating a prospective provider, see our security company selection guide.
