Mobley v. Workday: when the vendor is the employer
Mobley v. Workday is a federal class action alleging that Workday's AI screening platform caused unlawful employment discrimination across hundreds of employers. The court refused to dismiss, treating Workday as a potential agent of the employers — a posture that materially changes vendor and deployer risk.
- Short name
- Mobley v. Workday
- Jurisdiction
- United States — N.D. Cal. federal court
- Penalty ceiling
- Title VII / ADEA remedies; class-wide exposure
- Last updated
- May 21, 2026
Applies to
- Employers using AI hiring vendors
- AI hiring vendors operating in the US
What it is
Mobley v. Workday is a putative federal class action filed in the Northern District of California in 2023, alleging that Workday’s AI hiring screening platform discriminates against applicants on the basis of race, age, and disability. The plaintiff alleges he applied to and was rejected from over a hundred jobs that used Workday, and that the common cause of the rejections was Workday’s screening system rather than the individual employers’ decisions.
This is not a statute. It is litigation. But its operational implications for deployers are large enough that we treat it like a regime.
Why this case matters
In July 2024, the court issued a published order partially denying Workday’s motion to dismiss. The order took the position that Workday — a vendor — could be liable under Title VII and the ADEA as an agent of the employers that used its platform, even though Workday is not itself the employer.
This is the analytical move that changes the calculus. Before Mobley, the operating assumption was that vendor and employer have clean separation of liability: the vendor faces contract claims; the employer faces Title VII claims. After Mobley, the agency theory blurs that line. Vendors can be joined as defendants in employment discrimination cases. Employers can be exposed to amplified liability because the vendor’s practices may be imputed to them. [TODO: confirm latest case posture before relying on this page; the docket is active.]
What the deployer should do
The case has not resolved on the merits, so the proper response is defensive documentation:
- Maintain a defensible record of the AI hiring tool’s use. What you deployed, when, for what roles, and under what oversight.
- Document the bias-testing posture. What testing the vendor did, what testing you did, what gaps were identified, what mitigations were taken.
- Document the human-decision boundary. Where does the AI’s output stop being deterministic and start being recommended? Who reviews? With what criteria?
- Contract for indemnification and information. Your contracts with the AI hiring vendor should give you the right to obtain the bias-testing artifacts you need, and to be defended by the vendor in the case of platform-level discrimination claims.
How Casework helps
The Casework engagement produces the documentation a deployer would want to put in front of plaintiff’s counsel in a Mobley-style suit: the FRIA, the RMS, the post-market monitoring records, the bias-audit-framework deliverable. The engagement also surfaces the contractual gaps with your vendor.
We do not litigate. If a notice arrives, we coordinate with your outside counsel under the regulator-response support add-on.
Looking at this regulation from the vendor side instead? HireAIScore covers vendor compliance posture against this regulation.