Incident Report
A formal written record documenting a workplace event that caused or could have caused injury, illness, property damage, or environmental harm, used for regulatory compliance, investigation, and prevention.
What Is an Incident Report?
Key Takeaways
- ✓An incident report is a formal document recording what happened, who was involved, where and when it occurred, and the immediate actions taken.
- ✓Incidents include injuries, illnesses, near-misses, property damage, environmental spills, and security events. Good reporting systems capture all of these.
- ✓Timely reporting is both a legal requirement and a practical necessity. Details fade, witnesses forget, and evidence gets cleaned up within hours.
- ✓Heinrich's 300:29:1 ratio shows that near-misses vastly outnumber actual injuries. Capturing near-misses is where prevention happens.
- ✓Incident reports serve four purposes: regulatory compliance, investigation, workers' compensation claims, and trend analysis for prevention.
An incident report is the starting point for everything that follows a workplace event: the investigation, the corrective actions, the insurance claim, the regulatory filing, and the lessons learned. Without a documented report, there's no evidence that anything happened, no data to analyze, and no trail for regulators or insurers to follow. The term "incident" is deliberately broad. It covers injuries (someone got hurt), illnesses (someone got sick from a workplace exposure), near-misses (something almost caused harm but didn't), property damage (equipment was broken or destroyed), and environmental events (chemical spills, releases). The most valuable category for prevention is near-misses, because they reveal the same hazards that cause injuries without someone actually being harmed. Most organizations underreport near-misses because workers don't see the point of reporting something when nobody got hurt. That's a culture problem, not a reporting problem. Companies that actively encourage near-miss reporting and act on the data consistently outperform their peers in safety metrics.
What Should Be Reported
Different types of incidents have different reporting requirements. Understanding the categories helps ensure nothing falls through the cracks.
| Incident Type | Examples | Regulatory Reporting Required? | Internal Report Required? |
|---|---|---|---|
| Fatality | Death of worker or visitor from workplace event | Yes (OSHA: 8 hours; RIDDOR: immediate) | Yes, immediately |
| Serious injury | Hospitalization, amputation, loss of eye | Yes (OSHA: 24 hours; RIDDOR: 10 days for over-7-day injuries) | Yes, within 24 hours |
| Recordable injury/illness | Medical treatment beyond first aid, restricted work, days away | OSHA 300 log entry required | Yes, within 24 hours |
| First-aid-only injury | Minor cuts, bruises, sprains treated on-site | No OSHA 300 log entry (but track internally) | Yes, recommended |
| Near-miss | Event that could have caused harm but didn't | No regulatory requirement | Yes, strongly encouraged |
| Property damage | Equipment failure, structural damage, vehicle incident | Varies by type and jurisdiction | Yes, for investigation and insurance |
| Environmental | Chemical spill, air emission, water contamination | Yes, if reportable quantities exceeded (EPA/state) | Yes, immediately |
What to Include in an Incident Report
A good incident report captures the facts without speculation. It should answer six questions: who, what, when, where, how, and what was done about it.
Essential information
Every report should document the date, time, and exact location of the incident. The name, job title, and department of the person involved (or the reporter, for near-misses). A factual description of what happened, including the sequence of events leading up to the incident. Any injuries or illnesses and their nature (laceration, fracture, exposure). Names of witnesses. Immediate actions taken (first aid administered, area secured, supervisor notified). Equipment, substances, or conditions involved. Weather or environmental conditions if relevant.
What to avoid
Don't assign blame in the initial report. "John wasn't wearing his safety glasses" is an observation. "John caused the injury by being careless" is an opinion that belongs in an investigation, not the incident report. Don't speculate about causes. "The machine malfunctioned" is fine if you observed it. "The machine probably malfunctioned because of poor maintenance" is speculation. Stick to what you saw, heard, and did. The investigation will determine causes.
Supporting documentation
Photographs of the scene, equipment, and conditions are invaluable. Take them immediately, before cleanup or repairs. Equipment maintenance logs, training records, previous inspection reports, and relevant SOPs should be referenced. Witness statements should be collected separately (not in a group) while memories are fresh. Diagram the scene if the spatial layout is relevant. Security camera footage, if available, should be preserved before it's overwritten.
OSHA Recordkeeping Requirements
In the US, OSHA's recordkeeping standard (29 CFR 1904) requires most employers to maintain injury and illness records. Understanding what's recordable and what's not saves confusion and compliance risk.
OSHA 300 log
The OSHA 300 Log of Work-Related Injuries and Illnesses records each OSHA-recordable case during the year. A case is recordable if it involves death, days away from work, restricted work or job transfer, medical treatment beyond first aid, loss of consciousness, or a significant injury or illness diagnosed by a physician. The 300A summary (annual totals) must be posted in the workplace from February 1 through April 30. Establishments with 250+ employees in certain industries must submit data electronically through OSHA's ITA portal.
First aid vs. medical treatment
The distinction matters because first-aid-only cases aren't OSHA-recordable. First aid includes: non-prescription medications at non-prescription doses, wound cleaning, bandaging, butterfly closures (but not sutures), hot/cold therapy, rigid splints for transport, and single-use eye patches. Medical treatment is anything beyond first aid: prescription medications, sutures, physical therapy, surgical procedures, and diagnostic tests leading to treatment. If someone gets a tetanus shot after a puncture wound, it's still first aid. If they need stitches, it's medical treatment.
From Report to Investigation
An incident report captures facts. An investigation determines causes and identifies corrective actions to prevent recurrence.
Root cause analysis
Surface-level causes ("the worker slipped") don't prevent future incidents. Root cause analysis digs deeper: Why was the floor wet? Was there a spill response procedure? Was the area marked? Was the worker wearing appropriate footwear? Was the floor material appropriate for the environment? The "5 Whys" technique, fishbone diagrams, and fault tree analysis are common tools. The goal is to identify systemic failures (missing procedures, inadequate training, equipment design issues) rather than individual blame.
Corrective and preventive actions (CAPA)
Every investigation should produce actionable recommendations ranked by the hierarchy of controls. Track each corrective action with an owner, deadline, and verification step. "Retrain the worker" is almost never a sufficient corrective action by itself, because it implies the worker was the problem. If the system allowed the incident to happen, the system needs to change. Effective CAPA includes engineering fixes (guard the hazard), process changes (modify the procedure), and verification (confirm the fix actually works).
Building an Effective Reporting Culture
The biggest barrier to incident reporting isn't the process. It's the culture. Workers won't report if they fear punishment, don't believe anything will change, or think it's too complicated.
- Remove barriers: Make reporting easy. Mobile apps, QR codes at workstations, verbal reports to supervisors (who then document them), and anonymous options all increase reporting rates.
- Respond visibly: When someone reports a hazard or near-miss, act on it and communicate what was done. If workers see their reports leading to real changes, they'll report more. If reports disappear into a black hole, they'll stop.
- Separate reporting from discipline: Incident reporting should be a learning process, not a punitive one. Workers who fear disciplinary action for reporting a near-miss will simply stop reporting. Some companies adopt "just culture" frameworks that distinguish between human error, at-risk behavior, and reckless conduct.
- Set reporting targets for near-misses: If your facility has zero near-miss reports, the problem isn't perfect safety. It's underreporting. Some organizations set targets like "one near-miss report per 10 workers per month" to normalize reporting.
- Celebrate good catches: Recognize workers who report hazards and near-misses. A monthly "safety observation of the month" or a simple thank-you from management reinforces that reporting is valued.
Incident Reporting Statistics [2026]
Data showing reporting patterns, compliance rates, and the relationship between near-miss reporting and injury prevention.
Frequently Asked Questions
Who should file an incident report?
How quickly should an incident be reported?
Should near-misses be reported?
Can incident reports be used against employees?
What's the difference between an incident report and a workers' compensation claim?
How long should incident reports be retained?
Written by Adithyan RK