# Capture the near miss while the evidence still exists

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
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Capture the near miss while the evidence still exists

ID: MHC-D-RESEARCH-1267 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/capture-the-near-miss-while-the-evidence-still-exists

A near miss is most useful before it turns into a polished story.

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

### Use when

- Something almost went wrong, was caught just in time or reached an unsafe state without the full consequence.

### Avoid when

- Do not turn every harmless variation into an investigation. Prioritize credible consequence, recurrence or evidence that an important control was bypassed or nearly failed.

### Explanation

Record the event before memory and the system state drift. Capture what was intended, what actually happened, when the deviation became visible, what could have happened, and which logs, messages, files or observations still preserve the sequence. Keep description separate from explanation. Reporting creates evidence for review; it is not evidence that the risk has already been reduced.

### Steps

1. Another reviewer can reconstruct the deviation and the detection point from preserved evidence without relying on the operator's memory.

### Example

A bulk update targeted the correct file but the wrong environment was selected; a preview exposed the mismatch before commit. Save the selection, preview and timestamps before changing anything.

### Check

Another reviewer can reconstruct the deviation and the detection point from preserved evidence without relying on the operator's memory.

### Limits

- Do not turn every harmless variation into an investigation. Prioritize credible consequence, recurrence or evidence that an important control was bypassed or nearly failed.

### Evidence and sources

- 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)
- supports: AHRQ's CANDOR guide frames adverse-event and near-miss investigation around preventing future events through systems review rather than assigning blame. — RS-D0175F3DBA3A507B. A systems approach does not remove individual accountability for reckless or knowingly unsafe behavior. (A Systems Approach)
- 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
- RS-D0175F3DBA3A507B: System-Focused Event Investigation and Analysis Guide — https://www.ahrq.gov/patient-safety/settings/hospital/candor/modules/guide4.html

### Vedokrok editorial review

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.

#### 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.

**Editorial takeaway:** 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.

#### Editorial evidence

- supports: OSHA’s investigation guide places completion of emergency response and a safe, secure scene before investigation and evidence preservation. — RS-OSHA-INCIDENTGUIDE2015. Selected official passages. The queued-software-operation example is an independent editorial adaptation, not an OSHA instruction for software. (Safety First, printed p. 6; Preserve/Document the Scene, printed p. 7)
- limits: OSHA distinguishes implementing controls from checking that those controls work, so recording an incident does not itself establish reduced risk. — RS-OSHA-HAZARD-CONTROL. Workplace-safety guidance supplies the boundary; no causal effect or universal reporting procedure is claimed. (Action item 6: Follow up to confirm that controls are effective)
- RS-OSHA-INCIDENTGUIDE2015: Incident Investigations: A Guide for Employers — https://www.osha.gov/sites/default/files/IncInvGuide4Empl_Dec2015.pdf
- RS-OSHA-HAZARD-CONTROL: Safety Management: Hazard Prevention and Control — https://www.osha.gov/safety-management/hazard-prevention

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/ask-what-stopped-the-near-miss-from-becoming-harm
