Engineering ISO 45001 to Defend Section 16(1) Executive Liability

When a critical incident occurs on a South African mining or construction site, the Department of Employment and Labour (DoL) does not investigate the Safety Officer. They investigate the CEO under Section 16(1) of the OHS Act.

Many executives rely on a generic ISO 45001 certification as proof of compliance, assuming the certification alone acts as a legal shield. This is a fatal miscalculation.

Standard Certification vs. Legal Defensibility

ISO 45001 proves you have a framework in place. It does not map directly to the specific local realities required to mount an effective defence under South African law. A DoL inspector investigating a fatality will ask:

• •Did you take every step reasonably practicable to prevent this?
• •Was the hazard actively managed in real-time?
• •Was the specific employee properly trained and warned regarding this exact risk prior to the shift?

If your ISO system is decentralised — living on SharePoint, Excel trackers, and physical Daily Safe Task Instruction (DSTI) books — your legal counsel will struggle to prove active, real-time oversight.

The Command Centre Approach

SHEQ24 aligns ISO 45001 strictly to DoL defence parameters through radical centralisation:

The 16.2 Delegation Chain

Section 16(2) of the OHS Act allows a CEO to delegate specific duties in writing to a competent person. This delegation does not remove the CEO's liability — it creates a chain of accountability. SHEQ24's Appoint module manages this chain digitally, ensuring every 16.2 appointee has acknowledged their responsibilities with a legally binding digital signature, and that their competency certificates are current and on file.

An enterprise compliance OS is not just about passing a SABS audit; it is about protecting the executive team from severe statutory penalties and potential imprisonment.