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

No. Most near misses are internal reporting matters, not formal notifiable incidents. Notification thresholds under WHS law are reserved for actual dangerous incidents, a separate and narrower category.

Why do workers under-report near misses even with a process in place?

Self-filtering, fear that a report leads to blame, and the effort a report takes are the three consistent reasons. Workers tend to report only what genuinely scared them, and only if they trust it will not be used against them.

What is the single biggest fix for low near-miss reporting?

A demonstrated no-blame response, a debrief rather than a write-up, kept consistent over time. Policy documents alone do not shift behaviour; what happens to the first few people who report does.

Is a cluster of near misses at the same location meaningful?

Yes, more meaningful than a single dramatic report elsewhere. A repeated near miss at the same spot is an early signal that the layout or process at that location needs attention.

Why Near-Miss Reporting Under-Performs What Policy Assumes

Most warehouses have a near-miss reporting process. Most near misses still never get logged. The gap between the policy and the practice comes down to self-filtering, blame and effort, not a missing form.

Last updated 2026-08-23

What counts as a near miss, and what has to be reported

A near miss is an event that could have caused harm but did not, a forklift and a pedestrian in the same space a second apart, a pallet that shifted but did not fall, a load that clipped a beam without bringing anything down. Most of these carry no formal notification requirement to a regulator; that threshold is reserved for actual dangerous incidents as defined under WHS law. Internal reporting of the near miss itself is a workplace policy choice, not a legal notification, which is exactly why it depends entirely on the culture that supports it rather than a compliance obligation forcing it to happen.

Why most near misses never get logged

A forklift-to-pedestrian or forklift-to-rack near miss unfolds in one to three seconds and leaves no physical evidence behind. Whether it gets reported depends almost entirely on whether the person involved judged it worth reporting, and people instinctively self-filter, only logging the ones that genuinely scared them and staying quiet on the ones that felt routine, even when a genuinely different outcome was only a moment away.

Blame culture compounds the self-filtering. A worker who suspects a report will trigger a write-up, a retraining session treated as punishment, or scrutiny of their own conduct has a real incentive to say nothing, particularly if the near miss involved their own mistake rather than someone else's. Effort is the third factor, and it is the most fixable: a reporting process that takes ten minutes of form-filling after a five-second event will lose out to simply getting on with the shift, every time.

Why this matters more than it looks

The value of near-miss data is not the individual report, it is the pattern across many of them. A near miss that happens once is an anecdote. The same near miss happening repeatedly at the same blind aisle end or the same corner where forklift strikes keep occurring is a genuine early warning that something in the layout or the process needs fixing, before it produces an actual injury rather than a close call.

A site that only investigates after an injury is relying on the worst possible data source to find its hazards. Near-miss reporting, done well, is meant to be the cheaper, earlier signal, but it only works if enough of the actual near misses make it into the system to form a real pattern rather than a handful of the most dramatic ones.

What actually makes it work

The consistent theme in how this gets fixed is a genuine no-blame process: a debrief conversation about what happened and what would prevent it next time, rather than a write-up attached to the worker's file. That distinction has to be real and demonstrated repeatedly, not just stated in a policy document, because workers judge it by what actually happens to the first few people who report, not by what the poster on the wall says.

Making reporting fast matters as much as making it safe. A short verbal or app-based report logged in under a minute will get used far more than a multi-field form, and the system used to log it should be built around that speed, not around capturing every possible field a safety manager might one day want. It is the same dynamic that makes continuous, small-effort counting work better than an annual audit: frequent and low-effort beats occasional and high-effort, for reporting as much as for counting.

What good reporting does not replace

A working near-miss process is a leading indicator, not a substitute for the underlying controls it is meant to catch gaps in, sound racking inspection intervals, proper separation between people and moving plant, and equipment kept in good service condition. It tells you where those controls are being tested hardest; it does not replace having them in the first place.

Common questions

Does every near miss have to be reported to a regulator?: No. Most near misses are internal reporting matters, not formal notifiable incidents. Notification thresholds under WHS law are reserved for actual dangerous incidents, a separate and narrower category.
Why do workers under-report near misses even with a process in place?: Self-filtering, fear that a report leads to blame, and the effort a report takes are the three consistent reasons. Workers tend to report only what genuinely scared them, and only if they trust it will not be used against them.
What is the single biggest fix for low near-miss reporting?: A demonstrated no-blame response, a debrief rather than a write-up, kept consistent over time. Policy documents alone do not shift behaviour; what happens to the first few people who report does.
Is a cluster of near misses at the same location meaningful?: Yes, more meaningful than a single dramatic report elsewhere. A repeated near miss at the same spot is an early signal that the layout or process at that location needs attention.

Sources

Safe Work Australia — Incident notification — National guidance distinguishing notifiable dangerous incidents from broader internal near-miss reporting, used here to establish that most near misses are a workplace policy matter, not a regulator notification.

Part of our guide to rack protection and safety barriers.