US WARN Act Layoff Monitor — Multi-State Layoff & Closure Feed

One clean, normalised feed of new US mass-layoff and plant-closure (WARN Act) notices, pulled straight from each state's official source of truth. Every scheduled run checks all enabled states and emits only notices you have not seen before — no re-scraping the same filings, no duplicate rows.

Built for:

• Journalists & researchers — catch layoff filings the day the state posts them, with employee counts as clean integers and one schema across states.
• Sales & GTM intelligence — companies filing WARN notices are restructuring: prime timing for outreach, competitive moves and churn-risk flags on your accounts.
• HR-tech & outplacement — feed new filings into recruiting, severance and workforce-transition products.
• Distressed-asset & credit analysis — closures and large layoffs are an early operational-stress signal, published weeks before most press coverage.

State coverage (v1)

Every state below is parsed from the state government's own publication — never from third-party aggregators.

State	Source	Format
California	EDD WARN report	Excel, updated ~daily
New York	NY DOL WARN dashboard	Dashboard data export
Texas	TWC WARN notices via Texas Open Data	JSON API
Washington	ESD WARN database	HTML table
New Jersey	NJ DOL WARN notice archive	Excel archive
Maryland	MD Labor WARN page	HTML table
Colorado	CDLE WARN list	Real-time public sheet

Honest notes per state:

• Texas data comes from the state's open-data mirror, which lags the TWC website by roughly 4–8 weeks (the TWC site blocks automated access). Texas filings are complete, just slower.
• New Jersey publishes the posting month rather than a filing day, and does not label closures vs layoffs (closureType is unknown).
• Texas does not label closures vs layoffs either.
• Florida, Illinois, Ohio and Georgia are planned for v1.1 — their current publication channels (WAF-blocked portals, login-gated apps) need extra plumbing to monitor reliably.

Example output

{
  "state": "CA",
  "company": "Bumble Bee Foods, LLC",
  "locationCity": null,
  "locationRaw": "280 10th Avenue  Santa Fe Springs CA 90670 — Los Angeles County",
  "employeesAffected": 197,
  "noticeDate": "2026-08-06",
  "effectiveDate": "2026-10-05",
  "closureType": "closure",
  "industry": "31-33 Manufacturing",
  "sourceUrl": "https://edd.ca.gov/en/jobs_and_training/layoff_services_warn/",
  "noticeKey": "CA:1f4c2b9a8d3e7f01",
  "detectedAt": "2026-08-31T05:09:22Z"
}

• employeesAffected is always an integer (or null when the state did not publish a count) — messy source values like "1,024" are normalised.
• closureType is closure, layoff or unknown.
• noticeKey is a stable identity per filing, so you can dedupe downstream.

Input options

Option	Default	What it does
states	all 7	Which states to monitor
minEmployeesAffected	0	Only emit filings of at least this size (unstated counts excluded when set)
keywords	none	Case-insensitive match on company, industry and location
sinceDays	30	Backfill window by notice date on the first run
maxItems	500	Cap per run, shared evenly between the states with new notices; overflow emits on the next run

How to use it

Schedule the actor (daily or a few times per week matches state publication cadence). The first run backfills the sinceDays window; every later run emits only never-seen notices. A run where nothing new was filed emits zero rows and exits successfully.

Searches this actor answers: warn act layoff data, mass layoff notices API, plant closure feed, layoff tracker multi state, warn notice scraper.

Reliability

• One state's website changing layout never kills the run: that state logs a schema-drift warning and the other states continue.
• State checked, notice detected and actor start are the only charge events — you pay per new notice, not per page fetched.
• Sources checked against each state's live site; schema verified weekly.

Changelog

• 0.2 — maxItems is now shared fairly between the states in a run, so a small cap no longer fills up with the busiest state (California) and leaves the quieter ones for the next run. Overflow still carries over.
• 0.1 — initial release: CA, NY, TX, WA, NJ, MD, CO; seen-notice diff feed; employee-count normalisation; keyword and size filters.