Admin & certificates
Incident Report Template: Free Download, Example and Guide
An incident report records what happened when someone is hurt, nearly hurt, property is damaged or a security breach occurs at work. Done well, it captures facts while they are fresh, finds the real cause and makes sure the same thing does not happen again. Done badly, it becomes a blame letter that nobody learns from.
Below you will find a free Word incident report template, field-by-field instructions, a filled warehouse example with a timeline, a step-by-step process from the first minute to sign-off, and the reporting deadlines that apply in the US, the UK and the EU.
What is an incident report?
An incident report is a structured record of a single workplace event: when and where it happened, who was involved, what the injuries or damage were, what happened minute by minute, what was done immediately, why it happened and what will change. It is used internally by safety officers and managers, and externally as the basis for regulator notifications, insurance claims and customer communication.
It is not a disciplinary document. The goal is to learn, not to punish, so the report sticks to verified facts, separates what was seen from what was assumed, and traces causes back to systems such as training, layout, maintenance or procedures rather than stopping at 'human error'.
When should you write an incident report?
- An employee, contractor or visitor is injured or becomes ill at work, even if it seems minor
- A near miss happens: nobody was hurt, but they could easily have been
- Equipment, vehicles, stock or the building are damaged, or there is a fire, leak or spill
- A data breach, ransomware attack or major service outage occurs
- A customer reports harm or loss connected to your premises or service
How to fill in the incident report template
The download contains exactly these fields. If something is not yet known, write 'under investigation' rather than leaving it blank, and update the report later.
Incident details
| Field | What to write | Example |
|---|---|---|
| Report number and date | A reference that links to your incident log, plus the date written. | INC-2026-031 / November 6, 2026 |
| Date, time and location | As precise as possible, down to the area or room. | Nov 5, 2:20 PM, Dock 2, Building B, Columbus DC |
| Reported by | Name, role and relationship to the incident. | Marcus Lee, shift supervisor (first on scene) |
| People involved | Injured person and witnesses, with roles and injury. No Social Security numbers. | Dana Ortiz, receiving clerk, bruised right foot |
| Type and severity | Injury, near miss, property, environmental or security; minor, moderate or serious. | Injury / moderate (expected 3 days off) |
Timeline
| Field | What to write | Example |
|---|---|---|
| Time | Each event in order, before and after the incident. | 2:20 PM |
| What happened | Observed facts only; mark anything second-hand. | Reversing forklift wheel contacted foot |
| Person | Who acted at that moment. | Forklift operator Sam Patel |
| Action taken | What was done right then. | Forklift stopped, first aid given |
Causes and actions
| Field | What to write | Example |
|---|---|---|
| Immediate cause | The act or condition that directly led to the incident. | Reverse alarm not working; no marked walkway |
| Root cause (5 Whys) | Keep asking why until you reach a system or management cause. | Daily pre-use checklist has no alarm check |
| Corrective actions | Each action with an owner and a due date. | Install walkway barrier (Facilities, Nov 20) |
| Notifications | Regulator, insurer, customer: who, when and how. | Recorded on OSHA 300 log; insurer notified Nov 6 |
| Attachments | Photos, CCTV references, medical notes, witness statements. | 6 photos; CCTV 2:15–2:30 PM preserved |
Incident report example
A warehouse example where a reversing forklift bruised a clerk's foot. It is written in neutral language: times, facts and actions, no blame.
| Summary | Nov 5, 2:20 PM, Dock 2: reversing forklift wheel contacted a clerk's right foot |
|---|---|
| Injury | Dana Ortiz, bruised right foot; doctor advised 3 days of rest |
| Immediate actions | Forklift stopped, first aid, taken to urgent care, area cordoned off |
| Main causes | Faulty reverse alarm and no separated pedestrian walkway |
| Decision needed | Approve walkway barrier budget by Nov 12 |
Timeline
| Time | Event | Person | Action |
|---|---|---|---|
| 2:15 PM | Unloading of pallets begins at Dock 2 | Sam Patel (forklift), Dana Ortiz (checking) | Normal operation |
| 2:20 PM | Reversing forklift's rear wheel contacts Dana's right foot | Sam Patel, Dana Ortiz | Forklift stopped; supervisor called |
| 2:23 PM | First aid; swelling and pain noted | Marcus Lee (supervisor) | Ice applied; decision to drive to urgent care |
| 2:50 PM | X-ray shows no fracture; 3 days of rest advised | Marcus Lee | Doctor's note requested; family informed |
| 3:30 PM | Safety check before work resumes | Safety lead Priya Shah | Reverse alarm found faulty; forklift tagged out |
Tip: write the timeline the same day while memories are fresh; add the root cause and actions after the site walk and interviews.
Free download
Free, no sign-up. Opens in Excel, Google Sheets, Numbers, Word, Google Docs and LibreOffice.
Open the downloaded file in Nobami, our web office, to edit it right away.
How to handle an incident and write the report
- Look after people and make the area safe. Give first aid, call emergency services if needed, stop equipment and cordon off the area to prevent a second incident.
- Preserve evidence. Take photos from several angles, ask for CCTV and system logs to be kept, and only clean up once everything is recorded.
- Take short witness statements straight away. Ask each witness separately to write down what they saw. Memories merge quickly.
- Write the timeline as facts. Replace judgments like 'careless' with observations like 'the reverse alarm did not sound'.
- Find the root cause with 5 Whys. Do not stop at the person. Look at checklists, layout, training, staffing and maintenance.
- Assign actions and notify on time. Give every action an owner and a date, check regulator deadlines, and review progress at the next safety meeting.
Reporting deadlines in the US, UK and EU
United States: under OSHA rules, employers must report a work-related fatality within 8 hours, and an in-patient hospitalization, amputation or loss of an eye within 24 hours. Many employers must also record work-related injuries and illnesses on the OSHA 300 log. Your internal incident report is the evidence behind those entries.
United Kingdom: RIDDOR requires employers to report certain workplace injuries, diseases and dangerous occurrences to the Health and Safety Executive. Injuries that keep a worker off normal duties for more than seven consecutive days are among the reportable cases, with their own deadline.
EU and UK data breaches: under the GDPR, a personal data breach that is likely to pose a risk to people must be notified to the supervisory authority within 72 hours of becoming aware of it. Record the exact time you became aware in the incident report.
Sources
- Health and Safety Executive: RIDDOR reporting (checked November 8, 2026)
- European Commission: data protection (checked November 8, 2026)
General information, not legal advice. Reporting duties depend on your country, state, industry and the severity of the incident; check the regulator's current guidance.
Common incident report mistakes
- Closing the report with 'human error' so the underlying cause never gets fixed
- Mixing assumptions with facts, which later contradicts witness statements
- Cleaning up the scene before photos and CCTV are secured
- Missing a regulator deadline while waiting for the internal report to be perfect
- Listing actions with no owner or due date
- Copying medical details or ID numbers into a report that circulates widely
Incident report FAQ
What should an incident report include?
Date, time and location; who was involved; injuries or damage; a timeline of events; immediate actions; the immediate and root causes; corrective actions with owners and dates; notifications made; and attachments such as photos and statements.
Who should write the incident report?
Usually the supervisor or person in charge at the scene, with input from the injured person and witnesses. A safety lead or manager reviews it and signs off the actions.
Should near misses be reported?
Yes. Near misses are free lessons. Recording them reveals hazards before someone is actually hurt.
Is an incident report the same as a disciplinary report?
No. Keep the incident report factual and focused on prevention. If discipline is considered, handle it in a separate HR process.
How soon should it be written?
Start the same day, ideally within hours. Regulators may have shorter deadlines than your internal process, so notify them first if required.