Scope
A contestable service makes the disputed action identifiable, explains how review works and preserves the information needed to investigate it. The process must have somewhere to go: a reviewer with the authority to correct the decision or address its consequences. Feedback collection, a generic contact form and an explanation with no remedy are different capabilities.
Illustrative example
A service rejects a customer’s request using an outdated record. The customer can see which record mattered, submit a correction and track a review. A responsible reviewer can amend the outcome and explain the result. This illustrative scenario tests whether the route changes decisions when warranted, not simply whether a complaints button exists.
Terms and contribution
Contestability is an established research topic, including Alfrink, Keller, Kortuem and Doorn’s “Contestable AI by Design”. The contribution explored here is its integration into the author’s account of governable delegation and design delivery. It is not presented as a term invented by this journal.
Read in this order
- From Interface Craft to Governable Delegation — Start with the link between a service’s legitimacy and a person’s ability to challenge its actions.
- Designing for agency — Locate accountability when action is distributed across agents and organisational roles.
- Design Governance OS — Consider how review ownership, evidence and quality checks can become part of delivery practice.