Escalation deadline table
Each tier, its deadline, and what the responder may change.
Escalation deadlines
Publish a deadline for a human answer when a person escalates an automated decision, and staff to meet it. A missed deadline triggers a stated fallback, such as pausing the decision.
- 1 Evidence
- 2 Authority
- 3 Decision
- 4 Consequence
- 5 Challenge
- 6 Reconsideration acts here
- 7 Correction
Where it acts
At Reconsideration, one of the seven stages every consequential decision passes through. It sets a deadline for a human to look at an escalated decision again, and a fallback when the deadline passes.
Steps
Put the mechanism in motion
3 steps, in order. Check each one off as it is done; the records below show the work was done.
0 of 3 steps complete
Records this mechanism keeps
What a team running this mechanism keeps, and what each record is for.
Coverage roster
Who is on duty for each hour a deadline's clock runs.
Missed-deadline log
Each missed deadline and the fallback it triggered.
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-11 Escalation deadlines) - Publish escalation deadlines and the role that must answer at each tier. - Define what a missed deadline does, such as pausing or reversing the decision until a person answers. Reference: https://ethotechnics.org/mechanisms/patterns/escalation-deadlines
Product requirement
Product requirement (MEC-11) - Each escalation receipt shows the deadline and the role that must answer. - A missed deadline triggers the stated fallback with no manual step.
Audit evidence checklist
Audit evidence checklist (MEC-11) [ ] Escalation deadlines and responder roles are published. [ ] Missed deadlines, and the fallback each triggered, are logged. [ ] The staffing roster covers every hour a deadline's clock runs.
Postmortem trigger
Postmortem trigger (MEC-11) Trigger review when missed deadlines exceed the set threshold, or when a missed deadline did not trigger its fallback.
Example usage
A 24-hour deadline for frozen accounts
One scenario with each part of the mechanism in place.
How it plays out
A payments company publishes a 24-hour deadline for a human answer when a customer disputes an automated account freeze. Staff cover nights and weekends. If the deadline passes, the account unfreezes provisionally and stays open until a reviewer decides.
Anti-patterns
Common failure cases and counterfactuals
Each case passes on paper and fails in operation. The counterfactual shows what would have worked.
Escalation without coverage
A deadline is published, but no one is rostered nights or weekends, so an escalation filed Friday evening waits until Monday.
Counterfactual: The roster covers every hour the deadline's clock runs.
Exception: Office-hours coverage is acceptable if the clock counts only those hours and the notice says so.
Escalation to someone who cannot decide
The escalation reaches a person who can explain the decision but not change it, so the deadline is met and nothing moves.
Counterfactual: Each tier's responder can pause or reverse the decision within that tier's scope.
Exception: A first tier that only gathers facts is fine if it hands the case to a tier that can decide within the same deadline.
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). Escalation deadlines (MEC-11). Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/escalation-deadlines
MLA
Ethotechnics Institute. "Escalation deadlines (MEC-11)." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/escalation-deadlines.
Chicago
Ethotechnics Institute. "Escalation deadlines (MEC-11)." Ethotechnics Institute. Oct 6, 2026. https://ethotechnics.org/mechanisms/patterns/escalation-deadlines.
BibTeX
@misc{mechanism_escalation-deadlines,
title={Escalation deadlines (MEC-11)},
author={Ethotechnics Institute},
year={2026},
howpublished={Ethotechnics Institute},
url={https://ethotechnics.org/mechanisms/patterns/escalation-deadlines},
version={v1.2.1}
}
RIS
TY - WEB TI - Escalation deadlines (MEC-11) AU - Ethotechnics Institute PY - 2026 UR - https://ethotechnics.org/mechanisms/patterns/escalation-deadlines ER -