Incident Investigation

Incident Investigation Evidence Gaps: 4 Decisions That Distort the First 24 Hours

The first 24 hours can determine whether an incident investigation explains the work or merely records the event. This guide identifies four evidence gaps that distort early findings and gives EHS leaders decision rules for preserving evidence, testing accounts, and assigning stronger corrective action.

By 6 min read
investigative scene on incident investigation evidence gaps 4 decisions that distort the first 24 hours — Incident Investigat

Key takeaways

  1. 01The first 24 hours can determine whether an investigation explains the work or only records the event.
  2. 02Scene changes should be stabilized, documented, authorized, and linked to the original operating condition.
  3. 03Early witness accounts are hypotheses until physical evidence, records, and different roles have been compared.
  4. 04Records become useful when they are connected to the task, time, asset, decision, and control available in the field.
  5. 05A strong investigation separates a missed action from the barrier or management condition that allowed the exposure.

The first twenty-four hours after an incident often determine whether an investigation explains the work or merely documents the event. Evidence disappears through routine decisions about scene access, interviews, records, and early conclusions, which means a technically correct method can still produce a weak finding.

This article identifies four evidence gaps that distort an investigation before the formal analysis begins, then turns each gap into a decision rule for EHS managers and investigation leads.

1. What are evidence gaps in an incident investigation?

An evidence gap is a missing, altered, delayed, or poorly connected piece of information that prevents investigators from testing what happened against the work conditions that existed before the event. In the first twenty-four hours, the main risk is not a lack of data. It is accepting an early account before physical evidence, records, and worker knowledge have been compared.

ISO 45001:2018 requires organizations to determine what happened, why it happened, and whether corrective action is needed. That obligation is broader than collecting statements from the people who were closest to the event. It requires an investigation process that can distinguish an immediate action from a contributing condition and a systemic weakness.

James Reason's work on organizational accidents is useful here because it separates active failures from latent conditions. A rushed interview may capture the visible action, while a missing permit review, weak handover, or unavailable safeguard remains outside the record. The evidence gap is the mechanism that lets the visible action become the whole story.

2. Gap one: the scene is changed before it is documented

The first gap appears when the worksite is cleaned, restarted, moved, or repaired before investigators record its original condition. Production, emergency response, and environmental protection may require immediate changes, but those changes do not erase the need to preserve what can still be observed.

A photograph alone is rarely enough. Investigators need the position of equipment, controls, materials, access routes, line of sight, lighting, guarding, alarms, and the condition of the work area. A picture without scale, orientation, or a time record can preserve an image while losing the relationship between objects.

The decision rule is simple. Stabilize the hazard first, then define what may move and who records the change. If the scene must be altered, record the reason, the person authorizing it, the original location where possible, and any available video, maintenance, permit, or control-room record.

That discipline protects the investigation from a common error. The team does not confuse the safest post-event condition with the operating condition that existed when the event occurred.

3. Gap two: the first account becomes the official story

Early accounts are valuable because memory is fresh, yet they are also vulnerable to shock, social pressure, incomplete visibility, and the desire to make the event understandable. The first explanation should therefore be treated as a hypothesis, not as the conclusion.

Investigators should interview the people who performed the work, supervised it, planned it, maintained the equipment, and received the handover. Each person saw a different part of the system. Asking the same open question across roles makes it easier to compare what each person knew, expected, and could actually control.

A useful interview record separates direct observation from interpretation. “The isolation indicator was green” is different from “the equipment was safe to work on.” The first is an observation that can be tested. The second is a conclusion that may depend on a hidden assumption.

The decision rule is to delay causal language until the investigation has compared accounts with physical and documentary evidence. This protects workers from premature blame and protects leaders from closing the review around a story that feels coherent but cannot withstand verification.

4. Gap three: records are collected without their operating context

Permits, procedures, training records, inspection forms, and maintenance histories can make an investigation look well documented while leaving the real decision environment invisible. A form shows what was recorded. It does not automatically show what the team understood, what changed in the field, or which control was available at the moment of exposure.

Every record should be connected to a time, task, person, asset, and decision. A procedure revised after the incident cannot be used as evidence of what workers had before it. A training record confirms attendance, but it does not prove that the instruction matched the task or that the control could be used under the actual production constraint.

Andreza Araujo's safety-culture position is relevant to this distinction. In Safety Culture: From Theory to Practice, the practical test of culture is visible in decisions and routines, not in declarations alone. An investigation should therefore ask how the documented control was used, checked, bypassed, or weakened in ordinary work.

The decision rule is to build a short evidence chain for each important control. Identify the requirement, the expected condition, the field condition, the person who could act, and the information available at the time. This turns a folder of records into an explanation of how the work was actually governed.

5. Gap four: the team confuses a missed action with a missed barrier

An operator may miss a step, but that observation does not explain whether the system made the safe action clear, possible, supervised, and recoverable. Treating every missed action as the root cause narrows the investigation before it has tested the barriers around the person.

James Reason's latent-failure model helps investigators ask what conditions made the action more likely. The relevant questions include whether the task changed, whether the risk assessment still matched the work, whether the supervisor had time to verify the control, and whether the organization had accepted a weak signal as normal.

This does not remove personal accountability. It makes accountability more precise. A deliberate bypass, an unclear instruction, an unavailable control, and a decision made under conflicting priorities require different responses because they represent different failure conditions.

The decision rule is to name the failed action and the failed barrier separately. Then assign an owner who can change each one. If the only action is “remind the worker,” the investigation has probably stopped before it reached the management conditions that allowed the exposure.

6. How should an investigation lead protect evidence in the first day?

The investigation lead should establish a controlled sequence before the team begins debating causes. The sequence should preserve the scene, identify people and records, record changes, test early accounts, and keep hypotheses visibly separate from verified facts.

  • Secure the area and document any necessary change before work resumes.
  • Create an evidence register with the source, time, owner, and verification status.
  • Interview witnesses separately before conducting group reconstruction.
  • Compare records with the task as performed, not only with the written procedure.
  • List competing explanations and specify what evidence could confirm or reject each one.

This sequence is useful for serious incidents, high-potential near misses, and events in which the initial account seems unusually complete. A confident explanation is not the same as a tested explanation.

7. What should leaders review before accepting the findings?

Leaders should ask whether the investigation can explain the work conditions without relying on one person's memory or one form. They should also ask whether the proposed actions change the conditions that produced the exposure or merely restate an expectation.

A sound review checks four links. The evidence must support the finding, the finding must identify a controllable condition, the action must have a named owner and due date, and verification must show whether the risk actually changed. If one link is missing, the investigation is not decision-ready.

Leadership review is not an invitation to rewrite inconvenient evidence. It is a test of whether the organization is willing to see the difference between an individual mistake and a work system that made the mistake likely, difficult to detect, or costly to challenge.

8. The first twenty-four hours should preserve uncertainty, not hide it

The best early investigation is not the one that reaches a conclusion fastest. It is the one that preserves enough evidence to compare plausible explanations before the organization commits to corrective action.

Four decisions matter most. Preserve the scene before routine restoration, treat the first account as a hypothesis, connect records to operating context, and separate missed actions from missed barriers. Those decisions keep the review close to the work and give leaders a stronger basis for prevention.

When an investigation is conducted with that discipline, it does more than assign causes. It shows where risk was visible, where ownership failed, and which change can make the next decision safer. That is the standard an EHS manager should expect before signing off the report.

For more practical conversations about safety leadership and incident prevention, explore the Headline Podcast blog.

Topics incident-investigation evidence-preservation root-cause-analysis safety-leadership serious-injury-fatality-prevention

Frequently asked questions

What is an evidence gap in an incident investigation?
An evidence gap is missing, altered, delayed, or poorly connected information that prevents investigators from testing what happened against the work conditions that existed before the event.
Why are the first 24 hours important after an incident?
The first 24 hours often include scene changes, early interviews, record collection, and initial conclusions. Decisions made during that period can preserve evidence or narrow the investigation around an untested explanation.
How should investigators treat the first witness account?
The first account should be treated as a useful hypothesis rather than the conclusion. Investigators should compare it with physical evidence, records, and accounts from people who performed, planned, supervised, or maintained the work.
What is the difference between a missed action and a missed barrier?
A missed action describes what a person did or did not do. A missed barrier examines whether the system made the safe action clear, possible, supervised, and recoverable under the conditions of the task.
What should leaders check before accepting an investigation report?
Leaders should check whether evidence supports the finding, whether the finding identifies a controllable condition, whether actions have accountable owners and dates, and whether verification will show that the risk actually changed.

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