Guide · WARN Act
Understanding the WARN Act
What the federal WARN Act requires, who it covers, and what workers are entitled to when mass layoffs or plant closings occur.
The WARN Act requires 60 days' notice before a mass layoff of 50+ workers
The federal Worker Adjustment and Retraining Notification (WARN) Act requires employers with 100 or more employees to give 60 days' advance written notice before a mass layoff (generally 500+ workers, or 50+ when that is at least a third of the site) or plant closing. According to WARN Act filings submitted to state workforce agencies, October and January see the highest average layoff volume across the recorded history.
Understanding how to interpret WARN Act mass layoff tracking data requires context that raw numbers alone cannot provide. This guide breaks down the key concepts, common misconceptions, and practical steps for using this data effectively.
The short answer
The WARN Act forces most layoffs of 100+ workers into a public, dated 60-day filing, which is exactly why this dataset exists and why it is the earliest reliable signal of a mass layoff.
By the numbers
What the WARN record actually shows
- 8,798
- WARN notices tracked
- 1,411,142
- Workers on notice
- 6,943
- Employers filing
States with the most workers on WARN notice
Total workers listed on WARN notices, by state of filing, federal & state WARN-Act records
- Texas
Texas - 277,413 workers across 2,358 notices
277,413 workers
- Washington
Washington - 236,227 workers across 1,056 notices
236,227 workers
- California
California - 197,418 workers across 1,136 notices
197,418 workers
- Indiana
Indiana - 149,707 workers across 994 notices
149,707 workers
- Virginia
Virginia - 123,716 workers across 1,018 notices
123,716 workers
- Oregon 63,395
Oregon - 63,395 workers across 365 notices
63,395 workers
- Maryland 60,723
Maryland - 60,723 workers across 614 notices
60,723 workers
- Illinois 58,300
Illinois - 58,300 workers across 5 notices
58,300 workers
Why This Matters
Warn act mass layoff tracking data is increasingly important for workers, job seekers, journalists, policymakers. However, raw data without context can be misleading. Numbers that appear alarming may reflect normal patterns when viewed in historical context, and seemingly stable figures may hide significant underlying shifts. This guide provides the framework for interpreting the data on PlainLayoffs with appropriate nuance.
The challenge is that WARN Act mass layoff tracking data comes from government sources (U.S. Department of Labor / State Workforce Agencies) that were designed for regulatory compliance and statistical reporting, not for the questions that most people are actually trying to answer. Understanding the gap between what the data measures and what you need to know is essential for drawing valid conclusions.
Key Concepts
What the data captures: Official records from U.S. Department of Labor / State Workforce Agencies provide a structured view of WARN Act mass layoff tracking across the United States. These records follow standardized reporting requirements, which means the data is consistent and comparable across geographic areas and time periods. This consistency is the primary strength of government data, it enables apples-to-apples comparison.
What the data misses: No dataset captures everything. Government reporting has coverage gaps, reporting delays, and definitional boundaries that exclude certain activities or populations. Always check the scope and coverage notes on our about page before drawing conclusions from the data.
How to contextualize: Numbers are most meaningful when compared, against historical baselines, geographic peers, or industry averages. A figure that looks high in isolation may be perfectly normal for its category. Always compare within the appropriate reference group.
Practical Steps
Step 1, Start with the big picture. Before drilling into specific records, check the broad trends. What is the overall direction? Is the pattern you are investigating part of a larger trend or an isolated anomaly?
Step 2, Compare appropriately. When evaluating any specific data point on PlainLayoffs, compare it against similar entities rather than the national average. Geographic, industry, and size differences create natural variation that makes broad comparisons misleading.
Step 3, Check the source. Every data point on PlainLayoffs ultimately traces back to U.S. Department of Labor / State Workforce Agencies. When the stakes are high, career decisions, policy analysis, research publications, verify critical figures against the primary source. We provide source links on our data pages.
Step 4, Apply judgment. Data is a starting point, not an answer. The best decisions combine quantitative data with qualitative context, local knowledge, expert consultation, and direct observation. Use PlainLayoffs data to narrow your focus and inform your questions, not to replace professional judgment.
Common Misconceptions
One of the most frequent errors when working with WARN Act mass layoff tracking data is treating aggregate statistics as individual predictions. National or state-level averages describe populations, not specific cases. Your individual experience may differ significantly from what aggregate data suggests, and that is expected, averages compress enormous variation into a single number.
Another common mistake is assuming more recent data is always more relevant. Government data typically has a reporting lag. Depending on the dataset, the most recent available figures may describe conditions from 12-24 months ago. Current conditions may have shifted, particularly in rapidly changing sectors or regions.
A WARN notice is not a prediction of doom, it is a legal clock starting, giving workers 60 days to plan, retrain, and line up what comes next.
WARN Act Coverage Thresholds
The federal WARN Act applies only to employers with 100 or more full-time employees and covers layoff events affecting 50 or more workers at a single site. This means small-to-midsize employer layoffs are systematically excluded from WARN data.
Federal vs. State Mini-WARN Thresholds
| Jurisdiction | Employee Threshold | Layoff Trigger |
|---|---|---|
| Federal WARN | 100+ employees | 50+ workers affected |
| California (Cal-WARN) | 75+ employees | Any mass layoff |
| New York | 50+ employees | 25+ workers affected |
| New Jersey | 100+ employees | 50+ workers affected |
| Illinois | 75+ employees | 25+ workers affected |
Source: U.S. Department of Labor and state workforce agencies.
Worked Example: When WARN Does Not Apply
A tech startup with 85 employees in Austin, TX lays off 30 software engineers. Despite the significant impact on those workers, this event does not trigger WARN Act reporting because the employer has fewer than 100 employees. At severance costs of $8,000 ... $15,000 per affected employee, the total financial impact ranges from $240,000 ... $450,000, yet no WARN notice is filed and the event does not appear in PlainLayoffs data.
By contrast, a manufacturing plant in Ohio with 500 employees that closes one shift affecting 75 workers must file a WARN notice 60 days before the layoff date. The affected workers are entitled to either 60 days pay ($4,800 ... $7,200 at $15.00 ... $18.00/hr) or the notice period itself.
What to do with this
The WARN Act gives covered workers a 60-day head start, here is how to use it.
- First, check whether a layoff is even covered: the federal rules apply at employers with 100+ staff to cuts of 50+ workers. WARN eligibility checker
- If the 60-day notice was skipped, affected workers can be owed up to 60 days of back pay, estimate the amount. WARN pay estimator
- Look up a specific employer's filing history to see its WARN record and worker counts. Browse employers
Many states have their own mini-WARN laws with lower thresholds and extra rules, so confirm the requirements in the state where the layoff occurs.
Frequently Asked Questions
What data does PlainLayoffs use?
PlainLayoffs uses data from U.S. Department of Labor / State Workforce Agencies. All data comes from public government sources and is processed through our ETL pipeline for searchability and analysis.
How often is the data updated?
We update our database as new data becomes available from U.S. Department of Labor / State Workforce Agencies. Update frequency depends on the source agency's release schedule, which varies from weekly to annually depending on the dataset.
Is PlainLayoffs free to use?
Yes. PlainLayoffs is completely free, requires no account, and is supported by non-intrusive advertising. We believe public data should be freely accessible.
Layoff Trends by Industry Sector
WARN data reveals distinct patterns across industries. Technology and finance sectors tend to cluster layoffs in Q4 and Q1 (budget cycle-driven), while manufacturing layoffs track more closely to economic recession indicators.
Average WARN Event Size by Sector
| Industry | Avg Workers/Event |
|---|---|
| Technology | 410 |
| Manufacturing | 215 |
| Financial Services | 215 |
| Healthcare | 93 |
| Retail | 248 |
Source: WARN Act filings aggregated by PlainLayoffs, computed live as total workers affected divided by total notices filed per sector. Severance terms are not part of the WARN Act filing itself and are not tracked in this dataset; actual severance is set by employer policy or a separation agreement, not by federal law.
Seasonal Patterns
WARN filings show real seasonal variation. Across the full multi-year record, October and January average the highest total workers affected per month, while December and June average the lowest. Year-to-year swings are large enough that any single month can deviate sharply from its historical average; see the methodology page for how monthly totals are computed.
Sources: U.S. Department of Labor / State Workforce Agencies.
Last updated: April 2026
Worked example: putting the numbers together
Consider a 5,200-employee tech company announcing a 12% workforce reduction (624 affected). The notice is dated April 1 with separations effective May 31-60 days, satisfying federal WARN. In California, where 380 of the 624 are based, Cal-WARN also requires 60 days plus separate state filing, both met. But in New York, where 95 affected workers are based, NY-WARN requires 90 days. The 60-day notice violates NY law for those 95 workers, exposing the employer to up to 30 days of back pay and benefits per worker, roughly $30,000 to $45,000 per affected worker, or $2.8M to $4.3M aggregate damages just for the New York shortfall. State-specific timing matters more than the federal floor.
Decision-weighted comparison
| Jurisdiction | Employer threshold | Affected threshold | Notice required |
|---|---|---|---|
| Federal WARN | 100+ employees | 50+ at one site (or 33% + 50) | 60 days |
| California (Cal-WARN) | 75+ employees | 50+ in 30 days | 60 days |
| New York | 50+ employees | 25+ (33%) or 250+ | 90 days |
| New Jersey | 100+ employees | 50+ in 30 days | 90 days |
| Illinois | 75+ employees | 25+ (33%) or 250+ | 60 days |
| Tennessee | 50+ employees | 50+ in 3 months | 60 days |
How to use PlainLayoffs data to understand your situation
Start with the WARN Act overview to grasp your federal protections, then check state-level WARN extensions - California, New York, New Jersey, and Illinois each have stronger protections than federal law. Use the company layoff history to research employer patterns before accepting an offer, and the state-level filing tracker to see active WARN notices in your region. For navigating an active layoff, the navigation guide walks through severance review, COBRA timing, and unemployment filing windows. Every notice we publish comes directly from state Department of Labor WARN filings, public records by statute, with vintage stamps on every record.
The live counts on this guide are rendered directly from the PlainLayoffs database. Legal thresholds, historical examples, and illustrative figures cited in the guide text come from public statutes and general industry context, not this portal's live database. This guide's WARN Act figures are drawn directly from state filings. See our editorial standards & corrections policy, the methodology behind these numbers, or report a data error. Data current as of June 2026. A WARN filing is a legally required notice, not a judgment of a company's management or financial health; rankings here reflect filed notice volume only.
| Publisher | PlainLayoffs |
| Sources | Public state WARN-Act layoff registries |