Workplace safetyWorkplace inspections
Near-miss reports: capture observations without prejudging the cause
A near-miss report should capture what was observed, where and when, with an appropriate immediate response and review route. Recording an event is not the same as determining its cause or completing an investigation.
At a glance
A near-miss report should capture what was observed, where and when, with an appropriate immediate response and review route. Recording an event is not the same as determining its cause or completing an investigation.
Define the decision behind the record
Make the form accessible and avoid forcing the reporter to choose a definitive cause. Record only necessary personal information and define access. A useful early report can contain uncertainty; preserve that rather than encouraging staff to fill gaps with assumptions.
Preserve the observed sequence before drawing conclusions
Prepare a reporting route that captures event time, place, observed sequence and relevant accounts without requiring a cause to be known. Identify the responsible receiving role and immediate site reporting arrangements. Avoid unnecessary personal or sensitive information in broadly accessible evidence.
Keep observed facts, reported statements and later investigative conclusions distinct. Record the source of a statement and preserve uncertainty. If evidence is added later, retain its timing rather than making it appear available at the original report.
Link investigation, actions and feedback to the report. Test an uncertain account and a repeated condition: the record should allow review without forcing a blame label or a premature cause. Closing an action is separate from completing the investigation, and both should retain understandable decisions and evidence.
Worked example
An employee reports an event with no recorded injury but a concern about how work was organised. The report retains their description and the immediate response. An authorised person handles review and any subsequent investigation separately.
Build a usable record
Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.
- Event location and time
- Reporter’s factual description
- Immediate response
- Relevant evidence and uncertainty
- Review owner and status
Example record and review decision
Fictional record example: NEAR-01: location, time, observed sequence, people’s reported accounts and immediate response; REVIEW-01: later investigation.
Keep observations, reported statements and causal conclusions separate, preserving what was known at each stage.
A confident cause entered before investigation can bias later review and obscure contradictory evidence.
Test the review, not just the form
Review a sample for unnecessary personal data and unsupported conclusions. Confirm that subsequent investigation findings do not overwrite the initial report. The reporting process should clearly tell staff how urgent concerns are escalated.
A few useful answers
Should the reporter select the root cause?
Capture their observations and uncertainty. Determining causes belongs to the appropriate review or investigation process.
Must the reporter identify the root cause?
The initial report can preserve facts and uncertainty. Investigation may establish causes later; record those conclusions with their supporting evidence and responsible review rather than forcing a guess at entry.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
