DEV Community

Layoff Atlas
Layoff Atlas

Posted on Originally published at layoffatlas.com

Quiet Layoffs and the WARN Act: When Job Cuts Are Dressed Up as Performance Firings

A "quiet layoff" is a job cut that is not announced as one. Instead of a layoff notice naming dozens of affected workers, employees are let go one by one, often with individual performance reasons attached: a sudden poor review, a short performance improvement plan, a termination for "not meeting expectations." Each departure looks individual. Together, they can amount to the same thing as a layoff — minus the advance notice.

Whether the WARN Act applies does not turn on what the employer calls the departures. It turns on what actually happened: how many workers lost their jobs, over what period, and whether those losses count as "employment losses" under the law.

What the WARN Act actually counts

The federal WARN Act requires covered employers to give 60 days' written notice before a plant closing or a mass layoff. A covered employer generally has 100 or more full-time employees. A plant closing affecting 50 or more workers triggers notice, as does a mass layoff of 500 or more workers, or of 50 to 499 workers if they make up at least one-third of the workforce at a single site.

The key term is "employment loss," which covers a termination other than a discharge for cause, voluntary departure, or retirement; a layoff exceeding six months; or a reduction in hours of more than 50 percent in each month of a six-month period. That exclusion for discharges "for cause" is where the quiet-layoff question lives: a genuine termination for misconduct or documented poor performance is not an employment loss, but a layoff relabeled as one may still be.

Why the label does not decide it

An employer cannot avoid the WARN Act simply by writing "performance" on the paperwork. If a group of workers is being cut because positions are being eliminated or a unit is being restructured, the substance matters more than the label. The pattern is what counts: were the "performance" cases concentrated in one team, one site, or one short period? Did reviews change suddenly after years of satisfactory ratings? Were departing workers replaced, or did their roles disappear?

Timing matters too. The Act's 90-day aggregation rule lets layoffs split into smaller groups within a 90-day window be combined if they were not the result of separate and distinct causes. Staggering departures a few at a time does not automatically keep each group below the threshold.

Signs a round of departures may be a quiet layoff

No single sign proves anything, but several together matter:

  • Performance reviews turn negative across a whole team at once, especially after years of satisfactory ratings.
  • Workers are placed on short improvement plans in the same weeks, with similar language.
  • Departures cluster around a restructuring or downsizing that was never framed as a layoff.
  • Roles are eliminated rather than refilled, or the same work continues with contractors or at another location.
  • Severance offers arrive with a standard script and tight deadlines, though each case is presented as individual.

Any one of these can have an innocent explanation. A pattern across many workers is what separates an individual termination from a workforce reduction.

What workers can do

If you suspect your departure is part of a larger cut, document the pattern while you still can: the dates of reviews and terminations, who else left and when, what was said about the reasons, and whether the role was refilled. Keep copies of your reviews, improvement plans, and severance paperwork. If you are over 40 and offered severance for a release of claims, federal law generally gives you at least 21 days to consider it (45 days for a group termination) and seven days to revoke after signing.

If notice was owed and not given, the Act's remedy is generally back pay and benefits for each day of violation, up to 60 days, enforced through a lawsuit in federal court rather than a government complaint process. Workers in that situation often act together, since the claim turns on the group pattern. State mini-WARN laws in places like California, New York, New Jersey, and Illinois can add their own notice periods and remedies.

Why quiet layoffs distort the layoff data

Quiet layoffs are one reason WARN data undercounts actual job cuts. The registry only records notices that are filed and published. A workforce reduction never framed as a layoff produces no filing at all, so it never enters the count. Remember that when reading any WARN-based total: the figures describe reported plans, not confirmed job losses, and they miss the cuts employers never label as layoffs.

The filed notices still capture a great deal. As of the latest registry update on October 31, 2026, the 90-day window holds 686 notices covering 66,703 reported workers, with 29 worker counts unavailable. California (17,715 workers) and Washington (17,361) lead the state ranking, followed by Illinois (4,385), Texas (3,280), and Georgia (2,492). The heaviest upcoming week is November 14, with 8,453 workers scheduled, followed by November 21 (6,925) and November 28 (5,937).

If your job ends alongside many others, do not accept the label on your own paperwork as the final word. Count the departures around you, note the dates, and compare what happened with what the law counts. A layoff by another name is still a layoff.

Data source: Layoff Atlas

Top comments (0)