Open standards & artifacts for accountable systems.

Specification sheet

Permanent link /mechanisms/patterns/appeal-paths

MEC-06 Appeal paths inside the UI

Give people a built-in channel to dispute outputs, get human review, or learn how a decision was made.

Where it fits

Filters and handoffs

Tagged for Friction, Governance with validator handshakes. Includes 3 steps, 3 reusable assets, and 4 snippet blocks.

Scholarly metadata

Authorship

Contact: research@ethotechnics.org

Publication details

  • Published: Dec 3, 2025
  • Last updated: Jan 9, 2026
  • Version: v1.1.0
  • DOI: Pending Zenodo deposit

License: CC BY-SA 4.0

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

Archive snapshot: Wayback capture

Changelog

  • v1.1.0 · 2026-01-09 — Added citation metadata, mechanisms-level authorship details, and structured usage guidance.
  • v1.0.0 · 2025-12-03 — Initial public mechanisms release.

Copy citation (APA/BibTeX)

Cite this page Formats: APA, MLA, Chicago, BibTeX, RIS

Version

v1.1.0

Last updated

Jan 9, 2026

DOI

Pending Zenodo deposit

APA

Ethotechnics Institute Research Team. (2026). MEC-06 Appeal paths inside the UI. Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/appeal-paths

MLA

Ethotechnics Institute Research Team. "MEC-06 Appeal paths inside the UI." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/appeal-paths.

Chicago

Ethotechnics Institute Research Team. "MEC-06 Appeal paths inside the UI." Ethotechnics Institute. Jan 9, 2026. https://ethotechnics.org/mechanisms/patterns/appeal-paths.

BibTeX

@misc{mechanism_appeal-paths,
  title={MEC-06 Appeal paths inside the UI},
  author={Ethotechnics Institute Research Team},
  year={2026},
  howpublished={Ethotechnics Institute},
  url={https://ethotechnics.org/mechanisms/patterns/appeal-paths},
  version={v1.1.0}
}

RIS

TY  - WEB
TI  - MEC-06 Appeal paths inside the UI
AU  - Ethotechnics Institute Research Team
PY  - 2026
UR  - https://ethotechnics.org/mechanisms/patterns/appeal-paths
ER  -

Specification overview

At-a-glance details for planning and handoffs.

Capture the scope, assets, and validator handshakes before diving into the steps.

Spec essentials

What ships with this mechanism

  • 3 steps with checklist-ready owners.
  • 3 reusable assets for briefs and runbooks.
  • 4 reuse-ready snippet blocks.
  • 3 glossary anchors for shared terms.

Filters & validators

Where this spec sits in the system

Tagged in 2 filters with 2 linked validators.

Glossary anchors

Link back to the definitions.

Jump to the glossary terms that frame this mechanism.

Steps

Put the mechanism in motion.

Start with the field cues, then use the assets to keep the work legible.

3 steps with checklist-ready owners, plus linked assets for handoffs.

Assets

Keep outputs reusable.

Link or copy these assets into design docs, runbooks, and briefs so the mechanism travels with the work.

Appeal intake form

Collects the minimum details with pre-filled context from the UI.

Reviewer rota

Lists who reviews appeals, coverage hours, and escalation paths.

Outcome log

Keeps decisions, response times, and fixes visible to teams and leadership.

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 in-product appeal channel with published response timelines.
- Log appeal outcomes and feed them into governance review cycles.
Reference: https://ethotechnics.org/mechanisms/patterns/appeal-paths

Product requirement

Product requirement (MEC-06)
- Every appeal submission generates a receipt with response timeline and owner.
- Appeals are accessible from the decision surface without extra navigation.

Audit evidence checklist

Audit evidence checklist (MEC-06)
[ ] Appeal intake form includes pre-filled context.
[ ] Reviewer rota and escalation paths are documented.
[ ] Outcome log tracks response times and resolutions.

Postmortem trigger

Postmortem trigger (MEC-06)
Trigger review when appeal backlogs breach published response timelines.

Example usage

Adding appeals to a risk scoring tool

A concrete scenario to help teams see how the pieces fit together.

How it plays out

The team adds an on-screen “Dispute this score” link with expected response times, routes submissions to a staffed rota, and logs turnaround data to improve credibility with regulators.

Anti-patterns

Common failure cases and counterfactuals

Use these to avoid superficial compliance and clarify what success requires.

Appeal link buried

Appeals exist but are hidden in help docs or separate portals far from the decision.

Counterfactual: Appeal entry points sit next to the affected decision with visible timelines.

False-positive warning: Low-frequency contexts can use a help center if it is still clear and accessible.

Appeals without feedback

Collects disputes but provides no receipt, timeline, or outcome signal.

Counterfactual: Every appeal generates a receipt, timeline, and outcome log.

False-positive warning: Timelines can vary by case complexity if the variance is stated and tracked.

Validators

Pair validators with this mechanism.

Use these tools to size risk and keep the stewardship path visible.

Validator

Burden Modeler

Quantifies task load, cognitive friction, and risk exposure so you can reroute toil before it burns people out.

Validator

Maintenance Simulator

Tabletop simulation that plays through outages, maintenance windows, and handoffs to stress-test coverage.