Event definitions
Names and required fields for intervention, halt, and restore records.
Accountability latency tracker
Measure the time from a trigger firing to a named person intervening, halting the system, and restoring the people harmed, so the risk owner sees every missed target.
- 1 Evidence
- 2 Authority
- 3 Decision
- 4 Consequence
- 5 Challenge
- 6 Reconsideration
- 7 Correction acts here
Where it acts
At Correction, one of the seven stages every consequential decision passes through. It times how long it takes a named person to intervene, halt the system, and restore the people harmed.
Steps
Put the mechanism in motion
4 steps, in order. Check each one off as it is done; the records below show the work was done.
0 of 4 steps complete
Records this mechanism keeps
What a team running this mechanism keeps, and what each record is for.
Latency report
Latency trends with each missed target marked, prepared for the incident review.
Latency response runbook
Who acts on a missed target, where it escalates, and what they change.
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-07 Accountability latency tracker) - Record intervention, halt, and restore times with the person who acted, the trigger, and the system. - Publish accountability latency targets in the incident runbook. Reference: https://ethotechnics.org/mechanisms/patterns/accountability-latency-tracker
Product requirement
Product requirement (MEC-07) - The monitoring view shows accountability latency next to time to halt. - Each intervention emits a receipt linked to the repair log and the escalation owner.
Audit evidence checklist
Audit evidence checklist (MEC-07) [ ] Intervention, halt, and restore events are recorded with timestamps. [ ] Reports show median and worst-case accountability latency. [ ] Incident reviews record latency against target and what was changed. [ ] Missed targets move the grant's state and produce a reconsideration record.
Postmortem trigger
Postmortem trigger (MEC-07) Trigger review when accountability latency misses a published target, or when the events needed to measure it were not recorded.
Example usage
Tracking override time during a claims surge
One scenario with each part of the mechanism in place.
How it plays out
A car insurer records each time a reviewer overrides an automated claim denial. During a surge of storm-damage claims, median time to override rises from 20 minutes to 6 hours. The miss is logged against the target, the denial grant moves to review_required, and the risk owner adds two reviewers to the night roster.
Anti-patterns
Common failure cases and counterfactuals
Each case passes on paper and fails in operation. The counterfactual shows what would have worked.
Latency tracked without owners
The times are recorded, but no one is named to act when a target is missed.
Counterfactual: Each target names the owner who acts on a miss and where it escalates.
Exception: Two teams can share a target if the record says which one acts first.
Latency without repair links
Missed targets are logged but never tied to a fix, so the same delay comes back.
Counterfactual: Every missed target links to a repair log entry that says what changed.
Exception: A miss caused by a one-time outside event, such as a regional power outage, can close with a recorded reason instead of a fix.
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
Ethotechnics Institute. (2026). Accountability latency tracker (MEC-07). Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/accountability-latency-tracker
MLA
Ethotechnics Institute. "Accountability latency tracker (MEC-07)." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/accountability-latency-tracker.
Chicago
Ethotechnics Institute. "Accountability latency tracker (MEC-07)." Ethotechnics Institute. Oct 6, 2026. https://ethotechnics.org/mechanisms/patterns/accountability-latency-tracker.
BibTeX
@misc{mechanism_accountability-latency-tracker,
title={Accountability latency tracker (MEC-07)},
author={Ethotechnics Institute},
year={2026},
howpublished={Ethotechnics Institute},
url={https://ethotechnics.org/mechanisms/patterns/accountability-latency-tracker},
version={v1.2.1}
}
RIS
TY - WEB TI - Accountability latency tracker (MEC-07) AU - Ethotechnics Institute PY - 2026 UR - https://ethotechnics.org/mechanisms/patterns/accountability-latency-tracker ER -