Security guard post orders turn a facility’s expectations into practical instructions for each assigned post. Well-written security guard post orders clarify what guards should do, what they should observe, who to notify, and how to document a shift. For managers, the goal is not to write a long manual. It is to create instructions that are specific enough to guide consistent work and clear enough to use under pressure.

Request a security consultation

Call (833) 272-7247 to discuss site coverage.

This guide explains the purpose and core structure of post orders, including duties, patrol routes, access control, escalation, reporting, and shift handoffs. It also provides a practical checklist managers can use to review instructions without putting sensitive site tactics into a public document.

What are security guard post orders?

Post orders are written instructions for the work assigned to a security post or location. They define the guard’s responsibilities, routine procedures, reporting expectations, and the boundaries of the role. They help translate a service plan into day-to-day actions, while giving managers and security supervisors a shared reference for what a shift is expected to cover.

Orders are different from a general security policy. A policy may state that visitors must be handled consistently or that incidents must be reported. Post orders explain how those expectations apply at a particular assignment: which entrance is monitored, what information should be recorded, when a supervisor should be contacted, and what the guard should do if a situation falls outside the written procedure.

They should not attempt to replace training, supervision, emergency plans, or judgment. Instead, they provide a stable starting point. If an order is unclear, contradictory, or no longer reflects the site, the guard should know whom to contact rather than improvise a new rule.

A sample government document from the District of Columbia’s Protective Services Division describes post orders as establishing the duties and responsibilities officers follow while on duty and on post. That is a useful framing: the instructions connect assigned responsibilities with the specific post where they apply. Review the sample post orders as a reference for how duties can be laid out.

Why do clear post orders matter?

Clear instructions reduce avoidable variation between shifts. If one guard checks a delivery entrance and another assumes someone else covers it, a task can be missed even when both are working diligently. A written assignment identifies who owns each responsibility and how completion should be communicated.

Post orders also help managers assess whether a security plan is workable. They make the intended scope visible: which duties are routine, how patrols are documented, what counts as an issue requiring escalation, and which tasks are outside the guard’s assignment. That makes review more concrete than relying on broad statements such as “monitor the property” or “respond as needed.”

Good orders support continuity as well. A new guard or relief supervisor can understand the basic expectations without depending only on informal explanations. This does not eliminate the need for an on-site briefing. It gives the briefing a consistent written foundation and gives the team a place to record approved changes.

For managers overseeing several kinds of properties, the structure can remain consistent while the site-specific details differ. A warehouse, office, residential community, and event space may need different duties and escalation contacts. Each assignment should make those differences explicit, rather than copying generic instructions that do not fit the post.

What sections should post orders include?

Organize the document so a guard can find the immediate action they need. A concise contents page or clear headings can help when orders cover several posts. The exact layout will vary, but these sections form a practical foundation.

• Document control: Site or post name, version date, approving manager, and a way to identify replaced instructions.
• Purpose and scope: What the assignment covers and what is not part of the guard’s duties.
• Contacts and escalation: Role-based contacts, the order in which to notify them, and the expected method of contact.
• Post duties: Routine responsibilities by time, location, or event, including how completion is recorded.
• Access procedures: The approved process for visitors, deliveries, contractors, and other authorized entries.
• Patrol guidance: Approved areas, checkpoints or route references, timing expectations where appropriate, and reporting steps for blocked or inaccessible areas.
• Incident response: Initial priorities, notification thresholds, documentation requirements, and direction to follow the site’s approved emergency procedures.
• Shift handoff: The information to pass to the next guard or supervisor and how to note unresolved items.
• Reference materials: Links or references to current site policies, emergency contacts, and related procedures.

Use clear labels and ordinary language. Define any abbreviation the first time it appears. Avoid burying a critical instruction in a long paragraph or making guards search through unrelated background information to find a contact or procedure.

How should managers define duties and priorities?

Start with the actual assignment, not a generic list of everything a guard could possibly do. For each duty, name the action, the relevant place or condition, and the expected record or notification. “Check the loading area” is hard to evaluate. “During the assigned exterior patrol, observe the loading area for access concerns and record the patrol in the approved activity log” is more useful, provided it matches the site’s approved plan.

Separate routine tasks from conditional tasks. Routine duties happen as part of a normal shift, such as monitoring an assigned entrance or completing a scheduled patrol. Conditional duties apply when a defined event occurs, such as an access concern, a facility alarm notification, or an injury report. Explain the trigger and the first reporting step, without trying to predict every possible scenario.

Set priorities where tasks may conflict. If the guard cannot perform two duties at once, orders should identify which responsibility takes precedence and who can authorize a change in coverage. Instructions should not ask one person to monitor multiple places continuously when that is not feasible. Managers should validate staffing assumptions against the tasks actually listed.

For assignments that combine standing coverage and patrols, specify how the post remains covered when the guard leaves the immediate area. If relief, a second guard, or another approved arrangement is required, state that clearly. Do not imply that a guard should abandon an assigned responsibility to complete a secondary task.

How should post orders describe patrol routes?

Route instructions should let the assigned guard understand the approved coverage area without exposing unnecessary details in documents shared beyond the people who need them. Use a controlled site map or a clearly named route reference when appropriate. In the written orders, identify which areas are included, how to record completed patrols, and what to do when a planned area cannot be reached.

Do not rely on vague directions such as “patrol the property regularly.” Define the expectation in a way that can be followed and checked. That may include the authorized route reference, the required checkpoints, and how deviations are reported. If the schedule or route needs to change because of construction, an event, or a temporary closure, specify who approves the change and where it is documented.

For sensitive sites, limit the circulation of maps, timing details, and other operational specifics. Put detailed material in an appropriately controlled attachment rather than in a broadly distributed version of the orders. The public-facing article or general policy should not disclose a facility’s blind spots, security weaknesses, or exact response tactics.

Managers should test the written route against real conditions. Check whether entrances, gates, and common areas are named consistently, whether a guard can complete the route while maintaining other duties, and whether the process addresses blocked access. Include a way to report a route problem instead of expecting the guard to silently skip a checkpoint.

What should access-control instructions cover?

Access instructions should identify which entry points are part of the assignment, what the guard is expected to verify, and how exceptions are handled. The actual verification process must match the property’s approved policies. Avoid writing a broad direction such as “let authorized people in” without explaining what information or authorization the guard should rely on.

Consider separate procedures for visitors, deliveries, contractors, and scheduled service providers if their entry processes differ. For each group, state where they should check in, what information is recorded, and which site contact resolves questions. If authorization cannot be confirmed, provide a clear escalation path rather than instructing the guard to make an exception independently.

Instructions should also cover common complications: a visitor arrives outside expected hours, a delivery has no listed recipient, identification information does not match the expected details, or a person disputes a restriction. Keep the response procedural and role-appropriate. For example, identify the manager or site contact to call, the required log entry, and any relevant site policy to follow.

Avoid embedding access credentials, personal information, or detailed vulnerability information in versions of the orders that do not need them. Managers should decide who receives each attachment and how outdated copies are withdrawn when an access process changes.

How should escalation and documentation work?

Escalation instructions should tell the guard when to report an issue, whom to contact, and what to do if the first contact is unavailable. Use role names where they are more durable than individual names, and keep current contact details in a controlled reference. State whether the guard should notify a supervisor, a site representative, or emergency responders under the applicable site procedure.

Keep the sequence easy to follow. A useful instruction identifies the trigger, the immediate safe action within the guard’s role, the person to notify, and the record to complete. Do not make the guard choose between conflicting directions or assume that every issue requires the same response. If the site has separate emergency procedures, refer to the approved current procedure rather than duplicating a detailed response plan that may later become inconsistent.

Documentation expectations should be just as clear. Say which activity or incident record to use, what information to include, and when a supervisor must be notified. Depending on the site process, a record may capture the time, location, people involved where appropriate, observed facts, notifications made, and follow-up still needed. Distinguish direct observations from assumptions. Avoid telling guards to include unnecessary personal or sensitive information.

When digital reporting is part of the assignment, identify the approved method and the required checkpoints or report categories. ASAP Security uses GPS-tracked Daily Activity Reporting (DAR), according to the company information provided for this article. Managers can ask how reporting expectations align with the duties in the orders, and whether the records make it possible to review completed patrols and reported issues.

Call (833) 272-7247 to discuss guard reporting needs.

Post orders can also point to a separate, controlled incident procedure. A brief instruction should state when to preserve relevant records, whom to notify, and where follow-up belongs, without placing sensitive incident details into a general shift log. If managers want to understand what to expect from guard documentation, see this guide to digital Daily Activity Reports and guard logs.

What belongs in a shift handoff?

A handoff should make the next shift aware of current conditions and unfinished responsibilities. It is not simply a note that the previous guard has left. Define what must be communicated verbally, what must be entered in a written or digital record, and who receives urgent updates before the shift ends.

A concise handoff record can include the time of the handoff, outstanding follow-up, temporary changes approved during the shift, access or equipment issues relevant to the post, and any notifications already made. Include only information needed for continuity, and use the approved channel for sensitive material. If there are no unresolved items, the handoff process should still make that status clear.

Clarify who owns an open item after the handoff. For example, an unresolved maintenance concern may need a site manager’s follow-up, while a patrol route deviation may require supervisor review. The orders should indicate whether the outgoing guard must notify a specific person before leaving or simply document the issue for the next shift. That distinction prevents important work from disappearing between logs.

Managers can review a sample handoff for clarity. Ask whether someone unfamiliar with the previous shift could identify what remains open, what has already been reported, and who is responsible for the next step. If not, improve the template or the instruction rather than relying on memory.

How can managers keep orders current?

Assign an owner for review and define when a revision is needed. Triggers may include a change in site layout, entry process, guard responsibilities, escalation contacts, reporting tools, or management approval. A review schedule can also help catch gradual drift, but a scheduled review does not replace an update after a material change.

Use version control. Put an effective date and revision identifier on the document, record who approved the change, and make clear which version is current. When a revision is issued, remove or mark superseded copies so a guard is not left choosing between conflicting instructions. Keep a record of what changed and communicate material updates during a documented briefing.

Before approval, walk through the orders from the perspective of the assigned guard. Can the guard identify the first priority at the start of a shift? Are contacts and reporting channels current? Do instructions account for a closed entrance or an unavailable supervisor? Does the route fit alongside the other duties? A short practical review can reveal contradictions that are easy to miss at a desk.

For a broader view of physical coverage options, managers can compare the instructions with the organization’s security patrol services and 24-hour security guard coverage. The goal is alignment between the written assignment and the service actually requested, not extra duties added without discussion.

What should managers compare when reviewing post orders?

A review is easier when each section has a clear purpose. Use this table to check whether the order gives the guard enough direction, while keeping detailed site tactics in appropriately controlled documents.

What is a practical post-order review checklist?

Before approving or revising an order, work through this checklist with the site representative and security supervisor:

1. Confirm purpose: Does the document name the post, covered assignment, and limits of the role?
2. Check duty ownership: Does every recurring task have a clear owner, expected timing or trigger, and completion record?
3. Test priorities: If two responsibilities overlap, does the guard know which takes precedence and who can approve a change?
4. Review route practicality: Are the approved areas understandable, accessible, and compatible with other duties?
5. Verify access steps: Can guards handle routine visitors and common exceptions using approved procedures and contacts?
6. Trace escalation: For each reportable issue, can the guard identify whom to notify and what to do if that person is unavailable?
7. Check records: Are required logs, activity reports, and incident notifications named, with sufficient but not excessive detail?
8. Walk through a handoff: Would the next shift know what remains open and who owns follow-up?
9. Protect sensitive details: Are maps, access information, and operational specifics shared only in suitable controlled materials?
10. Confirm versioning: Is the approved revision dated, communicated, and distinguishable from superseded copies?
11. Brief and verify: Have affected guards and supervisors received the changes, and is there a way to confirm understanding?

Managers may find it helpful to compare the document structure with published examples. A private-security white paper from the Secure Community Network discusses establishing or revising post orders and training standards with client preapproval. See the post-order and training-standard reference. Treat examples as prompts for review, not templates to copy without adapting them to the approved site plan.

For general service questions, managers can also review the company’s security services FAQ and its Southern California service-area information.

Call (833) 272-7247 to discuss your site’s coverage plan.

Call (833) 272-7247 to discuss post-order needs.

Frequently asked questions

Who should write security guard post orders?

Managers and the security provider should coordinate the document. The site manager can confirm property rules, contacts, and operational priorities, while the security supervisor can help make duties and reporting expectations workable for the assigned post. The appropriate client representative should approve site-specific instructions before they are issued.

How long should post orders be?

There is no useful page count for every site. Keep the core instructions as concise as possible while covering duties, access, routes, escalation, documentation, and handoffs. Put detailed material in clearly referenced attachments when it needs tighter access controls or would make routine instructions difficult to scan.

Should post orders include emergency procedures?

They should tell guards when to use the site’s approved emergency procedures and who to notify, but they should not create conflicting or improvised emergency plans. Reference the current approved procedure and make sure the relevant contacts and reporting expectations align with it.

When should a manager revise post orders?

Review them when duties, site access, routes, reporting tools, escalation contacts, or other material conditions change. Assign an owner, date each approved revision, remove outdated copies, and brief affected personnel so the written instructions match current expectations.

Make the instructions usable on the next shift

Strong post orders are specific, current, and practical at the point of use. They define responsibilities, clarify reporting and escalation, and help the next shift understand what has happened and what remains to be done. Review them with the people responsible for the site and the assigned coverage, then revise any instruction that is unclear or no longer reflects the approved plan.