Khanyitas

POPIA Staff Training: What's Actually Required

23 May 2026 · Information Officers and HR managers

POPIA Staff Training: What's Actually Required

For Information Officers and HR managers trying to get their organisations compliant, staff training is one of the most visible — and most misunderstood — requirements under the Protection of Personal Information Act. This article unpacks what the Act says, what the Information Regulator's guidance indicates, and where organisations commonly fall short.

> Disclaimer: This article is general information based on published Information Regulator guidance and the text of POPIA. It is not legal advice. For your specific situation, consult a qualified attorney.

---

Why Training Sits at the Heart of POPIA Compliance

POPIA is not just a policy-on-paper exercise. The Act establishes that personal information must be processed lawfully and that organisations — referred to as responsible parties — are accountable for how their people handle data. If an employee mishandles a customer's personal information, the responsible party bears accountability, not only the individual.

This accountability logic is what makes staff training structurally important. An organisation can have the best privacy policy in the world; if the people processing data every day have never read it or do not understand it, the policy provides little real protection.

---

What POPIA Says About Training

POPIA does not prescribe a specific number of training hours, a course format, or a certification standard. What it does do is create a framework of duties that are practically impossible to meet without a trained workforce.

Section 55 places duties squarely on the Information Officer. Among other responsibilities, the Information Officer is required to encourage compliance with the conditions for lawful processing, deal with requests from data subjects, and work with the Information Regulator. Fulfilling these duties in an organisation where staff are unaware of basic data-handling obligations is not realistic — which is why the Information Regulator's guidance consistently emphasises awareness and training as a core component of a compliance programme.

Section 19 requires a responsible party to put appropriate, reasonable technical and organisational measures in place to prevent loss, damage, or unauthorised access to personal information. Regulatory guidance from the Information Regulator (inforegulator.org.za) treats staff awareness training as an organisational measure that contributes to section 19 compliance. An untrained employee who clicks a phishing link, emails a customer list to the wrong address, or leaves a printed form on a shared desk is a foreseeable organisational risk — and a risk that training is designed to reduce.

Section 17 requires responsible parties to maintain documentation of their processing activities. Training records are part of the broader documentation picture that demonstrates a good-faith, structured compliance programme.

---

What the Information Regulator's Guidance Indicates

The Information Regulator has published a POPIA compliance framework and various guidance notes (available at inforegulator.org.za). Across these materials, the Regulator's position is consistent: staff awareness is not optional. Organisations are expected to be able to demonstrate that employees who handle personal information understand:

The Regulator's guidance does not specify that training must be delivered in any particular format. In-person workshops, e-learning modules, documented induction sessions, and regular refreshers are all recognised approaches — what matters is that the training is documented, role-appropriate, and actually delivered.

---

Role-Appropriate Training: A Practical Framework

Not every employee needs the same depth of training. A practical approach ties training content to how closely a role interacts with personal information:

All staff (baseline awareness) - What counts as personal information - The organisation's privacy policy and how to find it - How to recognise a potential breach and who to report it to - Basic secure-handling practices (clean-desk, password hygiene, phishing awareness)

Staff who regularly collect or process personal information (customer-facing roles, HR, finance) - Lawful basis for processing (section 11) - Purpose limitation: why data collected for one purpose cannot simply be reused for another (section 15) - Notification obligations when collecting data directly from a person (section 18) - Handling data subject requests (sections 23 and 24)

Information Officers and compliance leads - Full working knowledge of all conditions for lawful processing - Breach notification obligations and timelines under section 22 - Restrictions on special personal information (sections 26 and 27) - Cross-border transfer requirements under section 72 - Maintaining the record of processing activities (section 17) - Liaison with the Information Regulator

---

Common Gaps the Information Regulator Flags

Based on published enforcement communications from the Information Regulator, these are recurring weaknesses in organisational training programmes:

  1. Once-off induction with no refresh cycle. Staff who received a single briefing three years ago are unlikely to remember it — or to know about regulatory updates since then.
  2. Generic training not linked to actual processing activities. A logistics company whose drivers handle delivery addresses has different risks from a medical practice. Training that doesn't reflect the organisation's real data flows is less effective.
  3. No documentation. The absence of attendance registers, completion certificates, or training records makes it very difficult to demonstrate compliance in the event of a complaint or investigation.
  4. Ignoring operators and temporary staff. POPIA's obligations extend to processing by operators (third parties who process on your behalf) and the Regulator expects responsible parties to ensure that temporary and contract staff who handle personal information are also trained.

---

Practical Steps for Information Officers and HR Managers

  1. Map your processing activities first. Understand what personal information your organisation collects, who handles it, and at which points. This shapes your training design.
  2. Document everything. Keep records of who was trained, when, on what content, and with what outcome. Link this to your section 17 processing records.
  3. Build a refresh cycle. Annual refreshers are widely recommended. Trigger an out-of-cycle refresh when there is a significant regulatory development, a new product line, or an internal breach.
  4. Assign accountability. The Information Officer is ultimately responsible, but day-to-day delivery can sit with HR. Make sure the handoff is explicit and documented.
  5. Test, don't just tell. Short assessments — even simple quizzes — give you evidence that training landed and flag staff who need additional support.

---

A Note on Special Personal Information and Sector-Specific Rules

Organisations that process special personal information (health data, biometric data, religious or political views, and similar categories listed in section 26) face stricter requirements. Training for staff who handle these categories should cover section 26's prohibitions and the narrow circumstances under section 27 in which processing may be authorised. If your sector is also subject to FICA obligations, additional staff competency requirements apply — consult the Financial Intelligence Centre's published guidance at fic.gov.za.

---

Bottom Line

POPIA does not hand organisations a training syllabus — it hands them accountability. The practical consequence is that any credible compliance programme needs documented, role-appropriate staff training delivered on a regular cycle. The Information Officer carries formal responsibility for driving this, and HR typically owns the mechanics of delivery.

If your organisation has not yet formalised its POPIA training programme, the published guidance at inforegulator.org.za is the right starting point.

> Disclaimer: This article is general information based on published Information Regulator guidance and the text of POPIA. It is not legal advice. For your specific situation, consult a qualified attorney.