Risk Management

Hazard Review vs Task Observation vs Control Verification: Which Evidence Should a Supervisor Trust?

A hazard review, a task observation, and a control verification check different parts of the risk story. This comparison helps supervisors choose the first evidence route, recognize its blind spots, and connect findings to a decision that can actually change the work.

By 7 min read
risk management scene on hazard review vs task observation vs control verification which evidence should — Hazard Review vs T

Key takeaways

  1. 01A hazard review tests whether the team has identified the relevant exposure and selected controls that match it.
  2. 02A task observation tests how the work is actually performed, including the conditions that make a weak practice likely.
  3. 03Control verification tests whether a specified critical control is present, usable, and effective in the current operating state.
  4. 04The first evidence route should match the uncertainty that could make the next decision unsafe.
  5. 05A completed form is not proof of control effectiveness unless the evidence reaches the work and the decision owner acts on it.

A supervisor receives three different signals before a high-risk job begins. The risk assessment says the controls are adequate. A field observation shows that the crew has adapted the sequence to keep production moving. A verification check finds that one specified control is present but difficult to use. Which signal should change the decision?

This comparison is for supervisors, EHS managers, and operations leaders who need evidence that can guide work before exposure becomes routine. A hazard review, a task observation, and a control verification do not answer the same question, so the first method should match the uncertainty that could make the next decision unsafe.

What question does each evidence route answer?

A hazard review tests whether the risk has been understood, a task observation tests how work is performed, and control verification tests whether a specified protection is available and usable now.

A hazard review is strongest when the team needs to reason about exposure before work starts or after the process changes. It examines the task, the initiating events, the possible consequences, and the controls that should prevent or limit harm. ISO 45001:2018 places hazard identification and operational planning inside the management system because a control cannot be managed well when the organization has not defined the exposure it is trying to control. The ISO 45001 standard overview gives the formal context for that expectation.

A task observation begins with a different question. What does the work require when the plan meets the actual conditions of the shift? The observer looks at access, sequence, tools, communication, interruptions, supervision, and the informal adjustments that are often absent from a written assessment. The observation is not a search for a person to blame. It is a test of whether the operating system makes the intended practice possible.

Control verification is narrower and more demanding. It asks whether a named control is present, in the required condition, available to the people who depend on it, and capable of performing its intended function. The National Institute for Occupational Safety and Health's hierarchy of controls keeps the conversation connected to the strength of the protection, rather than allowing a completed instruction to look equivalent to an engineered change. NIOSH's hierarchy of controls explains that control selection logic.

When should a hazard review lead?

Start with a hazard review when the main uncertainty is whether the team has framed the exposure correctly or selected controls that fit the changed work.

This route fits new work, temporary work, non-routine maintenance, process changes, unfamiliar contractors, and jobs where the consequence is serious but the exposure pathway is poorly defined. It is also the right starting point when different people describe the hazard in different ways. Before anyone argues about whether the control is effective, the team needs a shared description of what can happen and why.

A useful review does not stop at a list of hazards. It identifies the event sequence, the point at which exposure becomes possible, the control that should interrupt the sequence, and the evidence that would show the control is working. The review should also name the assumptions on which the decision depends, because an assumption about isolation, staffing, weather, access, or equipment condition can become the weakest part of the plan.

The blind spot is that a well-reasoned review can still describe work that nobody can execute. A control may be technically appropriate but unavailable during the shift, incompatible with the tool, or too slow for the operational rhythm. The hazard review should define what must be observed or verified next instead of presenting the document as final proof.

When does a task observation provide better evidence?

Use a task observation when the uncertainty concerns the gap between the written method and the conditions under which people actually perform the work.

Task observations are valuable when the work contains frequent interruptions, handoffs, production pressure, awkward access, variable equipment, or decisions that depend on local judgment. Those conditions can turn a reasonable procedure into a fragile one without creating an obvious document change.

The observer should follow the task far enough to see the decision points. Which step requires the worker to choose between two priorities? Where does the crew wait for information? Which control becomes difficult when the job is late? What happens when the expected equipment is unavailable? These questions reveal the conditions that shape behavior, which is more useful than recording that a worker did or did not follow a sentence in a procedure.

Observation findings should lead to a specific change. The change may involve equipment, layout, staffing, sequencing, supervision, training, or the procedure itself. If the only outcome is a reminder to be more careful, the organization has recorded the symptom while leaving the condition that produced it untouched.

When should control verification come first?

Start with control verification when a serious exposure may already be present and the decision depends on whether a named protection is available in the current state.

Verification is the right first route when the team cannot confirm isolation, guarding, ventilation, interlocking, access restriction, line identification, fall protection, emergency communication, or another control whose absence would materially change the risk. The supervisor does not need a longer discussion before checking the condition that could make the work unacceptable.

Verification should be specific enough to fail. “Control in place” is too vague. A stronger test states what must be seen, where it must be found, who can confirm it, and what limitation would prevent the work from continuing. The United Kingdom Health and Safety Executive describes the same practical principle in its guidance on controlling risks, which emphasizes selecting controls, putting them into practice, and checking that they remain effective. HSE's risk-control guidance provides a useful external reference for that cycle.

The blind spot is scope. Verification can show that one control is available while missing an unrecognized exposure, a poor task sequence, or a second control that has degraded. A green result is not permission to stop thinking. It is evidence about the control that was tested.

How should a supervisor choose the first method?

Choose the method that can remove the most consequential uncertainty before the next irreversible decision.

Ask what would make the work unsafe if the current assumption were wrong. If the answer is “we may have misunderstood the hazard,” lead with a hazard review. If it is “the written method may not survive the shift,” lead with a task observation. If it is “the critical barrier may not be available now,” lead with control verification.

The decision can be recorded in a short matrix that prevents teams from treating every review as interchangeable.

Evidence routeBest first questionStrongest decisionMain blind spot
Hazard reviewHave we understood the exposure and chosen a fitting control?Define the control strategy before work or changeMay describe work that cannot be executed as planned
Task observationWhat conditions shape the work as it is actually done?Change task design, support, sequence, or supervisionMay overrepresent one shift or one observer's view
Control verificationIs this specified protection present and usable now?Release, pause, escalate, or restore a critical controlMay confirm one control while missing another exposure

The matrix is not a scoring tool. It keeps the evidence attached to the decision it can support. If a supervisor uses a task observation to claim that an engineering control works, the method has been stretched beyond its evidence. If an assessment is used to claim that a field barrier is available, the organization is relying on an assumption.

What should happen when the evidence disagrees?

Treat disagreement between methods as a decision signal, not as a reason to select the most convenient result.

Suppose the hazard review identifies a guarding requirement, the observation shows that the guard is routinely removed for access, and verification confirms that the guard is installed at the start of the shift. The three findings are not contradictory. Together, they show that the control exists but is not reliable across the task sequence.

The response should follow the failure mechanism. A design problem requires design action. A recurring work-around requires attention to access, tools, production demands, or supervision. A missing or degraded control requires restoration before the exposure is accepted. The owner should be able to explain which evidence changed the decision and how the correction will be checked.

James Reason's distinction between active failures and latent conditions remains practical here. A worker's action may be the visible point of failure, while the conditions that made the action likely sit in equipment design, priorities, training, supervision, or management decisions. A review that records only the visible act has not yet explained why the control failed in the work system.

How can leaders prevent evidence theater?

Evidence becomes theater when the organization measures completion instead of using findings to change exposure, control condition, or decision ownership.

A completed review is weak evidence when nobody can state what decision it supported. A high observation count is weak evidence when observations repeat the same finding without changing the task. A verification pass rate is weak evidence when the checklist is easy to pass but disconnected from the condition that matters.

Leaders can test the quality of the process by sampling closed findings. Was the original uncertainty stated clearly? Did the action change the hazard, the control, or the conditions of work? Did someone with authority accept the remaining exposure? Was the result checked under the same operating conditions that produced the original concern?

That last question matters because a correction can pass in a quiet inspection and fail during the busy part of the task. The evidence should travel to the condition that creates the risk, which may require a night shift, a maintenance window, a contractor interface, or a production recovery period.

Which evidence should a supervisor trust first?

A supervisor should trust the method that tests the weakest assumption behind the next decision. Hazard review is strongest for framing the exposure and selecting the control strategy. Task observation is strongest for exposing the conditions that shape work as performed. Control verification is strongest for confirming whether a specified critical protection is available now.

The safest sequence is not always to run all three methods in a fixed order. It is to start where the consequence of being wrong is greatest, then use the other methods to test the limits of the first finding. That approach turns evidence into a decision process instead of a collection of completed forms.

Andreza Araujo's Safety Culture: From Theory to Practice makes the broader point that culture becomes visible in routines and decisions, not only in stated values. In risk management, the same test applies. A control is credible when the organization can explain its purpose, observe its use, verify its condition, and act when the evidence no longer supports the original decision.

Topics risk-management hazard-review task-observation control-verification supervision decision-quality

Frequently asked questions

What is the difference between a hazard review and control verification?
A hazard review examines the exposure, initiating events, consequences, and proposed controls. Control verification examines whether a defined control is present, usable, and working in the current operating state.
When should a supervisor start with a task observation?
Start with a task observation when the main uncertainty concerns how work is performed under real production pressure, including interruptions, access, tools, supervision, and changing conditions.
Can a risk assessment prove that a control works?
No. A risk assessment can justify a control choice, but it does not prove current availability, correct installation, usability, or performance. Those questions require verification and field evidence.
How often should critical controls be verified?
The cadence should follow the control criticality, change exposure, inspection or test requirements, operating experience, and the quality of evidence available. A calendar interval alone should not decide the frequency.
What should a supervisor record after the review?
Record the exposure, evidence used, control status, limitations, immediate safeguards, accountable owner, due date, and the condition that requires escalation or a pause in work.

About the author

Andreza Araújo

Safety Culture Expert | Senior EHS Executive

Andreza Araújo is a safety culture expert and senior EHS executive with more than 25 years of experience in environment, health and safety. She is a Civil Engineer and Occupational Safety Engineer from Unicamp, holds a Master's degree in Environmental Diplomacy from the University of Geneva, and completed sustainability studies at IMD Switzerland. Andreza has served in Global Head of EHS roles in Fortune 500 environments, leading cultural transformation programs across multinational operations. She has represented Brazil as a speaker at the United Nations in Paris and has spoken at the International Labour Organization in Turin. She is the author of more than 16 books on safety culture in Portuguese, Spanish, English and German. Her work has earned more than 10 EHS awards, including two recognitions from Indra Nooyi, former PepsiCo CEO.

  • Civil & Safety Engineer (Unicamp)
  • M.A. Environmental Diplomacy (University of Geneva)
  • Sustainability Cert (IMD Switzerland)
  • People Management & Coaching (Ohio University)
  • UN Paris speaker representative for Brazil
  • ILO Turin speaker
  • LinkedIn Top Voice
  • Indra Nooyi PepsiCo CEO recognition (2x)

Documentaries

Watch Andreza's documentaries

Three productions on safety culture, organizational failure and the human lessons behind major disasters.

Podcasts

Listen to Andreza's podcasts

She hosts three shows on safety leadership, EHS and organizational culture, in English and Portuguese.

Summarize with AI