Mechanism MEC-24

Rescue register

Record every failure a person caught before it reached someone else, so near-misses become evidence about the condition, not silence in the incident count.

  1. 1 Evidence acts here
  2. 2 Authority
  3. 3 Decision
  4. 4 Consequence
  5. 5 Challenge
  6. 6 Reconsideration
  7. 7 Correction

Where it acts

At Evidence, one of the seven stages every consequential decision passes through. It turns failures people caught before they reached anyone into evidence about the system.

Steps

Put the mechanism in motion

3 steps, in order. Check each one off as it is done; the records show the work was done.

Records this mechanism keeps

What a team running this mechanism keeps, and what each record is for.

Rescue register

One row per caught failure: near-miss condition, catcher, labor spent, and whether the source was fixed.

Repeat-condition list

Conditions that have produced more than one rescue, with the decision taken on each.

Rescue and incident series

Both counts on one axis, so a falling incident count cannot hide a rising one.

Reuse-ready snippets

Copy policy, audit, and incident language

Use these snippets in requirements, audits, and postmortems with the mechanism permalink.

Policy requirement

Policy requirement (MEC-24 Rescue register)
- Failures caught by a person before reaching anyone else are recorded as occurrences.
- Each rescue record names the near-miss condition and whether the source condition was fixed.
- Rescue counts and incident counts are reviewed together, never separately.
Reference: https://ethotechnics.org/mechanisms/patterns/rescue-register

Product requirement

Product requirement (MEC-24)
- The rescue register is an artifact in the human impact safety case.
- A rescue record cannot be closed without either a fix or a recorded decision not to fix.

Audit evidence checklist

Audit evidence checklist (MEC-24)
[ ] Rescue records exist for the review period.
[ ] Each names the near-miss condition and the labor spent catching it.
[ ] Repeat rescues against one unfixed condition appear as a standing item.

Postmortem trigger

Postmortem trigger (MEC-24)
Trigger review when rescues rise while incidents fall, or when the same condition is rescued more than once.

Example usage

Zero incidents, three hundred rescues

One scenario with each part of the mechanism in place.

How it plays out

A medication reconciliation defect produces no incidents for a year because nurses catch every mismatch before dispensing. The register shows 300 rescues against the same unfixed interface, 4,000 hours of checking nobody rostered, and an interface the institution decided not to change. The incident count reads zero. The register reads a system held together by people.

Anti-patterns

Common failure cases and counterfactuals

Each case passes on paper and fails in operation. The counterfactual shows what would have worked.

A clean incident log as proof of safety

A clean incident log is read as a safe system, while the rescues that produced the clean log go unrecorded.

Counterfactual: Rescues and incidents are one series, and the register is part of the safety case.

Exception: A falling incident count is good news only when rescues are flat too.

Hero accounting

Regular rescues against one unfixed condition are praised as reliable staff rather than read as a defect in the condition.

Counterfactual: A repeat rescue is a standing item against the condition, owned by whoever controls it.

Exception: Reliability of the person is evidence about the system, not about the person.

Diagnostics for this mechanism

Tools that size the risk this mechanism addresses.

Diagnostic

Delegation audit

Walks a team through one workflow against six questions and returns an exposure score, the permissions nobody can justify, and whether its decisions can be undone. Start here when the system keeps no decision records yet; use the record conformance checker once it does.

Cite this page · v1.2.1 · updated Oct 6, 2026 · CC BY-SA 4.0

APA

Kanav Jain. (2026). Rescue register (MEC-24). Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/rescue-register

MLA

Kanav Jain. "Rescue register (MEC-24)." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/rescue-register.

Chicago

Kanav Jain. "Rescue register (MEC-24)." Ethotechnics Institute. Oct 6, 2026. https://ethotechnics.org/mechanisms/patterns/rescue-register.

BibTeX

@misc{mechanism_rescue-register,
  title={Rescue register (MEC-24)},
  author={Kanav Jain},
  year={2026},
  howpublished={Ethotechnics Institute},
  url={https://ethotechnics.org/mechanisms/patterns/rescue-register},
  version={v1.2.1}
}

RIS

TY  - WEB
TI  - Rescue register (MEC-24)
AU  - Kanav Jain
PY  - 2026
UR  - https://ethotechnics.org/mechanisms/patterns/rescue-register
ER  -

Authorship

Contact: hello@ethotechnics.org

Publication details

  • Published: Dec 3, 2025
  • Last updated: Oct 6, 2026
  • Version: v1.2.1

License: CC BY-SA 4.0

Credit Ethotechnics Institute, include the page title and version, and link to the canonical permalink.

Archive: Wayback Machine history

Latest change

v1.2.1 · Oct 6, 2026 — Rewrote the copy of MEC-01 to MEC-12 in plain sentences. A halt is described as containment while the rule is fixed and people are restored, upheld appeals are counted against the rule in MEC-06 and MEC-08, and MEC-04 is renamed Hard clock.

Earlier versions (3)
  • v1.2.0 · Oct 1, 2026 — Filed every mechanism under the six safeguards, led the starters and role paths with challenges that reach the rule, and added that obligation to MEC-06.
  • v1.1.0 · Jan 9, 2026 — Added citation metadata, mechanisms-level authorship details, and structured usage guidance.
  • v1.0.0 · Dec 3, 2025 — Initial public mechanisms release.