US WARN Act layoff notices — one normalized dataset

Every state publishes layoff notices differently. This dataset merges 39 states into one schema, deduplicated, refreshed daily. Updated 2026-09-02.

Get the free dataset on GitHub (CSV/JSON, no login) · browse layoffs by employer · layoffs week by week · month by month · year by year · per-state RSS feeds (OPML) · compare data sources · search notices · Hugging Face mirror

Biggest layoff notices — 2026-08

Monthly trend — last 12 months

Per-state monthly series, machine-readable: data/trends.json (CC BY 4.0). Newly-added notices, last 7 days: data/latest.json.

Latest 25 notices

Coverage

"Source last scraped" is when our pipeline last pulled that state's portal successfully (a stale stamp means the portal was unreachable and we kept the last good copy). "Newest notice on file" is the most recent notice date the state has published — many states post in batches, so a date a week or two old is normal. Both are also in data/coverage.json.

Sources behind their usual cadence (5)

We compute this on every refresh instead of hiding it behind an "updated today" stamp: a state whose newest notice is older than its expected posting cadence (60 days; Texas 75, Mississippi 120) is listed here with what we know about why. Machine-readable: data/stale.json.

Not covered (12 states): Arkansas — agency site blocks automated access, Hawaii — agency page unparseable (obfuscated links), Idaho — agency PDF is corrupt, Massachusetts — agency site blocks automated access, Minnesota — agency site blocks automated access, Missouri — agency site blocks automated access, Nevada — agency site blocks automated access, New Hampshire — agency site blocks automated access, North Dakota — no public WARN listing located, Ohio — listing is a browser-only app, no data endpoint, Virginia — listing is a browser-only app, no data endpoint, Wyoming — WARN filings are non-public by state statute. We do not guess or backfill these from third parties; a state is added the day it publishes a usable public listing. States added in the last 48 hours show 0 free rows until their delay window passes.

What normalization actually does

State portals spell the same employer many ways — store numbers, site tails, legal suffixes, ALL CAPS. company_canonical collapses them so you can count and watch one employer across states and years. Real examples from the free files:

Paid tiers, refunds, contact

What the two paid tiers are for. The real-time feed ($49/mo) is a private GitHub repo that receives every new notice the moment our pipeline sees it — no 48h delay — and includes the rolling history while you subscribe; access ends when the subscription ends. The historical archive ($199 one-time) is every notice we hold back to 1988 — 45,755 rows across all covered states versus the 8,112 rows (2024–present) in the free files. It arrives in two parts, and we would rather you know before you pay than after: (1) the ZIP that downloads instantly from Gumroad is the last monthly build we uploaded there (the listing states its exact row and state count); (2) the complete current build — CSV + JSON + coverage metadata, rebuilt every month and yours to keep — comes from the private GitHub repo you are invited to after checkout, usually within a few hours and at most 24h. Enter your GitHub username at checkout; on the repo, the green "Code" button offers "Download ZIP", so no git is required. Buy the archive if you need the back-catalogue once and keep it forever; subscribe if you need today's notices today. Try before you buy: one state's complete back-catalogue is free as a sample — Oregon, 1988→present, 1,369 rows, identical schema to the archive.

Delivery. Both tiers ask for your GitHub username at checkout. An automated job sends the repo invitation within one refresh cycle (usually a few hours, at most 24h).

Refunds. Archive: full refund within 7 days of purchase if the data is not as described — just ask. Real-time feed: cancel any time from your Gumroad receipt or library; you keep access until the end of the paid month, and if the invite never arrives we refund the month in full.

Contact. Open an issue at github.com/APVentureEngine/warn-act-notices/issues (templates for data errors, missing invites and general questions) — it is checked on every refresh cycle, daily or better. Gumroad buyers can also reply to their receipt email, which reaches us through Gumroad.