Handling bias complaints from candidates rejected by AI screening

When a candidate emails you saying your AI screening was biased, you have roughly 48 hours before the situation either resolves quietly or becomes a public exposure. Most TA teams in India have no documented procedure for this. A candidate from a tier-2 campus writes in: “Your AI rejected me because of my accent” — the TA lead scrambles, the vendor sends a data export that proves nothing, and the candidate either goes quiet or posts on LinkedIn. Either way, you got lucky. You won’t always.

This isn’t a legal brief. It’s a field guide for the HR ops person who gets that complaint during campus season.

Why AI bias complaints are structurally different from other candidate grievances

When a candidate says “your interview was too long” or “I never got a response,” HR teams have standard handling. When a candidate says “your AI scored me lower because of my accent” or “your system discriminated against me based on region,” the complaint immediately implicates the vendor’s scoring logic — which TA teams typically cannot access or audit without a formal escalation.

This is the core asymmetry. You’re being asked to explain a decision made inside a model you don’t fully control, against parameters you may not have set. The EU AI Act (Article 6) classifies hiring AI as a high-risk system precisely because of this accountability gap — and enforcement begins August 2026. Indian companies using EU-linked vendors, or those selling into European markets, need a bias complaint workflow before then, not during their first live incident.

SHRM’s 2025 AI-in-HR survey found that 88% of HR leaders see AI screening as a compliance risk. The same organizations, for the most part, have no formal procedure for the next step: what to do when a candidate actually files a complaint.

The four-step response framework

This framework is calibrated for TA directors running AI voice screening at 1,000 to 3,000 candidates per campaign.

Acknowledge within 24 hours — without admitting fault. The acknowledgment does two things: confirms receipt, and signals that a process exists. Don’t write “we’re sorry our AI rejected you.” Write: “We’ve received your note and are reviewing the specific session. We’ll respond within [X business days].” In India, even without legal compulsion, word travels fast in campus placement communities. A candidate who gets a thoughtful response is far less likely to escalate than one who gets silence.

Pull the session record before responding substantively. Every AI screening session should have a timestamped transcript or audio log. If your vendor cannot provide this within 48 hours, that’s a capability gap to address before your next campaign — not during a live complaint. You’re looking for the questions asked, the candidate’s responses, and whatever scoring rationale is logged. Not to overturn the score yet — to establish your factual basis.

Apply documented human-in-the-loop review. Here’s the take that will make a vendor uncomfortable: not every bias complaint warrants score reversal. Reversing scores on demand to avoid escalation is actually less fair to candidates who were correctly rejected on merit. What the complaint warrants is documented human review — a TA lead who reads or listens to the session and checks whether the rejection was consistent with the JD’s screening criteria. If the rubric says “verbal communication in English is required for this client-facing role” and the AI scored low on that dimension, that’s a defensible decision. If the AI scored low for reasons that can’t be traced to any JD requirement, that’s a flag — and a reason to formally escalate to your vendor for model review.

Close the loop with the candidate, regardless of outcome. If the review confirms the rejection stands: explain what the screening evaluated and why those criteria apply to the role. Don’t share scores. Share the criteria. If the review reveals an error: reinstate the candidate and flag the session for model review. Candidates who receive clear explanations — even when the outcome is rejection — rarely escalate further.

What Mobley vs Workday means for your complaint process

The Mobley vs Workday case (2024) was the first major AI-hiring discrimination lawsuit in the US, filed by a Black applicant who alleged systematic rejection across hundreds of applications via Workday’s AI hiring recommendations (background on AI hiring lawsuits). The case is still active, but its evidentiary logic is what Indian TA teams should study: the burden to show that an AI hiring tool was applied consistently against job-related criteria falls on the employer, not the candidate.

This matters in India even without direct legal application. Models trained on US or EU speech data often underperform on Indian accents, regional dialects, and non-native English fluency patterns. Campus candidates from tier-3 colleges speaking regional-inflected English are exactly the population most at risk from models calibrated on standard American or British speech — which means your bias complaint rate from those cohorts may be higher than from tier-1 pipelines, and your documentation for those decisions needs to be proportionally stronger.

Our analysis of the Mobley ruling and what it means for Indian TA teams covers the specific fact pattern worth knowing before your next high-volume drive.

Build the log before the first complaint arrives

In pilot campaigns screening over 1,099 candidates through structured AI voice interviews, the volume of formal bias complaints was very low — but the infrastructure to handle them was built from the first campaign. Session records with timestamps. A complaint log with reviewer name, decision, and outcome. An escalation path to the vendor. A closure template for candidates.

The practical minimum before your next campaign: one shared document where every bias complaint is logged with date, session ID, reviewer, decision, and outcome. That’s your audit trail if the question ever becomes a legal one.

HireQwik’s per-JD screening rubric approach means candidates are always evaluated against role-specific criteria, not a generic template — exactly the kind of traceable, documented link between JD requirements and screening decisions that a bias review depends on.

One clear take: organizations that wait for regulation to build this workflow will be building it while an active complaint is in flight. The setup cost is two hours. The crisis cost is two weeks and a lawyer.