Ask your projects data anything. Get answers in seconds. Plexa MCP Connector is live. See it in action

A dropped scaffold plank inside a taped exclusion zone below a scaffold tower, with workers looking up at the level it fell from

Near miss

Also known as: Near hit, close call, near miss incident

Definition

A near miss is an unplanned event that could have caused injury, illness or damage but did not. It is reported and investigated because the sequence behind it is the same sequence that produces an injury, with only chance deciding which outcome occurred.

What Counts as a Near Miss

A near miss is defined by what could have happened rather than by what did. The test is whether, with slightly different timing or position, someone would have been hurt or something would have been damaged.

Typical construction examples are a dropped tool landing in an area that happened to be empty, a load swinging clear of a worker, a reversing truck stopping short, a worker stepping onto an unsecured penetration cover, a scaffold plank left unsecured and discovered before use, and a service struck without anyone being injured.

The distinction from a hazard is useful. A hazard is a condition with potential to cause harm, such as an unguarded edge. A near miss is an event that has already occurred and did not result in harm. Reporting systems benefit from capturing both, but they are different things and conflating them makes the data unreadable.

The reason near misses matter is that the underlying failure is identical to the one in an injury event. The control that was missing, the step that was skipped, the assumption that was wrong, all happened, and asking where the failed control sat in the hierarchy of controls usually explains why it gave way. Only the outcome differed, and outcomes are the part nobody controls. A site that investigates near misses with the same seriousness as injuries gets the same learning at a fraction of the cost.

For a deeper look, read Notifiable Incidents in Construction: What You Must Report, and When. Try the free LTIFR and TRIFR Calculator.

When a Near Miss Is Actually Notifiable

This is the part that catches people, and it is worth getting right. A near miss is not automatically notifiable, and the absence of an injury is not what decides it.

Under the model work health and safety laws, certain dangerous incidents must be notified to the regulator immediately even though nobody was hurt. The categories include things like an uncontrolled escape of a substance or gas, an uncontrolled implosion, explosion or fire, electric shock, the fall or release from height of plant, substance or thing, the collapse or partial collapse of a structure, the collapse of an excavation or its shoring, the damage or collapse of plant required to be licensed or registered, and the interruption of the main system of ventilation in an underground excavation.

So a scaffold that partially collapses with nobody on it, or a load that falls from a crane into an empty zone, may well be a notifiable dangerous incident as well as a near miss. The duty to notify and preserve the site applies in the same way as for a serious injury.

The practical rule is to classify every near miss against the dangerous incident categories before filing it as internal only. Treating a notifiable dangerous incident as just a near miss, because luckily nobody was standing there, is how notification obligations get missed.

How to Run Near Miss Reporting That Works

Near miss reporting is the easiest safety system to put in place and the easiest to kill. The failure mode is always the same: people stop reporting because reporting costs them something.

Make it quick. If reporting takes more than a minute or two, it will not happen during a shift. The person who saw it is usually busy.

Keep blame out of it. A near miss report frequently involves the reporter having made the mistake. If the response is disciplinary, the next one does not get reported, and the information disappears.

Close the loop visibly. The strongest driver of reporting is seeing something change. Report back at prestart what was reported and what was done, by name of the issue rather than the person.

Investigate proportionately. High potential near misses, the ones that could have killed somebody, get a full investigation. Lower potential ones get recorded and trended. Treating every report identically either overwhelms the system or trivialises the serious ones.

Watch trends rather than counts. A rising number of reports usually means the system is working, not that the site is getting worse. The number worth watching is repetition of the same mechanism.

Separate near misses from hazards and from recorded injuries such as a lost time injury in the data, so each can be read on its own.

Common Mistakes With Near Miss Reporting

Treating a low report count as good news. A site reporting no near misses is almost never a site without them. It is a site where reporting is not safe or not easy.

Missing the notification. The most serious error on this page: some near misses are notifiable dangerous incidents in their own right. Check the categories before deciding it is internal only.

Investigating the person instead of the sequence. The useful question is what allowed this to happen, not who did it.

No severity rating. Without a potential consequence rating, a trapped finger and a near fatality sit side by side in the same list and get the same attention.

Recording and never analysing. A register that is filled in weekly and read annually produces compliance and no learning.

Excluding subcontractors. Most of the workforce on a commercial site is not directly employed. If the reporting system is only used by the builder's staff, most of the information never arrives.

Frequently asked questions

What is a near miss in construction?

−

An unplanned event that had the potential to cause injury, illness or damage but did not. A dropped tool landing in an empty area or a load swinging clear of a worker are typical examples, where only timing or position prevented harm.

What is the difference between a near miss and a hazard?

−

A hazard is a condition with the potential to cause harm, such as an unguarded edge. A near miss is an event that has already happened and happened not to cause harm. Both are worth reporting, but they are different records.

Does a near miss have to be reported to the regulator?

−

Not usually, but some do. Certain dangerous incidents must be notified immediately even with no injury, including structural or excavation collapse, a fall of plant or material from height, electric shock, and uncontrolled fire or escape of substance.

Why report near misses at all if nobody was hurt?

−

Because the failure behind a near miss is the same failure that causes an injury, and only chance decided the outcome. Investigating them gives the same learning as an injury investigation without anyone being harmed.

Is a high number of near miss reports a bad sign?

−

Usually the opposite. A rising report count normally means workers trust the system enough to use it. The figure worth watching is the same mechanism repeating, which shows a control that is not working.

On this page

Free Playbook

The Missing AI Playbook for Construction Safety

Learn practical AI workflows for incident reports, SWMS, compliance checks, safety data and training, with real prompts you can use and review yourself.

Related terms

Browse the glossary

Site & HSEQ Management

Make reporting a near miss take under a minute

Capture near misses and observations on a phone with a photo, rate the potential, and show the crew what changed as a result.

Project record

Live

Variation V-014

Priced

RFI-022

Answered

SWMS-031

Approved

Progress claim 7

Submitted

Site & HSEQ Management

Make reporting a near miss take under a minute

Capture near misses and observations on a phone with a photo, rate the potential, and show the crew what changed as a result.

Project record

Live

Variation V-014

Priced

RFI-022

Answered

SWMS-031

Approved

Progress claim 7

Submitted

One platform. One data model. Every project.

Book a 30-minute walkthrough with our team, built around how you run your sites.

One platform. One data model. Every project.

Book a 30-minute walkthrough with our team, built around how you run your sites.

© 2026 Plexa Pro Pty Ltd. ABN 63 668 433 136