Safety & WorkforceFree templatePDF, Excel, Word exportUnited States

Incident Investigation Report Template

A good investigation finds the system failures behind an incident rather than blaming the person. This template gives you a structured report with facts, timeline, evidence, root causes, corrective actions and a recordkeeping check, ready to export as PDF or Word.

Fill in

Live preview
Download:

Incident Investigation Report Template

Incident Investigation Report

Company: Acme Precision Ltd Report no.: INC-2026-0042 Date and time: 2026-10-14 14:20 Location: CNC machining cell 4 Incident type: Injury Outcome: Medical treatment Person involved: Machine operator, 3 years on the cell

Description of the incident

While clearing a chip jam, the operator opened the door with the spindle coasting and a hand contacted the tool, causing a laceration to the right palm.

Timeline

14:15 jam alarm. 14:18 operator pressed feed hold. 14:20 door opened, injury occurred. 14:22 first aid applied. 14:40 taken to clinic.

Evidence collected

ItemCollected byLocation / referenceDone
Photos of the scene
Witness statements
Machine and interlock records
Training records
Procedure and JSA in effect

Immediate cause

Door opened before spindle fully stopped; hand reached into the work area.

Root causes

Door interlock allowed opening at spindle coast down. Work instruction did not include a wait or stop confirmation. Chip jams occur weekly due to coolant nozzle position.

Corrective and preventive actions

Verify interlock lock time with machine supplier. Update work instruction and retrain operators. Reposition coolant nozzle. Add chip jam to the weekly maintenance review.

Action tracking

ActionOwnerDue dateStatusVerified by

Recordkeeping check

Recordable on OSHA 300 log: Yes / No Reportable to OSHA within 8 or 24 hours: Yes / No Workers compensation notified: Yes / No

Approvals

Investigator / Date
Department manager / Date
Safety manager / Date

A starting point, not legal advice. Reporting deadlines and recordkeeping rules vary by jurisdiction. In the US, 29 CFR 1904.39 requires reporting a work-related fatality within 8 hours and an in-patient hospitalization, amputation or loss of an eye within 24 hours.

Track corrective actions to closure

An optional review of a simple action tracker tied to your incident and maintenance data.

Optional. The tool and every export work without this. No spam.

How to use this template

Start as soon as the scene is safe. Take photos, preserve equipment and machine data, and interview witnesses separately and early. Enter the basic details, write a neutral description of what happened, and build a timeline from facts rather than opinions. Then record the immediate cause and use a method such as 5 Whys or a fishbone to reach root causes in the system: equipment, procedure, training, supervision, environment and management. Assign each action an owner and a due date, and verify effectiveness later.

Method behind the report

Effective investigations separate immediate causes, the unsafe act or condition, from root causes, the underlying gaps that allowed it. Stopping at human error produces actions like retrain the operator, which is the weakest control. Ask why until you reach something you can change, such as a missing interlock, an unclear instruction or an overloaded schedule. Apply the hierarchy of controls to corrective actions and favour engineering fixes over reminders.

  • Interview witnesses separately and early
  • Use open questions and avoid leading ones
  • Keep facts, evidence and conclusions in separate sections
  • Verify closed actions after 30 to 90 days

Worked example

In the example, an operator cut a hand clearing a chip jam. The immediate cause was opening the door during spindle coast down. Asking why showed that the interlock did not hold the door long enough, the instruction did not mention waiting, and jams happened weekly because of a nozzle position. The actions target all three: interlock verification, procedure update and a mechanical fix for the jam, rather than only retraining.

Common mistakes

Common errors are writing the report days later from memory, naming a person as the cause, listing only training as the action, and closing actions without checking they worked. Another is missing a reporting deadline because nobody checked the recordkeeping rules on the day. Include the recordkeeping section on every report, and feed the rates into your TRIR and DART numbers so incident data and metrics agree.

Frequently Asked Questions

How soon should an investigation start?

Immediately once the area is safe. Evidence and memory degrade quickly, so photograph the scene, secure equipment and speak to witnesses the same day if possible. Complete the written report within days, not weeks.

Who should lead the investigation?

A trained person who was not involved, often a supervisor or safety professional, with a worker representative and someone who knows the process. Including the affected worker's view improves the findings.

What is the difference between immediate and root cause?

The immediate cause is what directly led to the incident, such as opening a door early. Root causes are the underlying system weaknesses, such as a faulty interlock or unclear procedure, that allowed it to happen.

Do near misses need investigation?

Yes, at a proportionate level. Near misses reveal the same causes as injuries without the harm. Use a short near miss form and escalate to a full investigation when the potential severity was high.

If incident reports and corrective actions sit in different places, we can help bring them into a single tracked workflow connected to your ERP and maintenance data.