Why this matters
The case for near-miss reporting is that small warnings are corrected locally but never become visible enough to prevent a similar event elsewhere. For managers responsible for learning from weak signals before they become repeat events, the immediate concern is whether the available facts support a timely and proportionate decision.
- Search intent
- Managers looking for practical WorkSafe guidance on near-miss reporting.
- Read time
- 3 min read
- Hub
- Hazards, Incidents and Near Misses
Short answer
Near-miss reporting should give the responsible manager current evidence, clear ownership and a recorded basis for deciding what should be escalated, investigated, trended or closed at source. It is effective when the live status can be tested without reconstructing events from separate files or conversations.
What this means in practice
Near-miss reporting can be tested in a realistic situation. For example, a manager may need to decide what should be escalated, investigated, trended or closed at source while several teams are updating location, photographs, immediate controls, investigation notes and corrective actions. In that moment, the manager must decide what should be escalated, investigated, trended or closed at source; the record should make the relevant facts and accountable role immediately clear.
Near-miss reporting: a record can be complete on paper and still fail the manager. That happens when small warnings are corrected locally but never become visible enough to prevent a similar event elsewhere, removing the context needed to choose a proportionate response.
Near-miss reporting: a defensible review uses location, photographs, immediate controls, investigation notes and corrective actions. Keeping those records connected prevents a later note or photograph from being mistaken for proof that the original concern was resolved.
Near-miss reporting: WorkSafe can make near-miss reporting visible at the point responsibility changes hands. Linking the source record, action and verification reduces ambiguity about what is open and what has genuinely been resolved.
For near-miss reporting, day-to-day control should produce faster reporting, better investigation context and earlier visibility of recurring risk. WorkSafe does not guarantee compliance outcomes, but it can make the control trail easier to manage and explain.
Key checks
- Which role creates, reviews and accepts the near-miss reporting record?
- Is superseded evidence clearly distinguishable from current proof?
- Does the review result lead to a stated operational decision?
Common mistakes
- Moving near-miss reporting between teams without a named handover point.
- Keeping photographs or notes outside the record they are intended to support.
- Assuming an updated status explains the decision history.
What good looks like
For near-miss reporting, ownership is named, the status reflects current conditions and supporting records stay attached to the decision. Routine completions and exceptions can be reviewed separately, allowing the manager to justify what should be escalated, investigated, trended or closed at source.
When to use WorkSafe
Use WorkSafe for near-miss reporting where evidence passes between roles, shifts or systems and the current position is difficult to establish quickly. Configure the first workflow around the source record, accountable role and proof needed to decide what should be escalated, investigated, trended or closed at source.
Apply these checks to one recent near-miss reporting case and note where its ownership, decision or verification becomes unclear.