Meta Sued for AI-Driven Layoffs That Allegedly Penalised Workers on Protected Leave
Not legal advice. This article discusses legal and regulatory developments and is generated with AI assistance under human editorial review. It is provided for informational purposes only and does not constitute legal advice. Laws and regulations vary by jurisdiction and are subject to change. You should consult your own qualified legal counsel before taking or refraining from any action based on the content of this article. Read our AI Transparency statement.
The News
Twenty-six current and former Meta workers filed a lawsuit on July 14 in the U.S. District Court for the Northern District of California, alleging that Meta used 'a constellation of internal artificial-intelligence systems' to score, rank, and select employees for its approximately 10% reduction in force. The plaintiffs claim the AI tools relied on inputs — performance ratings, calibration scores, productivity metrics, AI-token consumption — that 'by design, cannot be accumulated by an employee who is on protected medical or family leave, or whose output is reduced by a disability.' The lawsuit alleges Meta did not neutralise those inputs to account for protected leave, effectively penalising workers for exercising their legal rights. The plaintiffs cite violations of the Americans with Disabilities Act, the Family and Medical Leave Act, the Pregnancy Discrimination Act, the Pregnant Workers Fairness Act, and Title VII. A Meta spokesperson said the claims 'lack merit' and that 'workforce management and organizational decisions were and are made by people, not AI.'
Why It Matters
This is the first major U.S. lawsuit to directly challenge AI-driven layoff selection on discrimination grounds, and it lands at the intersection of two issues every TA leader should be tracking: AI governance in employment decisions and the legal exposure of algorithmic workforce management. The core allegation — that AI inputs systematically disadvantage anyone who took protected leave — is a design flaw that any organisation using AI for performance scoring, reduction-in-force selection, or even hiring funnel optimisation could replicate without realising it. If your HR analytics team is feeding productivity metrics into any decision system without adjusting for leave, accommodation, or part-time status, the same legal theory applies. The Workday applicant-screening case is already working through the courts; this expands the perimeter from hiring into separations.
Taking Action
All action is situated in your corporate context. These are starting points, not prescriptions — choose what fits.
Connect
Who to talk with in your enterprise
Your employment counsel: Ask specifically whether any internal tool — AI-powered or not — that scores, ranks, or flags employees for any employment decision (hiring, promotion, RIF, performance management) has been audited for disparate impact on employees who have taken protected leave or requested accommodations.
Your HR analytics lead: Request a list of every input variable fed into your workforce decision systems. Flag any metric that is functionally unachievable during leave or reduced by accommodation. That list is your exposure inventory.
Inspect
What to take a closer look at
Identify your most recent reduction-in-force, performance calibration, or high-potential identification exercise. Trace the data inputs used. If any metric — productivity, output, AI-tool usage, attendance, calibration score — was included without being adjusted or neutralised for protected leave status, document the gap and raise it with legal counsel before the next cycle.
Reflect
What to think about more deeply
If your AI system recommends someone for layoff, and that person was on maternity leave when the data was collected, who is responsible for the decision — the system, the manager who approved it, or the person who designed the inputs?