Appeal intake form
Asks only for what the person must add, with the decision and its reason code filled in.
Appeal paths inside the UI
Put an appeal next to each automated decision, so the person decided about can dispute it and get a human answer by a stated date. Upheld challenges count against the rule.
- 1 Evidence
- 2 Authority
- 3 Decision
- 4 Consequence
- 5 Challenge acts here
- 6 Reconsideration
- 7 Correction
Where it acts
At Challenge, one of the seven stages every consequential decision passes through. It gives the person decided about a way to dispute the decision and a date for a human answer.
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.
Reviewer roster
Who answers appeals, the hours covered, and where an unanswered appeal goes next.
Outcome log
Each appeal's result, the time taken, and the rule an upheld challenge counted against.
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-06 Appeal paths inside the UI) - Provide an appeal channel inside the product, with a published answer date and a named reviewer role. - Count upheld challenges by the rule that produced them, and send the count to the rule's owner. A set number sends the rule back for review. Reference: https://ethotechnics.org/mechanisms/patterns/appeal-paths
Product requirement
Product requirement (MEC-06) - Every appeal returns a receipt with the answer date and the role that will answer. - The appeal is one step from the decision screen. - Each upheld challenge records the reason code of the rule it overturned.
Audit evidence checklist
Audit evidence checklist (MEC-06) [ ] The appeal form pre-fills the decision and its reason code. [ ] The reviewer roster and the escalation path are written down. [ ] The outcome log records each appeal's answer time and result. [ ] Upheld challenges are counted by rule, and the count reaches the rule's owner.
Postmortem trigger
Postmortem trigger (MEC-06) Trigger review when appeals pass their published answer date, or when a rule reaches its upheld-challenge threshold and its owner has not reviewed it.
Example usage
Adding appeals to a credit-limit tool
One scenario with each part of the mechanism in place.
How it plays out
A lender puts a “Dispute this limit” link beside each automated credit-limit cut, with the reason code filled in and a ten-day answer date. In the first quarter, 62 of 80 upheld challenges trace to one income-verification rule. The count reaches that rule's owner, and because it passes the threshold of 50, the rule goes back for review.
Anti-patterns
Common failure cases and counterfactuals
Each case passes on paper and fails in operation. The counterfactual shows what would have worked.
Appeal link buried
Appeals exist, but only in help pages or a separate portal, so few of the people the system decides about find them.
Counterfactual: The appeal sits next to the decision, with the answer date shown.
Exception: A help-center route works for rare decisions if the decision notice links straight to it.
Appeals without feedback
Disputes are collected, but the person gets no receipt, no answer date, and no outcome.
Counterfactual: Every appeal returns a receipt and an answer date, and the outcome is logged.
Exception: Answer dates can vary with case complexity if the notice states the range and the log tracks it.
Appeals that only fix cases
Each upheld challenge reverses one decision. The rule that produced it stays, and the next person meets the same error.
Counterfactual: Upheld challenges are counted by rule, and a set number obliges the rule's owner to revise it or publish why not.
Exception: A challenge upheld because of a data-entry error in one case need not count against the rule, if that reason is recorded.
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). Appeal paths inside the UI (MEC-06). Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/appeal-paths
MLA
Ethotechnics Institute. "Appeal paths inside the UI (MEC-06)." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/appeal-paths.
Chicago
Ethotechnics Institute. "Appeal paths inside the UI (MEC-06)." Ethotechnics Institute. Oct 6, 2026. https://ethotechnics.org/mechanisms/patterns/appeal-paths.
BibTeX
@misc{mechanism_appeal-paths,
title={Appeal paths inside the UI (MEC-06)},
author={Ethotechnics Institute},
year={2026},
howpublished={Ethotechnics Institute},
url={https://ethotechnics.org/mechanisms/patterns/appeal-paths},
version={v1.2.1}
}
RIS
TY - WEB TI - Appeal paths inside the UI (MEC-06) AU - Ethotechnics Institute PY - 2026 UR - https://ethotechnics.org/mechanisms/patterns/appeal-paths ER -