A near miss is an unplanned event that could have hurt someone or damaged equipment, but didn't. OSHA calls it a close call: an incident in which a worker might have been hurt if the circumstances had been slightly different. For a waste, transportation, or logistics operator, near misses are the cheapest safety data you will ever collect.
Why do near misses matter so much?
Near misses matter because the next one may not miss. Anyone responsible for drivers, helpers, and crews working around heavy equipment knows the call nobody wants to get: someone died today. Most days bring near misses, equipment defects, and risky habits instead. Each one is a chance to remove a risk before it reaches a person.
“Someone died today.” Words none of us ever want to hear.
Paul Marker
If you have been responsible for safety-sensitive employees, you know the possibility of that call follows you home, over the weekend, and into the middle of the night. You think about the people working around packers and loaders, the drivers sharing the road, and the neighborhoods your trucks run through every day.
That is why a near miss deserves the same attention as an injury. It is the same chain of events, stopped one link early, and it costs you nothing but the time to write it down and fix the cause. The question is how you get enough confidence to leave work without carrying every "what if" home. That confidence takes effort, consistent follow-through, and evidence that the work is getting done.
What counts as a near miss event?
A near miss event has two parts: something actually happened, and luck was the only reason nobody got hurt. A container that slipped off the forks and landed a foot from a helper is a near miss. A forklift with a bad horn is an unsafe condition. A cut that needed a bandage is an injury.
The line matters because each one goes to a different place. Unsafe conditions and unsafe acts are logged as safety observations and fixed. Near misses are reported and reviewed like any incident, just without the injury. Injuries and damage are incidents that may also meet OSHA's or DOT's definitions, which bring their own records.
OSHA's guidance is plain about it: the agency "strongly encourages" employers to investigate close calls as well as injuries (OSHA, Incident Investigation). A near miss is the same chain of events as an injury, stopped one link early.
What are examples of a near miss in waste and logistics?
Near misses at a fleet or waste operation tend to cluster in the same places: backing, the tipping floor, the shop, and anywhere people and equipment share space. The examples below are illustrative, not from any one operator, but every safety manager at a hauler will recognize them:
| Where | The near miss | What it points to |
|---|---|---|
| On the route | A rear-load truck backs down an alley and the helper steps out from behind it a second before the driver stops | Backing rules, spotter positions, camera coverage |
| On the route | A front-load arm clips a low power line drop at a commercial stop, with no damage | Route hazard notes for that stop, overhead checks |
| Roll off | A cable snaps loose while a box is being pulled onto the truck; the driver is clear of it | Cable and hook inspection on the DVIR, the stand-clear zone |
| Yard | A pickup cuts across the fuel island lane as a loaded truck pulls out | Traffic flow, marked pedestrian and light-vehicle lanes |
| Shop | A mechanic starts work under a packer body before the prop is set, and catches it himself | Lockout/tagout and blocking procedure, training |
| Transfer station | A loader operator nearly backs into a customer on foot on the tipping floor | Keeping customers out of the loader's path, signage, spotters |
| MRF | A sorter reaches toward the line during a jam just as it restarts | Jam-clearing procedure, lockout before reaching in |
None of these show up in an injury log. Every one of them is a cause you can fix this week, with a name, a location, and a time attached, if somebody wrote it down.
How is a near miss different from an incident, a recordable, or a DOT accident?
A near miss has no injury and no damage. An incident is any event that did cause harm. An OSHA recordable meets the 29 CFR 1904.7 criteria, and a DOT accident meets the 49 CFR 390.5 definition. Fleet operators deal with all of them, often on the same truck:
| Term | What it means | Where it's recorded |
|---|---|---|
| Unsafe act or condition | A hazard seen before anything happens: a missing guard, a worker skipping a step | Safety observation, your program's own log |
| Near miss | An event that could have caused injury or damage, but didn't | Near miss report, your program's own log |
| Incident | An event that caused an injury, illness, or damage, of any size | Incident report and investigation |
| OSHA recordable | A work-related injury or illness resulting in death, days away, restricted work or transfer, medical treatment beyond first aid, loss of consciousness, or a significant diagnosis | OSHA 300 log and 301 report (29 CFR 1904.7) |
| DOT accident | A commercial vehicle crash on a highway with a fatality, an injury treated away from the scene, or a vehicle towed for disabling damage | Accident register, kept 3 years (49 CFR 390.5, 390.15) |
One detail catches people out: the DOT definition excludes events that involve only loading or unloading cargo, or only getting in and out of a parked truck. A helper hurt at the hopper may be an OSHA recordable without ever being a DOT accident. For how the recordable count turns into TRIR and DART, see the injury rate section of our EHS guide.
Do you have to report near misses to OSHA or DOT?
No. No federal rule requires you to report a near miss to OSHA or FMCSA. OSHA's recordkeeping rule covers injuries and illnesses that meet its criteria, and FMCSA's accident register covers crashes that meet its definition. A near miss meets neither. Reporting them is a choice your program makes, and OSHA encourages you to investigate them.
That makes near misses the one safety record you fully control. Nobody audits the format or the count. The only test is whether the reports lead to fixes, which is also why they're easy to let slide.
Why don't crews report near misses?
Crews skip near miss reports for three reasons: the form is a hassle, they expect blame, and they never hear what happened to the last one. Each is a design problem, not a people problem. A report that takes ten minutes at the office, gets someone in trouble, and disappears will stop coming within a month.
The fixes follow from the reasons. Make the report short enough to finish from the cab or the floor. Treat the report as a good catch, never as evidence against the reporter. And close the loop where everyone can see it: say what was fixed, at the next toolbox talk, with the reporter's OK.
How do you set up near miss reporting?
A near miss reporting program needs four things: a short report anyone can file in minutes from where they are, a named person who reviews every report within a day, a fix with an owner and a due date, and a regular look at the trend. Most programs fail on the second and third, not the form.
Here is the order we'd build it in.
- Define it in one sentence. Put the definition and two examples from your own operation at the top of the form.
- Keep the report short. Seven fields, listed below. Anything longer belongs in the investigation, not the report.
- Make it reachable. Crews should be able to report from any device, at the yard or on the route, the same shift it happened.
- Assign a reviewer. One supervisor per site reads every report within one business day and decides: fix it now, or investigate.
- Track the fix. Every report that needs action gets a corrective action with one owner and one due date, and stays open until someone signs it off. Our corrective and preventive action guide has a free template for it.
- Report back. Share what was fixed at the next toolbox talk. That is what keeps reports coming.
- Watch the count. Track near misses per site per month next to TRIR and DART. A site that reports none isn't safe. It's quiet.
What should a near miss report include?
A near miss report should take a crew member under five minutes and fit on one page. Seven fields cover it: when, where, what happened, what could have happened, the equipment involved, a photo if it's safe, and who reported it. The reviewer adds the cause and the fix later.
Field by field:
- When: date and time.
- Where: site, route and stop, or area of the yard, shop, or floor.
- What happened: two or three sentences in the reporter's words.
- What could have happened: the injury or damage that almost occurred.
- Equipment involved: truck or unit number, container, machine.
- A photo, if it's safe to take one.
- Reporter: name, or anonymous if your program allows it.
The reviewer adds the rest: what caused it, whether it needs an investigation, and the corrective action. Keeping those off the reporter's form is what keeps it short.
Why are near misses a leading indicator?
Near misses are a leading indicator because they show where the next injury is likely before it happens. TRIR and DART are lagging: they count what already went wrong. Near misses, unsafe conditions, and DVIR defects point at the same hazards while there is still time to fix them, with no one hurt.
The useful numbers are simple: near misses reported per site per month, the share reviewed within a day, and the share whose corrective actions closed on time. A rising count with fast closures usually means trust is going up, not safety going down.
How do you prove near misses are getting fixed?
You prove it with records, not memory. For each commitment in your safety program, there should be a record that shows the work was done, who did it, and when. Nine questions cover most of it. If you can answer each one by pulling up a record, rather than making a call, your follow-through is real.
| The question | The record that proves it |
|---|---|
| Are we hiring people who can safely handle the work? | A complete driver qualification file, with road test and motor vehicle record, before the first route |
| Are new hires taught their responsibilities, and can they put the training into practice? | A training record plus a sign-off from a qualified observer, such as a supervisor or trainer |
| Are our people fit for duty and prepared for the work ahead? | Current certification and training records, and a start-of-shift check |
| Are we observing how the work is actually done, and coaching? | Safety observations by supervisor and site, with the coaching noted |
| Do crews feel comfortable reporting hazards and near misses, and do they see us act? | Near miss reports per site per month, each with the fix that was shared back |
| Are training, qualifications, and certifications current? | Expiration dates tracked ahead of time, with renewals booked before they lapse |
| Is equipment inspected each day by people qualified to inspect and operate it? | Daily DVIRs and pre-use inspections tied to the inspector's qualification |
| Are defects fixed promptly, with unsafe equipment kept out of service? | Each defect's path from write-up to repair to sign-off, and the out-of-service hold |
| Are corrective actions assigned, completed, and checked to make sure they worked? | One owner, one due date, a closure, and a follow-up check on every corrective action |
The last question is the hardest one: can we prove it? The inspection may be on paper, somewhere. The training record may be in a spreadsheet. The repair request may be in an email. Someone may have handled the corrective action, but the person responsible for the operation still has to chase down confirmation. Those open loops are what make confidence hard to come by.
Helping leaders close them is why we built SCOPE, the Lucent Axis Safety, Compliance & Operational Performance Ecosystem. SCOPE brings observations, incident and near miss reporting, inspections, training, driver qualifications, and corrective actions into one place. Near misses are reported from the field in minutes, from any device, and the supervisor is notified. Every follow-up shows what needs attention, who owns the next step, and whether that work has been completed.
The people doing the work still make safety happen. SCOPE helps them manage that work and gives leaders a clear view of where follow-through is needed. Rest comes easier when you can see that your people are prepared, reported concerns are being addressed, and essential actions are being completed. Gaps are less daunting when you know what still needs your attention. Read more in Introducing SCOPE, or see where near misses sit in the full program in What is EHS?
Frequently asked questions
Is a near miss an incident?+
Yes, in most safety programs. A near miss is an incident with no injury and no damage. It goes through the same report and review as any other incident, which is the point: you get to fix the cause without anyone getting hurt first.
What is the difference between a near miss and a close call?+
Nothing. OSHA uses close call and near miss for the same thing. Some programs also say near hit or good catch. Pick one term, put it on the form, and use it every time so crews know what you're asking for.
Does a near miss count toward TRIR?+
No. TRIR counts OSHA recordable injuries and illnesses, and a near miss has no injury. Near misses are a leading indicator you track alongside TRIR and DART, not a part of them.
Should near miss reports be anonymous?+
Allow it, but don't require it. An anonymous option gets reports from crews who don't trust the process yet. Named reports are easier to follow up on. Most programs offer both and let the reporter choose.
How soon should a near miss be reported?+
Before the end of the shift. Details fade fast, and the hazard is still there for the next crew. Set the expectation on the form and in toolbox talks: report it the same day, from wherever you are.
How do you know a near miss was actually fixed?+
Check the record, not the person. Every near miss that needs action should end in a corrective action with one owner, one due date, a closure, and a follow-up check that the fix worked. If confirming it means a phone call or an email search, the loop isn't closed yet.
This article summarizes federal rules as of October 2026 for general information. It isn't legal advice. Check the linked regulation and your state's rules before acting on a specific requirement.