APProjects/us-warn-act-layoff-notice-changes-daily

What changed in US WARN Act layoff notices

525 observed changes across 15 daily builds (2026-08-30 to 2026-09-13), touching 382 distinct notices in the daily US WARN Act dataset.

This is the answer to a question no state labor department will answer for you: what did the layoff filing say before it said this? State WARN portals publish a page. When a notice is amended, re-filed or pulled, the page simply changes - there is no history, no diff, no archive. This dataset is that diff, taken every single day.

Read this before you use a single row

A difference between two of our daily builds has two possible causes, and we usually cannot tell which one it was:

1. the state agency amended, re-filed or removed the notice, or
2. our own parser or normalizer got better and now reads the same source differently.

We do not guess. The cause_class column labels only what is mechanically decidable, and every headline number below is computed from value_changed rows only.

change_type=row_absent means the row stopped appearing in our build. It does not mean the employer withdrew the notice. A state re-organising its portal, a paginated page timing out, or a filing ageing out of a source's own window all produce a row_absent row.

Workers whose headcount was substantively revised: 0. An earlier build of this pipeline was about to publish a four-figure "workers revised" total; inspection showed every one of those events was an empty field being populated for the first time, not a number being changed. That is why the number here is computed from value_changed rows alone.

Columns

column	meaning
observed_date	the build in which the change was first seen
prev_observed_date	the build it is being compared against
id	stable notice id, joins to the main dataset
state	two-letter state posting the notice
company	employer as filed at observed_date
notice_date	date on the filing
change_type	amended (a field differs) or row_absent (row gone from our build)
cause_class	value_changed, field_populated, field_cleared, format_only, unknown
field	which column changed (blank for row_absent)
old_value / new_value	the two values, as printed

What is in here right now

change_type	rows
amended	263
row_absent	262

cause_class	rows
value_changed	124
format_only	24
field_populated	115
field_cleared	0
unknown	262

Fields that were amended:

field	times
location	97
notice_type	63
employees_affected	43
company	30
effective_date	27
notice_date	3

The suppression ledger (5 day-pairs)

Our own coverage window has widened several times (adding states, and opening the free window from 2024+ back to 1988). On a day when the row count swings more than ~5%, treating every missing row as a disappearance would manufacture tens of thousands of fake withdrawals. On those day-pairs we suppress disappearances and publish the pair in suppressed_snapshot_pairs.csv instead, so the gap is visible rather than silent. Amendments are still published for those days.

Why this cannot be copied

Anyone can re-scrape 48 state portals and match our current table within a week. Nobody can reconstruct what those portals said last Tuesday. This file starts at 2026-08-30, grows by one build every day, and cannot be backfilled by us or by anyone else. Every day it is not captured is lost permanently.

Freshness

Rebuilt daily by an automated pipeline (gen_revisions.py) straight from the git history of the free dataset's data/warn_notices.csv. Latest build in this copy: 2026-09-13.

Related

• Daily US WARN Act notices - every notice, 48 states, free, no login.
• Multi-state employers - who is laying off in more than one state.
• Notice-period dataset - how many days' notice each filing gave.
• Free CSV/JSON/RSS on GitHub - CC BY 4.0.
• The site - state pages, employer pages, live search.
• WARN Watch - same-day alert when an employer on your list files, $49/year.

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.

Use it, or keep watching it

This dataset is one cut of a single daily rebuild: 61,309 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-13; the files above are rebuilt every day, so the live count is the truth.

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 →

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.

• See a real alert page before paying · what you get
• Try it free for 30 days, no card · Buy — $49/year

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