Post orders are the instruction manual your guards follow when you’re not there. Without site-specific detail, guarding defaults to reactive presence rather than preventive control. This template helps South African property managers, business owners, and facility managers create clear, actionable post orders that turn generic security contracts into effective, documented protection aligned with PSIRA standards.
Executive Summary
- Generic contracts produce generic guarding – “Provide security services” doesn’t tell guards what to do at 2am when someone’s rattling the back gate or a contractor arrives without paperwork.
- Post orders bridge the gap – They translate your site’s risks, routines, and rules into step-by-step instructions guards can follow and supervisors can audit.
- SA context matters – PSIRA compliance, SAPS reporting protocols, POPIA considerations, and local estate or retail procedures must be baked into your briefing.
- You own the brief, not the guarding company – Security providers execute your instructions; if those instructions are vague, the outcome will be too.
- This template works across site types – Office parks, estates, retail centres, warehouses, construction sites. Adapt the sections, keep the structure.
Table of Contents
Why Most Guarding Briefs Fail (And It’s Not the Guard’s Fault)
Here’s what usually happens when a business or estate hires a guarding company: someone signs a contract, a guard arrives on Monday, and the facilities manager or estate chairperson spends ten minutes showing them the panic button and the toilet. The guard is told “just keep an eye on things,” handed a daily occurrence book, and left to figure out the rest.
Three weeks later, management is frustrated. The guard didn’t stop a contractor who wandered into a restricted area. Incident reports are vague or missing. Shift handovers consist of “all quiet” scribbled in the OB book. Vehicles come and go without being logged.
The problem isn’t usually that you hired a bad guard. It’s that nobody told them what “keeping an eye on things” actually means at your specific site.
Think about it like this: if you hired someone to manage your office and said “just handle things,” then got annoyed when they didn’t know how you wanted phones answered, clients greeted, or filing organised, that would be on you. Guards aren’t mind readers, and “provide security services” is about as useful as “handle office things.”
Post orders fix this. They’re the bridge between a contract that says “we’ll guard your site” and the actual daily reality of what happens when a delivery arrives during load-shedding, a tenant reports suspicious activity, or someone tries to access the building after hours without a key.
And here’s the thing: writing them doesn’t require a security degree. You already know your site better than any guarding company ever will. You know where the blind spots are, which doors must stay locked, what time the cleaners arrive, and which contractors have standing access. Post orders are just you writing that knowledge down in a way guards can act on.
The Post-Orders Template: Adapt It, Don’t Copy It
This template is designed for South African sites. It covers PSIRA-accredited guarding across office parks, estates, retail, and light industrial properties. You won’t use every section. Pick what’s relevant, adjust the detail level to match your site’s complexity, and get specific where it matters most.
Section 1: Site Overview and Guard Role
Start with the basics. Guards need to understand what kind of property this is, who uses it, and what their job is here.
What to include:
- Property type and address: “Greenfield Office Park, 47 Lever Road, Midrand. Three buildings, 120 tenants, visitor parking at front, tenant parking in basement.”
- Operating hours: “Business hours 7am–6pm weekdays. After-hours access by prior arrangement only.”
- Guard role summary: “Control vehicle and pedestrian access. Patrol buildings and perimeter twice per shift. Respond to alarms and tenant calls. Log all incidents and maintain daily occurrence book.”
- Key contacts: Who the guard calls when something goes wrong. Include names, roles, and after-hours numbers. “Estate manager: Sarah Nkosi, 082 555 1234. Armed response: XYZ Security, 086 123 4567. SAPS: Midrand station, 011 347 1600.”
Why this matters: Guards who understand the site’s purpose make better decisions. A retail guard needs to think differently about foot traffic than an office park guard. Make it explicit.
Example (office park): “Victory Business Park is a mixed-use office park in Centurion with 15 tenants ranging from accounting firms to tech startups. Tenant staff use access cards. Visitors report to the gatehouse. No residential units. Guard role: access control, building patrols, incident response, daily reporting.”
Example (residential estate): “Sunnyside Heights is a 120-unit sectional title estate in Pretoria East. Residents use remote-controlled access. Visitors and service providers must be logged. Guard role: boom gate control, perimeter patrols, noise complaints, pet control enforcement, contractor management.”
Section 2: Access Control Procedures
This is where guarding either works or unravels. Who gets in? How do they get in? What happens when someone doesn’t have the right documentation or authorisation?
Vehicle access:
- Residents/tenants: “Residents enter using remotes or access cards. Guards do not manually open for residents unless remote is faulty (log the incident and notify estate manager).”
- Visitors: “All visitors must provide ID document and vehicle registration. Guard logs: visitor name, ID number, vehicle reg, time in, unit/tenant visiting, time out. Visitors without ID wait outside boom until occupant collects them or confirms entry.”
- Deliveries and service providers: “Couriers and deliveries must have consignment note or proof of delivery. Service providers (DSTV, plumbers, electricians) must have work order or be confirmed by tenant. Log all service provider entries with company name, technician name, vehicle reg, and authorising tenant.”
- Contractors: “Contractors with standing access (cleaning, garden services, maintenance) are pre-approved and listed on the contractor register. New contractors require written approval from estate manager or tenant before first entry.”
Pedestrian access:
If your site has a pedestrian gate separate from the vehicle boom, spell out the rules. “Pedestrian gate locked after 6pm. Tenants use access cards. Visitors buzz intercom; guard confirms via phone before opening. No pedestrian access for contractors or deliveries (must use vehicle entrance).”
After-hours access:
Be specific about what happens when someone arrives outside normal hours. “After 6pm, only tenants with valid access cards may enter. If a tenant has lost their card, they must contact estate manager for temporary access authorisation (do not open gate based on ‘I live here’ claims). No contractor or visitor access after hours without prior written approval from management.”
What about friends and family?
This trips up estate guards constantly. A resident calls down and says “my brother is coming to visit, let him in.” Does the guard wave him through, or does standard visitor logging still apply?
Be clear: “Residents may pre-authorise visitors by calling or messaging the guard. Guard still logs visitor details (name, ID, vehicle reg, time in/out). Pre-authorisation speeds entry but doesn’t bypass documentation.”
Why this matters: Access control without documented criteria is just a boom gate that opens when someone looks friendly. Every “just this once” exception becomes the new standard unless the post orders make the rules non-negotiable.
Section 3: Patrol Routes and Frequencies
Guards who stand at the gate all shift aren’t guarding the site. They’re guarding the gate. Patrols need to be scheduled, routed, and documented.
Patrol frequency:
“Perimeter patrol every two hours. Building interior patrol once per shift (night shift only). Fire exit checks once per shift. Basement parking patrol every three hours (day shift), every hour (night shift).”
Patrol route:
Describe the actual path. “Perimeter patrol: start at main gate, walk western fence line to rear corner, check back service gate (must be locked), walk eastern fence line back to front, check pedestrian gate (locked after 6pm), return to gatehouse. Estimated time: 15 minutes.”
If your site has specific high-risk areas, flag them. “Pay attention to the rear service yard (blind spot from main gate) and the northwest corner near the old fence section. Check that back roller door is fully closed (it sticks). Shine torch into basement stairwell (loiterers have been reported).”
Patrol documentation:
“Record patrol completion time in OB book. Note any issues observed: lights out, gates left open, suspicious activity, damage, maintenance needed. Photograph anything requiring follow-up.”
Why this matters: “Do regular patrols” means nothing. “Walk the perimeter every two hours and log completion times” is auditable and creates accountability. If an incident happens at 11pm and the last logged patrol was at 6pm, that’s a conversation worth having.
Section 4: Incident Response and Escalation
An alarm goes off. Someone reports a break-in attempt. A tenant calls about a suspicious vehicle. What does the guard do right now?
Alarm activation protocol:
“If building alarm activates: (1) Contact armed response immediately (number above). (2) Do not enter building alone. (3) Observe from safe distance and report any movement, vehicles, or persons to armed response. (4) Once armed response clears the building, log incident in OB book with time, alarm zone, armed response officer name, and outcome.”
Suspicious activity:
“If guard observes suspicious persons on perimeter or hears unusual sounds: (1) Do not confront. (2) Activate panic button if immediate threat. (3) Call estate manager and armed response. (4) Observe and describe: number of persons, clothing, vehicle if present, direction of movement. (5) If safe, take photos from distance. (6) Log incident with full detail.”
Medical emergencies:
“If tenant or visitor has medical emergency: (1) Call emergency services (10177 or 082 911). (2) Notify estate manager. (3) Direct paramedics to exact location. (4) Do not leave post unattended (call for relief guard if needed). (5) Log incident: time, nature of emergency, person’s name, services contacted, outcome.”
Tenant disputes and noise complaints:
This one’s tricky, especially in estates. Be clear about the guard’s role. “If tenant reports noise complaint: (1) Log complaint with time, complainant name, and alleged source. (2) Call estate manager (after-hours number: 082…). (3) Do not knock on the alleged offender’s door or attempt to mediate unless estate manager instructs. (4) If complainant insists on SAPS involvement, provide station number but explain estate manager will follow up during business hours.”
When to call SAPS:
“Call SAPS immediately for: break-ins, vehicle theft, assault, trespassing with refusal to leave, domestic violence situations, suspected drunk driving leaving the estate. For all other incidents, contact estate manager first. SAPS incident case numbers must be recorded in OB book.”
Why this matters: Incident response without a decision tree leads to paralysis (guard does nothing because they’re unsure) or overreach (guard confronts suspects and escalates danger). Clear escalation removes guesswork.
Section 5: Daily Reporting and Shift Handovers
Logging isn’t bureaucracy. It’s proof that your site is monitored, evidence for insurance claims, and the audit trail when something goes wrong.
Daily occurrence book (OB) entries:
“Record at minimum: shift start time, shift end time, patrol completion times, all vehicle entries and exits (visitor log covers this), incidents (no matter how minor), maintenance issues observed, gate or access system faults, weather-related concerns (flooding, storm damage), shift handover notes.”
What counts as an incident?
“Anything unusual or requiring follow-up: alarms, suspicious activity, tenant disputes, access system faults, vehicles parked in no-parking zones, contractors arriving without paperwork, deliveries refused entry, medical calls, SAPS involvement, armed response callouts, power failures, gate damage.”
If nothing happened, write that honestly, but give context. Instead of “all quiet,” write: “No incidents. Four visitor entries logged (see vehicle register). Perimeter patrols at 10h00, 12h00, 14h00, 16h00. No maintenance issues observed.”
Shift handover procedure:
This is critical. Bad handovers are where incidents slip through. “Outgoing guard completes handover sheet listing: vehicles currently on site, contractors still working, expected deliveries, any ongoing issues (e.g., broken gate, tenant awaiting visitor). Handover sheet attached to OB book. Incoming guard reads handover, confirms current site status, and signs acknowledgement. Both guards present for minimum five minutes overlap.”
Why this matters: Logs that say “all quiet” for three weeks and then suddenly describe a major incident create liability questions. Consistent, detailed logging shows the site is actively monitored. And when a tenant claims “I told the guard about this last week,” the OB book either confirms or refutes it.
Section 6: Site-Specific Rules and Protocols
Every property has quirks. The back gate sticks. The alarm panel is temperamental. Contractors must park in Bay 12 only. Rubbish collection happens Tuesdays and Fridays. This section is your catch-all for “things guards must know that don’t fit neatly elsewhere.”
Keys and access devices:
“Guard has keys to: pedestrian gate, gatehouse, main building front door (emergency access only). Guard does not have keys to individual units or tenant offices. If tenant locks themselves out, contact estate manager (do not attempt entry). Lost keys must be reported immediately.”
Alarm codes and procedures:
If guards need to arm/disarm building alarms, provide codes and clear instructions. If they don’t, state that explicitly. “Building alarm codes are held by estate manager only. Guards do not arm or disarm alarms. If tenant requests alarm assistance, refer to estate manager.”
Pets and animal control:
Relevant for estates. “Pets must be on leash in common areas. If guard observes unleashed pet, log incident with unit number and time. Do not approach aggressive dogs. Notify estate manager. If stray animals enter estate, contact local animal welfare or estate manager (do not attempt to catch or feed).”
Parking enforcement:
“Visitor parking bays 1–10 only. Tenant parking in basement with allocated bay numbers. Vehicles parked in fire lanes, no-parking zones, or blocking access must be logged with vehicle reg and time. Contact estate manager if vehicle is not moved within 30 minutes.”
Refuse and cleaning schedules:
“Refuse collection: Tuesdays and Fridays, 6am–9am. Cleaners on-site: Monday, Wednesday, Friday, 8am–4pm (pre-approved, listed on contractor register). Guards ensure refuse trucks exit before 9am (blocks access during business hours).”
Load-shedding protocols:
This is South Africa. You need load-shedding procedures. “During load-shedding: gatehouse runs on backup battery (4-hour capacity). Boom gate operates manually if power exceeds 4 hours (procedure: unlock manual override, lift boom, re-lock after vehicle passes). Building alarms switch to battery backup. Notify estate manager if load-shedding exceeds scheduled times or if backup systems fail.”
Why this matters: Site-specific rules are what separate competent guarding from generic presence. These are the details that actually make life easier for everyone when they’re documented.
Section 7: PSIRA Compliance and Guard Conduct
Your security solutions contract should already specify PSIRA accreditation, but post orders reinforce conduct standards and legal boundaries.
PSIRA requirements:
“All guards must display valid PSIRA registration card on uniform at all times. Guards who arrive without visible PSIRA cards may not commence duty (contact guarding company for replacement guard). Registration must be Grade C or higher for this site.”
Conduct expectations:
“Guards represent estate/property management. Professional conduct required: no sleeping on duty, no alcohol or drugs, no personal visitors to guardhouse, no use of tenant facilities without permission. Mobile phone use permitted for work-related calls only (vehicle logging, incident reporting, contact with management). Personal calls during breaks only.”
Authority and limits:
Be very clear about what guards can and cannot do. “Guards may: refuse entry to persons without proper authorisation, conduct vehicle searches (random or scheduled, with signage), request identification, detain suspects until SAPS arrive (citizen’s arrest only in case of witnessed crime). Guards may not: use force except in self-defence, search persons without consent, enter private property without permission, issue fines or penalties.”
POPIA and privacy:
“Vehicle registers and visitor logs contain personal information. Guards must not share this information with third parties or take photographs of registers. Logs stored in locked gatehouse. Access restricted to estate management and authorised personnel only.”
Why this matters: Conduct standards in writing protect both the guard and the property. When a tenant complains about a guard’s behaviour, post orders provide the benchmark for whether that guard followed instructions or overstepped.
How to Actually Implement Post Orders (Not Just Write Them)
You’ve written site-specific post orders. Now what? Here’s how to turn the document into operational reality rather than a file that lives in a drawer.
Step 1: Walk the site with the guard
Don’t just email the post orders. Schedule 30 minutes on the guard’s first day to physically walk the site together. Show them patrol routes, point out the back gate that sticks, demonstrate how the manual boom override works, introduce them to the estate manager or key tenants. People remember what they see and do, not just what they read.
Step 2: Test understanding
After the walkthrough, ask scenario questions. “A contractor arrives without a work order. What do you do?” “The alarm goes off at 2am. Talk me through your response.” If the guard can’t answer based on the post orders, the orders aren’t clear enough, or the walkthrough didn’t stick. Fix it.
Step 3: Keep one copy at the post, one with management
Guards need access to post orders during shifts. Laminate a copy and keep it in the gatehouse. Management keeps the master version and updates it when procedures change.
Step 4: Review and update quarterly
Sites evolve. New tenants arrive. Access systems get upgraded. Contractors change. Cleaning schedules shift. Review post orders every three months, and whenever something significant changes. A post order that says “call John on 082…” when John left six months ago isn’t helpful.
Step 5: Audit compliance
This is where your residential estate security in Pretoria or office park guarding actually proves its value. Check OB books monthly. Are patrols logged? Are vehicle entries documented? Do incident reports match the level of detail required? If guards aren’t following post orders, figure out why. Is the procedure unclear? Is supervision lacking? Are shifts too long for realistic compliance?
Common Mistakes Property Managers Make (And How to Avoid Them)
Mistake 1: Writing post orders once and never updating them
Your site isn’t static. Post orders shouldn’t be either. That phone number for the estate manager that’s been wrong for eight months? The contractor who finished the job three months ago but is still listed as having standing access? These gaps erode trust in the document. Schedule quarterly reviews.
Mistake 2: Making post orders too vague
“Be alert.” “Keep the property safe.” “Respond to incidents.” These aren’t instructions; they’re platitudes. If you can’t imagine a brand-new guard reading your post orders and knowing exactly what to do in a specific situation, keep writing.
Mistake 3: Making post orders impossibly detailed
The opposite problem: 40-page instruction manuals that nobody reads. Balance detail with usability. Core procedures belong in post orders. Minor updates (new tenant names, contractor schedule tweaks) can live in weekly briefings or updates.
Mistake 4: Assuming the guarding company writes the post orders
Guarding companies can provide templates, but they don’t know your site. They don’t know that the back fence is sagging, that Unit 12’s tenant often forgets his access card, or that contractors must park in Bay 12 because Bay 11 blocks the fire lane. You own the site-specific knowledge. Write it down.
Mistake 5: No feedback loop
Guards observe things management never sees. If a guard consistently logs “rear gate left open after refuse collection,” that’s useful intelligence. Create a feedback mechanism where guards can flag procedural issues, site maintenance needs, or unclear instructions. Post orders should improve based on operational reality.
What Good Guarding Actually Looks Like
Post orders don’t guarantee perfect security. Determined criminals, freak accidents, and unforeseeable incidents happen. But clear post orders dramatically increase the odds that your site is monitored consistently, incidents are documented, and responses follow a logical protocol instead of whatever the guard guesses is appropriate.
Good guarding means a guard who can explain why they denied entry to someone, not just “they looked suspicious.” It means shift handovers that brief the incoming guard on what’s happening, not just “all quiet.” It means an OB book that actually helps you understand what occurred on Tuesday night when the alarm went off, because the guard logged times, actions, and outcomes.
And when something does go wrong (because eventually it will), post orders provide the audit trail for insurance claims, SAPS investigations, and liability assessments. “We had documented procedures, they were followed, here’s the log” is a much stronger position than “we hired a guard and hoped for the best.”
Your retail security in Pretoria or office park guarding is only as good as the instructions you give. Generic contracts produce generic outcomes. Site-specific post orders, walked through on day one, audited regularly, and updated as your site changes, produce accountable, effective guarding.
And honestly? Most properties don’t have them. Which means if you do, you’re already ahead.
Key Facts: Post Orders Essentials
- PSIRA guard grading: Grade C minimum for access control and patrol duties; Grade B for supervisory roles; ensure post orders specify required grade.
- Vehicle register retention: Maintain logs for 90 days minimum; longer if your insurance or lease agreement specifies (some commercial leases require six months).
- Incident escalation timing: Post orders should specify response windows (e.g., “contact estate manager within 15 minutes of alarm activation,” “SAPS for break-ins and assaults immediately”).
- POPIA compliance note: Vehicle logs and visitor registers contain personal information; storage must be secure, access controlled, and retention/disposal aligned with POPIA principles.
- Shift handover overlap: Minimum five minutes for simple sites; 10–15 minutes for complex sites with multiple access points, ongoing contractor work, or high tenant density.
- Post order review frequency: Quarterly minimum; immediately after significant incidents, system upgrades, or staffing changes.
- Authority limits for guards: Guards may refuse entry and conduct vehicle searches (with signage); they may not search persons without consent, use force except in self-defence, or issue fines.
- Load-shedding contingency: All SA post orders must include backup power capacity, manual gate operation procedures, and alarm battery backup protocols.
FAQ (People Also Ask)
Q1: What are post orders in security, and why do I need them?
Post orders are site-specific instructions that tell guards what to do in daily operations and emergencies. They cover access control, patrol routes, incident response, reporting, and site rules. Without post orders, guards default to generic presence rather than active monitoring. Clear post orders convert “provide security” into actionable tasks like “log all vehicles,” “patrol perimeter every two hours,” and “call armed response if alarms activate.” They’re the bridge between a security contract and effective, documented guarding at your property.
Q2: Who is responsible for writing post orders for a guarding company?
Property managers, estate trustees, or business owners write post orders because they know the site’s risks, routines, and rules. Guarding companies execute the instructions but don’t have site-specific knowledge (back gates that stick, contractor schedules, tenant access rules). You can ask your guarding company for a template, but you must customise it with your site’s detail. Effective post orders require collaboration: you provide site knowledge, the guarding company ensures procedures align with PSIRA standards and practical implementation.
Q3: How often should post orders be updated?
Review post orders quarterly at minimum, and immediately after significant changes: new access systems, contractor schedule changes, tenant turnover, security incidents that reveal gaps, or PSIRA regulation updates. Sites that never update post orders end up with documents listing phone numbers for people who left months ago or procedures for systems that have been replaced. Quarterly reviews keep post orders accurate, relevant, and trusted by guards who rely on them daily.
Q4: What should be included in a shift handover procedure?
Effective handovers require a written sheet listing: vehicles currently on-site, contractors still working, expected deliveries, ongoing incidents (e.g., faulty gate, tenant awaiting emergency service), and any instructions from management. Outgoing guards complete the sheet and brief incoming guards verbally (five-minute minimum overlap). Incoming guards read the handover, confirm site status, and sign acknowledgement. Most security gaps happen during shift changes because information isn’t transferred. Documented handovers close that gap.
Q5: Can security guards search vehicles and people on my property?
Guards can conduct vehicle searches on private property if entry conditions are communicated (signage at gate, terms in lease agreements or estate rules). Searches must be consistent and non-discriminatory to avoid disputes. Guards cannot search persons without consent (it’s assault). They can request bag checks, but refusal must result in denied entry, not forced search. Authority limits must be explicit in post orders. Legal advice is recommended if your site requires enhanced search protocols, especially in retail or high-value logistics environments.
Q6: What are the PSIRA requirements for guards at my site?
All guards must be PSIRA-registered and display valid registration cards on duty. Grade C is standard for access control and patrol work; Grade B for supervisory roles. Registration confirms guards have completed required training in security practice, legal powers and limitations, conflict management, and reporting. Post orders should specify “PSIRA Grade C minimum” and instruct gate supervisors to verify visible registration cards before guards commence shifts. Guards without valid PSIRA registration may not work; contact the guarding company for immediate replacement.
Q7: How do I handle load-shedding in security post orders?
All South African post orders must include load-shedding protocols: backup power capacity for gatehouse and boom gate (note duration, typically 4–6 hours), manual boom gate operation procedure if power exceeds backup capacity, alarm system battery backup confirmation, and instructions for guards to notify management if load-shedding exceeds scheduled times or backup systems fail. During extended outages, specify whether patrols increase or access control procedures change (e.g., vehicle logging continues manually even if electronic systems are down).
Q8: What’s the difference between an occurrence book and post orders?
Post orders are instructions (what guards must do). The occurrence book (OB) is documentation (what guards did). Post orders say “patrol perimeter every two hours and log completion times.” The OB book contains entries like “Perimeter patrol completed 14h00, no issues observed” or “Perimeter patrol 02h00, rear gate found open, secured and logged, estate manager notified.” Post orders are written once and updated periodically. OB books are filled out daily. Both are essential: post orders guide action, OB books provide the audit trail.
TL;DR
Post orders convert generic security contracts into site-specific instructions guards can follow and supervisors can audit. Effective post orders cover access control, patrol routes, incident escalation, daily reporting, shift handovers, and site-specific rules. Property managers own the content because they know the site’s risks and routines. Review quarterly, walk through procedures with new guards, and audit OB books monthly for compliance. Clear post orders don’t guarantee perfect security, but they dramatically improve consistency, accountability, and documented incident response across South African estates, office parks, and commercial properties.