AI Risk Wire

Cases › biased or discriminatory › LR-2026-0628

26 Meta employees sue over AI-assisted layoff selection allegedly ignoring protected leave

Confirmed Why: 3 independent outlets · 3 independent reports

Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.

Status: no action reported

Severity major
Reported 14 Jul 2026
Developer and model Meta
Industry social media

No source states: loss or records, agent tool, could do, deployer.

Severity major: Test: many third parties, meaning a stated count of two or more affected parties. Fact: the 26 unnamed employees are stated as affected.

Twenty-six current and former Meta employees sued the company in a federal court in California, alleging that AI systems used to select workers for its May layoff round did not account for protected leave or disabilities. The complaint says the systems drew on performance ratings, productivity metrics and AI-token consumption, which by design could not accumulate during protected absences, and that the company did not adjust for them. The plaintiffs allege this disproportionately selected people on medical, parental or family leave. Meta says the claims lack merit and that workforce decisions were made by people, not AI. The plaintiffs have asked the court for a preliminary injunction pending an independent audit, and no ruling had been reported at the time of the sources.

What happened

1 · What it was doingMeta's internal AI systems were used to choose which employees to cut in the May layoff round, according to the complaint.
2 · What went wrongThe lawsuit alleges the company did not account for protected leave in the scores and did not pause the system for an individualized leave-neutral review.
3 · What it reached or didThe lawsuit says people on protected medical or family leave were disproportionately selected for dismissal.

What was done

No source states an action or fix.

Risks

Read from the sources; not yet reviewed by a person.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Application

Bias testing · Risk assessment per deployment · Output filtering and redaction

Similar incidents

All cases of this kind ›

Evidence

No source states: how it was caught, when it happened, when it was found, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.

Show the full account: 4 items from the primary sources

What happened, in order

  1. May Plaintiffs were among about 10% of Meta's workforce cut in the company's May layoff round.
  2. July 22 Separations of the 26 employees were set to begin.

Not dated in the sources:

  • Plaintiffs filed the lawsuit in federal court in California and said they wish to pursue their claims individually in arbitration.
  • No federal judge had yet ruled on the plaintiffs' emergency request to block the firings.
Show every field, with its source and grade

The AI system

Developer
Meta
C one secondary source states it

What happened

Earliest source we hold
2026-07-14
D inferred by us from the described behaviour, reason shown
What went wrong
biased or discriminatory
C one secondary source states it
primary risk
RK16
D inferred by us from the described behaviour, reason shown

Impact

Severity
major
D inferred by us from the described behaviour, reason shown
Why this severity
Test: many third parties, meaning a stated count of two or more affected parties. Fact: the 26 unnamed employees are stated as affected.
D inferred by us from the described behaviour, reason shown

Context

Industry
social media
C one secondary source states it
Country
United States
C one secondary source states it

Notes on gaps

All harms are allegations by plaintiffs; Meta denies them and says decisions were made by people. No remediation is reported. The Workday case and the Model Capability Initiative security failure are separate matters and were excluded. Reversibility reflects the plaintiffs' own stated view.

LR-2026-0628 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON