Study for the Certified OHS Practitioner (Australia) exam by drilling decisions, not definitions. Practise ranking controls against the hierarchy of control, justifying choices with reasonably practicable reasoning, separating facts from opinion in written reports, and working case scenarios to a fixed method. Alternate content revision with timed scenario drills, and use a self-check rubric to find the reasoning gaps that re-reading notes will not reveal.
Why a PPE-first answer signals hazard-spotting, not practitioner judgment
The hierarchy of control ranks risk controls from elimination down to personal protective equipment. Practitioner-level answers start high in the hierarchy, justify why lower-order controls are needed, and treat PPE as the last layer rather than the first response.
Learn the hierarchy as a reasoning sequence: elimination, substitution, isolation, engineering controls, administrative controls, and PPE. Higher-order controls remove or reduce the hazard at its source, while administrative controls and PPE depend on people complying every time, under fatigue, pressure, and forgetfulness. When you rank controls in a scenario, name the level each control sits at and explain what the control requires of human behaviour. That distinction between source-level controls and behaviour-dependent controls is the core of the concept.
Worked scenario: a workshop uses a solvent-based degreaser and workers report headaches. A plausible mistake is answering 'provide gloves and respirators.' A stronger decision works down the hierarchy: eliminate by switching to an aqueous parts washer if reasonably practicable; if not, substitute a lower-hazard solvent; install local exhaust ventilation; only then issue gloves and respiratory protection with fit-testing and maintenance noted. This matters because ranking controls, rather than naming products, is what demonstrates practitioner judgment, and the drill is designed to build exactly that reasoning.
| Hierarchy position | Control type | Degreaser scenario example | What to document |
|---|---|---|---|
| 1. Highest | Elimination | Remove the solvent process by switching to an aqueous parts washer | Feasibility check and consultation with users |
| 2 | Substitution | Replace the solvent with a lower-hazard product | Comparison of hazards of old and new products |
| 3 | Isolation | Restrict degreasing to a segregated, ventilated bay | Who has access and how access is controlled |
| 4 | Engineering controls | Local exhaust ventilation at the source | Installation, testing, and maintenance arrangements |
| 5 | Administrative controls | Job rotation, procedures, training | Why higher controls did not fully control the risk |
| 6. Lowest | PPE | Gloves and respiratory protection | Fit-testing, maintenance, and residual risk note |
Using 'reasonably practicable' as a weighing test, not a slogan
In Australian WHS contexts, 'reasonably practicable' is a balancing test: it weighs what could be done against the likelihood and consequence of the risk, and the cost, time, and effort of the control. Use it in answers to structure judgment, not to decorate conclusions.
Understand the two sides of the weighing. On one side is how likely and how serious the harm could be; on the other is what is known about the hazard and the availability, suitability, and cost of controls. A control can be discounted if its cost is grossly disproportionate to the risk reduction it would achieve, but difficulty or expense alone does not excuse inaction, and a duty holder's inability to afford a control is not by itself a defence. Practise stating both sides of the weighing in one or two sentences.
Apply the test conditionally, because scenarios supply the facts. Example: guarding a conveyor nip point versus relying on training alone. Write something like: 'If interlocked guarding is available and its cost is not grossly disproportionate to the potential entanglement injury, guarding is reasonably practicable; training alone would leave the hazard unchanged.' The conditional phrasing shows you know the test depends on scenario facts, and it keeps you from asserting a universal real-world conclusion from a simplified paper exercise.
Keeping hazard identification, risk assessment, and risk control distinct
Hazard identification finds what could cause harm; risk assessment analyses how likely and how serious that harm is; risk control selects and implements measures. Case answers lose coherence when these three steps blur into one undifferentiated 'risk management' paragraph.
Practise naming which step each sentence belongs to. 'Unguarded blades, hot surfaces, and congested walkways' is hazard identification. 'Entanglement could cause serious injury, and the walkway layout makes contact likely' is risk assessment. 'Install fixed guarding, reroute the walkway, and then supervise and train' is risk control, with the ordering showing the hierarchy at work. A useful drill is to take a paragraph of mixed writing and label every sentence H, A, or C; the mislabeled sentences are usually where your reasoning is muddled.
The distinction also shapes document structure. A hazard register entry, a risk assessment form, and a control action plan serve different purposes and are read by different audiences, so an answer that claims a toolbox talk 'identifies hazards' reveals a conceptual slip. In case scenarios, present the three steps in sequence and make the hand-offs explicit: what identification found, what the assessment concluded, and what each control is expected to achieve.
| Step | Question it answers | Typical evidence in a scenario | Documentation output |
|---|---|---|---|
| Hazard identification | What could cause harm? | Observed sources of harm, tasks, substances, plant, layout | Hazard register or identification checklist |
| Risk assessment | How likely and how severe? | Injury potential, exposure, people affected, existing controls | Risk assessment record with likelihood and consequence reasoning |
| Risk control | What will be done, and in what order? | Feasible controls ranked by the hierarchy | Action plan with responsibilities, timeframes, and review dates |
Writing investigation documentation that separates facts from blame
Practitioner documentation distinguishes observed facts, analysis of contributing factors, and recommended actions mapped to the hierarchy. A report that attributes an incident to a worker's carelessness offers no basis for corrective action and shows weaker analytical structure.
Worked scenario: a forklift nearly strikes a pedestrian in a warehouse. A plausible mistake is writing: 'The operator was travelling too fast and the worker was not watching; a toolbox talk has been scheduled.' That narrative names people, not conditions, and its single action sits at the lowest effective level. A better report records facts (where the interaction occurred, visibility, whether marked walkways and barriers existed), analyses contributing factors (gaps in the traffic management plan, reliance on administrative controls only), and proposes actions ranked from engineering controls upward, each with an owner and a review date.
This matters because the structure is the analytical skill itself: evidence first, interpretation clearly labelled as interpretation, and recommendations traceable to findings, so a reader can follow each finding to its control without guessing how you got there. It is the writing habit to rehease for both the documentation and the case-analysis study areas. Practise by rewriting blame-style incident notes into this three-part structure until the conversion feels mechanical.
| Report element | Blame-style version | Structured version | Why the difference matters |
|---|---|---|---|
| Opening | Names the person at fault | States time, place, task, and observed conditions | Facts can be verified; labels cannot |
| Analysis | 'Carelessness' as the cause | Contributing factors: layout, traffic plan, control gaps | Multiple factors point to multiple fixes |
| Recommendation | A single toolbox talk | Actions ranked by the hierarchy, each with an owner and review date | Recommendations become derivable from the findings |
A repeatable method for case analysis questions, with a timed drill
Work case scenarios with a fixed method: list the hazards, classify the duty holders and roles, weigh candidate controls against the hierarchy and reasonably practicable reasoning, state your assumptions, and note residual risk. Drilling the sequence under time pressure turns it into a reliable habit for any scenario-based question.
The method prevents two failure modes in your own writing: answering only the first hazard you notice, and producing an unranked list of controls. Under time pressure, write hazards as short bullets before drafting prose, because the listing step is where coverage is decided. Classify roles explicitly, since a PCBU, a supervisor, and a worker carry different obligations in the same scenario, and answers that assign actions to the wrong duty holder read as conceptually confused even when the controls themselves are sensible.
Practical exercise (20 minutes): take any workplace description, real or invented, and answer three questions without notes. Which hazards are present; what control would you recommend first and why; what would you still be worried about after that control. Then score yourself against the rubric below. A score of four or more of five is a reasonable study milestone for moving on; anything lower tells you to repeat the drill with a different scenario before adding new content. The free practice questions for this credential at /free-practice/certified-ohs-practitioner-australia give you extra scenarios to run through the same rubric.
- Named the hierarchy level of each proposed control
- Separated observed facts from your interpretation
- Stated at least one explicit assumption about the scenario
- Included consultation with affected workers in the process
- Flagged residual risk and a review point after controls
Ethics scenarios: knowing when to escalate and where competence ends
Studying ethics and professional standards at practitioner level means building boundary reasoning: acting within your competence, consulting affected workers, reporting honestly, and escalating unresolved risk. Strong answers show a decision path for each boundary rather than a general statement that safety comes first.
Build a stock of boundary responses. If a task exceeds your competence, the answer is to identify the limit, decline to give the unsupported opinion, and refer to or escalate to someone appropriately qualified. If a risk stays uncontrolled after you have raised it, the answer traces a path: document the advice given, escalate internally, and use the available formal channels if the risk remains. Writing out these paths in advance means an ethics scenario becomes a retrieval task instead of an improvisation.
Consultation is the second pillar. Australian WHS frameworks emphasise consulting workers who are affected by health and safety decisions, so answers that show you would talk to the operators before selecting a control demonstrate the standard, not just the technique. Practise by adding a consultation line to every control recommendation in your drills: who you would speak with, about what, and how their input would change the decision if it contradicted your initial preference.
A six-week preparation sequence and concrete readiness checks
Map the syllabus areas onto a six-week cycle: core concepts, safety assessment and interpretation, applied decision-making, methods and documentation, ethics and professional standards, then full case scenarios. Alternate content weeks with drill weeks so application practice is built in rather than left to the final days.
A realistic adaptable sequence: weeks one and two, study the named concepts (hierarchy of control, reasonably practicable, the three-step risk process) and rewrite one real or invented workplace document per week; week three, run three timed 20-minute scenario drills using the section-five rubric; week four, practise investigation-style writing by converting blame narratives into structured reports; week five, rotate ethics boundary drills and consultation planning; week six, complete mixed case scenarios end-to-end and revisit only the rubric lines you repeatedly miss. Adjust the weighting toward whichever area scores lowest in week three, and pull additional scenario material from the study guides collection at /study-guides if you run out of workplace descriptions to work from.
Readiness checks, used as learning milestones rather than pass predictions: you can rank six controls for an unfamiliar scenario and justify each ranking in one sentence; you can state the reasonably practicable weighing in both directions; you can label a mixed paragraph as identification, assessment, or control with no errors; you can write a three-part incident report in fifteen minutes; you can recite your escalation path and competence boundary without notes. A short administrative note: certification levels, eligibility, fees, and application details are set by the AIHS, so confirm them on the issuer's certification page rather than relying on secondary summaries.
- Control ranking justified sentence-by-sentence for an unfamiliar scenario
- Reasonably practicable weighing stated on both the risk and the effort side
- Three-step process labelled correctly in a mixed paragraph
- Structured incident report completed within a self-imposed time limit
- Escalation path and competence boundary stated from memory
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.