Recourse and dispute affordances
A 'dispute this action' affordance on each receipt that opens a complaint pre-filled with the action record and a service-side response clock.
When something goes wrong (the agent filed incorrectly, used wrong data, or the citizen disagrees with an outcome), there must be a clear, accessible path from the specific action to a dispute mechanism. The dispute must be anchored to the specific action record, not require the citizen to re-narrate the entire history.
Every action record carries a clear path from the specific action to a dispute mechanism, with the complaint pre-populated from the action record and time-bound response obligations on the service provider.
Dispute affordances are pre-populated from the action record so citizens need not re-narrate history. A plain-language 'dispute this action' route anchored to the receipt, with assisted channels for those who cannot self-serve, keeps recourse genuinely accessible.
The chargeback model's 'anchor the dispute to a specific transaction and shift the burden to investigate' becomes a dispute button on the receipt that pre-fills the complaint from the action record.
No surface has been built yet; the approach above is the brief for one.
- Established Headline
Chargeback and ombudsman models are well-established recourse mechanisms.
- Emerging
GDPR contest affordances for automated decisions are beginning to appear.
- Frontier
Agent-action-anchored dispute flows in government services remain undesigned.
Financial services chargeback flow. Under Regulation Z (US) and PSD2 (EU), card holders have reversal rights; the issuer must acknowledge a dispute within 30 days, investigate, and within 90 days correct or explain. Pre-dispute resolution services resolve issues before they escalate to formal chargebacks. See Wikipedia — Chargeback and Wikipedia — Fair Credit Billing Act.
Ombudsman complaint mechanism. The ombudsman model requires the public body to "explain what it did and why" when a complaint is lodged; the ombudsman assesses whether the decision was reasonable and lawful and can surface systemic problems, though recommendations are not binding. See Office of the Ombudsman Malta — Accountability and Transparency International — Complaint Mechanisms Guide.
GDPR Article 22 contest rights. Beyond explanation, Article 22 provides the right to contest an automated decision and to express one's own point of view. This requires concrete interface affordances: a way to initiate a contest, a channel to add information, and a mechanism to receive a revised decision. See GDPR Local — Automated Decision Making.
The chargeback model is particularly instructive: the dispute is anchored to a specific transaction with a unique identifier, the burden shifts to the service provider to investigate, and there are time-bound response obligations.
For agent-mediated government services, each action receipt should include a "dispute this action" affordance that pre-populates the complaint with the action record, so the citizen need not re-describe what happened. The ombudsman model adds the requirement that disputes can surface systemic issues, not just individual errors.
Where this goes wrong is recourse that is effectively inaccessible, trapping citizens in engaged phone lines while errors stand. Anchoring disputes to specific action records with time-bound response obligations forces earlier correction.
The worst case