Safety Leadership

Field Assurance: 5 Decisions That Keep Risk Evidence Close

Field assurance fails when visits collect observations without changing decisions. These five leadership choices turn field evidence into action.

By 7 min read
leadership scene showing field assurance 5 decisions that keep risk evidence close — Field Assurance: 5 Decisions That Keep R

Key takeaways

  1. 01Define the exposure, control, decision boundary, and proof of usability before beginning a field assurance visit.
  2. 02Verify controls at the transition where work conditions change, because static demonstrations rarely prove operational reliability.
  3. 03Separate an absent control from a failed control so corrective actions address design, ownership, supervision, or degradation.
  4. 04Route bad news to a decision-maker with authority, context, and a response time linked to the exposure.
  5. 05Build a repeatable assurance rhythm with Andreza Araujo's safety-culture perspective, then verify whether leadership claims survive field conditions.

A field visit can look serious while changing nothing. A leader walks the area, asks whether the procedure is followed, records two observations, and returns to the next meeting with a cleaner dashboard but the same exposure.

Field assurance is stronger when it answers a harder question. What evidence would make a responsible leader change the work, escalate the risk, or confirm that the control is operating as intended? The answer depends on five decisions that belong to leadership, not only to the safety function.

Why field assurance is a leadership decision

Field assurance is the disciplined testing of whether a safety control works under the conditions where people face exposure. It is a leadership decision because the result determines priorities, resources, escalation, and ownership.

Inspection is often treated as a search for deviations from a standard. That is useful, although it is incomplete. A standard can be present, a form can be signed, and a control can still fail when the task changes, the equipment degrades, or production pressure narrows the available choices.

OSHA's Recommended Practices for Safety and Health Programs place management leadership, worker participation, hazard identification, and prevention within the same operating system. ISO 45001:2018 follows a similar logic by connecting leadership, consultation, risk assessment, incident investigation, and continual improvement. The common thread is not paperwork. It is the quality of decisions made from evidence.

The Headline Podcast editorial lens is especially interested in that point because senior leaders often receive assurance as a summary rather than as a decision instrument. A good review should make it easier to say what is safe to continue, what must change before work continues, and who has the authority to act.

Decision 1: Define the evidence before the visit

A field review becomes reliable when leaders define the evidence they need before entering the work area, including the control, the exposure, the decision boundary, and the proof that the control is usable.

Without a prior evidence question, the visit drifts toward what is easiest to see. The reviewer notices housekeeping, PPE, and visible order because those features are available to the eye. The review may miss whether an isolation point is correctly identified, whether a rescue decision can be made in time, or whether the supervisor knows when to stop the task.

James Reason's work on latent conditions is useful here. The visible deviation is often connected to design, planning, communication, training, supervision, or competing priorities that existed before the person reached the task. The evidence plan should therefore include the conditions that shape the decision, not only the final behavior.

A senior leader can set four questions before the visit. Which exposure matters most? Which control is supposed to prevent it? What would failure look like in the field? Which person can change the condition if the evidence is weak? That preparation turns a walk into an assurance review.

Decision 2: Verify controls where exposure changes

Controls should be tested at the point where the exposure changes, because a control that works in a quiet demonstration may be unavailable, bypassed, or misunderstood during real work.

Consider a temporary repair, a confined-space entry, or a maintenance task that crosses from routine work into an abnormal condition. The control is not proven by its existence in a procedure. It is proven when the people involved can recognize the change, access the control, and act before the consequence becomes irreversible.

That is why field assurance should follow the work sequence rather than the site map. Observe the handover, the authorization, the first change in task conditions, and the point at which the supervisor must decide whether to continue. Each transition creates a different test of control reliability.

Leaders can use a simple distinction. Ask whether the control is designed, available, understood, and used. If one answer is no, the review should not be closed with a training action by default. The gap may belong to engineering, planning, staffing, maintenance, or decision rights.

For a related view of evidence quality, compare this review with the four evidence levels for safety escalation. The useful question is not how many observations were collected, but how much uncertainty was removed.

Decision 3: Separate absence from failure

An absent control and a failed control require different responses, because one points to a design or ownership gap while the other may reveal degradation, drift, or poor operating conditions.

Suppose a lifting plan does not include the required exclusion zone. That is an absence. Suppose the exclusion zone is marked, but workers and vehicles repeatedly cross it during the lift. That is a failure of operation, supervision, layout, or work planning. Calling both findings a missing procedure hides the difference that should shape the corrective decision.

This distinction also protects workers from shallow conclusions. If every weak result becomes a reminder to follow the rule, the organization may record action without removing the condition that made the rule difficult to follow. A corrective action should state what will change in the work, who owns the change, and what evidence will show that the change held under pressure.

Andreza Araujo's book Safety Culture: From Theory to Practice frames safety culture through the coherence between what leaders declare and what the operation experiences. Field assurance gives that coherence a test. The question is whether the stated control survives contact with scheduling, staffing, equipment, and competing priorities.

Decision 4: Give bad news a route to action

Field evidence only protects people when bad news can travel to a decision-maker who has authority, context, and a defined time to respond.

A review can identify a serious weakness and still fail if the result enters a queue with no escalation threshold. The supervisor may know the exposure is unacceptable, while the manager sees only an open action and a due date. That difference between lived risk and administrative status is where important warnings become late.

OSHA's guidance on management leadership and worker participation supports a practical implication. People must be able to communicate hazards and participate in solutions, while management provides the resources and direction needed to correct them. Speaking up is not the endpoint. The response is part of the control.

Before a field review begins, define what requires immediate stop, what requires same-shift correction, and what can be managed through a planned improvement. The threshold should be tied to exposure and control reliability, not to the seniority of the person who reports the concern.

Leaders who want to strengthen this route can also use the tests that separate safety review from governance. They address the same weakness from the executive side, where follow-through becomes visible.

Decision 5: Close the loop with the owner

Assurance is complete only when the control owner understands the finding, changes the condition, and demonstrates that the revised control works in the field.

Assigning an action is not the same as transferring ownership. The owner needs enough authority to change the condition, enough time to do the work, and enough clarity to know what acceptable performance looks like. When those elements are missing, the action remains attached to a person who can report progress but cannot remove the exposure.

A useful closeout conversation has three parts. Describe the exposure in operational terms, agree on the decision that must change, and set a verification point that tests the changed condition. If the action is only a document revision, ask what a worker or supervisor will do differently during the next comparable task.

This is where the four decision rights behind control ownership become practical. The person who owns a control should be able to recognize its failure, escalate its weakness, and secure the response without waiting for a safety department to carry the entire burden.

A practical field assurance review

A practical review moves from exposure to evidence to decision, then confirms that the person with authority can change the condition before the next comparable task.

For a high-consequence activity, the review can follow this sequence:

  • State the exposure and the control that should prevent or limit it.
  • Ask the people doing the work what changes the risk during the task.
  • Observe the control at the transition where conditions become less predictable.
  • Classify the result as designed, available, understood, used, or failed.
  • Set the escalation route, owner, decision, and verification date before closing.

The sequence is short by design, but it is not superficial. It forces the review to connect what leaders expect with what workers can actually do, which is the point at which assurance either becomes useful or turns into another reporting ritual.

Executive teams need a summary that supports a decision. ?Three observations were raised? is weak. ?The isolation control is present, but the handover does not prove that the next shift can identify the correct boundary. The task remains conditional until the handover is redesigned? is actionable.

What executives should ask next

Executives should ask whether field assurance changes work before exposure becomes an incident, rather than asking only how many reviews were completed.

Five questions reveal the quality of the system. What evidence changed a decision this month? Which control was found to be present but unusable? Where did worker input change the planned response? Which escalation took too long? What action was verified under the same pressure that created the original weakness?

Those questions create a better conversation between operations, safety, and the board. They also resist the temptation to treat assurance as a score. A high completion rate can coexist with weak evidence, delayed escalation, and unresolved ownership.

Field assurance earns its place in leadership governance when it makes uncertainty visible early enough to change the work. That is the standard worth carrying into the next site visit, review meeting, and investment decision.

For more conversations about the decisions that shape safer workplaces, follow the Headline Podcast and continue building a leadership routine that can hear evidence before it becomes a serious event.

Topics field-assurance safety-leadership risk-evidence control-verification executive-safety

Frequently asked questions

What is field assurance in workplace safety?
Field assurance is the structured testing of whether a safety control works under the conditions where people face exposure. It goes beyond checking whether a procedure exists. A strong review examines whether the control is designed, available, understood, usable, and supported by clear ownership. The result should help leaders decide whether work can continue, must change, or requires escalation before the next comparable task.
How is field assurance different from a safety inspection?
A safety inspection usually looks for hazards or deviations in a defined area. Field assurance asks whether the management system and its controls can produce a reliable decision under operating pressure. Inspections remain useful, but assurance adds questions about control purpose, changing conditions, worker input, escalation, and verification. The distinction matters because a clean inspection can coexist with a control that fails during a handover, abnormal task, or production constraint.
Who should own a field assurance finding?
The owner should be the person with enough authority and resources to change the condition that created the exposure. That may be an operations leader, maintenance manager, engineering owner, or project decision-maker rather than the safety professional who recorded the finding. The safety function can challenge the evidence and verify the response, while the operating owner remains accountable for making the control reliable.
What evidence should executives review after a field visit?
Executives should review evidence that connects exposure, control performance, decision rights, and follow-through. Useful evidence includes what changed during the task, what workers reported, where the control became difficult to use, how quickly the concern reached an owner, and whether the corrective action was tested under comparable conditions. Completion counts alone do not show whether risk was reduced.
How does safety culture affect field assurance?
Safety culture affects whether people describe the work honestly and whether leaders respond coherently when evidence is uncomfortable. In Safety Culture: From Theory to Practice, Andreza Araujo emphasizes the gap between declared values and experienced conditions. Field assurance helps close that gap when worker input changes decisions, leaders resource the response, and verification confirms that the operating reality improved.

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