Near-Miss Reporting: Why It Matters [+ Template]

Last updated: March 2026

Last month, a scaffolding plank slid off a platform on a commercial build in Red Deer. Nobody was standing underneath. No injury, no damage, no WCB claim. The foreman shrugged and said, "Good thing nobody was there." That was it. No report, no follow-up, no investigation. Two weeks later, the same thing happened on the same scaffold. This time, a labourer was underneath. He spent six weeks off work with a fractured collarbone.

That first event, the one everyone ignored, was a near miss. And it was trying to tell them something. We help contractors build safety programs every week at Safety Evolution, and the pattern is always the same: the warning signs were there, but nobody wrote them down.

A near-miss incident report is a written record of a workplace event that could have caused injury, illness, or property damage but did not. It captures what happened, what went wrong, and what needs to change so the next time is not the time someone gets hurt.

A near-miss report documents a workplace event where no injury occurred, but easily could have. A tool dropped from scaffolding that misses a worker by a metre. A forklift backing into a rack that doesn't quite collapse. These incidents don't trigger WCB claims or regulatory reports, so most contractors ignore them entirely.

That's a mistake. Near-misses are the clearest warning signal your safety program produces, and companies that track them consistently have fewer serious incidents. This guide covers what counts as a near-miss, why reporting them matters for your COR or SECOR certification, and includes a template your crew can start using today.

What Is a Near Miss vs. an Incident vs. an Accident?

The terminology trips people up, so let's clear it out. These three terms describe different points on the same spectrum:

• Near miss (also called a close call or near hit): An unplanned event that could have caused injury or damage but didn't. A hammer falls from a scaffold and lands where someone was standing 10 seconds earlier. Nobody hurt, nothing damaged. Still a near miss.
• Incident: An unplanned event that disrupts normal work. It may or may not cause injury. A worker trips over an unsecured extension cord, stumbles, catches themselves. No injury, but the event happened. Some definitions classify near misses as a type of incident.
• Accident: An unplanned event that did cause injury, illness, or property damage. That same hammer hits someone's shoulder. Now it's an accident, a WCB claim, and a potential OHS investigation.

The difference between a near miss and an accident is often nothing more than timing or luck. The hazard was the same. The failure was the same. The only difference was whether someone happened to be standing in the wrong spot. For a deeper breakdown of how these terms relate, see our guide on incidents vs. accidents and why you should investigate both.

Why Does Near-Miss Reporting Matter?

Most contractors think that if nobody got hurt, there's nothing to report. They're wrong. Near misses are the single best leading indicator you have.

In the 1930s, researcher Herbert Heinrich studied thousands of workplace incidents and found a ratio: for every 1 major injury, there were 29 minor injuries and 300 no-injury incidents. Frank Bird updated that research in the 1960s with data from over 1.7 million incidents and found a similar pattern: 1 serious injury for every 10 minor injuries, 30 property-damage events, and 600 near misses.

The takeaway is simple. Near misses are not random. They are the wide base of a pyramid that narrows toward serious injuries and fatalities at the top. Every near miss you ignore is a warning you chose not to read.

Here's what near-miss reporting actually does for your operation:

• Identifies hazards before they cause harm. A near miss exposes the same root cause that a real injury would. You get the lesson without the hospital visit.
• Creates a paper trail for COR and SECOR audits. Auditors want to see that you are proactively identifying and correcting hazards, not just reacting to injuries. A stack of near-miss reports with documented corrective actions is exactly what they look for.
• Reduces your incident rate over time. Companies that track near misses consistently see fewer actual injuries because they are catching the problems upstream.
• Protects you in an OHS investigation. If someone does get hurt and OHS shows up, they want to see that you had a system in place. "We didn't know" is not a defence. A documented near-miss program proves you were actively managing risk.

In Alberta, the OHS Act requires employers to report "potentially serious incidents" (PSIs), which are events where a reasonable person would determine that, under slightly different circumstances, there would be a high likelihood of serious injury. That includes many near misses. BC's Workers Compensation Act has similar requirements. Ignoring near misses isn't just bad practice; in many cases it is a regulatory gap waiting to be flagged.

How Do You Build a Near-Miss Reporting Program?

You don't need expensive software or a full-time safety manager to start. You need a simple process your crew will actually follow. Here is how to build one from scratch.

Step 1: Define What Counts as a Near Miss

Your crew needs a clear, plain-language definition. Something like: "Any event where no one was injured and no property was damaged, but the potential for either was present." Give real examples from your jobsite. A load swinging near a worker. An unsecured trench wall. A missing guardrail on a platform. Keep it practical. If people have to debate whether something qualifies, they won't report it.

Step 2: Make Reporting Dead Simple

This is where most programs fail. If reporting requires a 30-minute form, a trip to the office, and a conversation with three people, it won't happen. Give your crew a one-page form, a mobile app, or even an index card in their vest pocket. The report should take less than 5 minutes. Basic fields: date, time, location, what happened, what could have happened, and what you think caused it. That's it. You can do a deeper investigation later. The goal right now is to capture the event before the details fade.

Step 3: Eliminate the Blame

This is the blunt truth: if your crew thinks reporting a near miss will get them written up, yelled at, or pulled off a job, they will never report anything. Period. You will have zero near-miss reports, and you'll think your site is safe. It's not. Your workers just stopped telling you about the problems.

Make it a clear, stated policy: near-miss reports are non-punitive. No discipline for the reporter. Ever. Some contractors go further and recognize people who report, because those workers are doing the hardest part of safety: speaking up.

Step 4: Investigate and Take Corrective Action

A near-miss report sitting in a filing cabinet does nothing. Every report needs a basic investigation. Why did it happen? Was it a process failure, a training gap, a missing piece of equipment? Then assign a corrective action with a deadline and an owner. "Fix the scaffold" is not a corrective action. "Install toe boards on all platforms above 3 metres by Friday, assigned to Jake" is.

This is the step that turns near-miss reporting from paperwork into prevention. If your team sees that their reports actually lead to changes, they will keep reporting. If nothing changes, they will stop. For a step-by-step approach to investigating these events, see our guide on how to write an incident report.

Step 5: Close the Loop with Your Crew

When someone reports a near miss and you fix the hazard, tell the whole crew. Bring it up in the next toolbox talk. "Last week, Mike reported a loose guardrail on the second floor. We inspected all guardrails and replaced three. Good catch." This does two things. It proves the system works. And it tells everyone else that reporting is worth their time.

Step 6: Track Trends and Review Monthly

Once you have reports coming in, look at the patterns. Are most near misses happening in the same area? On the same shift? Involving the same type of equipment? A single near miss is a data point. Ten near misses about the same hazard is a pattern that demands action before someone gets hurt. Review your near-miss data monthly. If you're working toward COR or SECOR certification, your auditor will want to see this kind of proactive analysis.

What Should a Near-Miss Incident Report Include?

Your near-miss report form does not need to be complicated. Here is a template outline you can adapt for your operation:

You can download a ready-to-use version of this form as part of our free Incident Report and Investigation Kit, which includes near-miss report templates, investigation checklists, and corrective action tracking sheets.

Real Examples of Near Misses on Construction Sites

If you run a crew, you have seen these. The question is whether anyone wrote them down.

• Falling object: A wrench slips out of a tool belt on the third floor and lands on empty scaffolding below. Nobody was on the scaffold at the time. The near miss reveals that tool tethering is not being enforced.
• Trench collapse (partial): A section of an unshored trench wall slumps inward while a worker is 2 metres away. If they had been inside the trench at that moment, it could have been a burial. The near miss reveals that shoring was skipped because the crew expected to "only be in there for a few minutes."
• Vehicle near-contact: A dump truck reverses on site and comes within a metre of a worker who didn't hear the backup alarm over their hearing protection. Nobody was hurt. The near miss reveals a gap in traffic management planning and spotter assignments.
• Electrical flash: A worker cuts into what they believed was a de-energized cable. A brief arc flash occurs but no contact is made. The near miss reveals a lockout/tagout failure in the isolation procedure.

Each of these is the exact same hazard that causes serious injuries and fatalities on Canadian construction sites. The only difference is luck. Near-miss reporting takes luck out of the equation.