AI-driven layoffs: without cause or redundancy in U.S. employment law

Is an AI-driven layoff without cause or redundancy under U.S. law?

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.

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.

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. 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.

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.” That is probably the cleanest single sentence in the source set on the U.S. position.

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. That is the key commercial reality. The label is not semantic. It allocates money.

Sources for this answer

Law-firm commentary

A.1 Squire Patton Boggs commentaryPDF

Supports the cited proposition. (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.

See Squire Patton Boggs, Global Guide on Redundancies.

Case law

A.2 US Courts, Akridge v. Alfa Ins. Companies (ALND 5:22-cv-01350)PDF

Federal employees cannot maintain a claim under 42 U.S.C. § 1981 against federal agencies or officials, and Title VII requires that federal personnel actions be free from discrimination, meaning they must not be tainted by differential treatment based on a protected characteristic.

“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.”

See US Courts, Akridge v. Alfa Ins. Companies (ALND 5:22-cv-01350).

Law-firm commentary

A.3 Baker McKenzie commentary

Multinational employers must navigate diverse and complex local employment laws, including mandatory dismissal protections, procedural requirements for mass layoffs, and specific regulations regarding severance and releases, when implementing global workforce reductions.

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

See Baker McKenzie, Cutting Costs Without Cutting Corners: 10 Practical Tips for Managing Legal Risk in Global Reductions in Force.

Can AI-driven layoffs trigger WARN Act notice requirements?

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.

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.

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.

Sources for this answer

Law-firm commentary

B.1 Polsinelli commentary

Virginia's new Paid Family and Medical Leave (PFML) program establishes a state-administered leave framework that provides broader coverage, distinct job-restoration rights, and different qualifying criteria than the federal Family and Medical Leave Act (FMLA).

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.

See Polsinelli, WARN-ings May Be Required Before a RIF or Shut Down.

Commentary

B.2 Law and the Workplace, Congress Proposes Major Overhaul of WARN: What Employers Need to Know About the Fair Warning Act

The proposed Fair Warning Act (H.R. 5761) seeks to significantly amend the federal WARN Act by lowering coverage thresholds, extending notice periods, increasing employer liability, and restricting the use of pre-dispute arbitration and class action waivers.

House Democrats have introduced the Fair Warning Act (H.R. 5761), which would significantly rewrite federal WARN for the first time since 1988.

See Law and the Workplace, Congress Proposes Major Overhaul of WARN: What Employers Need to Know About the Fair Warning Act.

Which state non-compete rules matter after an AI-driven layoff?

Often the layoff label weakens non-compete enforcement, especially in states that condition enforceability on cause, layoff status, or continued compensation.

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. 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. 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.

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. 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.

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 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.

Sources for this answer

Primary law

C.1 Massachusetts General Laws c. 149, Section 24L

Massachusetts General Laws c. 149, Section 24L establishes the statutory requirements for the validity and enforceability of noncompetition agreements between employers and employees in Massachusetts.

To be valid and enforceable, a noncompetition agreement must meet the minimum requirements of paragraphs (i) through (viii).

See Massachusetts General Laws c. 149, Section 24L.

Primary law

C.4 Mass.gov, Massachusetts law about noncompetition agreements

Under Massachusetts law, restrictive covenants in employment contracts are enforceable in equity if they are reasonable in scope, necessary for the protection of the employer's legitimate business interests, and consistent with the public interest.

A covenant not to compete contained in a contract for personal services will be enforced if it is reasonable, based on all the circumstances.

See Mass.gov, Massachusetts law about noncompetition agreements.

Law-firm commentary

C.2 Hunton Andrews Kurth commentary

Recent Virginia legislation, including Senate Bills 170 and 240, imposes new restrictions on the enforceability of non-compete agreements for employees fired without cause and for retail franchisees, effective July 1, 2026.

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.

See Hunton Andrews Kurth, New Virginia Non-Compete Restrictions Become Law.

Commentary

C.5 Baker Donelson commentary

Proposed Virginia legislation would render non-compete agreements unenforceable against employees terminated without cause unless specific severance conditions are met and disclosed, while simultaneously expanding employer liability for attempted enforcement.

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.

See Baker Donelson, Virginia Tightens the Screws on Non-Competes Again.

Law-firm commentary

C.6 Troutman Pepper Locke commentary

Virginia's new legislation, SB 170 and HB 627, significantly expands restrictions on noncompete agreements by requiring severance for termination without cause, banning noncompetes for health care professionals, and prohibiting employee nonsolicitation covenants.

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.

See Troutman Pepper Locke, Virginia Enacts New Restrictions on the Use of Noncompetes.

Law-firm commentary

C.3 Jackson Lewis commentary

Washington state law will effectively ban all employment non-compete agreements as of June 30, 2027, regardless of when they were signed, and requires employers to notify employees that existing covenants are void.

Effective June 30, 2027, all non-competition agreements will become void and unenforceable.

See Jackson Lewis, Washington's Recently Amended Non-Competition Restrictions Render Past or Existing Covenants Unenforceable.

Case law

C.7 New York State Courts, Kliger v. Fairmont Ins. Brokers LLCPDF

Under New York law, restrictive covenants in employment contracts are enforceable only if they are reasonable in scope and duration, and courts may partially enforce or "blue pencil" overbroad covenants to protect an employer's legitimate business interests.

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

See New York State Courts, Kliger v. Fairmont Ins. Brokers LLC.

Commentary

C.8 Underberg & Kessler, Non-Compete Agreements Face an Uncertain Future in New York

While New York courts and the Governor have signaled potential future restrictions on non-compete agreements, the current legal landscape in New York remains governed by existing precedent following the veto of state-level legislation and the federal invalidation of the FTC's proposed nationwide ban.

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.

See Underberg & Kessler, Non-Compete Agreements Face an Uncertain Future in New York.

Does contract language decide severance for an AI-driven layoff?

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.

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. 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.

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.

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.

Sources for this answer

Law-firm commentary

D.1 Proskauer commentary

Employers may benefit from structuring severance pay arrangements to qualify as ERISA plans because ERISA preemption can limit exposure to state law claims, preclude punitive damages, and eliminate jury trials.

Many severance pay plans, whether voluntary or involuntary, written or unwritten, will be subject to the Employee Retirement Income Security Act of 1974 (“ERISA”).

See Proskauer, Managing Change/Reductions in Force Tip of the Month.

Commentary

D.2 Trucker Huss commentary

ERISA coverage for severance plans offers significant advantages to employers, including federal preemption of state law claims, the ability to utilize discretionary eligibility criteria, and the application of a deferential arbitrary and capricious standard of review for administrative decisions.

the administration of the arrangement must require “an ongoing administrative program to meet the employer’s obligation.”

See Trucker Huss, Why Employers Should Embrace ERISA Coverage of Their Severance Plans.

Commentary

D.3 AT&T Corp. Severance Plan SEC Filing

AT&T Inc. is a Delaware-incorporated holding company that operates as a major telecommunications provider in the United States, subject to SEC reporting requirements and FCC regulation.

AT&T Inc. (“AT&T,” “we” or the “Company”) is a holding company incorporated under the laws of the State of Delaware in 1983

See AT&T Corp. Severance Plan SEC Filing.

Law-firm commentary

D.4 Squire Patton Boggs commentaryPDF

Supports the cited proposition. (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.

See Squire Patton Boggs, Global Guide on Redundancies.

When does failure to adapt to AI become cause for termination?

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.

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.

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.

Sources for this answer

Law-firm commentary

E.1 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

See Baker McKenzie, Cutting Costs Without Cutting Corners: 10 Practical Tips for Managing Legal Risk in Global Reductions in Force.

Law-firm commentary

E.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.

See Polsinelli, WARN-ings May Be Required Before a RIF or Shut Down.

Will courts treat AI layoff cause narratives as pretext?

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'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. 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. 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.

Sources for this answer

Law-firm commentary

F.1 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.

See Polsinelli, WARN-ings May Be Required Before a RIF or Shut Down.

Law-firm commentary

F.2 Mayer Brown commentary

The Delaware Court of Chancery's decision in Fortis Advisors, LLC v. Krafton, Inc. highlights the risks of using AI in M&A strategy, the strict application of contractual termination and earnout provisions, and the court's willingness to grant equitable remedies like specific performance and earnout period extensions.

communications with AI platforms may not be privileged, may be subject to discovery, and may be used against the party that generated them.

See Mayer Brown, AI as Star Witness: How a Buyer's AI Conversations Sank Its Earnout Avoidance Strategy.