# Ask what stopped the near miss from becoming harm

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Ask what stopped the near miss from becoming harm

ID: MHC-D-RESEARCH-1268 · Version: 0.1.0 · Kind: question
Source: https://vedokrok.com/knowledge/ask-what-stopped-the-near-miss-from-becoming-harm

A good ending can hide whether the system was protected or merely lucky.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A near miss ended safely and the team is tempted to close it because 'the control worked.'

### Avoid when

- A single near miss cannot establish a control's failure probability. Use the analysis to choose what to verify, redesign or measure next.

### Explanation

Identify the last thing that interrupted the failure path. Was it a designed safeguard, an independent human check, an unrelated circumstance or pure timing? Then ask whether the same catch would still exist under a different operator, higher load or slightly different sequence. The aim is not to praise or blame the final catcher; it is to understand how much protection actually exists.

### Question

An error reached the final step but happened to be noticed because a colleague walked past the screen. Was the process protected?

### Example

A reviewer notices a wrong customer before activation. If review was optional and happened only because that person had spare time, the system should not count it as a reliable barrier.

### Check

The review names the actual catching mechanism and whether it is designed, repeatable and independent enough to rely on.

### Limits

- A single near miss cannot establish a control's failure probability. Use the analysis to choose what to verify, redesign or measure next.

### Evidence and sources

- supports: AHRQ safety-engineering guidance recommends combining prospective and retrospective analysis with ongoing surveillance, and notes that workarounds can signal that a process is not functioning well. — RS-00E7F25184BF4AAC. The guidance is written for healthcare systems; transfer to knowledge work is at the general system-design level. (Strategy 1 rationale and opportunities)
- supports: OSHA recommends investigating close calls and near misses to identify underlying hazards, contributing causes and program shortcomings, and grouping similar events to find trends. — RS-68FF51A7951C10DC. The guidance concerns occupational safety. The same record structure may be useful elsewhere, but the regulatory context does not transfer. (Hazard Identification and Assessment; Conduct incident investigations)
- limits: 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. — RS-2EA215EDE3EC0E64. The review concerns patient safety and does not test every type of operational near-miss program. (PSNet summary)
- RS-00E7F25184BF4AAC: Engineering Safe Practices Affinity Group — https://www.ahrq.gov/action-alliance/engineering-safety-practice/index.html
- RS-68FF51A7951C10DC: Safety Management - Hazard Identification and Assessment — https://www.osha.gov/safety-management/hazard-identification
- RS-2EA215EDE3EC0E64: The value of learning from near misses to improve patient safety: a scoping review — https://psnet.ahrq.gov/issue/value-learning-near-misses-improve-patient-safety-scoping-review

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/layer-safeguards-so-one-miss-is-not-the-last-chance
