How to Standardize Security Post Orders Across a Commercial Property Portfolio

Post orders turn a security contract into daily operating instructions. They tell an officer where to be, what to observe, which tasks to perform, what to document, and when to escalate a condition to the property team or security supervisor.

Weak post orders create avoidable variation. Two officers can interpret the same assignment differently. Relief officers may miss a critical loading-dock check. Reports may use inconsistent categories. A portfolio manager can receive pages of activity without a reliable way to compare performance across properties.

The answer is not one generic document for every building. It is a controlled portfolio standard with site-specific instructions.

What Post Orders Should Accomplish

Effective post orders should answer five practical questions:

1. Assignment: What is the officer or patrol responsible for during this shift?
2. Location and timing: Where must the work occur, and at what times or frequencies?
3. Authority and boundaries: What may the officer do, and what must be escalated?
4. Documentation: What activity and incidents must be recorded, and in what format?
5. Communication: Who must be contacted, in what order, and under which conditions?

Washington’s postassignment training topics include job assignments and post orders, patrol, observation and incident reporting, access control, emergency response, and life-safety awareness. A portfolio’s post orders should connect those general competencies to the actual property. See WAC 308-18-305.

Government security planning offers a useful structural example: a GSA/FEMA agreement required post orders to identify guard locations, service hours, and duration, with changes coordinated when requirements changed. Commercial properties need their own contract-specific process, but the operating principle is sound—location, timing, scope, and change control should be explicit. See the GSA/FEMA security agreement.

Build a Two-Layer Post-Order System

Use two connected documents instead of rewriting everything for each site.

Layer 1: Portfolio operating standard

The portfolio standard contains requirements that should be consistent across locations:

• Professional conduct and appearance.
• Communication and escalation structure.
• Incident categories and report-quality standards.
• Required acknowledgments and shift handoff.
• Confidentiality and handling of sensitive property information.
• Rules for interacting with tenants, visitors, vendors, and law enforcement.
• Supervisor review and corrective-action process.
• Version-control and approval requirements.

Layer 2: Site-specific post orders

The site document contains the details that make the assignment usable:

• Property address, site contacts, and emergency contacts.
• Post location, schedule, and relief procedure.
• Property map, approved patrol areas, and prohibited areas.
• Access points, keys, credentials, gates, and visitor/vendor procedures.
• Patrol checkpoints, timing windows, and variable-route expectations.
• Opening, closing, vacant-suite, parking, loading, or perimeter checks.
• Site-specific hazards and known operating constraints.
• Camera/monitoring coordination that the client and provider have expressly approved.
• Report recipients and escalation thresholds.

This structure creates consistency without pretending an office tower, warehouse, construction site, and retail property operate the same way.

Nine Sections Every Site Document Needs

1. Purpose and scope

State why the assignment exists and what success looks like. Keep it operational. For example: maintain a visible presence at the primary entrance, complete agreed perimeter patrols, document access exceptions, and escalate urgent conditions.

2. Schedule and staffing

Identify the post hours, shift boundaries, relief expectations, and the procedure if an officer is late or coverage is at risk. Do not leave the call-off process in a separate document that the property manager never sees.

3. Contacts and escalation

List contacts in order and define when to use each one. Separate emergencies from routine property issues. Include the security supervisor and the property contact who has authority to change instructions.

4. Access and boundaries

Explain credential handling, visitor and vendor procedures, deliveries, restricted spaces, and any actions the officer is not authorized to take. Clear boundaries protect the client, officer, tenants, and provider.

5. Patrol requirements

Define patrol zones, required checkpoints, timing windows, and conditions that require an additional check. Avoid making every patrol identical and predictable unless the assignment requires fixed timing.

6. Observation and reporting

Specify what belongs in a routine activity report and what requires an incident report. Define minimum details such as time, location, people involved, observations, actions taken, notifications, and disposition.

7. Emergency and life-safety procedures

Reference the client’s approved emergency plans and define the officer’s assigned role. Do not invent responsibilities that conflict with the property plan, emergency responders, or the security contract.

8. Shift handoff

Require the outgoing and incoming officer to exchange unresolved conditions, equipment or credential status, expected visitors or contractors, and any temporary instruction.

9. Approval and revision history

Every controlled copy should show the version, effective date, approver, and revision summary. Temporary instructions should have an expiration or review date.

Create a Change-Control Process

Properties change. Tenants move, construction phases advance, gates fail, parking patterns shift, and new problem areas appear. Post orders should be reviewed whenever the operating environment materially changes.

Useful review triggers include:

• A serious incident or repeated pattern.
• A new tenant, vacancy, or major move-in/move-out.
• Construction, renovation, or a changed site perimeter.
• A new access, camera, or reporting system.
• A shift in post hours or patrol frequency.
• Repeated officer questions or report-quality problems.
• A change in the client’s emergency or escalation contacts.

Use one documented change path: requested change, operational review, client approval when required, version update, officer acknowledgment, and verification in the field.

For broader provider evaluation, use our commercial security vendor scorecard.

Measure Whether the Post Orders Work

The purpose of a post order is consistent execution, not document completion. Review a small set of measures:

• Coverage delivered as scheduled.
• Agreed patrol or checkpoint completion.
• Report submission and correction times.
• Missing information or repeated report defects.
• Incident escalation against the approved contact path.
• Officer acknowledgment of the current version.
• Recurring exceptions that indicate the instructions need to change.

Time-stamped and GPS-verified activity can help property managers confirm agreed work without turning the relationship into surveillance for its own sake. The goal is transparent service and earlier correction when execution drifts.

Standardization Should Improve Site Knowledge

A strong portfolio standard supports consistency, but security still depends on people who understand the property. Whenever possible, maintain a core officer team and use a structured orientation for relief staff. The site-specific post orders should help an officer learn normal traffic, approved vendors, tenant routines, recurring trouble areas, and the conditions that deserve attention.

Chandler Solutions provides commercial security officers, mobile patrol, construction-site security, fire watch, GPS-verified activity, and digital reporting across Western Washington. We favor consistent assignments, direct operational accountability, and site instructions that make expectations measurable.

If one property or patrol route in your portfolio needs clearer security execution, contact Chandler Solutions to discuss the requirement and the measures that should guide a 30-45 day pilot.