Standards · How we work

Changelog

A dated record of real changes to PlainLayoffs's dataset: corrections, data refreshes, and features. See the editorial & corrections policy for how reports are verified. We never backfill or invent an entry; a gap between dates means nothing changed.

See the editorial & corrections policy for how reports are verified, and the methodology page for how the dataset is built.

  1. Feature

    Added a per-employer shareable social-preview image (visible when a page is shared to X, LinkedIn, or another platform), showing the employer name, industry, state, and total workers affected.

  2. Correction

    Cleaned 6 employer records whose name field had picked up raw HTML and a state agency's footnote text during ingestion (for example, a note about a late or corrected filing), which was rendering verbatim in the page title and headline. Two of the six turned out to be duplicate entries for a company already tracked cleanly elsewhere; those were merged into the existing record rather than left as a second page.

  3. Correction

    Fixed the "Workers Affected by Year" chart on every employer detail page, it was showing 0 for every year due to a field-name mismatch in the chart code, even though the correct total was displayed correctly everywhere else on the same page.

  4. Correction

    Corrected 8 notice records with an implausible effective date (predating the WARN Act or set more than two years before the notice was filed) to use the filing date instead.

  5. Correction

    Identified and merged 76 duplicate employer records (38 groups of the same company ingested more than once under slightly different name spellings) into a single page per employer, consolidating their WARN notice histories.

  6. Data refresh

    Refreshed and re-verified the full dataset against the latest published WARN Act notices from every covered state agency.

  7. Launch

    PlainLayoffs launched, tracking WARN Act mass-layoff and plant-closing notices filed with state workforce agencies.

Found an error? Report a data issue and we'll verify it against the source filing and, if confirmed, fix it at the source and log it here.