Post Orders, SOPs, and Operational Planning
Post orders versus SOPs
Post orders are site-specific: they tell a guard exactly what to do at a named gate, control room, or patrol route, including hours, keys, visitors, alarms, and escalation numbers. SOPs are generic procedures that apply across sites, such as radio use, report writing, or use of force. Both are binding; neither overrides lawful instructions or the law.
Operational planning
A workable plan has an objective, tasks, resources, timeline, command and communication, contingency, and review. For a shift, this may be a simple handover plan; for an event, it may be a written operational order with a map, posts, reliefs, and emergency rendezvous. Issue orders clearly, confirm understanding, and supervise execution.
Worked example
A client requests extra cover for a cash delivery. The supervisor should not simply add a guard. The reasoned plan states the objective (protect the transfer and the public), tasks (inner and outer cordon, door control, traffic management), resources (two guards, radios, incident log), timeline (arrival, transfer, departure), command (who calls the police and who authorizes movement), contingency (vehicle breakdown, hostile crowd), and review (debrief). The reasoning: extra bodies without tasks create confusion, while a written plan assigns accountability and reduces gaps.
Traps
Treating post orders as advisory; using an old plan after the site layout changes; planning without reliefs or contingencies; failing to confirm that guards understand the order; changing a client instruction without authorization.