ReviewDesk
← Back

ReviewDesk guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

How should you handle a formal complaint about an automated decision?

Generate a free adverse-outcome letter — no sign-up Build a free pre-use notice See pricing

The short answer. Treat the complaint as a case, not a correspondence: log it on the same docket the day it arrives, assemble the decision's complete file, have it read by someone other than the original reviewer, and answer from the record — specifically, in the order the complaint raises its points. Most complaints about automated decisions are really about silence, vagueness or a specific factual error; the file you kept for the decision answers all three, if it was kept. ReviewDesk's trail, histories and vault exist for this day.

What is complaint handling for automated decisions?

A formal complaint about an automated decision is an escalated challenge — from the person, their representative, or a regulator or ombuds channel — alleging the decision, its explanation or its review was wrong or unfair. Handling it well means processing it through the same evidentiary discipline as the original decision: one docket, the complete file, an independent read, a specific answer, and the outcome recorded with the case.

What is a complaint actually telling you?

Usually one of three things, and the triage task is to discover which before drafting anything. A factual claim: the record was wrong — which the correction machinery may never have been offered or may have mishandled. A process claim: the person was not told, not explained to, or not reviewed — which your own trail will confirm or refute in minutes. Or a merits claim: the decision itself, on correct facts through a fair process, is challenged as wrong — which is a genuine second look at the criteria's application. Each claim type has a different honest answer, and a reply that treats a factual complaint as a merits dispute (or the reverse) convinces the complainant that nobody read their letter.

Read the complaint the way reviewers are taught to read requests in the checklist: the person's own points, in their order, become the answer's structure. Complaints are the only programme documents the author chooses the headings for — accept the gift. An answer that mirrors the complaint's structure point by point is recognisably an answer; an answer that opens with your process description is recognisably a defence, and defences invite escalation the way answers invite closure.

Why must the complaint join the same docket?

Because fragmentation is how complaint handling corrupts records. The complaint answered from a director's inbox, by email, outside the case history, creates a second, shadow file: the docket says one thing, the correspondence says another, and any later reader — the person's adviser, an examiner, your own successor — must reconcile two partial truths. File the complaint on the original case the day it arrives, assemble the complete file around it, and let every subsequent act be a docket event. The person experiences one matter; the record shows one matter; the organisation speaks once.

The docket also disciplines the clock. Complaints carry their own urgency — a person who has escalated has usually already waited — so assign the case an explicit internal deadline and an owner senior enough to act on what the file shows. ReviewDesk's escalation mechanics from the escalation guide apply to complaint cases with tighter internal targets, because a complaint is definitionally a case where the standard machinery has already been judged insufficient by the person it served.

Who should read the complaint case?

Someone other than the original reviewer, senior enough to concede error without permission-seeking, with the authority to order the remedy the file supports. Independence here is not a courtesy; the complaint frequently implicates the review itself, and a defence of one's own review written by its author persuades nobody — sometimes including its author, midway through drafting. The independent reader works from the assembled file: original decision, notice, letter, request, review note, communications, and now the complaint, in chronological order. Assembly discipline from the response guide applies unchanged; the reader's freshness is the new ingredient.

If the file shows the complaint is right — in whole or in a part that matters — concede that part completely, remedy it visibly, and record the concession with the same prominence as the original decision. Partial concessions drafted to minimise ('while we accept the letter could have been clearer…') read as their opposite. A clean concession is the strongest sentence a complaint answer can contain, because it proves the answer was written by someone who read the file rather than defended it.

How should the answer be built?

From the record, point by point, with the documents doing the work. For a process claim, the answer cites the artefacts: the notice version and its date, the letter with its number, the review with its reviewer's note — attached or exported where the channel allows, per the vault guide. For a factual claim, it states what was checked, against what source, and the corrected state. For a merits claim, it gives the second look's reasoning — genuinely a second look, engaging the complaint's strongest argument by name. Close with the remedy where one is owed, the person's remaining routes stated accurately, and the file's availability to them.

Tone follows the letter discipline of the tone guide at higher stakes: no defensiveness disguised as thoroughness, no legal fog, no counter-attack on the complainant's manner. A person can be rude and right; the answer addresses the rightness. And never let the answer claim a record the file does not contain — the complaint context is precisely where the 'not recorded' honesty of the evidence guide earns its keep, because complaints are read by people whose profession is checking.

What remedies should be on the table?

Whatever the file supports, without a negotiation posture: correction and re-decision where facts were wrong; a fresh review by a different reviewer where the first was thin; the outcome's practical consequences undone where they can be (the application restored, the flag cleared, the fee or charge reversed where the decision caused it) — verified in the originating system, per the post-review guide. An apology that is specific — naming what failed, in the process's own terms — rather than atmospheric. And where the complaint exposes a systemic fault, the fix's description and date: complainants who learn their case repaired the pipeline for others consistently rate the handling higher than complainants who merely won.

Record the remedy's completion, not just its promise, on the case. A complaint closed on a promised remedy that nobody verified is a second complaint gestating with better evidence. The closure rule for complaints mirrors the inbox's two halves and adds the third: outcome decided, answer sent, remedy verified in the system it belongs to.

What does the programme owe itself after a complaint?

The pattern read. One complaint is a case; the year's complaints are a curriculum. Classify each by claim type and root cause, and let the annual review of the programme-review guide consume the classification: factual complaints indict data sources, process complaints indict communication machinery, merits complaints indict criteria or their explanation. A programme whose complaints decline in the factual class year over year is fixing its data; one whose process complaints persist is not listening to its own postbag.

Finally, protect the people who handled the original case from the complaint's blast radius where the file shows they worked properly. A complaint is an allegation, and the file — not the allegation's volume — is the evidence of their work. Organisations that treat every complaint as a staff failure teach their reviewers to write defensive notes and avoid overturns; organisations that read the file first, and defend it where it deserves defending, keep reviewers honest in both directions. The record protects everyone who worked inside it. That, in the end, is what it is for.

Your five actions for complaint handling for automated decisions

  1. Log the complaint on the original case the day it arrives; assign a senior owner and a tighter internal clock.
  2. Classify before drafting: factual, process or merits — and structure the answer by the complaint's own points, in their order.
  3. Give the file to an independent reader with authority to concede and remedy; concede cleanly where the file says the complaint is right.
  4. Answer from the record with artefacts cited, remedies verified in the originating system, and remaining routes stated accurately.
  5. Classify the complaint into the programme's pattern read — data, communication or criteria — and minute the fix it commissions.

Worked example: a complaint that the file answered in four days

A fictional lender receives a formal complaint, via a representative, alleging a decline was unexplained, the review a rubber stamp, and the underlying record wrong about a satisfied judgment. The case is docketed the same morning onto the original file. The independent reader's assembly takes an hour: notice version 3, the generated letter with its three reasons (the judgment among them, identified by date and court), the review note engaging the applicant's documents across four paragraphs — and the bureau confirmation, dated after the review, that the judgment was indeed satisfied and the file stale, which had arrived through a channel nobody had routed to the case.

The answer concedes the third point completely — the record was wrong, the correction is now filed and verified, the application re-assessed and approved at the requested amount — answers the process points with the artefacts themselves, and describes the routing fix that now sends bureau confirmations to the case automatically. Four days, one letter, no second round. The complaint was a third right, and the file said so plainly enough that conceding it cost nothing but the postage on pride. The lender's complaint log gains a root cause and a fix; the representative gains a story about a firm that reads its own files. Both were produced by the same habit: keeping the record as if this day were coming, because it always is.

Frequently asked questions

How is a complaint different from a review request?

Altitude and authorship: a complaint challenges the decision, its explanation or its review itself, often through a representative or a formal channel. Handle it as a case on the same docket — with an independent reader and a tighter clock — not as correspondence.

Who should handle the complaint?

Someone other than the original reviewer, senior enough to concede error and order remedies without escalation. The complaint frequently implicates the review itself, and self-defence persuades nobody.

What if the complaint is partly right?

Concede the right part completely and remedy it visibly; answer the rest from the record. A clean partial concession is the strongest signal that the answer was written from the file rather than from instinct.

Should the answer attach the records?

Where the channel allows, yes — the notice version, the letter, the review note, the correction evidence. The file is the argument; sending it converts assertion into demonstration and usually ends the exchange.

Is this guide legal advice?

No. ReviewDesk is templates and workflow tooling, not legal advice. Complaint handling is described as an operating discipline; formal complaints may carry legal obligations — consult counsel promptly for those.

Keep reading: How do you prepare for future automated-decision rules without knowing what they will say? · What must a Colorado pre-use notice for an automated decision tool say? · What must a California ADMT pre-use notice include? · What does Illinois HB 3773 require when AI is used in employment decisions? · What is automated decision-making technology (ADMT)? · All ReviewDesk guides · ReviewDesk home · Try the free desk · Free letter generator · Free notice builder · Pricing

ReviewDesk is built by Ingenious AI. Templates and workflow tools — not legal advice.