Private security & SAPS: stronger partnerships, better outcomes — what businesses should expect

South Africa’s private security industry and the police are working closer than before. For businesses that buy security services, that shift matters: it changes what a good security provider does, what you should require in a contract, and how you measure outcomes. Below is a short, practical guide — grounded in recent policy and industry reporting — on how private–public cooperation works, what it actually delivers, and the simple checks you should ask your security supplier to meet.

The reality in two lines

  1. The private security sector is huge and active: PSIRA records show millions of registered officers but a much smaller number who are active on payrolls; the sector remains larger than the police force and continues to grow.
  2. SAPS and the private security industry have formal and informal cooperation arrangements — from information-sharing and joint initiatives to memoranda and provincial MoUs — aimed at faster follow-up, intelligence flow and coordinated operations. Recent SAPS commentary and Police Magazine pieces highlight the growing co-operation.

How cooperation between SAPS and private security actually helps your business

  • Faster evidence handover and follow-up. Private guards are often first on scene. Established liaison channels speed handover of CCTV, statements and tracking data to the police — which improves recovery and prosecution chances.
  • Shared situational awareness. Where private firms feed incident reports into a local picture (hotspot maps, vehicle-recovery logs), SAPS can focus scarce resources more efficiently. Programmes like “Eyes & Ears” and industry–police task teams have been used during high-risk periods (e.g., festive seasons) with useful results. 
  • Complementary capabilities. Private industry often provides continuous monitoring, rapid armed follow-up and telematics-based recovery; SAPS provides criminal investigation and prosecution. When both parties have clear roles, outcomes improve.

Caveats and limits — what the partnership will not do for you

  • It is not a substitute for policing. Private security protects paying clients and commercial assets; it does not replace public policing in under-served communities. Expect cooperation to help in investigations and recovery, not to shift core policing duties.
  • Outcomes vary by precinct and relationships. Where local SAPS stations are under-resourced or relations are weak, cooperation will be limited. A national MoU or policy statement is useful, but the day-to-day value depends on local practice.
  • Regulation is changing. Proposed amendments to the Private Security Industry Regulations in 2025 and PSIRA’s evolving oversight mean compliance standards and reporting requirements are in flux; this affects how companies must operate and how they interface with SAPS.

What a modern, responsible security supplier should offer you (a short checklist)

Ask prospective suppliers to show, in writing, how they will work with SAPS and with you:

  1. Local police liaison protocol. The name and contact details of the local station liaison(s) they regularly use; a simple escalation flow for serious incidents (who calls who, within what time).
  2. Evidence & chain-of-custody process. How CCTV, witness statements and telematics logs are preserved, for how long, and how they are handed over to SAPS.
  3. Verified recovery arrangements. If they offer vehicle recovery or armed follow-up, ask for written SOPs, insurance/indemnity cover, and police coordination steps (and proof of past recoveries, anonymised).
  4. Regulatory compliance. Proof of PSIRA registration for the company and key officers, and an outline of how they’ll meet any new regulatory reporting.
  5. Data-sharing & privacy rules. A clear statement on how incident data (including staff personal data) is stored, shared with SAPS, and protected under POPIA.
  6. Performance KPIs tied to cooperation. Not just “patrols per month” but measurable outputs: time to handover evidence to police, response time to high-risk incidents, recovery rate for stolen assets.

Contract clauses worth adding (practical, not legal-ese)

  • A short “SAPS liaison” clause: supplier must maintain an active liaison and provide contact details on contract start and update them quarterly.
  • Evidence retention guaranteed: CCTV & telematics footage held for X days and exported immediately on request.
  • Recovery & escalation SLA: a written description of how an incident triggers police notification and the supplier’s role afterwards.
  • Compliance warranty: supplier warrants PSIRA registration and confirms observance of current regulations (and undertakes to notify you of regulatory changes that materially affect service).

A quick example (how it plays out)

A retail park experiences an after-hours break-in. The private patrol is first on site, secures the scene, takes initial statements, preserves CCTV footage and notifies the supplier’s control room. The control room alerts SAPS liaison and the local station attends with the evidence already prepared (exported footage, timestamps, witness notes). Faster handover improved the chance of recovery and of a usable case for investigators. That practical sequence — guard → control room → SAPS liaison — is exactly the flow you should require in a provider.

What businesses should do next (practical short steps)

  1. Require the checklist above in procurement (liaison, evidence handling, PSIRA proof).
  2. Test the relationship: run a tabletop incident (30–45 minutes) with the supplier and your local SAPS station to see how it flows in practice. If SAPS can’t or won’t participate, that’s useful information about local capacity.
  3. Include cooperation KPIs in the SLA and review them quarterly (evidence handovers, response times, recoveries).
  4. Watch regulation: ask suppliers how they’ll adapt to the 2025 draft regulation changes and PSIRA oversight improvements.

Final note (a quiet, practical offer)

Private–public cooperation is a real advantage when it’s local, practised and contractual — not just aspirational. If you’re reviewing security contracts this quarter, start by insisting on the three operational proofs above: a named SAPS liaison, a clear evidence-handover process, and PSIRA compliance.

If you want, send me the suburb of one of your sites and I’ll draft a one-page checklist you can drop into a procurement pack — showing exactly how to phrase those three requirements in an RFP or contract. No sales pitch; just a short, usable clause set you can copy and send to suppliers.