WARN Layoff Notices Feed: Multi-State WARN Act Layoffs & Plant Closures in One Schema

Get WARN Act layoff and plant-closure notices from official state workforce agencies in one clean, normalized dataset: California (EDD), Texas (TWC), Washington (ESD), Virginia (Virginia Works), Oregon (HECC) and Colorado (CDLE). Each record has the company, city, county, number of employees affected, notice date, effective (layoff) date, layoff vs closure, permanent vs temporary, industry where published, and a link to the official source or notice PDF. Filter by company, city or county and minimum headcount, then schedule it daily in new since last run mode for a layoff alert feed that only bills you for notices you have not seen.

WARN (Worker Adjustment and Retraining Notification) notices are usually filed 60 days before a mass layoff or closure, which makes them one of the earliest public signals of company distress, restructuring and talent becoming available.

Who it is for

• B2B sales and revenue teams: layoffs and site closures are buying triggers for outplacement, staffing, HR tech, benefits, legal, relocation, liquidation, commercial real estate and IT asset recovery. Filter by minEmployees to focus on big events.
• Recruiters and talent teams: know which companies are releasing engineers, nurses, warehouse or manufacturing workers in your city 60 days ahead, and reach the talent pool first.
• Commercial real-estate, landlords and economic developers: closures and relocations signal upcoming vacancies; watch by county or city.
• Journalists, newsletters and researchers: a daily, multi-state layoff tracker with links to the official state records for verification.
• Investors and analysts: company-level distress signals, headcount affected and timing, per state.
• Workforce boards and nonprofits: a single feed of notices across states for rapid-response planning.

Why this WARN Actor

• Six official state sources, one schema: CA, CO, OR, TX, VA, WA, merged newest-first.
• Normalized fields, not raw columns: employeesAffected as a number, ISO dates, noticeType (layoff / closure / relocation), permanence (permanent / temporary), isAmendment flag, city, county, workforceArea, industry, unionized (VA), plus the state's original type text in layoffTypeRaw.
• Stable noticeId per notice for dedupe in your CRM or warehouse.
• Filters: states, days back, company keyword, city/county keyword, minimum employees, include/skip amendments.
• New since last run mode with saved history per State key (named key-value store), for daily alerts without duplicates.
• Resilient: if one state's site is down, the run continues with the others and reports it in failedStates.
• Polite and compliant: declared User-Agent, spaced requests, robots.txt crawl-delays honored, official public lists only.
• Privacy by design: company-level data only. Personal contact names (e.g. Virginia's "Contact Person") and union contact details are dropped.
• Fast and cheap: a default run takes about 10-15 seconds at 512 MB.

Quick start

1. Click Start with the default input. You get the 40 newest WARN notices across all six states from the last 30 days.
2. Narrow it down: choose states, set minEmployees (e.g. 100), a companyKeyword (e.g. Amazon) or a locationKeyword (e.g. Seattle, Harris, Los Angeles), and raise maxItems for bigger pulls.
3. Daily layoff alerts (schedule tip): create an Apify Schedule (e.g. every weekday at 7:00) with:

{ "mode": "sinceLastRun", "stateKey": "daily-all", "daysBack": 14, "maxItems": 500 }

Each run delivers only notices not delivered before for that stateKey. Add a webhook or the Slack / Google Sheets / email / HubSpot integration to route them to your team. Use one stateKey per schedule (e.g. tx-100plus, seattle-tech).

Example: big layoffs in Texas and Washington in the last 60 days

{ "states": ["TX", "WA"], "daysBack": 60, "minEmployees": 100, "maxItems": 200 }

Input

Field	Default	Meaning
states	all six	CA, CO, OR, TX, VA, WA
daysBack	30	Notices dated in the last N days (1-730)
companyKeyword	none	Company name contains this text (case-insensitive)
locationKeyword	none	City, county, location or workforce area contains this text
minEmployees	0	Minimum employees affected (0 = no minimum)
includeAmendments	true	Set false to skip notices flagged as amended/updated
maxItems	40	Cap per run (also caps your spend), newest first
mode	window	window = everything in the window; sinceLastRun = only new notices (use for schedules)
stateKey	default	Saved history name for sinceLastRun

Output (real records, Oct 2026)

{
  "noticeId": "CA-b790a0c688b5f21d",
  "state": "CA",
  "stateName": "California",
  "company": "Dropbox, Inc.",
  "noticeDate": "2026-10-28",
  "receivedDate": "2026-10-28",
  "effectiveDate": "2026-11-18",
  "effectiveEndDate": null,
  "employeesAffected": 57,
  "noticeType": "layoff",
  "permanence": "permanent",
  "layoffTypeRaw": "Layoff Permanent",
  "isAmendment": false,
  "city": "San Francisco",
  "county": "San Francisco",
  "location": "50 Hawthorne Street San Francisco CA 94105",
  "address": "50 Hawthorne Street San Francisco CA 94105",
  "locationState": "CA",
  "workforceArea": null,
  "industry": "54 Professional Scientific and Technical Services",
  "reason": null,
  "unionized": null,
  "totalNotifiedAllStates": null,
  "sourceRecordId": null,
  "sourceAgency": "California Employment Development Department (EDD)",
  "sourceUrl": "https://edd.ca.gov/en/jobs_and_training/Layoff_Services_WARN/",
  "noticeUrl": null,
  "firstSeenAt": "2026-10-31T05:01:53.178Z"
}

{
  "noticeId": "WA-c08c69c753bb4cd1",
  "state": "WA",
  "company": "Comcast",
  "noticeDate": "2026-10-29",
  "effectiveDate": "2026-12-31",
  "employeesAffected": 159,
  "noticeType": "layoff",
  "permanence": "permanent",
  "location": "Statewide",
  "sourceAgency": "Washington Employment Security Department (ESD)",
  "noticeUrl": "https://fortress.wa.gov/esd/file/WARN/Public/DownloadFile.aspx?file=3b33f7df-fb60-454e-9761-9137ca511101.pdf"
}

One example per state: sample-output.json. Every run also writes a summary (window, per-state counts, failed states, source update cadence) to the OUTPUT record. Export as JSON, CSV, Excel or via the API.

Field notes

• noticeDate: date on the notice (CA, CO, TX, VA) or date received by the state (WA, OR). receivedDate: processed/received date where published.
• effectiveDate: first layoff/closure date; effectiveEndDate: end of the layoff period (CO).
• employeesAffected: workers affected in that state (CO also gives totalNotifiedAllStates).
• address: worksite business address (CA only). locationState: Oregon lists some employers by headquarters city in another state.
• industry: NAICS sector where published (CA, CO). workforceArea: TX workforce development area, CO workforce area.
• Fields a state does not publish are null. Records are as published by each state; companies sometimes file multiple notices (one per site) or amendments.

Data sources, update timing and fair use

State	Official source	Coverage / cadence
CA	EDD WARN report (.xlsx)	Current program year (from July 1), updated twice a week
CO	CDLE "Real-Time WARNs" list (public sheet linked from cdle.colorado.gov)	Current calendar year
OR	HECC Rapid Response WARN listings	As received
TX	TWC WARN Act listings (.xlsx, current + previous year)	Weekly
VA	Virginia Works WARN notices (CSV export)	As received, multi-year history
WA	ESD WARN layoff and closure database	As received

These are public records published by state agencies for public use. This Actor reads only the official public listings, identifies itself with a User-Agent, spaces requests per host and honors robots.txt crawl-delays. Not affiliated with or endorsed by any state agency or the U.S. Department of Labor. Always confirm critical decisions against the official record linked in sourceUrl / noticeUrl. Not legal advice.

FAQ

Which states are next? More states are planned (e.g. NY, NJ, IL, MD, IN, MI). Tell us in the Issues tab which ones you need. Why fewer notices for small states? Volume follows the economy: California files ~60 notices a month, Colorado a handful. Can I get history? Yes, raise daysBack (up to 730) and maxItems. Depth depends on each state's published list (see table).

Pricing

Pay per event (Apify takes care of billing; you only pay for what is delivered):

Event	Price	Charged
apify-actor-start	$0.005	once per run
notice-record	$0.004	per WARN notice delivered

A default test run (40 notices) costs about $0.165. A daily all-state sinceLastRun alert (~3 new notices/day) costs about $0.017/day. maxItems and Apify's max cost per run cap your spend; the Actor stops delivering when your budget is reached, so you are never charged for more than you set. No separate platform-usage charges: compute is included in the event prices.