14.3 Non-conformance, Corrective Action and Continual Improvement

14.3 Non-conformance, Corrective Action and Continual Improvement

[!NOTE] SACPCMP Blueprint Context: This section closes the performance chapter by covering what happens after an inspection, audit or investigation produces a finding. It draws on ISO 45001 clause 10.2, on GAR 9(3) and 9(4), and on the stop-work and remediation duties in CR 5(1)(q) and CR 7(1)(c)(viii).

---

1. Classifying What You Found

Before any corrective action can be designed, the finding must be classified correctly, because the classification determines who owns it and how fast it must move.

• Unsafe condition — a physical state: an unguarded penetration, a damaged sling, an untagged scaffold.
• Unsafe act — a behaviour: a worker unclipping to move along a leading edge.
• System non-conformance — a required process is absent, undefined, or not followed: no anchor points were designed into the slab edge, so unclipping was inevitable.
• Legal non-compliance — a specific statutory duty is unmet: no fall protection plan exists at all, contrary to CR 10(1)(a).

The most common professional failure in South African construction is stopping at the second category. "Worker did not clip on" produces a disciplinary record and changes nothing. Behind almost every unsafe act sits a system non-conformance, and the CHSO's value lies in finding it.

---

2. The Corrective Action Notice

A corrective action notice (CAN) is the instrument that moves a finding to closure. A defensible CAN has seven fields, and an auditor reviewing another contractor's system should test for exactly these:

The last field is the one most often missing and the one that determines whether the same finding recurs.

---

3. Root Cause: Going Past the Obvious

Root cause analysis techniques are covered in detail in the incident investigation chapter; here the point is that they apply equally to audit findings, not only to injuries. The three questions that reliably move an analysis from symptom to cause on a construction site are:

1. What made the safe way harder than the unsafe way? Workers overwhelmingly take the path of least resistance. If the nearest anchor point is 12 metres away and the task takes 40 seconds, the control has designed its own defeat.
2. What changed? New subcontractor, new shift pattern, new supervisor, design revision, weather, programme pressure. Most site failures are traceable to a change that was not managed under ISO 45001 clause 8.1.3.
3. Who was supposed to catch this, and why didn't they? If a weekly CR 24(d) electrical inspection should have found a damaged distribution board and did not, the corrective action belongs to the inspection process, not just the board.

---

4. Choosing the Control Level

A corrective action that sits low in the hierarchy of controls is a corrective action that will need repeating. Rank every proposed action:

CR 10(4)(d) is a legislated hierarchy: it does not merely prefer fall prevention over fall arrest, it prohibits reaching for arrest while prevention remains reasonably practicable. Any corrective action that proposes harnesses where guardrails would work is, on its face, non-compliant.

---

5. Escalation and Continual Improvement

Not every finding belongs to the site. A finding that recurs across three audits, or that appears on multiple sites in the same contractor's portfolio, is evidence of a defect at a level the site cannot fix — procurement buying non-compliant equipment, a training provider producing incompetent operators, a tender that priced insufficient supervision. Those findings must escalate to management review under ISO 45001 clause 9.3, where resource decisions can actually be taken.

The measure that tells a CHSO whether the loop is working is not the number of findings raised. It is:

$\text{Corrective action close-out rate} = \frac{\text{Actions verified effective by due date}}{\text{Total actions raised}} \times 100$

A site raising 60 findings a month with a 90 per cent verified close-out rate is healthier than a site raising 6 findings a month with a 40 per cent rate. High finding counts with high close-out rates indicate a system that is looking hard and fixing what it finds; low finding counts indicate a system that has stopped looking.

[!IMPORTANT] Statutory close-out has its own timetable. For incidents, GAR 9(2) requires investigation within 7 days from the date of the incident; GAR 9(3) requires the findings to be entered in Annexure 1 immediately after the investigation is completed; and GAR 9(4) requires the record to be examined by the health and safety committee at its next meeting, with the necessary actions implemented and followed up to prevent recurrence. Section 19(4) requires that committee to meet at least once every three months, so a corrective action arising from an incident must not be parked until a meeting that may be eleven weeks away — the follow-up duty is continuous, and the committee examination is a governance checkpoint on top of it.