Every workplace safety program depends on a clear understanding of incident vs near miss vs accident. These three terms describe related but distinct events, and each one calls for a different level of response. A near miss warns without harming anyone. An incident covers any unplanned event, whether or not it causes injury. An accident confirms that harm has already occurred. Confusing these categories weakens reporting data and slows down corrective action. This guide explains each term, connects them through Frank Bird’s well-known 100:10:1 safety rule, and outlines best practices for reporting all three consistently across a facility.
What Is an Incident?
An incident is any unplanned event that disrupts normal work, regardless of whether it causes harm. It is the widest of the three categories, covering near misses, accidents, and every other deviation from standard procedure.
Most incidents involve minor injuries or no injuries at all, such as a worker bruising a knee on a loose cable or a technician spilling a small amount of chemical without exposure. Reported consistently, these small events reveal weaknesses in a safety system before a serious accident develops.
What Is a Near Miss?
A near miss is an unplanned event where no injury, illness, or damage actually occurred, but the potential was clearly present. Near misses are sometimes called close calls.
A forklift operator who narrowly avoids a pedestrian is a near miss. No one gets hurt, but the conditions for a serious accident, limited visibility, foot traffic in a vehicle lane, and no barrier were fully present. Near misses remain the most underreported category, since workers often assume that nothing happening means nothing worth documenting.
What Is an Accident?
An accident is an unplanned event that results in injury, illness, property damage, or another negative consequence. Unlike a near miss, an accident represents a completed chain of failure.
Accidents range from a minor cut needing a bandage to major injuries such as fractures, amputations, or hospitalization. Because accidents involve confirmed harm, they typically trigger mandatory reporting under frameworks like OSHA and ISO 45001.
Frank Bird's Safety Rule
Safety professionals often use a simple ratio to describe how these three categories relate to each other: roughly 100 near misses occur for every 10 incidents, and roughly 10 incidents occur for every 1 accident. This 100:10:1 pattern comes from Frank Bird’s landmark industrial safety research, and the underlying pattern holds up consistently across industries.
The pyramid reads bottom to top. The wide green base holds 100 near misses, events with no injury or damage. The orange middle tier narrows to 10 incidents, typically minor injuries or property damage. The narrow red peak represents 1 accident, a serious outcome involving major injury or significant damage.
The shrinking width makes the point: every accident was preceded by a much larger base of smaller warning signs. Acting on the near misses at the base does more to prevent an accident than any response applied after the fact at the top.
Because of this rule, a strong EHS program treats near miss and incident reporting as leading indicators rather than administrative afterthoughts. Addressing near misses early removes risk from the pyramid before it has a chance to climb toward an accident.
Key Differences Between Incident, Near Miss, and Accident
Understanding incident vs near miss vs accident comes down to one factor above all others: outcome. The table below breaks down how the three categories compare across the details that matter most for reporting and response.
| Factor | Near Miss | Incident | Accident |
|---|---|---|---|
| Outcome | No injury, illness, or damage occurs, but the hazard was fully capable of causing one | May cause a minor injury or no injury at all; often the first sign of a process gap | Confirmed injury, illness, or property damage; the harm has already happened |
| Scope | A specific type of incident where the outcome stayed at zero harm | The broadest term technically includes every near miss and every accident | The most severe category, ranging from minor to major injuries |
| Example | A forklift narrowly missing a pedestrian in a warehouse aisle | A worker bruising a knee on a loose cable or a small unexposed chemical spill | A fall resulting in a fracture that requires hospitalization |
| Typical response | Investigate and correct the hazard early, before it produces an actual injury | Investigate, provide first aid if needed, and log root cause for prevention | Full investigation, medical treatment, and formal root cause analysis (RCA) |
| Reporting obligation | Usually internal only, though it should still be logged in the EHS system | Internal by default; regulatory only if the severity threshold is met | Often mandatory regulatory reporting, such as OSHA recordkeeping or ISO 45001 |
Common Misconceptions About Incident, Near Miss, and Accident Reporting
Even well-run EHS programs run into a handful of recurring misconceptions that quietly undermine reporting quality.
- Near misses do not need to be reported. Some workers assume that because no one got hurt, there is nothing worth documenting. This single misconception is the biggest reason Frank Bird’s safety rule breaks down in practice. Without near-miss data, safety teams lose their earliest and least expensive warning signs, and hazards stay hidden until they eventually cause real harm.
- Root cause analysis only applies to accidents. Skipping RCA for incidents and near misses lets the same underlying hazard resurface again and again until it finally causes a serious injury. Root cause analysis delivers the most value when applied early, not only after a major injury has already happened.
- Investigations are optional for minor events. When a minor incident does not result in injury, some teams skip the investigation step entirely. That gap allows small process failures, worn equipment, and procedural shortcuts to go uncorrected until they combine into something far more serious.
- No action plan follows the report. Filing an incident or near miss report without a documented corrective action plan turns the entire exercise into paperwork. The real value of reporting comes from the action that follows it, including an assigned owner, a clear deadline, and a way to verify the fix actually worked. Without that follow-up step, the same report can appear month after month with nothing ever changing on the ground.
Each of these misconceptions shares a common thread. They all treat the smaller, less severe categories, near misses and minor incidents, as less important than accidents. Frank Bird’s 100:10:1 ratio argues the opposite. The smaller categories are where prevention is cheapest and most effective, and they arrive in far greater numbers, which gives safety teams more chances to catch a hazard before it causes real harm.
Best Practices for Reporting All Three
A consistent reporting culture across near misses, incidents, and accidents depends less on policy language and more on daily habits, though the right EHS software makes those habits far easier to sustain. The following practices help organizations capture all three categories reliably.
- Make reporting easy. Provide a simple channel, such as EHS software with a mobile app, a QR code posted at the worksite, or a short paper form, so workers can log a near miss or incident within minutes of it happening.
- Incentivize frequent near miss reporting. Recognize or reward workers and teams who consistently report near misses, whether through a simple shoutout, a small prize, or a team leaderboard. Rewarding the behavior, not just tolerating it, pushes reporting rates up faster than policy alone.
- Protect workers who report. A blame-free reporting culture encourages employees to report near misses honestly instead of hiding them out of fear of discipline or blame.
- Investigate every category. Apply the same root cause analysis discipline to near misses, incidents, and accidents. Severity should determine how deep the investigation goes, not whether an investigation happens at all.
- Track trends, not just individual events. Use EHS software to spot patterns across near misses and incidents before they escalate into accidents. Recurring events at the same location, task, or shift usually point to a systemic hazard rather than a one-off mistake, and trend data makes that pattern visible long before a supervisor would notice it by memory alone.
- Close the loop with corrective action. Every report should end with a documented action plan, a named owner, and a deadline. Reporting without follow-through does very little to reduce risk.
- Review data on a regular schedule. Set up periodic reviews of near-miss, incident, and accident trends so leadership can direct resources toward the highest-risk areas of the facility.
None of these practices require complex tooling to start. A paper log and a weekly review meeting can build the habit. However, as reporting volume grows across shifts and locations, most organizations move to EHS software so that near miss, incident, and accident data lives in one searchable system instead of scattered spreadsheets and forms.
Conclusion
The difference between incident vs near miss vs accident comes down to outcome and warning value. A near miss warns without causing harm. An incident is the umbrella term for any unplanned event, most often resulting in minor injuries or no injuries at all. An accident confirms that harm, sometimes major injury, has already occurred.
Organizations that report and investigate all three categories consistently catch hazards earlier and stop them from escalating. EHS software makes this discipline easier to sustain, giving safety teams a single system to log, investigate, and close out every near miss, incident, and accident before the same failure has a chance to repeat itself. Over time, that consistency is what shifts a safety program from reacting to accidents to preventing them.