EHS glossary>Safety term

The Definition of Incident Investigation

Incident investigation is the structured process of finding out what happened, why it happened and what must change so an injury, near miss or other unplanned event does not happen again.

Plain-English definition
Real-world example
Incident Investigation definition

Definition of Incident Investigation

Incident investigation is the structured process an organization uses to find out what happened during an unplanned event, why it happened and what needs to change to prevent it from happening again. The event may be an injury, an illness, property damage, a spill, a fire or a near miss where no one was hurt but easily could have been.

The purpose of an investigation is prevention, not blame. A good investigation looks past the person closest to the event and asks why the conditions, equipment, procedures, training, supervision and management systems allowed it to happen. Most incidents have several contributing causes, and the deepest ones, often called root causes, usually sit in systems rather than in individual behavior. Fixing only the surface cause, such as retraining one worker, leaves the underlying problem in place for the next person.

OSHA encourages employers to investigate all incidents, including near misses, as part of an effective safety and health program. ISO 45001 requires organizations to investigate incidents and nonconformities, determine their causes and take corrective action. Investigation findings also feed key metrics such as the incident rate and help prioritize improvements.

Reporting Requirements That Often Trigger Investigations

Some incidents must be reported to OSHA, and they almost always warrant a full investigation. Under 29 CFR 1904.39, employers must report:

  • A work-related fatality within 8 hours of learning about it.
  • A work-related inpatient hospitalization, amputation or loss of an eye within 24 hours of learning about it.

States that run their own OSHA-approved programs may have additional or stricter reporting rules. Separately, recordable injuries and illnesses must be entered on the OSHA 300 log, and environmental releases may need to be reported to environmental agencies. Reporting and investigation are different obligations; meeting one does not satisfy the other.

The Incident Investigation Process

1. Respond and secure the scene

Care for the injured first, then make the area safe and preserve evidence. Restrict access, take photographs and avoid moving equipment or materials unless it is necessary for safety.

2. Assemble the team

Choose investigators who are trained in the method being used and who are as independent as practical from the event. Include someone who knows the work well, such as an experienced operator, and involve worker representatives where possible.

3. Gather information

Collect physical evidence, documents and accounts. Interview witnesses and the people involved as soon as practical, one at a time, in a non-threatening setting, with open questions that focus on what they saw and did. Review procedures, training records, maintenance logs, permits, inspection records and any previous similar incidents.

4. Build the sequence of events

Lay out what happened step by step, from the conditions that existed before the event through the event itself and the response. Timelines and causal factor charts help reveal where things departed from what should have happened.

5. Determine causes

Identify the immediate causes, such as an unguarded pinch point or a slippery floor, then ask why those conditions existed. Common tools include:

  • 5 Whys: asking why repeatedly until a systemic cause is reached.
  • Fishbone diagrams: grouping possible causes into categories such as people, methods, equipment, materials, environment and management.
  • Causal factor and barrier analysis: examining which controls failed, were missing or were bypassed.
  • Structured methods such as TapRooT or Apollo root cause analysis for complex or high-severity events.

6. Develop corrective actions

Each root cause should have a corrective action with an owner and a due date. Use the hierarchy of controls so that fixes favor eliminating or engineering out the hazard rather than relying on reminders or more training.

7. Report, share and follow up

Document the findings and share the lessons with everyone who does similar work, including other sites. Check later that actions were completed and that they actually worked.

Common Investigation Pitfalls

  • Stopping at worker error. Conclusions such as careless or failed to follow procedure explain little. Ask why the procedure was hard to follow, why shortcuts were normal and why supervision did not catch it.
  • Waiting too long. Memories fade and scenes change quickly. Start within hours, not days.
  • Investigating only injuries. Near misses and property damage events reveal the same hazards without the cost of an injury.
  • Weak corrective actions. Actions such as remind staff or retrain do not change conditions and rarely prevent recurrence on their own.
  • No follow-through. Actions that are never verified, or lessons that never leave the department, waste the investigation.
  • A blame culture. If people expect to be disciplined, they will stop reporting and stop speaking openly in interviews.

Example of Incident Investigation

A worker at a metal fabrication shop suffered a crushed finger while changing tooling on a press brake. The initial report concluded that he had not followed the lockout procedure and recommended retraining. The safety manager reopened the investigation and interviewed the operator, two coworkers and the shift supervisor. She found that tooling changes happened several times a shift, that the lockout point was on the far side of the machine, and that operators routinely used the foot pedal in inch mode with the machine powered to align dies, because the written procedure did not describe a safe way to do it. Production targets left little time for full lockout/tagout at every change.

The corrective actions focused on the system rather than the individual. The shop installed a lockable disconnect at the operator's side of each press brake, worked with the manufacturer to set up a safe die-setting mode with reduced speed and two-hand control, rewrote the tooling change procedure with input from operators, and adjusted production standards to include changeover time. Supervisors began observing one tooling change per shift. The findings were shared with the company's other two shops, which had the same machines.

Frequently Asked Questions: Incident Investigation

Should near misses be investigated?

Yes. Near misses share the same causes as injuries, and investigating them is one of the cheapest ways to prevent a serious incident. The depth of the investigation can be scaled to the potential severity of what could have happened.

Who should lead an incident investigation?

Usually a supervisor or safety professional trained in investigation methods, supported by a team that includes people familiar with the work. For serious events, a more senior or independent lead helps avoid conflicts of interest.

How soon should an investigation start?

As soon as the scene is safe and the injured have been cared for, ideally within the same shift. Early action preserves evidence and captures accurate witness accounts.

What is the difference between an immediate cause and a root cause?

The immediate cause is the condition or action that directly led to the event, such as a missing guard. The root cause is the underlying reason that condition existed, such as no process for checking guards after maintenance. Fixing root causes prevents a wider range of future incidents.

Part of SafetyIQ's EHS glossary: plain-English definitions of workplace health and safety terms.

> Keep learning

More EHS terms

Browse the full glossary >

> See it in action

Put these safety terms into practice with SafetyIQ

Capture hazards, run inspections, track training and close out corrective actions in one platform built for high-risk, field-heavy work.

Book my free demo
★★★★★
4.8 out of 5 stars on
G2
G2 High Performer, Fall 2026