"Your team performs at the level you set — not the level you hope for."
Standard Operating Procedures and Post Orders
Instructor Sele: A security operation without documented procedures depends entirely on individual memory and judgment — and fails the moment the wrong individual is on duty. SOPs and post orders are how SafeHaven encodes professional standards into every post, every shift, every guard.
Section 1 — What Are Standard Operating Procedures?
SOPs are documented, step-by-step instructions that define how specific tasks and processes are performed — consistently, correctly, and to the required standard — by all staff, regardless of individual experience.
SOPs exist for access control, incident reporting and escalation, shift handover, armoury management (armed ops), CCTV monitoring and log maintenance, emergency response, and guard conduct and uniform standards. SOPs are company-wide; post orders build on them for the specific requirements of each client site.
Section 2 — What Are Post Orders?
Post orders are site-specific documents that define the exact duties, responsibilities, and procedures for a specific guard post at a specific client location. They are produced by the SOC in consultation with the client and signed by both parties.
Every set of post orders must include: post location and hours of coverage, site-specific access control procedures, patrol routes and frequencies, client-specific rules, site emergency procedures (assembly points, evacuation routes, contacts), escalation authority, and any special permissions or restrictions.
Post orders are a legal document. Guards must read and sign them before their first shift. If asked to do something not covered, they escalate to the SOC — not improvise.
Section 3 — Writing Effective SOPs and Post Orders
Good SOPs and post orders are clear and unambiguous (written so a person new to the role can follow them), specific (exact times, locations, names and numbers — not "periodically" or "relevant authorities"), actionable (tell the guard what to do, not just the objective), and current (reviewed annually and after every significant incident or change).
"Ensure all visitors are logged" is a weak post order. "All visitors must present a valid government-issued ID, be logged with name, ID number, host name, and time in/out, and be issued a visitor badge before proceeding past the reception gate" is operational.
Section 4 — The Security Audit
The SOC must conduct regular security audits to verify SOPs and post orders are being followed. An audit assesses physical security measures, access control effectiveness, guard performance against post orders, incident history and response quality, and contractual compliance.
Audit findings must be documented and actioned. A finding recorded but not actioned is a legal and operational liability.
- •SOPs define company-wide standards; post orders define site-specific duties — both mandatory
- •Every guard must read and sign their post orders before the first shift — no exceptions
- •Post orders must be specific, actionable, and current — vague orders produce vague compliance
- •Security audits verify compliance with SOPs and post orders — findings must be actioned
- •If a guard is asked to do something not in the post orders, they escalate to the SOC
"I audited a site where the visitor log had not been completed for three days. The guard told me: 'We've been busy.' I pulled the CCTV. In those three days, 47 people had entered the building with no record of who they were. In a subsequent investigation of a theft from that building, we had no way to identify anyone who had been on site. Unlogged visitors are ghosts. The post order existed. It was not followed. That is a supervision failure and a documentation failure simultaneously."
What is the purpose of Standard Operating Procedures (SOPs)?