Control · C-080 · Fairness & Customer Outcomes
Customer remediation for AI errors
When an AI error is found, all affected customers are identified, told, and put back in the position they should have been in, whether or not they complained.
- Control type
- Corrective
- Risks addressed
- 5
- Audience
- Heads-of · Practitioner
- Frameworks
- PRIN 2A.2 · PRIN 2A.6
- Responsible AI domain
- Lifecycle stage
- Reviewed
- 2026-11-11
What it does
It puts right the harm an AI error has caused. Because a model applies the same fault to every similar case, one discovered error implies others. The control establishes the scope, finds the customers affected, corrects the decision or record, compensates for loss and tells them what happened. The business owner of the system is accountable; operations and compliance run the exercise. It operates after an error is identified, by incident, complaint, appeal or monitoring.
How to implement it
- Define what triggers a remediation review, including a single upheld complaint that points to a systematic fault.
- Use decision records to identify every customer affected, over the whole period.
- Decide the remedy by reference to where the customer would otherwise have been.
- Contact customers proactively, in plain language.
- Fix the cause before reprocessing cases through the same system.
- Record the exercise and report it to governance, and to the regulator where required.
Evidence it operates
Design: a remediation procedure with triggers and governance. Operation: records of exercises with scope, method, numbers and amounts; customer communications; evidence that the root cause was fixed; reporting to the board or regulator.
Where it fits
After detection, alongside AI incident response and rollback. It is a primary control for inadequate contestability and redress, and supports wrongful automated refusal and poor customer outcomes from AI-driven journeys. It depends on AI record-keeping and audit trail to find who was affected.
Limits
It acts after harm. Some losses cannot be made good, such as a missed house purchase. Finding affected customers depends on records that may not have been kept. Remediation is expensive, which creates pressure to define the scope narrowly; the decision on scope therefore needs independent challenge.
Risks this mitigates
Primary mappings
- Inadequate contestability and redress High
- Provides the remedy when a challenge succeeds. People affected by an AI-supported decision cannot challenge it, cannot have it reviewed by someone with the authority and information to change it, or cannot obtain a remedy.
Supporting mappings
- Deepfake impersonation and synthetic identity fraud Critical
- Puts right customers who were defrauded. Generated voice, image, video or documents are used to impersonate customers or to create false identities, defeating verification and authentication.
- Exploitation of vulnerable groups by AI Critical
- Puts right people harmed before the use was stopped. An AI system exploits vulnerabilities arising from a person's age, disability or social or economic situation to distort their behaviour in a way that causes, or is likely to cause, significant harm.
- Poor customer outcomes from AI-driven journeys High
- Puts affected customers right. An AI-driven customer journey causes foreseeable harm to retail customers, or fails to support their understanding and needs, and outcome monitoring does not detect it.
- Wrongful automated refusal High
- Corrects wrongly refused cases. A system incorrectly declines, blocks or withdraws a product, payment or claim, and the person affected has no effective way to have it corrected.
Framework and clause references
| Framework | Clause | Title |
|---|---|---|
| FCA Consumer Duty (PRIN 2A) | PRIN 2A.2 | Cross-cutting obligations Acting in good faith when harm is found. |
| FCA Consumer Duty (PRIN 2A) | PRIN 2A.6 | Consumer support outcome Putting things right. |
How to cite
Axiom Verity (2026). Customer remediation for AI errors. Reference Library, C-080. https://axiom-verity.com/controls/customer-remediation-for-ai-errors. Reviewed 2026-11-11.
Found an error or a better source? Report a correction.