US WARN Act layoff notices — every state, one normalized file

Before you buy: checkout collects your email, the employer terms and states you type, a page key, and (optional) a Slack/Discord/Teams webhook URL. What we do with each of those, how long we keep it, how to have it deleted, and the refund terms (14 days on WARN Watch, 7 days on the archive) are all on Privacy & terms. Seller of record: Gumroad. Questions: open an issue.

Not buying today? Three free ways to stay in the loop: 30-day WARN Watch trial (3 employers or 1 state, no card) · email updates when coverage or tiers change (Gumroad, unsubscribe any time) · RSS of every new notice.

Is the paid tier worth it? An honest answer.

The free files are the whole dataset from 2024 on — no delay, no login — and they stay free. None of it is secret: the state portals are public and biglocalnews/warn-scraper is open source. We measured the gap on 2026-09-03, when the archive held 45,755 rows (it holds 45,775 in today's build — this paragraph deliberately keeps the numbers from the day the measurement was taken): only 1,188 of them (2.6%) were older than what the state portals still serve today. So the $199 archive is not scarce data — it is 39 portals already scraped, de-duplicated into one schema with stable ids, as a 7 MB CSV (plus JSON) you can load in one line.

What you are paying for is maintenance. Portals change layout, drop fields and go quiet; keeping 39 of them normalized every day is the work. WARN Watch is the same trade: a year of daily checks against your employer list that you never have to keep running. If that is not worth more to you than an afternoon and a cron job, use the free files with our blessing — that is what they are for.

Already paying for ZoomInfo, Apollo or Sales Navigator?

Then you already get the layoff signal — a flag on a company record, inside the tool your team lives in. Keep it. What a sales-intelligence seat does not hand you is the filing itself as data: the date the notice was filed, the date the cuts take effect, the worker count as filed with the state, the state’s own notice text, and every earlier filing by that same employer — 45,775 of them back to 1988, as a CSV you can join to your own tables under CC BY 4.0. Those are two different products: one tells a rep to call today; the other lets you count, chart, audit and cite. We sell the second, and we do not sell seats.

Who that second product is for: anyone who has to answer a question with the record instead of a notification — WARN-compliance and employment-law research (how many notices in a state ran under the 60-day line, and which employers filed them), labor economists and reporters (a state-by-state series since 1988, stable ids, one schema), workforce boards and outplacement firms planning where the next cohort lands, and engineers who would rather have a file than a per-seat login. See the notice-period analysis → · How this compares to the paid trackers ↓

The one question a single-state feed cannot answer

Every state publishes its own WARN notices, and several publish an RSS feed — so do we, one per state, free. Subscribe to all 39 and you still cannot see this, because the answer does not exist inside any one of them: which employers are cutting in several states at once. That only appears after 39 portals are merged onto one resolved employer name, which is the work this dataset does every day.

Block has filed 28 WARN notices across 15 states since 2024 (Arizona, California, Colorado, Connecticut, Florida, Georgia, Illinois, Indiana, Montana, North Carolina, Oregon, Pennsylvania, South Carolina, Washington, Wisconsin), covering 745 workers. Reading one state's feed, you would have seen a fraction of that and had no way to know the rest existed.

See all 436 multi-state employers → Watch your employers — $49/year

Counts are the free tier (2024–present) as of 2026-09-07, recomputed in the same run that rebuilt the dataset — the number above and the number on the linked page are always the same build.

Half of US layoff notices arrive under the 60-day line

How this compares to the paid trackers

Layoff data is not an empty market — it is a market where the bulk file is usually the thing you have to pay for. The column that matters is the middle one.

Where we are honestly not the best. WARN Firehose holds more history than anyone here and bundles H-1B, SEC and bankruptcy data behind one API. layoffdata.com reaches all 50 states and territories where we cover 39. LayoffAlert.org gives free email alerts on a named company — the thing our Watch charges $49/year for. Buy those if that is what you need. What none of them do is hand you the complete, normalized, daily-rebuilt file with no login, which is the whole reason this exists.

Full comparison — every row sourced and dated, rebuilt daily →

Biggest layoff notices — last 30 days (2026-08-08 to 2026-09-07)

Grouped per notice (a phased notice with several layoff dates counts once, workers summed). 5 row(s) in this window whose state record names only a facility, not an employer, are omitted here but kept in the CSV as published. 3 row(s) are dated by the layoff/closure date and marked "layoff": Michigan, Pennsylvania and South Carolina publish no notice date at all.

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

Grouped per notice (a phased notice with several layoff dates counts once, workers summed). Rows whose state record names only a facility, not an employer, are omitted here but kept in the CSV as published. 2 row(s) are dated by the layoff/closure date and marked "layoff": Michigan, Pennsylvania and South Carolina publish no notice date at all.

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 (7)

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.

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

There are exactly two paid products, and neither of them is access to this data. The daily dataset above — every state we cover, 2024 to today, no delay, CSV + JSON + RSS — is free and stays free. We sell (1) WARN Watch, which runs your employer and state list against every refresh and tells you the day a notice lands, and (2) the 1988–present historical archive, which is the back catalogue the free files do not include. There is no subscription and nothing auto-renews; a third product that used to sell same-day access was withdrawn once the free files stopped being held back, which is why you will not find it for sale anywhere on this page.

What the two paid tiers are for. WARN Watch ($49/year, one payment) takes up to 25 employer terms and any number of whole-state watches, matches them against every daily refresh for 365 days, and publishes hits to a private alert page + RSS feed — no login, no email required; limits and a live comparison are on the WARN Watch page. The historical archive ($199 one-time) is every notice we hold back to 1988 — 45,775 rows across all covered states versus the 9,443 rows (2024–present) in the free files. How it is delivered, so you know before you pay rather than after: the build is a ZIP attached to the Gumroad listing, so it downloads from your receipt and library the moment you pay — no account here, no GitHub, no email wait. Inside: CSV + JSON + coverage metadata + README, about 3.9 MB; the attached ZIP is a dated build (the listing names the build date), and we refresh it when a new monthly build is cut. Want it current every day instead? Enter a GitHub username at checkout and an automated job also invites you to a private repo mirror that is rebuilt daily, if you would rather git pull than re-download; that box really is optional and leaving it blank costs you nothing. Buy the archive if you need the back-catalogue once and keep it forever; buy WARN Watch if you want your own employers and states checked for you every day. 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. Archive: the ZIP is attached to the Gumroad listing, so it downloads from your receipt the moment you pay — no account, no GitHub, no waiting. Optionally enter a GitHub username at checkout and an automated job also invites you to a private repo mirror rebuilt daily; leaving that box blank costs you nothing. WARN Watch: your private alert page is created on the next refresh (usually a few hours, at most 24h), and the alert finder opens it at any time from your email address plus the page key you chose at checkout. Forgotten the page key? Reply to your Gumroad receipt — it is stored with your order, so we can send you the direct link.

Refunds. Archive: full refund within 7 days of purchase if the data is not as described — just ask. WARN Watch: full refund within 7 days, no questions asked; if your alert page is not live within 24 hours of purchase, ask and we refund immediately.

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.