Meta is facing a fresh legal challenge that targets not just the decisions behind recent layoffs, but the machinery that may have helped shape them. According to a lawsuit filed by 26 former Meta employees, the company used internal AI tools as part of the process for identifying which workers would be laid off—and those systems allegedly failed to properly account for employees who were on protected leave, including parental leave and medical leave. The plaintiffs argue that the result was a scoring and ranking approach that disproportionately selected people who had exercised legally protected rights, effectively turning time away from work into a disadvantage.
The case, reported earlier by Reuters and now detailed further in court filings shared publicly, centers on how Meta allegedly combined performance-related data with automated scoring. The employees claim that Meta relied on a “constellation” of internal AI-driven systems—multiple tools working together rather than a single model—to gather information and produce outputs used in layoff selection. While companies often describe these systems as decision-support tools, the plaintiffs’ complaint suggests something more consequential: that the AI-influenced scoring was treated as a meaningful signal in determining who would be dismissed, and that the system’s logic did not adequately exclude or neutralize the impact of protected leave.
What makes the allegations particularly significant is the specific harm the plaintiffs say they experienced. They contend that the scoring used for layoff decisions did not merely ignore protected leave—it allegedly penalized employees for taking it. In other words, the complaint describes an outcome where leave periods were not treated as context that should adjust evaluation, but as missing or reduced performance evidence that the system interpreted negatively. The plaintiffs argue that this created a feedback loop: employees who were absent due to circumstances covered by employment protections were scored in a way that made them more likely to be selected for layoffs.
This is not the first time AI has been scrutinized in workplace settings, but it is one of the sharper examples of how automated systems can collide with legal and ethical obligations. Layoffs are already among the most sensitive and high-stakes decisions an employer can make. When AI enters the picture—especially when it influences rankings, prioritization, or “signals” used by human decision-makers—the question becomes less about whether AI was used at all and more about how it was configured, governed, and audited. The plaintiffs’ argument implies that Meta’s approach may have lacked the safeguards needed to prevent protected status or protected behavior (like taking leave) from being indirectly transformed into a negative metric.
To understand why this matters, it helps to look at how performance data typically works in large organizations. Performance evaluations are rarely based on a single number; they are usually built from multiple sources: project outcomes, manager assessments, peer feedback, productivity indicators, and sometimes behavioral or operational signals. When employees take leave, many of those inputs naturally change. A person on parental leave may not be delivering work during that period. Someone on medical leave may have reduced capacity or may be temporarily unavailable. In a fair evaluation system, those changes should trigger adjustments—either by excluding the leave period from certain calculations, normalizing results, or explicitly marking the employee’s status so that the absence of output does not translate into lower performance scores.
The plaintiffs allege that Meta’s AI-driven scoring did not do that. Instead, they claim the system failed to account for protected leave when producing rankings. That failure, according to the complaint, meant that employees on leave were disproportionately selected for layoff based on scoring that allegedly did not incorporate the legal and practical reality of their absence. The complaint’s framing suggests that the system’s logic treated protected leave as a factor that reduced an employee’s apparent performance, rather than as a circumstance requiring correction.
There is also a broader issue embedded in the allegations: the opacity of “constellations” of internal tools. Many organizations use multiple models and systems for different tasks—data collection, classification, prediction, summarization, risk scoring, and more. Even if each individual tool seems reasonable in isolation, the combined effect can be unpredictable. A constellation can amplify biases or create new ones when outputs from one system become inputs to another. If one component fails to recognize leave status, downstream components may interpret the resulting data gaps as performance deficits. If another component weights certain signals more heavily, the impact of missing data can become even more pronounced.
In the plaintiffs’ view, Meta’s constellation produced a ranking system that did not properly exclude protected leave. That allegation raises a governance question: what did Meta do to ensure that protected leave was recognized across every stage of the pipeline? Did the system have a reliable way to identify leave status? Were leave periods excluded from performance calculations? Were employees flagged so that their scores were adjusted or held harmless? And crucially, were those safeguards tested under real-world conditions—especially in the context of layoffs, where the stakes are immediate and the margin for error is low?
The lawsuit also highlights a tension that has become increasingly common in AI governance debates: the difference between “using AI” and “being responsible for AI outcomes.” Companies often argue that AI tools are advisory, that humans make final decisions, or that the system is only one input among many. But plaintiffs are essentially asking the court to consider whether the AI outputs were influential enough to matter—and whether the company took adequate steps to prevent foreseeable harm. If an AI-influenced ranking systematically disadvantages employees on protected leave, then the company’s responsibility may extend beyond the final click of a human decision-maker.
This case arrives at a moment when employers across industries are experimenting with AI for HR and talent management. AI can be used for recruiting, scheduling, performance analytics, employee engagement analysis, and workforce planning. In theory, these tools can reduce manual bias and improve consistency. In practice, they can also introduce new forms of bias—especially when training data reflects historical patterns or when the system is not designed to handle exceptions like medical incapacity or parental caregiving. Even when the AI is not “biased” in the traditional sense, it can still produce discriminatory effects through proxies. For example, if the system uses productivity metrics that naturally decline during leave, then leave becomes a proxy for lower performance—even though the lower performance is not a reflection of capability.
The plaintiffs’ allegations suggest that Meta’s system may have fallen into exactly that trap. Protected leave is not a performance problem; it is a protected life event. Yet if the scoring system treats absence as a deficit without adjustment, it can convert a protected event into a negative employment signal. That is why the complaint’s emphasis on “penalizing” employees for exercising their rights is central. It frames the harm not as an accidental mismatch between data and context, but as a predictable outcome of a system that did not incorporate the necessary protections.
Another important dimension is the timing and context of layoffs. Layoffs are often conducted quickly, with intense pressure to meet business goals. That urgency can compress the time available for careful review and can increase reliance on automated tools. If AI systems are used to generate lists or rankings, the speed of the process can make it harder to catch edge cases—like employees on leave—unless the system is designed to surface those cases clearly. The plaintiffs’ claims imply that such safeguards were either missing or insufficient.
The lawsuit also invites scrutiny of how companies validate AI systems in high-stakes contexts. In lower-stakes applications, errors might be tolerable or reversible. In layoffs, errors can permanently affect livelihoods. That means validation should include not only accuracy metrics but also fairness and compliance checks. It should test whether the system behaves differently for employees with protected characteristics or protected statuses. It should also examine whether the system’s outputs remain stable when employees are absent for legitimate reasons. If the system cannot handle those scenarios, it should not be used—or it should be used only with strong guardrails.
Meta, like other large employers, has likely faced increasing pressure to demonstrate that its AI tools are governed responsibly. The company has invested heavily in AI research and deployment across its products and internal operations. But internal HR use is a different domain than consumer-facing AI. HR decisions are governed by employment law, anti-discrimination rules, and contractual obligations. They also involve human dignity and economic security. That means the bar for fairness and transparency is higher, and the consequences of failure are more severe.
While the lawsuit alleges wrongdoing, it is also important to note what is not yet established. Allegations in a complaint are claims, not findings. Meta will have the opportunity to respond, and the court will determine what evidence supports the plaintiffs’ narrative. Still, the specificity of the allegations—particularly the claim that protected leave was not excluded from scoring—suggests the plaintiffs believe they have concrete documentation or internal records supporting their position. The fact that the complaint references a constellation of AI tools indicates the plaintiffs are not making a vague accusation that “AI was involved,” but rather pointing to a particular mechanism they say produced a discriminatory outcome.
For employees and HR professionals watching this case, the practical takeaway is not simply “AI is bad.” It is that AI systems used in employment decisions must be engineered for the realities of human life and legal protections. That includes designing data pipelines that recognize leave status, ensuring that performance metrics are normalized appropriately, and building audit trails that allow investigators to trace how outputs were generated. It also includes training decision-makers—both human and automated—on what counts as protected leave and how it should affect evaluation.
There is also a cultural takeaway. Many organizations treat performance evaluation as a continuous measurement of contribution. But contribution is not always linear, and caregiving and medical events are not deviations from work ethic—they are part of life. A fair system must reflect that. If AI is used to measure performance without accounting for protected absences, it risks encoding a narrow definition of “availability” as “value.” That is precisely the kind of proxy discrimination that fairness frameworks try to prevent.
The lawsuit may also influence how regulators and courts think about AI in employment. In many jurisdictions, discrimination law focuses on outcomes and effects, not just intent. Even if an employer did not intend to discriminate, a system that produces disproportionate harm to protected groups can still raise legal issues. The plaintiffs’ claim that employees on