Protocol
Make the situation safe, then preserve the near miss
A near miss deserves a record while the details are fresh. Evidence capture must not delay stopping an active danger.
Before you use it
- Use when
- Something almost went wrong, was caught just in time or reached an unsafe state without the full consequence.
Keep this limit in mind
- Do not turn every harmless variation into an investigation. Prioritize credible consequence, recurrence or evidence that an important control was bypassed or nearly failed.
Current editorial reading
Put containment first
Follow the applicable emergency or stop procedure if harm can still occur. Once the situation is safe, preserve the remaining evidence before routine cleanup changes it. For example, if a bulk update is queued for the wrong environment, cancel the pending run first; then retain the run ID, target, preview and timestamps. Record any state changed by the safety response rather than trying to recreate the unsafe condition.
Leave a record someone can check
Write the intended result, observed deviation, detection point, credible consequence and available evidence. Separate what the record shows from your explanation of why it happened. Ask another reviewer whether the sequence can be reconstructed, and mark gaps openly. Keep the record proportionate to the risk: the aim is a useful account, not a perfect archive that takes priority over containment.
Take it with you
A complete report shows what happened and what interrupted it. Reducing the chance of recurrence still requires a separate decision about causes, safeguards and follow-through. This is a general workflow adaptation, not a substitute for a domain’s emergency procedures.
Sources and evidence (2)
What we checked
OSHA’s investigation guide places completion of emergency response and a safe, secure scene before investigation and evidence preservation.
Selected official passages. The queued-software-operation example is an independent editorial adaptation, not an OSHA instruction for software.
Incident Investigations: A Guide for Employers · Safety First, printed p. 6; Preserve/Document the Scene, printed p. 7
OSHA distinguishes implementing controls from checking that those controls work, so recording an incident does not itself establish reduced risk.
Workplace-safety guidance supplies the boundary; no causal effect or universal reporting procedure is claimed.
Safety Management: Hazard Prevention and Control · Action item 6: Follow up to confirm that controls are effective
Editorial sources (2)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingMake the situation safe, then preserve the near miss
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaReview a risky success, not only a visible failure
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
OSHA recommends investigating close calls and near misses to identify underlying hazards, contributing causes and program shortcomings, and grouping similar events to find trends.
The guidance concerns occupational safety. The same record structure may be useful elsewhere, but the regulatory context does not transfer.
Safety Management - Hazard Identification and Assessment · Hazard Identification and Assessment; Conduct incident investigations
A 2022 scoping review found limited evidence that near-miss reporting and learning itself improves patient safety, so reporting should not be treated as proof that risk has fallen.
The review concerns patient safety and does not test every type of operational near-miss program.
The value of learning from near misses to improve patient safety: a scoping review · PSNet summary
AHRQ's CANDOR guide frames adverse-event and near-miss investigation around preventing future events through systems review rather than assigning blame.
A systems approach does not remove individual accountability for reckless or knowingly unsafe behavior.
System-Focused Event Investigation and Analysis Guide · A Systems Approach
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details