ISPON HSE Level 1 study materials
ISPON HSE Level 1 study resources

ISPON HSE Level 1: HSE Management Systems and Safety Culture

ISPON HSE Level 1 · Work through your exam, one topic at a time.

All guide sections

HSE Management Systems and Safety Culture

What the exam tests

Management-system frameworks, PDCA, and the difference between safety culture and safety climate, plus leading and lagging indicators.

Frameworks

ISO 45001:2018 (occupational health and safety, which replaced OHSAS 18001) and ISO 14001:2015 (environment) follow PDCA. Plan: context, policy, hazard and aspect identification, legal and other requirements, objectives. Do: resources, competence, operational control, procurement, contractors, emergency preparedness. Check: monitoring, internal audit, incident investigation, compliance evaluation. Act: management review, corrective action, continual improvement. Certification proves a system exists; it does not prove every risk is controlled.

Safety culture, in Reason's ladder from worst to best: pathological (blame and cover-up), reactive (act only after events), calculative (systems and numbers), proactive (act before events, lessons sought), generative (safety is how work is done).

Leading indicators: near-miss reporting rate, inspection completion, training hours, audit close-out. Lagging indicators: LTIFR, TRIR, days lost, compensation claims. A just culture separates human error from reckless behaviour so that reporting stays high.

Worked example

Near-miss reports fall from 40 to 5 in a quarter and management celebrates. Reasoning: the fall probably reflects fear rather than improvement if sanctions followed earlier reports. Fix: remove names from reports, thank reporters, act visibly on findings, and track reporting rate plus close-out time as leading indicators.

Traps

  • Treating an ISO 45001 certificate as proof of legal compliance.
  • Managing only with lagging indicators, which describe the past.
  • Launching a poster campaign and calling it culture change.
  • Investigating incidents to find someone to blame rather than to find system failures.