What professional security guard post orders should cover

Make responsibilities specific to the site

Generic instructions such as ‘remain alert’ are difficult to supervise. Post orders should state where the guard is positioned, what must be checked, which records must be maintained and who must be contacted when something is unusual.

Cover routine, exception and emergency work

The document should describe normal entry and patrol routines, but also address the moments when judgement matters: an unidentified visitor, a resident complaint, a fire alarm, an unattended package, a medical emergency or an attempted forced entry.

• Shift timing, reporting point and uniform standard
• Visitor, vendor, staff and vehicle procedures
• Patrol route and frequency
• Keys, registers, passes and equipment handover
• Emergency contacts and escalation sequence
• Prohibited conduct and confidentiality expectations

Use post orders as a living operating document

The client and agency should review post orders during mobilisation and again after real operating patterns become visible. Changes should be dated, communicated during shift handover and checked by supervisors. Clear instructions protect residents, visitors, guards and the client organisation alike.

Define authority and legal boundaries

A private security guard protects people or property within the assigned role; the guard is not a police officer. Post orders should state when to observe, challenge politely, deny access under the client's authorised policy, preserve a scene, call the supervisor, contact police or emergency services and record what happened. They should never encourage unlawful searches, punishment, intimidation or concealment of an incident.

The PSARA framework also expects guards to assist police when required and to report violations of law noticed during duty. The practical instruction is simple: prioritise life safety, do not exceed authority, call the appropriate public emergency service and preserve accurate facts for the client and authorities.

Standardise logs, handovers and incident reports

Every record should have a defined purpose. A visitor register captures authorised entry; a material register records assets moving out; a patrol log confirms time and location; a key register records custody. Collecting excessive personal information without a clear reason creates clutter and privacy risk without improving security.

An incident report should distinguish facts from assumptions. Record date, time, location, people involved, observations, immediate action, notifications, evidence preserved and follow-up owner. At shift change, the outgoing guard should hand over open incidents, keys, passes, equipment and unusual site conditions to the incoming guard.

• Use short, legible formats that can be checked during supervision.
• Number pages or protect digital logs against casual alteration.
• Escalate urgent events immediately; do not wait to finish paperwork.
• Store records only for the client's defined operational and legal need.

Train and test the instructions

Issue post orders during induction, demonstrate the difficult procedures and ask the guard to explain them back. Supervisors can test one scenario at a time: an ambulance at the gate, a lost child, an unidentified contractor or a failed access-control device. Short drills reveal gaps that signatures on a document do not.