What OSHA Expects to See in an Incident Investigation Report

I keep a specific email in a folder I use when training new safety staff. It's two lines long: worker injured, forklift involved, sent to urgent care. That was the entire incident investigation record a client had on file for an event serious enough to trigger an OSHA hospitalization report. The email itself wasn't wrong. It just wasn't an investigation, and that gap is what gets a lot of companies into trouble.

That gap is more common than most safety managers realize, and it catches companies off guard because OSHA's requirements around incident investigation are less straightforward than people assume. There is no single federal standard that says every employer must produce a formal incident investigation report for every injury. But there are specific circumstances in which a report is legally required, and in every other case, OSHA treats the absence of one as a red flag during any inspection that follows an incident.

After nearly three decades investigating incidents across petrochemical, construction, and industrial sites, I can tell you the companies that handle this well aren't the ones with the fanciest report template. They understand the difference between what's required, what's expected, and what actually prevents the next incident.

What You'll Learn About What OSHA Expects in an Incident Investigation Report

• What OSHA actually requires in writing versus what it expects to see in an incident investigation report
• The specific circumstances in which a formal incident investigation report is a legal requirement
• The core elements every complete incident investigation report should include
• How reporting timelines under 29 CFR 1904.39 differ from the investigation itself
• The most common documentation gaps that turn a routine inspection into a bigger problem
• How investigation quality affects your standing with Avetta, ISNetworld, and similar platforms

Quick Answer: What OSHA Expects in an Incident Investigation Report

Outside of Process Safety Management-covered facilities, federal OSHA does not mandate a specific incident investigation report format for general industry or construction. What it does require is accurate injury and illness recordkeeping under 29 CFR 1904, including the OSHA 300 Log, 300A summary, and 301 Incident Report, plus prompt reporting of fatalities and severe injuries. What OSHA expects to see, and will ask for during any inspection that follows an incident, is documentation showing the event was investigated: what happened, why it happened, and what was done to prevent it from happening again.

What's Actually Required Versus What OSHA Expects

It helps to separate three different things that get lumped together as “incident reporting.”

1. Recordkeeping Under 29 CFR 1904

Employers with more than ten employees, outside certain exempt industries, must maintain the OSHA 300 Log, complete the 300A annual summary, and fill out a 301 Incident Report or equivalent for every recordable injury or illness. These forms document that an event occurred and its outcome. They are not, by themselves, an investigation of why it happened. Records must be retained for five years.

2. Reporting Timelines Under 29 CFR 1904.39

Separate from recordkeeping, employers must report certain severe events directly to OSHA within a fixed window: a fatality within 8 hours, and an inpatient hospitalization, amputation, or loss of an eye within 24 hours. These timelines govern notification to OSHA, not the investigation itself, though in practice the investigation usually begins the moment the reporting call is made.

3. Formal Incident Investigation, in Which It's Actually Mandated

The clearest federal requirement for a written incident investigation report applies to facilities covered under OSHA's Process Safety Management standard, 29 CFR 1910.119(m). For any incident, including a near miss, that resulted in or could reasonably have resulted in a catastrophic release of a highly hazardous chemical, the employer must initiate an investigation within 48 hours, produce a report addressing what happened, the contributing factors, and the resulting recommendations, retain that report for five years, and establish a system to resolve the findings. For Gulf Coast petrochemical operations, this is not optional.

Outside of PSM-covered processes, there's no equivalent federal mandate for a general incident investigation report. But that doesn't mean OSHA won't ask for one.

Why OSHA Asks for Investigation Records Even When None Are Legally Required

During any inspection that follows an injury serious enough to trigger a report under 1904.39, the compliance officer evaluates whether the hazard that caused the incident is still present and whether the employer took it seriously. An employer with a documented investigation, root cause analysis, and completed corrective action is demonstrating exactly that. An employer with nothing beyond the 301 form looks, at best, unprepared, and at worst, indifferent to a hazard that could injure someone else.

This is exactly why our OSHA Safety Compliance Checklist post lists incident investigation reports and workers' compensation first reports of injury among the documents an OSHA compliance officer will commonly ask to see, even outside a formal PSM program.

The Core Elements of a Complete OSHA Incident Investigation Report

Whether or not a formal report is legally mandated for your operation, the same structure applies if you want the document to hold up under scrutiny, and more importantly, to actually prevent a repeat incident. A complete report should cover:

• Date, time, and exact location: Enough specificity to reconstruct the scene, not a general area description.
• Description of the event: A factual account of what happened, separate from opinions about who was at fault.
• Personnel and witnesses involved: Names, roles, and statements gathered close to the time of the event, before recollections shift.
• Root cause analysis: Analysis that goes past the immediate cause to the underlying system gap, not a one-line explanation like operator error.
• Corrective actions with owners and dates: Specific actions, who is responsible for each, and a target completion date, not a general statement of intent.
• Verification that corrective actions were completed: Follow-up documentation showing the action was actually implemented, not just proposed.
• Connection to your written program: Evidence the finding fed back into training, procedures, or the relevant hazard-specific program.

The Gap I See Most Often: No Root Cause

The single most common weakness I find in incident investigation reports is a stated cause of “operator error”, full stop, with nothing behind it. That's a description of what happened, not an explanation of why it happened. A thorough investigation keeps asking why until the answer lands on a system gap: inadequate training, a procedure that didn't match actual field conditions, a guard that was removed and never replaced, a staffing decision that put an inexperienced worker on a task alone. Investigations that stop at blame don't change anything, and they tend to erode trust with the crew, who quickly learn the process exists to find someone to write up rather than to fix what's actually broken.

An Example From Our Client Work

The following is representative of a pattern we see often, with details adjusted for confidentiality. A scaffolding and rigging subcontractor working a refinery turnaround near Geismar had a near miss involving a dropped load. The site supervisor's initial write-up was two sentences: rigging failed, no injury, crew resumed work after inspection. When we walked the investigation back with the crew, the actual sequence involved a sling rated below the load weight, a last-minute substitution because the correct rigging wasn't on site, and no one flagging the mismatch before the lift.

The revised report documented all three factors, tied the corrective action to a specific rigging inventory check added to the pre-lift checklist, and closed the loop with a toolbox talk referencing the near miss directly. Six months later, during a client audit ahead of a major turnaround, that documentation was one of the reasons the company's safety program passed without findings. The near miss became evidence of a functioning safety system rather than a hidden liability.

How Investigation Quality Affects Prequalification Standing

Avetta, ISNetworld, and Veriforce all weigh your incident history, but they weigh your response to that history just as heavily. A citation or recordable injury with a documented investigation, root cause, and completed corrective action attached reads very differently to a hiring client than the same event with no visible follow-up. For more on how these consequences connect, see our breakdown of what construction site safety violations really cost beyond the fine, and our guide to what OSHA can ask for during an inspection.

Building This Into Your Program, Not Just Your Paperwork

A good investigation report is the output of a good investigation process, not a form filled out after the fact to satisfy a file. For a full walkthrough of how to run the investigation itself, from securing the scene through developing corrective actions, our companion piece, 9 Steps for Effective Accident Investigations, covers the process step by step. Once a root cause is identified, tracking the resulting corrective action through to completion is its own discipline; our guide to Safety Improvement Plan vs Corrective Action Plan (CAP) walks through which document to use once an investigation identifies a fix. Our Safety Auditing services are also how we most often catch incomplete investigation records before they surface during an actual OSHA inspection.

Frequently Asked Questions About OSHA Incident Investigation Reports

Does OSHA require every employer to complete a formal incident investigation report?

Not universally. Outside of Process Safety Management-covered facilities under 29 CFR 1910.119(m), there is no blanket federal requirement for a formal investigation report. Employers are required to maintain accurate injury and illness records under 29 CFR 1904, and OSHA routinely requests investigation documentation during inspections even when it isn't independently mandated.

How many steps are there in the accident investigation process?

Most structured approaches use a sequence of roughly nine steps, from securing the scene and providing first aid through gathering evidence, interviewing witnesses, determining root cause, and writing the final report with corrective actions. We cover the full process in our guide to effective accident investigations.

What's the difference between reporting an incident to OSHA and investigating it?

Reporting under 29 CFR 1904.39 is a notification obligation: fatalities within 8 hours, and inpatient hospitalizations, amputations, or losses of an eye within 24 hours. Investigating the incident, determining what happened and why, is a separate process that typically continues after the report is made.

How long should incident investigation reports be retained?

For PSM-covered facilities, 29 CFR 1910.119(m) requires investigation reports to be retained for five years. OSHA 300 Logs, 300A summaries, and 301 Incident Reports must also be retained for five years under 29 CFR 1904. As a practical matter, we recommend the same five-year retention for all incident investigation documentation, regardless of whether PSM applies.

What's the most common mistake in incident investigation reports?

Stopping at the immediate cause instead of identifying the root cause. A report that says the cause was operator error, without asking why the operator made that error, doesn't hold up under an OSHA inspection and doesn't prevent the next incident.

Do near misses need to be investigated the same way as injuries?

Yes, and for PSM-covered processes, this is explicitly required for any near miss that could reasonably have resulted in a catastrophic release. Near misses are the least expensive data you'll ever get about a hazard in your operation.

About the Author

Lance Roux, CSP, is the founder and principal consultant at SafetyPro Resources, LLC. He has nearly three decades of experience across construction, oil and gas, manufacturing, chemical processing, refinery, and power generation industries, including conducting incident investigations for Process Safety Management-covered facilities along the Gulf Coast. Lance serves as an expert witness in workplace incident litigation and is the past president of the ASSP Louisiana Chapter. SafetyPro Resources is based in Baton Rouge and serves Louisiana, Texas, Mississippi, and the broader Gulf Coast.

Need help building an incident investigation process that holds up under an OSHA inspection? Talk to a SafetyPro consultant.

Other Helpful Articles

• What Is Avetta Certification, and Why Do Contractors Need It?
• Construction Site Safety Violations: The Real Cost
• Safety Management System vs Safety Program vs Plan:
• Safety Improvement Plan vs Corrective Action Plan (CAP)
• OSHA Updates Heat Safety Rules:
• Heavy Equipment Spotter & Pedestrian Safety