What happens if an employer misses WARN notice?

Under the federal Act, employees can recover back pay and benefits for each day of missed notice, up to 60 days, plus civil penalties for failure to notify the local government unit — and several state statutes add their own remedies on top (New Jersey's amended law, notably, mandates severance). Missed notice is also a reputational event: WARN filings are public and tracked by the press.

Do remote employees count, and where?

This is one of the least settled questions in WARN practice. The federal Act counts workers at, or assigned to, a "single site of employment," a concept written before distributed work; agencies and courts have taken differing views on how remote employees aggregate. Treat any layoff touching a substantially remote population as a flag for counsel, not a spreadsheet judgment.

Do voluntary departures and transfers count toward thresholds?

Generally no — employment losses exclude voluntary departures, retirements, and discharges for cause, and certain transfers or reassignment offers within commuting distance can also fall outside the count. But the aggregation rules (including the 90-day look-back/look-forward) are technical, and characterizing a departure as "voluntary" has been litigated. Count conservatively; confirm with counsel.

Defensible restructuring

WARN, jurisdiction by jurisdiction: a working guide for restructuring teams

OrgTool Learn · 9 min read · Updated July 2026

FOR INFORMATIONAL AND EDUCATIONAL PURPOSES ONLY. NOT LEGAL ADVICE. Statutes and case law change — verify current requirements with qualified employment counsel before acting.

The WARN Act is where restructuring plans meet a stopwatch. The federal Worker Adjustment and Retraining Notification Act (1988) requires covered employers to give written notice — to affected workers, their representatives, the state dislocated-worker unit, and local government — before certain closings and layoffs take effect. Get the analysis wrong and the cost isn't just legal exposure; it's a public filing, back-pay liability, and a timeline the whole transaction now bends around.

The federal baseline

Covered employers: generally those with 100 or more full-time employees.
Notice period: 60 calendar days before the employment action.
Plant closing: a shutdown of a single site (or facilities/operating units within it) causing employment loss for 50 or more full-time employees.
Mass layoff: at a single site, an employment loss for 500+ full-time employees — or for 50–499 where they make up at least 33% of the active full-time workforce at that site.
Aggregation: separate actions at one site within any 90-day window are combined unless the employer shows they arise from separate and distinct causes — the rule that catches "rolling" layoffs sized to slip under thresholds.

The statute recognizes narrow exceptions — the faltering company (for closings), unforeseeable business circumstances, and natural disasters — each of which reduces, but does not eliminate, the notice obligation, and each of which is construed narrowly. Planning a RIF around an exception is planning to litigate it.

The unit of analysis is the establishment

Everything in WARN turns on the single site of employment — thresholds are evaluated per establishment, not per company. A 400-person reduction spread across eight sites can trigger nothing; 60 people at one site can trigger everything. This is why WARN analysis belongs inside the scenario model rather than after it: as a selection shifts between locations, threshold status flips site by site, and the plan's legal geometry changes with every edit.

Why the states change the answer

Roughly half the states layer their own "mini-WARN" statutes on top of the federal floor, and the material ones differ on every parameter that matters — who is covered, what counts as a triggering event, how much notice is owed, and what the remedy is. Four stand out for restructuring practice:

California — broader coverage than federal (the state act reaches smaller establishments and more event types), with fewer of the federal escape hatches. Cal-WARN has repeatedly been read more protectively than its federal counterpart.
New York — a longer notice period (90 days) and lower employee-count triggers than the federal Act.
New Jersey — the strictest of the group since its 2023 amendments: 90 days' notice and mandatory severance for covered mass layoffs, a genuine cost term, not just a timing term.
Illinois — its own thresholds below the federal ones, catching actions federal WARN would miss.

The professional habit this demands: never analyze "WARN" in the singular. A multi-state selection has to be evaluated against each applicable statute per establishment — and the honest tooling posture is to be explicit about which jurisdictions are evaluated and which are not. (OrgTool's restructuring workbench, for instance, evaluates federal, California, New York, New Jersey, and Illinois rulepacks, and says exactly that rather than implying fifty-state coverage.)

Sequencing WARN inside the plan

Because notice runs 60–90 days ahead of separation, WARN is a scheduling constraint on the whole restructuring program: announcement dates, system cutovers, severance budgets, and communications all key off it. The mature sequence is: model the selection → evaluate thresholds per site per statute → let the notice clock set the timeline → paper the record. Teams that discover a threshold late don't just add legal risk — they add two to three months to a plan the board thought was closing this quarter.

Key takeaways

Federal floor: 100+ employee employers, 60 days' notice, 50+/site closings, 500+ (or 50–499 & ≥33%) mass layoffs, 90-day aggregation.
The establishment, not the company, is the unit of analysis — thresholds flip as selections move between sites.
State mini-WARNs (CA, NY, NJ, IL among the most material) change notice, thresholds, and — in NJ — add mandated severance.
Exceptions exist and are narrow; treat them as litigation positions, not plans.
Evaluate WARN live inside the scenario, and let the notice clock drive the program timeline.