# Incident Investigation Report Template

> Source: https://netray.co/tools/incident-investigation-report-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Record what happened, the timeline, root causes and corrective actions in one report you can export and file.

## Category

ehs-workforce

## Region

United States

## Audience

- Safety manager
- Supervisor
- HR partner

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Report number

**Key:** report_no

**Type:** text

**Default:** INC-2026-0042

#### Incident date

**Key:** incident_date

**Type:** date

**Default:** 2026-10-14

#### Time

**Key:** incident_time

**Type:** text

**Default:** 14:20

#### Location

**Key:** location

**Type:** text

**Default:** CNC machining cell 4

#### Incident type

**Key:** type

**Type:** select

**Options:**

- Injury
- Illness
- Property damage
- Near miss
- Environmental release
- Fire

**Default:** Injury

#### Outcome

**Key:** severity

**Type:** select

**Options:**

- First aid
- Medical treatment
- Restricted work
- Days away
- Fatality
- No injury

**Default:** Medical treatment

#### Person involved (role)

**Key:** person

**Type:** text

**Default:** Machine operator, 3 years on the cell

#### What happened

**Key:** what

**Type:** textarea

**Default:** 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 of events

**Key:** timeline

**Type:** textarea

**Default:** 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.

#### Immediate cause

**Key:** immediate

**Type:** textarea

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

#### Root causes (5 Whys result)

**Key:** root

**Type:** textarea

**Default:** 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

**Key:** actions

**Type:** textarea

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

**Blocks:**

#### Incident Investigation Report

**Body:** Company: {{company}}
Report no.: {{report_no}}
Date and time: {{incident_date}} {{incident_time}}
Location: {{location}}
Incident type: {{type}}
Outcome: {{severity}}
Person involved: {{person}}

#### Description of the incident

**Body:** {{what}}

#### Timeline

**Body:** {{timeline}}

#### Evidence collected

**Table:**

**Columns:**

- Item
- Collected by
- Location / reference
- Done

**Rows:**

**0:** Photos of the scene

**0:** Witness statements

**0:** Machine and interlock records

**0:** Training records

**0:** Procedure and JSA in effect

#### Immediate cause

**Body:** {{immediate}}

#### Root causes

**Body:** {{root}}

#### Corrective and preventive actions

**Body:** {{actions}}

#### Action tracking

**Table:**

**Columns:**

- Action
- Owner
- Due date
- Status
- Verified by

**Rows:**

#### Recordkeeping check

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

#### Approvals

**Signatures:**

- Investigator
- Department manager
- Safety manager

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use this template

**Body:** 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

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### How soon should an investigation start?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

incident investigation report template, workplace accident investigation form, incident report form word, root cause analysis incident report, accident investigation template, osha incident investigation form, injury investigation report, incident report template pdf

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json