Hazard, Risk, and Exposure: Keeping Three Close Terms Separate
Treat the hazard as the source of potential harm, exposure as the pathway and intensity of contact, and risk as the combined judgment of likelihood and severity. Which of these a scenario asks about determines which answer option is defensible.
These three concepts are not interchangeable, and the difference shows up in what each one implies you should do. A hazard is a property of a thing or activity: an unguarded blade, a reactive chemical, work at height. Exposure describes how people meet that hazard: how close, how long, how often. Risk is a judgment that combines the hazard's severity with the likelihood of contact. An option that 'reduces exposure' does not necessarily reduce the hazard, and an option that 'reduces risk' may be doing so by attacking only one of the two factors. When you practice, watch for options that quietly blur these categories.
Make this a sorting test you run on every option. Ask three questions: what is the agent or energy source, who contacts it and how, and does the proposed action change the source, the contact, or only the consequence? The same test separates a near miss from an incident: a near miss is an event with the same potential for harm but no injury or damage actually realized. If you can classify ten everyday settings into hazard, exposure pathway, and risk driver in a few minutes, you have internalized the sorting; if options keep blurring together, redo the drill with settings from your own workplace.
Worked Scenario: Solvent Degreasing — Why PPE Is Not the Strongest Answer
The hierarchy of controls ranks elimination and substitution above engineering controls, administrative measures, and PPE. A scenario that already shows PPE in place is a good opportunity to ask whether you should stop there or evaluate the higher levels.
Scenario: a parts-degreasing station uses a solvent, and operators report dizziness during the afternoon shift. Current practice is elastomeric respirators plus a refresher training module. The tempting decision is to strengthen what already exists: better fit-testing, a stricter training sign-off, maybe more frequent reminders. This is the plausible mistake. PPE sits at the bottom of the hierarchy of controls because it protects one worker at a time and depends on fit, filter selection, wear-time, and maintenance all holding simultaneously. Training alone changes neither the agent nor the contact.
The better decision starts higher up the hierarchy: evaluate substituting an aqueous or less volatile cleaner, or enclosing the tank with local exhaust ventilation that captures vapor at the source. Substitution removes the agent for everyone at the station, including people who never wear a respirator; engineering controls remove it regardless of compliance. Before choosing, ask whether the higher level is feasible in the scenario, and be able to say why not if it is not. That justification, not the device itself, is what makes a control decision defensible. If your first written instinct is always a piece of equipment on the worker, revisit this section before moving on.
Reading Exposure Data: TWA, Action Levels, and Single-Sample Limits
Compare like with like: an eight-hour time-weighted average is not a short-term reading, and an action level is a program trigger, not a limit. One sample rarely justifies closing an exposure question.
Two boundary distinctions do most of the interpretive work here. First, averaging period: a time-weighted average (TWA) spreads exposure across a full work shift, while a short-term or peak reading captures a brief episode; a number from one cannot be judged against a criterion written for the other. Second, trigger versus limit: an action level is the value that starts a program — monitoring, medical surveillance, controls — while a limit is the value that defines non-compliance. Concluding 'no problem' from a reading below the limit ignores that the action level may already have been crossed.
Worked example, with assumptions labeled: suppose your program's hearing-conservation action level is 85 dBA as an 8-hour TWA, and a dosimeter returns an 87 dBA TWA on one shift. The mistake is to compare 87 against a higher limit, decide the number is 'not that bad,' and file the report. The better decision treats 87 as a program trigger: compare the same metric against the same criterion, repeat sampling across different shifts and tasks because a single dosimeter run may not represent variability, and begin the actions the trigger requires. The lesson generalizes: every exposure number carries three pieces of context — metric, averaging period, and criterion — and a defensible interpretation names all three.
Worked Scenario: The Ladder Fall — Stopping at 'Carelessness' Ends the Investigation Too Early
Investigation distinguishes the immediate cause, the event that directly triggered harm, from root causes in the system that allowed the event. Answers that blame individual behavior without tracing system conditions are premature.
Scenario: a maintenance worker falls from a step ladder while reaching sideways to service overhead equipment and fractures a wrist. The tempting decision is to record the immediate cause — lost three points of contact — assign refresher ladder training, and close the case. This is the mistake: it treats the last unsafe act as the whole explanation. A root-cause approach keeps asking why at each layer: why was a step ladder used for a two-handed task at height, was a more suitable platform available, who assigned the task and with what planning, and when was the ladder last inspected?
The better decision follows that chain to the system conditions, using a structured method such as repeated whys or a fishbone diagram grouped by people, equipment, environment, and procedure. Suppose the trace shows the platform lift was unavailable that day and the task was assigned to meet a same-day deadline. The corrective actions now differ in kind: equipment availability and task-planning controls, not merely training the injured worker. This matters because the two decision paths produce different futures — the first path waits for the next fall to see whether training worked, while the second removes the conditions that produced the fall.
Documentation That Holds Up: Findings, Owners, and Closure
Defensible documentation shows a finding, an assigned owner, a due date, and verified closure. A checklist tick, a verbal warning, or a sign-in sheet each fail that standard in a different way.
Distinguish three record types that are easy to mix together in practice. An inspection or audit record documents what was observed, where, and when — a checklist tick without the observed condition proves little. A corrective action log connects each finding to an owner, a due date, and verification that the fix actually works; without the closure step, the record shows intent rather than resolution. A training record must show more than attendance: content covered, date, provider, and some verification that understanding was achieved. Each type answers a different question, and an option that quietly substitutes one for another is describing a weaker system.
When you evaluate options, the language itself is the tell. 'Employees were informed of the hazard' describes a conversation; 'the finding was documented, assigned, tracked to closure, and verified on re-inspection' describes a system. The second is defensible precisely because it survives the question 'how do you know?' — about the condition, the fix, and the training alike. Build the habit into your practice answers: any decision you write should end with how completion will be verified, not merely announced. If your scenario write-ups routinely stop at 'workers were told,' your documentation reasoning is the weakest link to strengthen.
Decision Table: Matching the Situation Signal to the Strongest First-Line Response
Use this table as a pattern-recognition drill: for each situation signal, decide your own first-line response before reading the strongest one, then note why the tempting shortcut falls short in that specific case.
Cover the right-hand columns and work down the left. For each signal, write your first-line response and one sentence rejecting a lower control level. The value of the table is not memorizing its rows but rehearsing the reasoning pattern: every row's shortcut protects the worker at the point of contact, while every stronger response changes the source, the path, or the interaction itself.
Adapt the rows to your own industry by replacing each signal with one you have actually seen, and rebuild the table from scratch a week later. If your rebuilt versions consistently land on administrative rules or personal protective equipment first, that pattern is exactly what to drill against using the hierarchy section earlier in this guide.
| Situation signal | Strongest first-line response | Why the tempting shortcut falls short |
|---|---|---|
| Unguarded point of operation on a machine press | Engineering control: fixed or interlocked guard at the source | Rules and PPE depend on moment-to-moment compliance and do not separate the worker from the energy |
| Recurring solvent odor near a degreasing station | Substitution with a less volatile cleaner, or local exhaust capture at the source | Diluting the air around the worker or issuing respirators leaves the agent in place |
| Repeated forklift–pedestrian near misses at the same corner | Engineering: physical barriers, separated walkways, visibility aids at the intersection | Painted lines and reminders reduce neither vehicle path nor pedestrian path |
| Compressor noise above the program's action level | Acoustic enclosure or treatment at the source | Hearing protection is the last line and fails through fit and wear-time |
| Trips caused by debris accumulating along a walkway | Elimination: change the material flow or add containment so debris never reaches the path | Housekeeping training does not change the walking surface or the source of debris |
A Four-Week Scenario-Drill Sequence with a Self-Check Rubric
Spend two weeks rebuilding concept boundaries, then two weeks on timed written decisions. Score your answers against the rubric below; treat scores as learning milestones, not predictions of any passing standard.
Weeks one and two: rebuild boundaries before drilling decisions. Work through the paired concepts in this guide — hazard versus risk versus exposure, TWA versus short-term reading, action level versus limit, immediate versus root cause, checklist versus closed-loop documentation — and write one original two-sentence example for each pair showing the boundary. Then take one full practice scenario per day from the free practice set, with the options covered, and write your decision before reading them. Weeks three and four shift to timed written drills using the five-line format: hazard class, exposed group, control level chosen, why higher levels are impractical here, and how completion will be verified. Target roughly three minutes per written decision without notes.
Score each five-line answer against this rubric, one point per line: names the control level explicitly rather than only the device; justifies rejecting higher controls with a feasibility reason specific to the scenario; distinguishes triggers from limits when numbers appear; identifies the root-cause layer rather than stopping at behavior; and ends with verification and closure. Four out of five across consecutive answers is a reasonable milestone that your decision reasoning is consolidating. Readiness checks before exam day: you can classify ten unfamiliar hazards into source, pathway, and risk driver in under ten minutes; you can recite the hierarchy with a different example for each level from memory; and your last five rubric-scored answers all include the verification line. For administrative details — eligibility, scheduling, current requirements — rely on the issuer, TEEX, rather than on study materials: see https://teex.org.
- Week 1: write boundary examples for the five concept pairs; no timed drills yet.
- Week 2: one daily scenario, decision written before reading options; compare against the decision table.
- Week 3: timed five-line written decisions, scored against the rubric; log which rubric line fails most often.
- Week 4: rebuild the decision table from memory with your own industry rows; retake your two weakest earlier scenarios.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.