Datasets:

APProjects
/

us-multi-state-employer-layoffs-warn-notices-by-state

pretty_name: >-
  US employers laying off in more than one state (multi-state WARN Act notices,
  by employer and state)
license: cc-by-4.0
language:
  - en
task_categories:
  - tabular-classification
tags:
  - warn-act
  - layoffs
  - multi-state
  - multi-state-layoffs
  - layoff-notices
  - employers
  - companies
  - by-state
  - plant-closings
  - workforce-reduction
  - labor
  - labor-market
  - sales-intelligence
  - economics
  - public-records
  - government-data
  - daily-updated
  - united-states
size_categories:
  - 1K<n<10K
configs:
  - config_name: employers
    data_files: data/multi_state_employers.csv
    default: true
  - config_name: notices
    data_files: data/multi_state_notices.csv

Which US employers are laying off in more than one state?

Every state publishes its own WARN Act layoff notices, and every state's list stops at its border. The employer that filed in Texas on Monday and Ohio on Wednesday appears as two unrelated rows on two unrelated portals. This dataset is the merge: the free-window notices from 48 states, grouped by employer, kept to employers that filed in two or more states, rebuilt every day.

The headline (free window, 1988 - today, as of 2026-09-16)


Employers with WARN filings in 2+ states	2,756
Employers with filings in 5+ states	605
Workers named in those employers' filings, as filed	2,915,291
Underlying notices (one row each in `notices`)	25,119
States spanned	48

Tracking specific employers or states? Name up to three and every daily rebuild is matched for you - alert page + RSS, optional Slack/Discord/Teams webhook. Free 30-day watch, $0, no card, nothing renews.

Most states, top 20

employer	states	which	notices	workers as filed
Aramark	37	AL AZ CA CO CT DC DE FL IA ID IL IN KS KY MA MD MI MN MO MS NC NJ NV NY OH OK OR PA RI SC SD TN TX UT VA WA WI	279	49,229
Sodexo	37	AL AZ CA CO CT DC DE FL HI ID IL IN KS KY LA MA MD MI MN MO NC NE NJ NV NY OH OK OR PA RI SC TN TX VA WA WI WV	265	28,690
Walmart	30	AK AL AZ CA CO CT DC FL GA IL IN KS MA MD MI NC NJ NM NY OH OK OR PA SC TN TX UT VA WA WI	142	23,084
Conduent	30	AZ CA CO CT DE FL GA ID IN KY LA MD MI MO NC NE NM NV NY OH OK OR PA RI SC SD TN VA WA WI	97	3,605
ABM	27	AL AZ CA CO DC FL GA IL IN MA MD MN MO NC NJ NV NY OH OK PA SC TN TX UT VA WA WI	122	12,448
Macy's	26	AL AZ CA CT FL GA ID IL IN KS KY MD MI MN NC NJ NY OH OK OR PA TN TX UT VA WA	171	17,428
Wells Fargo	25	AL AZ CA CO FL IA ID IL MD MN MT NC ND NE NJ NV NY OR PA SC SD TX UT VA WA	170	12,482
Yellow	24	AL AZ CA CO DC FL ID IL IN KS ME MI MN NC ND NM NV NY OH PA TX VA WA WI	83	13,286
Cygnus Home Service	24	AZ CA CO CT ID IL IN MA MD MI MO NC ND NE NM NY OH PA SC TX UT VA WA WI	56	1,085
David's Bridal	23	AK AL CA CO CT GA MA ME MN MO NC NE NJ NM NV NY OH OR PA TN TX WA WI	82	22,433
Verizon	23	AL CA CO CT IA IL KS KY MD MI MN NE NJ NM NY OH OR PA SC TN TX VA WA	63	13,379
United Airlines	22	CA CO CT FL HI IL IN MI MN NC NE NJ NV NY OH OK OR PA RI TX VA WA	64	81,360
Cinemark	22	AZ CA CT ID IL IN KS MD MI MT NC NV NY OH PA SC TN TX UT VA WA WI	140	11,297
Enterprise Holdings	22	CA CT FL HI IN KS MD MI MN MO NC NM NV NY OH OK OR PA TN TX VA WI	100	8,054
Kmart	21	AL AZ CA FL IL IN KS KY MD MI MN NC NE NJ NY OR PA TN UT VA WA	243	20,049
First Transit	21	CA CT FL IL IN MD MN NC NJ NV NY OH OK OR PA TN TX UT VA WA WI	54	6,683
Saks &	21	AL AZ CA FL HI IL MA MD MI MO MS NC NJ NV NY OH OR PA TN TX VA	52	4,353
Block	21	AZ CA CO CT FL GA HI IL IN MA MN MO MT NC NV NY OR PA SC WA WI	39	877
Paper Source	21	CA CO CT FL IN KS MD MI MN MO NC NJ NV NY OH OR PA TX VA WA WI	48	754
Hostess Brands	20	AK AL AZ CT ID IL IN KS KY MD MI NJ NY OR PA SD TN VA VT WA	128	7,848

Most workers, top 10

employer	workers as filed	states	notices
United Airlines	81,360	22	64
Aramark	49,229	37	279
Boeing	43,967	14	420
OS Restaurant	38,864	13	132
Northwest Airlines	31,875	3	17
Sodexo	28,690	37	265
Walt Disney Parks and Resorts U.S	24,843	2	27
Walmart	23,084	30	142
David's Bridal	22,433	23	82
General Motors	22,412	13	42

What is in the files

data/multi_state_employers.csv (config employers, default) - one row per employer, 2,756 rows:

column	meaning
`employer`	canonicalized employer name (see method)
`n_states`	number of distinct states with a filing
`states`	space-separated two-letter codes
`notices`	number of filings across those states
`workers_as_filed`	sum of `employees_affected` across those filings, exactly as each state filed it
`first_notice`	earliest notice date (or effective date where the state gives no notice date)
`last_notice`	latest such date

data/multi_state_notices.csv (config notices) - every underlying filing, 25,119 rows, the same columns as the daily notices dataset (id, state, company, company_canonical, company_dba, location, employees_affected, notice_date, effective_date, notice_type, first_seen) plus employer, the merged employer key that matches employer in the employers file (a row's own company_canonical may be one of that employer's other spellings). Join on id to the daily dataset, on employer to the employers file.

Both files cover the free window (1988 to today). The same merge over the full 1988+ archive is part of the paid archive - stated up front rather than discovered after download.

Method, and what it does NOT say

Grouping is deterministic string canonicalization, not corporate-entity resolution. Legal suffixes (Inc, LLC, Corp) are stripped, "dba" parts are split off, plant/site tails after dashes are dropped, ALL-CAPS is fixed. Nothing is looked up. Consequences you must expect: a subsidiary filing under its own name is not merged into its parent, and two spellings the rule cannot reconcile may split one employer into two rows. On top of that, a conservative alias merge folds spellings that share a distinctive token prefix into one employer ("Boeing Compnay", "Boeing - El Paso" -> Boeing) only when that token is at least 90% pure across the archive; it under-merges on purpose. Treat employer as a display key, not a legal identity.
workers_as_filed is a sum of headcounts as filed. States amend and re-file notices; where the source portal lists an amendment as a separate row, the workers are counted again. It is not a deduplicated headcount.
A filing in two states says the employer had two WARN-triggering events; it does not say they were the same decision, the same week, or the same business line.
"Notice" means one row on a state WARN portal. States differ in what they publish (some list every site, some one row per employer per event).

Freshness

Rebuilt daily from 48 state labor-department portals by an automated pipeline; the underlying build was 2026-09-16. A static copy of this list is wrong within a week - the multi-state view only exists because something merges the portals every day.

Daily WARN notices dataset - every notice, every state, free.
Notice-period dataset - how many days' notice each filing gave.
The multi-state page - the same list, rendered.
Free CSV/JSON on GitHub - CC BY 4.0, no login.
WARN Watch - alerts when your employers or states file, $49/year.
Full historical archive - every notice back to 1988, free.

License

CC BY 4.0. Underlying notices are US state public records. Attribution: "WARN Feed, https://approjects-warn-act-notices.static.hf.space".

Not affiliated with the US Department of Labor or any state agency.

A layoff record you can audit, not just download

This dataset is one cut of a single daily rebuild: 61,330 US WARN Act layoff notices from 48 state agencies, 1988 to today, one schema, no login, no delay, CC BY 4.0. Snapshot as of 2026-09-17; the files above are rebuilt every day, so the live count is the truth.

Several projects publish a current WARN scrape and two of them carry more rows than we do. None of them publish what the records used to say:

617 observed changes to already-published notices, logged daily since 2026-08-31. data/revisions.csv records every field that differed between two consecutive daily builds — employee counts, effective dates, notice types, company names — with the old value, the new value and the date we saw it. We publish the observation and not the cause: a change is equally explained by the agency amending the notice or by our own parser improving, and we do not guess which (see data/revisions.README.txt). A scrape that starts tomorrow cannot backfill any of it; it only exists if someone was watching.
6,799 notices whose state agency page no longer lists them. Agencies take notices down. We keep them, flagged as archive-only, so a count you ran last year still reconciles.
Point-in-time employer identity. The ticker crosswalk resolves a filer to the company as it existed at the time of the notice — Kmart, Sears Holdings, Symantec — not to whatever is on today's ticker file.

If you have to defend a number to an editor, a referee or a compliance reviewer, that provenance layer is the part you cannot rebuild yourself. How to cite this dataset →

Look something up right now — free, no signup, nothing to install. Check any employer or state against the last 180 days → It runs in your browser against these same files.

Building something with it? The same files are a free HTTP API — JSON and CSV, no key, no signup, access-control-allow-origin: * so fetch() works from a browser: endpoints, schema and curl examples →

Need one industry only? The same filings, cut by an auditable employer-name rule (each row keeps the rule that fired): tech companies · hospitals & healthcare · retail store closings · restaurants & hotels · factory & plant closings · banks, insurance & finance · warehouses, trucking & logistics · all 20 sectors.

Or have it watch a list for you. Coming back to look is the part a CSV cannot do. WARN Watch — $49 for a year, one payment, nothing auto-renews, 14-day refund, no login: up to 500 employer names plus whole states, matched on every daily refresh, delivered to a private alert page + calendar (.ics) + RSS + an optional Slack / Discord / Teams webhook. Every alert carries that employer's whole filing history from the archive, which a keyword rule on an RSS feed cannot see. There is no built-in email — we do not claim one.

Not deciding today? Join the update list → — one email when a new dataset or tier is published; nothing promotional. A state added or a column renamed ships in the daily release instead, no address needed. The list is shared across APProjects datasets, holds an email address only, is run by Gumroad, and any message unsubscribes you. Rather give no address at all? Watch the repo's releases — GitHub notifies you on every daily republish, and a new state or changed field is in those notes the day it lands.

Reaching a human. WARN Feed is published by APProjects, an automated data publisher — that is stated plainly rather than dressed up. Corrections, coverage gaps, schema questions and refund requests all go here and are read: open an issue. Payments are handled by Gumroad as merchant of record, so an invoice can carry your company name.

Source, scrapers and methodology · the 48-state site

_{Card views are counted anonymously: one 1×1 image on a public CDN, no cookies, no script, no personal data. The count is public: jsDelivr stats.}