Get told the day one of your companies files a layoff notice

US employers must file a WARN Act notice with the state before a mass layoff. Those notices are public, but they land on 48 different state portals in 48 different formats, on no schedule. WARN Watch runs your list of employers — and whole states if you want them — against every notice we collect, every day, for a year. Matches appear on your own alert page and RSS feed within a refresh cycle of us seeing them.

How it works

1. You pay once and give us your list right at checkout: paste the whole list into the box, comma separated, up to 500 names — nothing has to be made public. If a link is easier, one to a CSV, TXT or published sheet (one employer per row) works too. Plus any two-letter state codes.
2. We check them daily. Our pipeline scrapes 48 state labor-department portals, normalizes every notice into one schema, and matches your terms against the same-day build — on the employer name as filed, on our canonical employer name and on the trade name, so "general motors" also catches "General Motors, LLC -- Lansing Region" and store-number variants.
3. Matches land on your page, your calendar, your feed and — if you want — your channel. A private alert page (you reach it in one click: press View content in your Gumroad receipt, then Open my alert page. Nothing to type. If you lose the link, the alert finder turns your purchase email and the page key you chose at checkout in the box labelled “Page key” into a lookup that forwards to your page, locally in your browser — the key is not a password, we store it readable so we can resend your link, so never reuse a real one; we never publish the email, and the email alone does not open it), a private calendar (a .ics address: add it once in Google Calendar, Outlook or Apple Calendar and every matched separation date shows up as an event with a 14-day reminder from your own calendar app), an RSS feed you can point any reader at — including Slack, Microsoft Teams and Outlook, which all read RSS natively: in Slack it is /feed subscribe <your feed address> and every match lands in that channel on the refresh that finds it. We never ask you for an incoming-webhook URL or any other credential; that one stays on your side, where you can revoke it without telling us. Find your page any time at https://approjects-warn-act-notices.static.hf.space/alerts/.

What you get, exactly

• Up to 500 employer terms (typed, or a link to your sheet/CSV), changeable by replying to your receipt.
• Day one: your list against the archive. Every name you gave us, scored against every notice we hold back to 1988 — has it filed, how many times, in how many states, how many workers, when last — as a table on your alert page and a downloadable CSV, rebuilt daily. A feed filter cannot do this: a feed only carries new items, and the free alert sites take one company per signup.
• Whole-state watches — every new notice in the states you name.
• All 48 states we cover: AK, AL, AZ, CA, CO, CT, DC, DE, FL, GA, HI, IA, ID, IL, IN, KS, KY, LA, MA, MD, ME, MI, MN, MO, MS, MT, NC, ND, NE, NJ, NM, NV, NY, OH, OK, OR, PA, RI, SC, SD, TN, TX, UT, VA, VT, WA, WI, WV.
• Per match: employer as filed, our canonical employer, location, employees affected, notice date, effective date, notice type, and the day we first saw it.
• 365 days of daily checks from the day you buy. No subscription, nothing to cancel.
• Buying for a team, or need it on an expense line? Your Gumroad receipt has a Generate invoice link — add your company name and address there and it produces a PDF invoice. There is no per-seat limit: one purchase’s alert page, feed and webhook can be shared by your whole team.

How the alerts reach you

Four delivery channels, all included, none of them requiring you to install anything or create an account with us.

• Your calendar — the one that needs no setup. Your alert page carries a private .ics address. Add it once in Google Calendar, Outlook or Apple Calendar (“subscribe from URL”) and every separation date in your list appears as an all-day entry, with a reminder 14 days before the layoff takes effect. It re-checks itself every 12 hours, forever, with nothing for you to maintain. For most buyers this is the channel that actually works: the calendar is the one inbox that is already open all day.
• Slack, Microsoft Teams or Outlook. One command, no credential: in Slack, type /feed subscribe in the channel you want and paste your private feed address; every match is posted there on the refresh that finds it. We never ask you for a webhook URL.
• Your private alert page, rebuilt daily, with the day-one history report for every name on your list.
• RSS, for any reader or Outlook’s RSS folder.

Honest limits — please read before paying

• We do not send email ourselves. Use the calendar or webhook above, or turn the feed into email in about a minute: your alert page has a one-click Get these alerts by email button that opens Feedrabbit (free, no time limit, checks every 3 hours) with your private feed address already filled in — you type your email and nothing else. Blogtrottr and any RSS reader work too. If you would rather buy email outright, Layoff Lookout (17 states) sends it and starts at $2/mo.
• 48 states, not 50. The states we do not cover are listed on the dataset page; a state is added the day it publishes a usable public listing.
• We are as fast as the state agency. Some portals publish same-day; some post in weekly batches. We alert the day our scrape sees a notice — we cannot beat the source.
• No archive spam. When a state republishes its back catalogue, thousands of old notices arrive at once. A notice whose own date is more than 120 days older than the day we first saw it is treated as history, not news, and never paged to you.
• Matching is token-based, so subsidiaries and re-notices are caught but the occasional near-miss happens. Every alert links to the employer's page so you can check.
• Your page address is unguessable, not secret — here is the exact threat model. Sales and recruiting teams treat a target list as competitive information, so you should know precisely how yours is held. Your alert page lives at /alerts/<random 128-bit token>/ on a public static host (Hugging Face Spaces). The token is assigned at fulfilment and is not derived from your email or your page key, so nobody who knows either can compute it; the email + page key finder uses a separate, deliberately slow lookup (PBKDF2, 600,000 rounds) — but the host does publish a file list, so treat the address as unguessable rather than confidential. What the page can reveal to someone who has the address is the employer and state terms you gave us and the public WARN notices that matched them; it never holds your name, your email, your payment details — and it never holds a credential of yours, because we do not collect any. If a published page is not good enough for your list — and for some teams it should not be — reply to your receipt and ask for unpublished delivery: nothing at all is published for you (no page, no RSS file, no calendar, no list report) and matches go only to a delivery address you control. Already bought? Reply to your receipt — the switch (or a reissue of your page at a fresh address, if you just want to rotate it) takes effect on the next daily rebuild, and any page we had already published is deleted in that same rebuild.

“Can’t I just filter your free RSS feed?”

For one employer in one state: yes, and you should. Every state we cover has a free RSS feed on this site (OPML bundle, or feeds/<state>.xml), the whole dataset is free CSV, and a keyword rule in Zapier or your reader takes about five minutes. If that is your situation, keep your $49 — we would rather be useful than paid.

Here is the part a keyword rule cannot do, measured on the 61,345 notices in this build:

• Every alert carries the employer’s filing record. Not “this employer filed a notice” but “Boeing — 416th WARN notice from this employer since 1998 · 14 states · 43,948 workers to date · last filed 2025-04-04 · 1 of 5 locations this employer filed in CA that day” — computed against the full 1988-present archive at the moment we alert you. A feed carries only the new item; the history is not in it, and 51% of notices come from an employer that has filed before. See it on the live sample page.
• Every alert links to the official filing. Each match carries a link to the state agency’s own WARN page — 41 of our 48 states, every link checked live on 2026-09-09 — because the filed notice is where the site address and exact dates are, and in many states the employer contact named on the notice, and a trigger you cannot verify is not one you can act on.
• One rule, 48 states. 2,758 employers in this archive have filed in more than one state (the record is 37). A per-state feed rule is 48 rules to build and 48 to keep working.
• One alert per employer-day, not one per location. The largest single filing here is 102 separate notices from one employer, in one state, on one day — 102 feed items, one line from us.
• Nothing to keep running. When a state changes its portal, we fix the scraper; your rule would just quietly stop matching, and a watch that fails silently is worse than none.

The alternatives, compared honestly

Competitor rows are read from each vendor's own public pricing page (checked 2026-09-02); our rows come from this pipeline's live coverage file (generated 2026-09-19). If a price here is out of date, tell us and we will fix it — open an issue.

The data behind the alerts

61,345 normalized notices across 48 states, newest notice on file 2026-09-16, rebuilt every day. The dataset itself is free and open (CC BY 4.0) — you are not paying for records, you are paying for someone to run your list against them every morning for a year and hand you only what changed. If you would rather build that yourself, the files are right there and we will not be offended.

Who you are paying

Sold by APProjects (Gumroad seller "approj"), the same operator that publishes the open dataset at github.com/APVentureEngine/warn-act-notices. Receipts and invoices are issued by Gumroad. Questions before or after buying: the Contact link on the Gumroad page, or open a GitHub issue — issues are read on every refresh cycle, daily or better.

Sources: official state labor-department WARN listings, collected with the Apache-2.0 biglocalnews/warn-scraper plus our own normalization, dedup, employer canonicalization and freshness layer. Best-effort public records; verify critical rows against the official state source. Not affiliated with any state agency. Nothing here is legal or employment advice.