Focus your preparation on clause-to-evidence mapping: for every scenario fact, name the ISO 45001 clause whose process it tests, then write the finding as a system gap rather than a hazard description. Worked scenarios, a hierarchy-of-controls table, and a finding-grading rubric in this guide give you repeatable drills with self-checkable outputs.
Mapping Scenario Facts to Clause Requirements Instead of to Hazards
Scenario questions describe hazards, but ISO 45001 requirements address the processes that manage hazards. A defensible finding names the failed process — hazard identification, risk assessment, operational control — and cites the clause requiring that process.
Consider a scenario where a warehouse pedestrian is nearly struck by a forklift. The instinctive draft reads: 'Risk of forklift-pedestrian collision is not controlled.' That sentence audits the hazard, not the organization. ISO 45001 does not require the absence of collisions; it requires the organization to identify hazards (6.1.2.1), assess the resulting risks, plan and implement controls (8.1), and monitor performance (9.1). A stronger draft notices that near-miss reports existed but the risk assessment had never been revised, which points squarely at hazard identification and the planning cycle.
Push the same scenario one step further. The site has painted walkways, yet visiting contractors regularly cross them with pallet trucks. 'Walkways are inadequate' is again a hazard statement. The audit question is whether hazard identification ever covered contractor activities, which 8.1.4 addresses through procurement and contractor controls. The improved finding — hazard identification did not include contractor transport operations, contrary to 6.1.2.1 — matters because a clause-cited, process-focused gap can be verified, graded, and closed out, while a hazard-only statement invites argument and gives the organization no defined corrective path.
OH&S Risk, Other Risk, and OH&S Opportunity: Three Planning Objects
Clause 6.1 separates OH&S risks and opportunities, which concern worker safety outcomes, from other risks and opportunities, which concern the management system itself. Training must build the skill of grading the right object: harm to workers or failure of system effectiveness.
An OH&S risk is the effect of uncertainty on worker safety — for example, silica dust exposure during concrete cutting. Other risks to the OH&S management system look different: a single site supervisor holding all contractor-approval knowledge, a monitoring programme too weak to detect drift, or the loss of the only person competent to run incident investigations. OH&S opportunities (6.1.2.3) are chances to enhance performance, such as redesigning a task to remove manual lifting altogether. The planning requirement in 6.1.1 obliges the organization to address both families, so mixed narratives deserve classification practice.
Run a classification drill: take a fit-out scenario and label five facts. A new solvent introduced to a paint line is an OH&S risk requiring assessment under 6.1.2.2. The safety committee meeting cancelled indefinitely is an other risk to consultation and participation under 5.4. Adopting a pre-fabricated stair assembly that eliminates work at height is an OH&S opportunity. Expected observation from your first attempt: you will probably classify at least one system-level fact as a safety hazard. Correcting that mislabel matters because the actions the organization must plan, and the clauses an auditor would test, differ for each object.
Worker Consultation Under 5.4 Versus Communication Under 7.4
Consultation means seeking workers' views before decisions on defined OH&S matters; participation means involving them in the decisions themselves. Communication under 7.4 is the planned exchange of information. Scenario practice must train you to separate these mechanisms where they overlap.
Worked scenario: a facility buys a new chemical, briefs workers on handling at the next monthly meeting, and posts the safety data sheet. The communication obligation in 7.4 is arguably satisfied. The gap sits elsewhere: workers were never asked for their views on the chemical's hazards before the purchasing decision, and 5.4 requires consultation on hazard identification, and 8.1.4 covers procurement. The plausible mistake is citing 7.4 because briefings visibly occurred; the better decision is to test 5.4, because the missing element is two-way input before a decision, not one-way information afterwards.
Why the distinction matters: the corrective actions diverge completely. A 7.4 finding leads to revising the communication plan — who needs what information, when, and how. A 5.4 finding leads to establishing a mechanism through which workers' non-management input reaches decisions on hazard identification, incident investigation, and control selection. When you draft an answer, ask one diagnostic question: did information flow out to workers, or did views flow in before the decision? The direction of flow tells you which clause the scenario engages, and citing the wrong one produces a finding the organization cannot meaningfully correct.
Grading Findings: Correction, Minor Nonconformity, Major Nonconformity, or OFI
A major nonconformity signals the absence or total breakdown of a required process; a minor nonconformity is an isolated lapse in an otherwise functioning process; an opportunity for improvement applies where the requirement is met but performance could still strengthen.
Keep evidence and findings distinct while grading. Evidence is objective, verifiable fact: an inspection record, an interview statement, a missing signature. A finding is the result of evaluating that evidence against a requirement. Scenario test: one ladder out of twelve lacks its inspection tag versus an emergency preparedness process under 8.2 that has never produced a single drill anywhere. The isolated lapsed tag supports a minor nonconformity; a wholly absent drill programme suggests the 8.2 requirement is not functioning at all, which supports a major grading. An organization that fixed the tag but never analysed why it lapsed has performed a correction, not yet a corrective action under 10.2.
Add a consistent interrogation before you finalize any grade: Is the requirement absent, or merely lapsed once? Would the lapse plausibly recur without system change? Does the same evidence indicate other sites or shifts are affected? Then state the finding in the standard three-part structure — requirement cited, objective evidence described, gap stated — and only afterwards attach the grade. Treat grading as a heuristic anchored in your programme's definitions, because conventions differ between certification body schemes. The fastest building exercise: grade ten practice findings and justify each grade in one sentence; sentences that rely on 'it feels serious' reveal drafts that are not yet clause-anchored.
- Absent or broken process across the scope of the audit → supports a major nonconformity.
- Isolated lapse inside a demonstrably working process → supports a minor nonconformity.
- Requirement met, but a stronger method exists → opportunity for improvement, not a nonconformity.
- Hazard removed or evidence patched without cause analysis → correction only; the 10.2 trail remains open.
Applying the Hierarchy of Controls in 8.1.2 Scenarios
Clause 8.1.2 requires hazards to be eliminated and OH&S risks reduced using the hierarchy of controls, with personal protective equipment as a lower-order, last-resort measure. PPE-heavy scenarios are prompts to audit whether the hierarchy was applied, not merely whether PPE was issued.
Worked scenario: a machining shop reports rising noise levels; the response was issuing new earplugs and a PPE sign. The plausible mistake is recording conformity because protective equipment exists. The better decision tests 8.1.2: did the organization consider elimination, substitution, or engineering controls such as enclosures, and is that consideration documented? If the assessment cannot show why lower-order options were rejected or deferred, the finding is that the hierarchy was not applied — a system gap — rather than 'noise exposure persists', which is the hazard-statement trap section one described.
Use the same table in reverse during preparation: for each level, generate an audit question you would ask in a scenario. That converts a memorized list into a decision routine you can run under time pressure. It also disciplines your language: 'PPE is always wrong' overstates the clause. PPE is legitimate where higher-order controls are genuinely impractical; the audit issue is whether that judgement was made and recorded. Match the certainty of your finding to what the scenario evidence actually shows about the decision process.
| Control level | Typical scenario example | Audit question to ask |
|---|---|---|
| Elimination | Prefabricated stairs remove all work at height | Was removal of the hazard assessed as an option? |
| Substitution | Water-based coating replaces a solvent | Were less hazardous substances or processes evaluated? |
| Engineering controls | Machine guarding, local exhaust ventilation, acoustic enclosure | Were physical controls designed and verified before relying on behaviour? |
| Administrative controls | Job rotation, permits, exposure-time limits | Are procedures implemented and monitored, not just written? |
| PPE | Earplugs, gloves, respirators | Why were higher-order controls rejected, and is that reasoning documented? |
Auditing the Corrective Action Trail in 10.2 After an Incident
Clause 10.2 requires incident investigation, cause determination, corrective action, and review of effectiveness, with worker consultation where appropriate. Scenario practice trains auditors to follow the full trail instead of accepting the first visible fix as closure.
Worked scenario: a worker suffers a chemical splash; the organization issues splash-resistant gloves and updates training on that product. The plausible mistake is closing the finding on the strength of the gloves and the training record — that is a correction plus some action, not a completed corrective action. The better decision requests the investigation file: Was the incident investigated promptly with worker consultation? Did the cause analysis explain why the original control failed? Did the organization evaluate whether similar tasks or chemicals share the same weakness? Is there evidence of an effectiveness check after implementation?
Why it matters: each missing link is itself a gradable nonconformity, and which link is missing determines the clause you cite. No cause analysis points at 10.2's investigation requirements; no check of similar operations points at the same clause's requirement to review the effectiveness of actions and the need for changes to the OH&S management system; no worker input points back to 5.4. Practise writing the follow-up request list you would issue for such a scenario — the specific documents and interviews — because that mirrors what an auditor must see before declaring a corrective action complete.
A Five-Phase Preparation Sequence with a Finding-Writing Rubric
Sequence your study around output production: rebuild the clause map, convert hazards into requirement statements, grade findings against a rubric, mix timed scenario sets, then loop back to weaknesses. Score your own drafts; the rubric below defines what a finished answer contains.
Phase one: reproduce the clause structure 4 through 10 from memory, then check it against the standard and mark where documented information is explicitly required. Phase two: clause-to-evidence drills — write one short workplace scenario per clause, then rewrite each hazard statement as a requirement statement, as practised in section one. Phase three: grading drills using the interrogation questions from section four. Phase four: mixed sets of scenarios drawn from your practice bank, answered under a self-imposed time limit per question. Phase five: a weakness loop — re-drill any clause where your drafts needed three or more revisions. Spread the phases over whatever weeks you have available; the ordering, not the calendar, does the work.
Score every practice finding against this five-point rubric, one point per item: a clause is cited; the finding states a system gap rather than a hazard; the evidence described is objective and specific; the grade is justified in one sentence; a follow-up request lists what the organization must show. A self-check milestone to aim for before moving to mixed sets: eight out of ten drafted findings satisfy all five points. That score is a learning milestone signalling your drafts are internally consistent — it indicates readiness to attempt full timed practice, not a prediction of any exam result. For administrative details of the credential itself, rely on your certification body rather than study materials.
- Readiness check 1: you can reproduce the clause 4–10 map and name what each clause requires of the organization.
- Readiness check 2: given a narrative, you can classify facts as OH&S risk, other risk, or OH&S opportunity without hesitation.
- Readiness check 3: you can grade a set of findings with written justifications that reference process absence or lapse, not severity feelings.
- Readiness check 4: your finding drafts consistently pass the five-point rubric before you reread the model answer.
- Readiness check 5: you can list, unprompted, the evidence an auditor needs before closing a corrective action under 10.2.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.