Mobley and the agent theory: why the human gate is the architecture, not a feature
Somewhere between the resume and the rejection email, a decision gets made. A federal case in California asks who made it: the employer, or the software the employer rented.
Mobley v. Workday is active litigation in the Northern District of California, No. 3:23-cv-00770. Workday denies the claims. There is no settlement. Nothing in this post predicts how the case ends. This is not legal advice.
The case has already put one question on every board agenda: when a tool rejects your candidates, whose decision was it?
The question is not abstract. A large employer rejects most of the people who apply, and screening software touches every one of those rejections. If the vendor can stand in the employer's shoes, the architecture of the tool becomes the liability question.
Last reviewed: July 2026.
Where the case stands
Two orders define the case so far.
On March 6, 2026, the court ruled that the ADEA covers applicants. The federal age discrimination statute covers people applying for work, before they ever become employees.
On June 22, 2026, the court granted Workday's motion to dismiss in part and denied it in part. Claims under California's fair employment statute (FEHA) proceed. One claim under the Americans with Disabilities Act proceeds.
The case continues.
The theory that survived
The claims that proceed rest on a theory of agency. The court let the case go forward on the idea that a vendor can act as the employer's agent where rejecting and advancing candidates is delegated to the tool.
That theory does not need the tool to be an employee or a contractor. It needs one fact: the employer handed the reject-or-advance call to the software.
Look at your own stack through that lens. If a screening tool can reject a candidate and no person at your company ever sees the application, the delegation at the heart of the case reads like a description of the workflow. The exposure follows the decision, and the decision sits wherever the call was made.
Delegation is a spectrum, and the theory cares where on it your workflow sits. A tool that ranks applications while a recruiter chooses who advances is one end. A tool that rejects by default, at volume, while no person reviews the rejection, is the other. Most buying processes never ask which end they are purchasing.
The human gate as architecture
NODES was built on the opposite delegation. The system reads, scores, ranks, and drafts. The reject-or-advance call stays with a person, who approves every decision before anything runs.
That approval gate is architecturally locked. It is not a configuration option, a workflow setting, or a policy promise. The validator rejects any save that violates it, the same way it rejects an adverse action without a human approver.
A setting is a feature. The gate has to be load-bearing. Features get toggled when a quarter gets busy. Architecture holds.
Under the agency theory, the difference between a tool that decides and a tool that prepares a decision is the whole case. One delegates the call to software. The other keeps the call with a named person and leaves a record: who approved, what they saw, which evidence backed it. That record is the Decision Trace, and it exists because the gate exists.
What to ask every vendor
Procurement teams can act on the agency theory today, whatever the court does next.
- Who makes the reject-or-advance call on a candidate: the tool, or a named person?
- Can any rejection run without a human approval? If so, is that a setting someone can toggle, or is a rejection without approval impossible by construction?
- What record exists for each decision, and can your counsel read it without the vendor's help?
A vendor that cannot answer those three questions is asking you to carry its exposure. A vendor with a structural answer welcomes them. They are the questions a court would ask. The AI governance use case covers what the answers look like when the gate is structural, and the security and compliance page covers the review path.
Frequently asked questions
Is there a settlement in Mobley v. Workday? No. There is no settlement. The case is active litigation in the Northern District of California, and Workday denies the claims.
What has the court ruled so far? On March 6, 2026, the court ruled that the ADEA covers applicants. On June 22, 2026, the court granted the motion to dismiss in part and denied it in part. Claims under California's fair employment statute (FEHA) and one claim under the Americans with Disabilities Act proceed.
What is the agent theory in Mobley v. Workday? The theory the court allowed to proceed: a vendor can act as the employer's agent where rejecting and advancing candidates is delegated to the tool.
Does this case make AI screening illegal? No. The case is active, Workday denies the claims, and nothing here predicts an outcome. The structural question it raises belongs in every procurement review: who makes the call, and what is the record of it?
Related reading
- The Digital Omnibus and AI hiring: what changed, what did not
- Decision traces: the full research
- AI governance and compliance use case
- The published hiring research
Ask your vendors who makes the call. Then ask what the record shows. Book a 30-minute walkthrough.