# AI-driven layoffs: without cause or redundancy in U.S. employment law[^about] How U.S. law treats AI-driven layoffs, including without-cause termination, redundancy, WARN Act notice, severance, and non-compete effects. ## Is an AI-driven layoff without cause or redundancy under U.S. law? {#ai-layoff-without-cause-or-redundancy} **Short answer.** Usually, an AI-eliminated U.S. role is analyzed as a layoff, reduction in force, position elimination, or termination without cause rather than a separate redundancy category. [^squire-patton-boggs-global-guide-on-redundancies][^us-courts-akridge-v-alfa-ins-companies-alnd-5-22] The first point is negative but important: U.S. law does not give `redundancy` the kind of standalone statutory status it has in the U.K., Canada, or parts of Europe. The source reports are consistent that, in the U.S., the legal work is done by the at-will baseline, by contract, by RIF doctrine, by WARN, and by state restrictive-covenant rules. That is why the more accurate U.S. question is usually not whether an AI-driven exit is `redundancy` in the abstract, but whether it is a no-fault position elimination or a `for cause` separation under the actual agreement. [^squire-patton-boggs-global-guide-on-redundancies][^baker-mckenzie-cutting-costs-without-cutting-cor] The best case in the source set for the basic classification point is *Akridge v. Alfa Ins. Companies*, 93 F.4th 1181 (11th Cir. 2024). Both research runs cite *Akridge* for the proposition that software automation of an employee's duties can supply a legitimate, non-discriminatory business reason for eliminating the position. [^us-courts-akridge-v-alfa-ins-companies-alnd-5-22] That is not the same thing as saying every AI-driven exit is automatically lawful. It is narrower. But it does support the underlying classification instinct: when the work is gone because the function has been automated, the legal frame looks more like role elimination than employee fault. [^us-courts-akridge-v-alfa-ins-companies-alnd-5-22] The broad consensus from firms is narrower than the hype around AI. They are not saying AI creates a new employment-law category. They are saying the old categories still control, and AI changes which side of the line employers try to land on. Squire Patton Boggs states the point most plainly. Its global redundancy guide says: "There are no specific rules about redundancy. It is likely a dismissal on grounds of redundancy would be considered a dismissal without cause."[^squire-patton-boggs-global-guide-on-redundancies] That is probably the cleanest single sentence in the source set on the U.S. position. [^squire-patton-boggs-global-guide-on-redundancies] Baker McKenzie is aligned on the basic frame but adds the contractual consequences. Its RIF guidance treats a workforce reduction as something that can be executed through several mechanisms, including `performance-based terminations` and `redundancy-based layoffs`, and it emphasizes that executive compensation, severance, and equity rights often improve on a `termination without cause`. [^baker-mckenzie-cutting-costs-without-cutting-cor] That is the key commercial reality. The label is not semantic. It allocates money. ## Can AI-driven layoffs trigger WARN Act notice requirements? {#ai-layoffs-warn-act-notice} **Short answer.** Yes, AI can be the business reason for a large workforce reduction, but the WARN Act analysis still turns on employment loss counts and site-level thresholds. [^polsinelli-warn-ings-may-be-required-before-a-ri][^law-and-the-workplace-congress-proposes-major-ov] At scale, WARN overlays that baseline. Both source reports describe the federal WARN Act, 29 U.S.C. Section 2100 et seq., as attaching when enough employees suffer an employment loss at one site. The point for this article is not the mechanics of WARN notices. It is that AI does not create a separate mass-termination bucket. If enough roles disappear because the business automated them away, the event still looks like a `mass layoff` or related WARN event, not like a new AI-specific category. [^polsinelli-warn-ings-may-be-required-before-a-ri][^law-and-the-workplace-congress-proposes-major-ov] And the scale question does not go away just because the reason is AI. If automation eliminates enough roles at one site, the issue stops being individual classification and starts looking like classic WARN analysis. That is one reason the `we are not laying people off, we are just modernizing the workflow` line may not carry much weight when the headcount effect is large enough to count. [^polsinelli-warn-ings-may-be-required-before-a-ri][^law-and-the-workplace-congress-proposes-major-ov] ## Which state non-compete rules matter after an AI-driven layoff? {#state-non-compete-rules-ai-layoff} **Short answer.** Often the layoff label weakens non-compete enforcement, especially in states that condition enforceability on cause, layoff status, or continued compensation. [^massachusetts-general-laws-c-149-section-24l][^hunton-andrews-kurth-new-virginia-non-compete-re][^jackson-lewis-washington-s-recently-amended-non] The sharpest statutory consequences appear in restrictive-covenant law. Massachusetts is the clearest because the statute says so directly. The Massachusetts Noncompetition Agreement Act provides that a noncompetition agreement shall not be enforceable against ... employees that have been terminated without cause or laid off. [^massachusetts-general-laws-c-149-section-24l][^mass-gov-massachusetts-law-about-noncompetition] Virginia moves in the same direction starting July 1, 2026. Both source reports describe Senate Bill 170, codified at Va. Code Section 40.1-28.7:8, as making new or renewed non-competes unenforceable after a without-cause discharge unless the agreement was paired with disclosed severance or other payment. [^hunton-andrews-kurth-new-virginia-non-compete-re][^baker-donelson-virginia-tightens-the-screws-on-n][^troutman-pepper-locke-virginia-enacts-new-restri] Washington follows a different structure but lands in a similar place: a laid-off employee's non-compete generally requires continuing compensation through the restraint period. [^jackson-lewis-washington-s-recently-amended-non] New York is less statutory in the source set and more common-law. Both reports point to the older mutuality line, and both cite *Kliger v. Fairmont Ins. Brokers LLC*, a 2026 New York state-court decision, as recent support for the idea that employer-initiated no-fault termination weakens the case for enforcement. [^new-york-state-courts-kliger-v-fairmont-ins-brok][^underberg-kessler-non-compete-agreements-face-an] We think the right way to read that is modestly. New York is not a clean statutory analogue to Massachusetts. But it does mean the no-fault versus fault distinction can still matter even where the statute books are quieter. On restrictive covenants, the firms are unusually consistent. Hunton Andrews Kurth, Baker Donelson, and Troutman Pepper Locke all describe Virginia's new rule as hostile to post-employment restraints after without-cause terminations. Jackson Lewis does the same for Washington's compensation requirement after layoffs. Massachusetts is even less ambiguous because the operative text sits in the statute itself. [^hunton-andrews-kurth-new-virginia-non-compete-re][^baker-donelson-virginia-tightens-the-screws-on-n][^troutman-pepper-locke-virginia-enacts-new-restri][^jackson-lewis-washington-s-recently-amended-non][^massachusetts-general-laws-c-149-section-24l] That means the label affects leverage more than it affects taxonomy. If the separation is acknowledged as a no-fault role elimination, severance eligibility usually gets stronger and covenant enforcement usually gets weaker. Massachusetts makes that explicit. Virginia does so for newer agreements starting July 1, 2026. Washington does it by requiring pay if the employer still wants the restraint after a layoff. New York, at least on the sources here, remains more case-driven, but the no-fault versus fault distinction still matters. [^massachusetts-general-laws-c-149-section-24l][^hunton-andrews-kurth-new-virginia-non-compete-re][^jackson-lewis-washington-s-recently-amended-non][^new-york-state-courts-kliger-v-fairmont-ins-brok] Massachusetts is straightforward. Virginia and Washington are getting clearer. New York is still more doctrinal than mechanical. The result is that the same AI-driven layoff can weaken post-employment restraints decisively in one state and only argumentatively in another. [^massachusetts-general-laws-c-149-section-24l][^hunton-andrews-kurth-new-virginia-non-compete-re][^jackson-lewis-washington-s-recently-amended-non][^new-york-state-courts-kliger-v-fairmont-ins-brok] ## Does contract language decide severance for an AI-driven layoff? {#contract-language-ai-layoff-severance} **Short answer.** Yes, severance usually turns on whether the governing plan treats the exit as a RIF, position elimination, or other non-misconduct separation rather than cause. [^proskauer-managing-change-reductions-in-force-ti][^trucker-huss-why-employers-should-embrace-erisa][^at-t-corp-severance-plan-sec-filing] Severance turns on the same classification problem from the other direction. The source reports treat ERISA-governed severance plans as routinely distinguishing between RIF or without-cause exits, which qualify, and cause terminations, which do not. [^proskauer-managing-change-reductions-in-force-ti][^trucker-huss-why-employers-should-embrace-erisa][^at-t-corp-severance-plan-sec-filing] That is why the label matters so much in practice. The same event can look like routine business restructuring to the board and like a severance-triggering `without cause` event to the plan administrator. The practical consequence is that `redundancy` is often not a U.S. legal answer. It is a shorthand. The real answer lives in the contract language. Companies that use the word `redundancy` internally but draft severance plans around `reduction in force`, `position elimination`, `layoff`, or `termination without cause` will still end up inside those older categories. Companies that draft around `cause` versus `without cause` will end up litigating the boundaries of those terms instead. [^squire-patton-boggs-global-guide-on-redundancies-2][^proskauer-managing-change-reductions-in-force-ti][^trucker-huss-why-employers-should-embrace-erisa] The third consequence is that plan design can make the fight smaller than the rhetoric suggests. Some employers already draft severance plans broadly enough that most employer-initiated non-misconduct exits are covered. In those systems, the classification debate matters more for restrictive covenants than for cash. In other systems, especially executive contracts or narrow ERISA plans, the entire economics of the departure can turn on whether the company can sustain `cause`. [^trucker-huss-why-employers-should-embrace-erisa][^at-t-corp-severance-plan-sec-filing] Both research runs surface the same edge case: agreements that speak directly to technological displacement, or severance plans that treat most non-misconduct exits the same, can make the classification fight much smaller. Those clauses still appear to be unusual rather than standard. But where they exist, they matter more than any abstract debate about whether AI is special. [^at-t-corp-severance-plan-sec-filing][^trucker-huss-why-employers-should-embrace-erisa] ## When does failure to adapt to AI become cause for termination? {#failure-to-adapt-to-ai-cause} **Short answer.** The source set does not show a clean U.S. rule making failure to adapt to AI, by itself, cause for termination under narrow severance or covenant language. [^baker-mckenzie-cutting-costs-without-cutting-cor-2][^polsinelli-warn-ings-may-be-required-before-a-ri-2] The second consequence is that AI makes the `for cause` story more tempting. Once a company says the job has changed rather than disappeared, it can argue the employee did not meet the new standard. That is economically attractive because it can shrink severance exposure and preserve restraints. But the argument is only as good as the agreement and the record. Narrow cause definitions usually point to misconduct, dishonesty, felony conduct, or serious performance failure after process. A role that was substantially automated away still looks, perhaps more often than not, like a business restructuring dressed in newer language. [^baker-mckenzie-cutting-costs-without-cutting-cor-2][^polsinelli-warn-ings-may-be-required-before-a-ri-2] The source set repeatedly describes this as an issue of first impression. The employer-side argument is that the role changed, AI use became part of the job, and the employee failed to perform. The employee-side argument is that the role was mostly automated away and the performance frame is just a severance-avoidance device. No case in the source set resolves that directly. [^baker-mckenzie-cutting-costs-without-cutting-cor-2][^polsinelli-warn-ings-may-be-required-before-a-ri-2] ## Will courts treat AI layoff cause narratives as pretext? {#ai-layoff-cause-narrative-pretext} **Short answer.** That remains unsettled, but AI records can increase litigation pressure if they suggest the cause story was created after an economic decision was already made. [^polsinelli-warn-ings-may-be-required-before-a-ri-3][^mayer-brown-ai-as-star-witness-how-a-buyer-s-ai] Polsinelli's commentary shows where the litigation pressure comes from. Its warning is not really about AI specifically. It is about RIF pretext. The firm says litigation can arise when employees argue the `RIF was actually a pretext for discrimination`, and it recommends a written business-justification record. [^polsinelli-warn-ings-may-be-required-before-a-ri-3] Read against the AI question, that means this: the more an employer wants the economic upside of calling the exit `cause`, the more it invites a fight over whether the job really disappeared for business reasons. The most interesting outlier in the source set is Mayer Brown's writeup of *Fortis Advisors, LLC v. Krafton, Inc.* It is not an employment case. It is an earnout case. But the firm's point is still relevant here: if decision-makers use an AI system to backfill a `cause` narrative after the real decision has already been made, the logs can become evidence of pretext. [^mayer-brown-ai-as-star-witness-how-a-buyer-s-ai] That does not answer the AI-layoff classification question by itself. It does show why firms are more worried about post hoc relabeling than about AI creating entirely new doctrine. The employment-law answer is not yet in the source set. But the general pattern is visible. Polsinelli worries about RIF pretext. Mayer Brown's reading of *Fortis* shows courts taking a hard look at decision-maker intent where `cause` is used to avoid an economic obligation. Perhaps employment cases will borrow some of that skepticism as AI-driven exits become more common. [^polsinelli-warn-ings-may-be-required-before-a-ri-3][^mayer-brown-ai-as-star-witness-how-a-buyer-s-ai] [^about]: By Steven Obiajulu, J.D. Published by [openagreements.org](https://openagreements.org). Last reviewed 2026-04-19. License: CC BY 4.0. Steven Obiajulu, J.D. edits this topic article for Federal + multi-state coverage. It synthesizes legal sources and is not legal advice. This article is for informational purposes only and does not create an attorney-client relationship. [^squire-patton-boggs-global-guide-on-redundancies]: **Squire Patton Boggs commentary** — "There are no specific rules about redundancy. It is likely a dismissal on grounds of redundancy would be considered a dismissal without cause." *Squire Patton Boggs, Global Guide on Redundancies.* [^us-courts-akridge-v-alfa-ins-companies-alnd-5-22]: **US Courts, Akridge v. Alfa Ins. Companies (ALND 5:22-cv-01350)** — "‘Section 1981 provides a cause of action for individuals subjected to discrimination by private actors and discrimination under color of state law, but does not provide a cause of action for discrimination under color of federal law.’" *US Courts, Akridge v. Alfa Ins. Companies (ALND 5:22-cv-01350).* [^baker-mckenzie-cutting-costs-without-cutting-cor]: **Baker McKenzie commentary** — "Employment protections vary widely around the world. While at-will employment in the United States allows for relatively straightforward terminations (barring union involvement or statutory notice requirements), most jurisdictions around the world (including the majority of Europe, as well as Canada, Australia and Japan) provide mandatory protections against dismissal" *Baker McKenzie, Cutting Costs Without Cutting Corners: 10 Practical Tips for Managing Legal Risk in Global Reductions in Force.* [^polsinelli-warn-ings-may-be-required-before-a-ri]: **Polsinelli commentary** — "Virginia’s PFML program differs from its federal counterpart in who is covered, which relationships and reasons qualify, how benefits are funded, and when job-restoration rights attach." *Polsinelli, WARN-ings May Be Required Before a RIF or Shut Down.* [^law-and-the-workplace-congress-proposes-major-ov]: **Law and the Workplace, Congress Proposes Major Overhaul of WARN: What Employers Need to Know About the Fair Warning Act** — "House Democrats have introduced the Fair Warning Act (H.R. 5761), which would significantly rewrite federal WARN for the first time since 1988." *Law and the Workplace, Congress Proposes Major Overhaul of WARN: What Employers Need to Know About the Fair Warning Act.* [^massachusetts-general-laws-c-149-section-24l]: **Massachusetts General Laws c. 149, Section 24L** — "To be valid and enforceable, a noncompetition agreement must meet the minimum requirements of paragraphs (i) through (viii)." *Massachusetts General Laws c. 149, Section 24L.* [^hunton-andrews-kurth-new-virginia-non-compete-re]: **Hunton Andrews Kurth commentary** — "Under SB170, if an employee with a non‑compete is fired ‘without cause,’ then the non‑compete is unenforceable unless the employer provides ‘severance benefits or other monetary payment,’ which must be ‘disclosed upon execution’ of the agreement." *Hunton Andrews Kurth, New Virginia Non-Compete Restrictions Become Law.* [^jackson-lewis-washington-s-recently-amended-non]: **Jackson Lewis commentary** — "Effective June 30, 2027, all non-competition agreements will become void and unenforceable." *Jackson Lewis, Washington's Recently Amended Non-Competition Restrictions Render Past or Existing Covenants Unenforceable.* [^mass-gov-massachusetts-law-about-noncompetition]: **Mass.gov, Massachusetts law about noncompetition agreements** — "A covenant not to compete contained in a contract for personal services will be enforced if it is reasonable, based on all the circumstances." *Mass.gov, Massachusetts law about noncompetition agreements.* [^baker-donelson-virginia-tightens-the-screws-on-n]: **Baker Donelson commentary** — "the Bill amends Virginia's non‑compete statute, Virginia Code § 40.1‑28.7:8, to provide that a non‑compete agreement is unenforceable against any employee who is discharged without cause and does not receive severance benefits or other monetary payments." *Baker Donelson, Virginia Tightens the Screws on Non-Competes Again.* [^troutman-pepper-locke-virginia-enacts-new-restri]: **Troutman Pepper Locke commentary** — "The bill prohibits enforcement of all covenants not to compete that are entered into, amended, or renewed on or after July 1, 2026, if the employer terminates the employee’s employment without cause and does not provide severance benefits or other monetary payment to the employee." *Troutman Pepper Locke, Virginia Enacts New Restrictions on the Use of Noncompetes.* [^new-york-state-courts-kliger-v-fairmont-ins-brok]: **New York State Courts, Kliger v. Fairmont Ins. Brokers LLC** — "Courts regularly ‘blue pencil’ non-solicitation restrictive covenants so that they only enjoin [a] former employee's solicitations of clients for whom the employee serviced" *New York State Courts, Kliger v. Fairmont Ins. Brokers LLC.* [^underberg-kessler-non-compete-agreements-face-an]: **Underberg & Kessler, Non-Compete Agreements Face an Uncertain Future in New York** — "New York courts have narrowed the enforceability of non-compete agreements over the years – most notably in BDO Seidman v. Hirshberg – but they are still widely utilized." *Underberg & Kessler, Non-Compete Agreements Face an Uncertain Future in New York.* [^proskauer-managing-change-reductions-in-force-ti]: **Proskauer commentary** — "Many severance pay plans, whether voluntary or involuntary, written or unwritten, will be subject to the Employee Retirement Income Security Act of 1974 (‘ERISA’)." *Proskauer, Managing Change/Reductions in Force Tip of the Month.* [^trucker-huss-why-employers-should-embrace-erisa]: **Trucker Huss commentary** — "the administration of the arrangement must require ‘an ongoing administrative program to meet the employer’s obligation.’" *Trucker Huss, Why Employers Should Embrace ERISA Coverage of Their Severance Plans.* [^at-t-corp-severance-plan-sec-filing]: **AT&T Corp. Severance Plan SEC Filing** — "AT&T Inc. (‘AT&T,’ ‘we’ or the ‘Company’) is a holding company incorporated under the laws of the State of Delaware in 1983" *AT&T Corp. Severance Plan SEC Filing.* [^squire-patton-boggs-global-guide-on-redundancies-2]: **Squire Patton Boggs commentary** — "There are no specific rules about redundancy. It is likely a dismissal on grounds of redundancy would be considered a dismissal without cause." *Squire Patton Boggs, Global Guide on Redundancies.* [^baker-mckenzie-cutting-costs-without-cutting-cor-2]: **Baker McKenzie commentary** — "Employment protections vary widely around the world. While at-will employment in the United States allows for relatively straightforward terminations (barring union involvement or statutory notice requirements), most jurisdictions around the world (including the majority of Europe, as well as Canada, Australia and Japan) provide mandatory protections against dismissal" *Baker McKenzie, Cutting Costs Without Cutting Corners: 10 Practical Tips for Managing Legal Risk in Global Reductions in Force.* [^polsinelli-warn-ings-may-be-required-before-a-ri-2]: **Polsinelli commentary** — "Virginia’s PFML program differs from its federal counterpart in who is covered, which relationships and reasons qualify, how benefits are funded, and when job-restoration rights attach." *Polsinelli, WARN-ings May Be Required Before a RIF or Shut Down.* [^polsinelli-warn-ings-may-be-required-before-a-ri-3]: **Polsinelli commentary** — "Virginia’s PFML program differs from its federal counterpart in who is covered, which relationships and reasons qualify, how benefits are funded, and when job-restoration rights attach." *Polsinelli, WARN-ings May Be Required Before a RIF or Shut Down.* [^mayer-brown-ai-as-star-witness-how-a-buyer-s-ai]: **Mayer Brown commentary** — "communications with AI platforms may not be privileged, may be subject to discovery, and may be used against the party that generated them." *Mayer Brown, AI as Star Witness: How a Buyer's AI Conversations Sank Its Earnout Avoidance Strategy.*