Incident Report Examples: 12 Real-World Samples by Industry

An incident report example is a completed sample showing how to document a workplace incident: the facts, the people involved, and the corrective actions taken. Reading examples by industry helps you write clear, objective, and compliant reports that hold up in an audit or investigation.

‍

The fastest way to learn how to write a good incident report is to read a few good ones. A blank template tells you what fields exist; a filled-in example shows you how much detail to include, how to describe what happened without assigning blame, and where people usually go vague.

Below are twelve worked examples, one per common industry and incident type. Each is a realistic, anonymized sample you can model your own report on, followed by a short note on why it holds up. Copy the structure, swap in your details, and you're most of the way there.

The 12 examples at a glance

Jump to the scenario closest to yours.

What a good incident report includes

Whatever the industry, a solid report answers the same questions: who, what, when, where, why, and what happens next. Keep it factual and specific. The report is a record that has to stand up in an audit or a compliance review, not an argument.

One habit worth building: report near misses too, not just injuries. For every serious injury there are dozens of minor ones and hundreds of near misses (Heinrich / Bird, via Safety+Health), and the near misses are where you still have time to prevent something worse.

12 incident report examples by industry

These samples span the frontline industries most prone to incidents, from manufacturing and logistics to healthcare, retail, and hospitality. Find the one closest to yours and use it as a template.

1. Manufacturing: hand laceration from a press

Date & time: March 3, 2026, 10:15 AM

Location: Plant 2, Stamping Press Line 4

Reported by: J. Okafor, Line Supervisor

Person involved: Machine operator, 7 months in role

Description: While clearing a material jam on the stamping press, the operator reached into the die area without locking out the machine. The ram completed its cycle and struck the operator's left hand.

Injury: Lacerations to the left index and middle fingers. First aid given on site; operator referred to urgent care for stitches. No amputation or fracture.

Immediate action: Machine locked out and tagged; first aid applied; operator transported to urgent care; the line was stopped and the area cordoned off.

Root cause: Lockout/tagout was not performed before clearing the jam, and the guard interlock had been bypassed.

Corrective action: Retrain the line on LOTO by March 10; repair the interlock (Maintenance, March 5); add a jam-clearing procedure to the daily safety huddle.

‍

Why this works: It names the exact machine and the exact step that went wrong, states the injury factually with no blame, and links one clear root cause to specific fixes with owners and dates.

‍

2. Warehouse & logistics: forklift near miss

Date & time: April 12, 2026, 2:40 PM

Location: Distribution Center 1, Aisle B7

Reported by: M. Alvarez, Shift Lead

People involved: Forklift operator and a picker on foot (no contact)

Description: A forklift rounding the end of Aisle B7 came within roughly one meter of a picker who stepped out from between racks. The operator braked in time and no contact occurred. A pallet was already blocking the pedestrian mirror at the corner.

Injury / damage: None. Reported as a near miss.

Immediate action: Both workers stopped; the blocking pallet was moved; the corner was flagged to all shifts at handover.

Root cause: A blind corner with an obstructed convex mirror, plus no marked pedestrian walkway at the aisle end.

Corrective action: Reposition the mirror and keep the corner clear (facilities, April 14); paint a pedestrian walkway and add a "honk at corners" rule to the forklift SOP.

Why this works: Near misses are easy to skip because "nothing happened." This one captures the exact distance, the contributing hazard, and a fix, turning a non-event into prevention.

3. Construction: fall from height, arrested by harness

Date & time: May 2, 2026, 9:05 AM

Location: Tower B, Level 6, west edge

Reported by: D. Nguyen, Site Safety Officer

Person involved: Steel worker, subcontractor

Description: While moving along the Level 6 edge, the worker lost footing on loose decking and fell approximately 1.5 meters before the personal fall arrest system engaged and stopped the fall.

Injury: Minor bruising to the ribs from the harness. Assessed on site by the first-aid attendant; cleared to rest, no hospital visit.

Immediate action: Worker retrieved and assessed; the loose decking was secured; the area was closed pending inspection.

Root cause: Temporary decking was not fully fastened after the previous shift, and the pre-task inspection did not catch it.

Corrective action: Re-inspect all Level 6 decking (site engineer, same day); reinforce end-of-shift decking sign-off; toolbox talk on pre-task edge checks.

Why this works: It documents a success as well as an incident: the harness worked. Recording arrested falls keeps a spotlight on the conditions that nearly caused a serious one.

4. Healthcare: patient fall

Date & time: June 8, 2026, 11:50 PM

Location: Unit 4 East, Room 412

Reported by: R. Patel, RN

Person involved: Patient (68), medium fall-risk score

Description: The patient attempted to walk to the bathroom unassisted and lost balance near the bed. Staff found the patient on the floor; the bed alarm had not been switched on.

Injury: Skin tear to the right forearm; no head strike reported or observed. Physician notified; patient assessed and vitals stable.

Immediate action: Patient assisted back to bed; wound cleaned and dressed; physician and family notified; bed alarm activated.

Root cause: Bed alarm was not enabled after the previous care round, and the call light was out of reach.

Corrective action: Confirm bed alarms at each round for fall-risk patients; place call lights within reach; review fall-risk protocol at unit huddle.

Why this works: It sticks to what was observed ("found on the floor," "no head strike observed") rather than guessing how the fall happened, which matters in a clinical and legal record.

5. Retail: customer slip-and-fall

Date & time: July 19, 2026, 4:20 PM

Location: Store 214, produce section

Reported by: K. Brooks, Duty Manager

Person involved: Customer; two staff witnesses

Description: A customer slipped on a wet patch near the produce misters and fell to one knee. A "wet floor" sign was not in place at the time. The customer declined an ambulance.

Injury: Customer reported knee pain and a minor scrape. First aid offered; customer declined further treatment and provided contact details.

Immediate action: Area cordoned and mopped; wet-floor sign placed; customer details and witness names recorded; incident photographed.

Root cause: The produce misters left standing water and the scheduled floor check had been missed during a busy period.

Corrective action: Add a mister run-off mat; increase floor checks to hourly during peak; confirm signage stock at each entrance.

Why this works: Customer incidents can become claims, so this one records witnesses, photos, the customer's own words, and that treatment was offered and declined.

6. Hospitality: kitchen burn

Date & time: Aug 1, 2026, 7:35 PM

Location: Restaurant kitchen, fryer station

Reported by: S. Iqbal, Kitchen Manager

Person involved: Line cook, 3 weeks in role

Description: While lowering a basket into the fryer, hot oil splashed onto the cook's forearm. The cook was not wearing the provided fryer sleeve, which was in the wash.

Injury: Superficial burn to the right forearm, roughly the size of a palm. Cooled under running water and dressed; cook finished the shift after assessment.

Immediate action: Burn cooled and dressed from the first-aid kit; station wiped down; a spare fryer sleeve issued.

Root cause: Only one fryer sleeve was available per station, so none was on hand when the first was in the wash.

Corrective action: Stock two sleeves per station; add sleeve checks to the pre-service line check; brief new starters on fryer PPE.

Why this works: It's honest about the missing PPE without blaming the new cook, and the corrective action fixes the system (one sleeve per station) rather than just telling people to be careful.

7. Corporate office: trip over a cable

Date & time: Sept 9, 2026, 8:50 AM

Location: 3rd floor, open-plan desks near Pod C

Reported by: L. Meyer, Office Manager

Person involved: Employee walking to their desk

Description: The employee tripped over a power extension cable running across the walkway to a temporary hot desk and stumbled into a low cabinet.

Injury: Minor bruising to the shin. No treatment needed beyond an ice pack.

Immediate action: Cable rerouted and taped down; ice pack provided; area checked for other trailing cables.

Root cause: A temporary desk was set up without a nearby floor outlet, so the cable was run across the walkway.

Corrective action: Add a floor outlet near Pod C; keep cable covers on hand for temporary setups; add a walkway check to the weekly facilities round.

Why this works: "Minor" office incidents get under-reported. Logging this one keeps a paper trail and catches a hazard that could just as easily have caused a worse fall.

8. Education: playground injury

Date & time: Oct 3, 2026, 10:25 AM (morning recess)

Location: Primary school, main playground climbing frame

Reported by: A. Cole, Supervising Teacher

Person involved: Student (age 8); one adult witness

Description: The student fell from the second rung of the climbing frame onto the rubber matting while reaching for the next bar. The fall was observed by the supervising teacher.

Injury: Grazed left elbow and a bumped wrist. Cleaned and dressed by the first-aid officer; parents notified; no medical referral.

Immediate action: First aid given; parents contacted; the climbing frame checked for defects (none found).

Root cause: Normal play; no equipment fault identified. Supervision ratio was within policy.

Corrective action: No equipment action needed; reminder to students on safe climbing; note added to monitor the frame's high-traffic times.

Why this works: Not every incident has a fixable root cause, and this one says so plainly rather than inventing a fault. It still records supervision and parent notification, which schools need on file.

9. Transportation / fleet: backing collision

Date & time: Nov 14, 2026, 6:15 AM

Location: Depot yard, loading bay 3

Reported by: T. Owusu, Fleet Supervisor

Person involved: Delivery driver; no pedestrians involved

Description: While reversing into bay 3 in low light, the driver clipped a steel bollard with the rear offside corner of the van. No one was nearby.

Injury / damage: No injuries. Dented rear panel and a cracked tail light on the van; bollard undamaged.

Immediate action: Van moved clear and inspected; photos taken; vehicle logged off the road pending a body-shop check.

Root cause: Poor yard lighting at bay 3 and no banksman available at the early shift.

Corrective action: Repair or replace the bay 3 lighting (facilities, this week); reinstate a banksman for reversing before 7 AM; refresher on reversing procedure.

Why this works: Vehicle incidents need the same rigor as injuries. This one captures the damage, the photos, and the two conditions (lighting, no banksman) that made it likely.

10. Security: verbal altercation and theft

Date & time: Dec 5, 2026, 9:40 PM

Location: Store 118, main entrance

Reported by: P. Santos, Security Officer

People involved: One individual; two staff witnesses

Description: An individual concealed merchandise and attempted to leave without paying. When approached by staff, the individual became verbally aggressive, then left the store on foot. No physical contact occurred.

Loss / damage: Estimated goods value recorded; no property damage; no injuries to staff.

Immediate action: Staff disengaged and did not pursue, per policy; doors monitored; CCTV footage saved and timestamped; police reference number obtained.

Root cause: Not applicable to a deliberate act; noted that the exit was briefly unmonitored during a staff break.

Corrective action: Review break coverage at the entrance; confirm CCTV coverage of the exit; brief staff on de-escalation and no-pursuit policy.

Why this works: For security incidents, the report records exactly what staff did and didn't do (disengaged, saved CCTV, called police) which protects both the staff and the organization.

11. Food processing: chemical splash

Date & time: Jan 21, 2026, 1:10 PM

Location: Processing line 2, sanitation station

Reported by: H. Kim, Sanitation Lead

Person involved: Sanitation operator during changeover

Description: While diluting a concentrated sanitizer, the operator's face shield was raised and a splash reached the cheek and lower eyelid. An eyewash station was used within seconds.

Injury: Mild chemical irritation to the skin and eye; flushed at the eyewash station for 15 minutes; referred to a clinic as a precaution and cleared.

Immediate action: Eyewash used immediately; SDS consulted; area rinsed; clinic referral arranged; concentrate secured.

Root cause: Face shield was raised to see the measuring line, and the dilution step lacked a splash guard.

Corrective action: Add a splash guard and a graduated dispenser at the station; retrain on PPE-up for all dilution; post the SDS at the station.

Why this works: It shows the emergency response working (eyewash within seconds), names the SDS, and fixes the real reason PPE came off (the operator couldn't see the measuring line).

12. Any industry: near miss (dropped object)

Date & time: Feb 2, 2026, 3:05 PM

Location: Site A, beneath the level 3 scaffold

Reported by: G. Rossi, Foreman

People involved: Scaffolder above; laborer passing below (no contact)

Description: A hand tool slipped from the level 3 scaffold and fell to the ground, landing about two meters from a laborer walking below. The tool was not tethered and there were no toe boards on that section.

Injury / damage: None. Reported as a near miss with high potential severity.

Immediate action: Work above stopped; the drop zone was barricaded; the tool inspected and re-issued with a tether.

Root cause: Missing tool tethers and no toe boards on that scaffold section, plus an unbarricaded walkway below.

Corrective action: Fit toe boards and require tool tethers at height (this shift); barricade drop zones under active scaffold; add to the daily height-work checklist.

Why this works: It flags the near miss as high potential severity, so it gets the attention a dropped tool deserves before the day it actually hits someone.

Common mistakes to avoid

The examples above avoid the traps that make a report weak or, worse, a liability:

• Opinion instead of fact. "The operator was careless" is a judgment. "The operator reached into the die area without locking out" is a fact. Write the second one.
• Missing details. Leaving out the time, the witnesses, or what was done immediately makes a report hard to act on and easy to challenge later.
• Filing late. Write it the same shift, while memories are fresh and witnesses are still on site.
• Vague descriptions. "Hurt hand" tells you nothing. "Laceration to the left index finger" tells you what to treat and track.
• Skipping near misses. "No one got hurt" is exactly when you still have time to fix the cause. Fear of blame drives a lot of under-reporting (GAO), so keep it blameless.

How to write your own

Pick the example closest to your situation, keep the same field structure, and fill in your specifics. State the facts first, keep the root cause in its own line, and always end with a corrective action that has an owner and a date. If your team still reports on paper, moving capture to mobile means reports get written on the spot, with photos, instead of hours later from memory.

EngagedlyFX lets frontline workers file incidents and near misses from their phone, route them to the right owner, and track corrective actions to closure. See EngagedlyFX incident reporting or the broader safety solution.

Frequently asked questions

What is an example of an incident report?

An incident report example is a completed form documenting a workplace event, for instance a machine operator lacerating a finger while clearing a jam, noting the time, location, injury, witnesses, root cause, and corrective action. Examples model objective, fact-based writing.

How do you write a good incident report?

Stick to facts, not opinions; include who, what, when, where, and why; note witnesses and the immediate action taken; and file it the same shift. Keep the root cause separate from the description, and end with a corrective action that has an owner and a due date.

What should an incident report include?

Date and time, specific location, the person reporting, people involved and witnesses, an objective description, the injury or damage, immediate action taken, root cause, and corrective actions. Standard fields keep reports consistent and audit-ready.

What are the four types of incidents?

Commonly: near misses, no-harm events, minor or recordable injuries, and serious or sentinel events. Reporting all four, not just injuries, is what lets an organization spot patterns and prevent the serious ones.

What is the difference between an incident report and an accident report?

An accident report documents an event that caused injury or damage. An incident report is broader: it also covers near misses and unsafe conditions where no harm occurred, which are often the most useful for prevention.

The bottom line

A good incident report is specific, factual, and finished with a fix. Use the example closest to your industry as a template, report near misses as seriously as injuries, and make filing easy enough that people actually do it. The reports you capture today are the injuries you prevent next quarter.

Want incident and near-miss reporting your frontline will actually use, on the same app they use for shifts and updates? Book a demo of EngagedlyFX.

Related reading

• Enhanced workplace safety through employee engagement
• How safety can protect and engage essential employees
• Best practices for frontline success in manufacturing and construction
• How Archer Mechanical built a safer, more connected workforce
• EngagedlyFX incident reporting feature

‍