Does the WARN Act cover AI layoffs? It depends on headcount
The short answer
Yes, the WARN Act covers AI layoffs, because it never asks why the jobs went. It asks how many and where. If an employer with 100 or more employees cuts at least 33 per cent of the active workforce (and at least 50 people) at one site inside a 30-day window, or cuts 500 or more, it owes 60 days' written notice. If the AI cut is smaller than that, WARN is silent and the only rules that apply are the contract and state law.
What the act actually says
The Worker Adjustment and Retraining Notification Act is short. An employer with 100 or more employees, excluding part-timers, or 100 or more employees who together work at least 4,000 hours a week, must give at least 60 days' written notice before a plant closing or a mass layoff.
A mass layoff has a specific definition in the regulation: an employment loss at a single site of employment during any 30-day period for at least 33 per cent of the active employees, excluding part-time employees, and at least 50 employees. There is an alternative route: 500 or more employees at a single site, regardless of percentage.
Notice goes to the affected employees or their union, and to the state dislocated worker unit. It is not a negotiation and it is not a consultation. It is a deadline.
Why most AI layoffs never trigger it
Run the numbers on a typical AI restructuring and the reason becomes obvious. A 300-person site cutting 40 roles is at 13.3 per cent, below the 33 per cent floor, and under 50 people, below the headcount floor. No notice is owed beyond whatever the contract says.
The same is true of a 120-person site cutting 30. That is 25 per cent, still short. A 200-person site cutting 60 hits 30 per cent and 60 people, which clears the headcount floor but misses the percentage floor by a hair. Only when a company cuts a third of a site at once does the federal law bite.
This is why so many announcements read as "we are restructuring around AI" in increments. The increments are often below the line, and the aggregate is spread across months.
The 30-day window is not a loophole, but it is a trap
The regulation counts employment losses inside a 30-day period, and it also looks at 90-day periods where two or more groups of cuts each fall below the threshold but together would meet it. An employer that splits a single decision into two rounds six weeks apart to stay under 33 per cent is doing something the regulation was written to catch.
In practice, that means the question to ask is not "how many were cut in this round" but "how many were cut at this site in the last 90 days". If the answer crosses a third of the workforce, the notice obligation may have applied to the first round, not the second.
What a WARN notice has to contain
The notice is a statement of specifics: the name and address of the employment site, the name and phone number of a company official to contact, a statement of whether the action is permanent or temporary, the expected date of the first separation and the expected schedule, the job titles affected, and whether bumping rights exist.
That list matters for anyone trying to work out whether AI is the real cause. Bumping rights, job titles and the schedule are the details a company cannot easily fake, and they are the details a state publishes.
California adds the AI line from January 2027
California is the first state to write AI into this paperwork. Senate Bill 951, effective 1 January 2027, expands the information an employer must give when a Cal-WARN layoff is caused in whole or in substantial part by an AI system or other automated technology.
Cal-WARN itself is broader than the federal act: 60 days' notice, and it covers an establishment with 75 or more employees in the preceding 12 months. SB 951 does not change either number. What it changes is disclosure: from January, the notice has to say that automation is part of why the roles are going.
That is a small change with a long tail. A WARN notice is a public document. Once AI has to be named in it, the number of AI-attributed layoffs in California becomes countable, which is more than can be said for most of the United States today.
Two worked examples
Example one. A software company with 400 employees at one site announces that AI support tooling removes the need for 70 support roles. Seventy is 17.5 per cent of 400, so the percentage floor of 33 per cent is missed. It is above 50 people, but the regulation requires both conditions. No WARN notice.
Example two. The same company cuts 140 roles at that site over 30 days. That is 35 per cent and more than 50 people, so both conditions are met, and 60 days' written notice is owed to employees and to the state. If the company instead cuts 70 in March and 70 in June, the 90-day aggregation rule is the thing to test.
What to check if this happens to you
- Count the site, not the company. WARN works per single site of employment, so a national cut of 300 spread across ten offices may trigger nothing.
- Count the window. Thirty days for a single round, 90 days where rounds may be aggregated.
- Check the state list. Many states publish WARN notices, which give you the filed date, the site and the job titles.
- Read your contract. Below the WARN thresholds, notice is a contract term, and many contracts say less than people assume.
- Ask about bumping rights. If they exist, the selection of who goes is not final.
How this compares with the UK and the Philippines
The UK has a lower trigger than WARN and no percentage test. Where an employer proposes 20 or more redundancies at one establishment within 90 days, collective consultation must start 30 days before the first dismissal, or 45 days where 100 or more are proposed. Twenty people is a far easier number to reach than a third of a site, which is why UK cuts of this size are usually announced with a consultation period attached.
The Philippines is heading in the opposite direction from the US. Its existing redundancy rules give one month's notice to the labour department and one month's pay per year of service, and the bill filed on 8 November 2026 would raise that to six months' notice and two months' pay for AI-driven dismissals. Three systems, three different answers to the same question, and the US is the one that asks about headcount rather than cause.
Questions people ask
Does WARN apply if the layoff is because of AI?
Yes, if the numerical thresholds are met. The act does not consider the employer's reason.
How many employees must be affected?
At least 33 per cent of active employees at a single site and at least 50 people, inside 30 days. Alternatively, 500 or more employees at a single site.
How much notice?
At least 60 days, in writing, to affected employees or their union and to the state dislocated worker unit.
Is there redundancy pay under WARN?
No. WARN provides notice, not compensation. Any payment comes from a contract, a company policy or a state programme.
Does this change in 2027?
In California, yes. SB 951 takes effect on 1 January 2027 and requires employers to disclose when a covered layoff is caused in whole or in substantial part by AI or automation.