Act
Contestability & Appeal
How can I challenge this decision?
Gives people a working route to challenge a decision and get a human review with a documented response.
- Evidence: research-based (Lyons et al. 2021, Kroll et al. 2017)
- Tested: concept only, mock data
Overview
Why it matters
A right you can't find is a right you don't have.
People affected by automated decisions often have a legal right to challenge them. That right only works with a visible path: a button, a person who reviews, and a response.
Unlike Human-in-the-Loop, which operators use inside the process, this pattern is used by the affected person, after the decision. Unlike Actionable Recourse, which helps with a future decision, it challenges the decision that was made.
What does it look like?
Applicant challenging an adverse credit decision
Applicant challenging an adverse credit decision
- Applicant receives: "Application declined." (case #4821)
- Below the decision: "Disagree with this decision? You have the right to request a human review."
- Applicant clicks "Request review."
- Form appears: reason for challenge (prefilled with their case summary), option to add information, upload documents.
- Applicant submits. Receives confirmation: "Your request has been received. A caseworker will review your case within 5 business days. Reference #4821-R1."
- Applicant can track status in their account.
Content moderation challenge
Content moderation challenge
- User's post is removed by an automated moderation system.
- Notification shows: "Your content was removed for [reason]. If you believe this was a mistake, you can appeal."
- User submits appeal with context the automated system didn't have.
- Human moderator reviews within 24 hours.
- Content is restored, or decision is upheld with an explanation.
Escalation
Escalation
- First-level review upholds the original decision.
- User is not satisfied.
- Interface shows: "If you remain dissatisfied, you can contact the Financial Services Ombudsman at [link] or file a complaint with [regulator]."
- User has a documented reference number from the original challenge to use in further escalation.
When does it fit?
Use it when
- Decisions affect rights, access to services or finances
- Law or regulation gives people a right to contest
- Decisions may rest on wrong, outdated or incomplete data
Skip it when
- The decision is clearly low-stakes
- There is no real review behind it: a fake appeal path is worse than none
Design
How do I apply it?
-
Show the path right after the decision.
That's when people are most motivated to act.
-
Never harder than applying.
If applying took ten minutes, challenging shouldn't take an hour.
-
Guarantee a human review.
The same system judging again is a repetition, not a review.
-
Give a timeline, and keep it.
A challenge without updates is worse than none.
-
Log every challenge.
Each one shows where people believe the system was wrong. See Audit Trail & Logging.
For your operations team
The interface is only as good as the process behind it. Agree review capacity, response times and escalation contacts before launch, and record every challenge as an event in the audit trail.
How can I show it?
Challenge action
"Request review", visible on the decision screen.
A clearly labelled, persistent action available after any adverse decision: "Challenge this decision" or "Request review." Not buried in a footer or help section. Visible at the decision result screen.
Human review promise
A clear statement that a person reviews it.
An explicit statement that the challenge will be reviewed by a human, not re-processed by the same automated system. This is the core of meaningful contestability.
What happens next
Who reviews, how long, possible outcomes.
Immediately after submitting a challenge, provide a clear explanation of the review process: who reviews it, what the timeline is, what the possible outcomes are. Reduces anxiety and sets expectations.
Reason form
Prefilled, with room for context and documents.
A structured form with a reason for the challenge (dropdown and free text), the option to upload supporting documents or evidence, contact information for follow-up, and a submission confirmation with a reference number. Prefill it with the case summary.
Status tracker
Received, under review, pending, resolved.
After submission, a status view showing where in the process the challenge is: received, under review, decision pending, resolved.
Escalation path
Ombudsman or regulator, if the review fails.
If the first-level review is unsatisfactory, information about further escalation, whether an ombudsman, a regulator, or a court, is made visible. Users should not have to research this independently.
What does it cost?
Access vs. gaming
Some people will use an open path to delay decisions. Design for proportion, don't close the path for everyone.
Real review vs. compliance theater
A form with no review behind it ticks a box and fails people. Be honest about capacity instead.
Speed vs. thoroughness
Five days is usable, six months is not. Design the process and the interface together.
Connections
Which patterns work with it?
Human-in-the-Loop
Who can review or override this decision?
HITL is exercised by operators within the process. Contestability is exercised by affected persons after the decision. Both are oversight mechanisms but serve different roles.
Actionable Recourse
What can I do to change this outcome?
Recourse helps users change the inputs to get a different future outcome. Contestability challenges the specific past decision. They address different goals and should be clearly distinguished in the interface.
Audit Trail & Logging
What is the complete record of this decision?
Every challenge must be logged. The audit trail is the foundation for meaningful review.
Decision Timeline
What happened and when?
Providing the decision timeline to the person challenging the decision helps them understand what happened and build a substantive case.
Sources (4)
Sources (4)
Lyons et al. (2021) — Conceptualising Contestability: Perspectives on Contesting Algorithmic Decisions
analyzes public submissions to Australia's proposed AI Ethics Framework to examine what people expect contesting an algorithmic decision to involve, finding contestability is broadly understood as a protection for individuals comparable to challenging a human decision. Published in Proceedings of the ACM on Human-Computer Interaction, 5 (CSCW1)
European Union (2016) — General Data Protection Regulation (GDPR). Article 22
the primary legal mandate for human review of automated decisions and the right to contest
European Union (2024) — EU AI Act, Article 14
extends human oversight requirements to high-risk AI systems
Kroll et al. (2017) — Accountable Algorithms
argues that algorithmic accountability requires not just transparency but contestability: a mechanism for challenging decisions through a process that is itself auditable
Your only appeal path is a "Contact us" form.
Or a regulator has asked how affected people can challenge your system's outcomes. That's where this pattern starts. Let's look at your interface together.
Work with me