APProjects/district-of-columbia-layoffs-warn-act-notices-daily

District of Columbia WARN Act layoff notices — every filing we hold since 2017, one CSV, rebuilt daily

143 District of Columbia WARN notices — every one this dataset holds, back to 2017 — free to download in full: no paywalled years, no login, no account · most recent notice filed 2026-07-27 · state source last checked 2026-09-11T12:19Z · official source: District of Columbia Department of Employment Services — WARN notices.

District of Columbia employers must file a WARN Act notice with the state before a qualifying mass layoff or plant closing. This page is generated from those filings, cleaned into one schema shared with 47 other states, and rebuilt every day. Nothing here is behind a login.

The data above is free forever — CC BY 4.0, no login, no API key, no delay, rebuilt daily.

If you only care about particular employers or states, you do not have to re-download the whole file and diff it yourself. WARN Watch runs your list against every daily refresh and gives you a private alert page, a calendar (.ics), an RSS feed and an optional Slack/Discord/Teams webhook — no login.

Try it free for 30 days — no card (up to 3 employers or one state) · then $49/year, one-off, no auto-renew, 14-day refund · see a real alert page first

Download District of Columbia layoff data

The file in this repository, data/dc_warn_notices.csv, is byte-identical to the free per-state file on GitHub linked below; the other files are the all-state siblings.

What	File
District of Columbia notices, all years (CSV, free)	data/by-state/dc.csv
All 48 states, all years (CSV, free)	data/warn_notices.csv
All 48 states (JSON, free)	data/latest.json
District of Columbia RSS feed	feeds/district-of-columbia.xml
Notice-period analysis, every state × year	data/notice_period_by_state_year.csv
Browsable page with search and charts	District of Columbia on the live site
Same data on Hugging Face	APProjects/us-warn-act-layoffs-notices-daily

Licence: CC BY 4.0 — use it commercially, just credit the source.

Most recent District of Columbia notices

Employer	Location	Employees	Notice filed	Effective
Elevance Health	Washington, DC	85	2026-07-27	2026-10-02
General Dynamic Information Technology	Washington, DC	64	2026-07-13	—
Medical Facility Associates	Washington, DC	1,270	2026-07-08	2026-09-06
Ideal US Talent Systems Worker Op Co LLC	Washington, DC	307	2026-05-01	2026-07-01
Republic National Distributing Company	Washington, DC	125	2026-04-23	2026-06-21
Noblis	Washington, DC	115	2026-04-22	—
General Dynamics Information Technology	Washington, DC	87	2026-04-17	2026-06-15
Bering Global Solutions, LLC	Washington, DC	108	2026-03-13	2026-03-31
Albertson's/Safeway	Washington, DC	87	2026-03-13	—
WP Company LLC	Washington, DC	277	2026-02-06	2026-04-10
Elior North America	Washington, DC	76	2026-02-02	2026-06-30
RATP DEV and Midtown Group	Washington, DC	52	2025-10-29	2026-01-03

Newest 12 of 143 free-window District of Columbia notices. The complete file is the CSV above — every notice we hold for this state, back to 1988, free and rebuilt daily.

How much notice did District of Columbia workers actually get?

No District of Columbia notice in the archive carries both a notice date and an effective date, so no notice-period statistic is available.

Year	Notices with both dates	Under 60 days	Share
2026	8	3	n<30
2025	20	5	n<30
2024	8	0	n<30
2023	4	0	n<30
2022	5	0	n<30
2021	2	1	n<30
2020	18	11	n<30
2019	9	2	n<30
2018	4	1	n<30
2017	5	1	n<30

Read this before quoting the notice-period numbers. Several states publish the date the state received the filing rather than the date workers were notified, so an interval a little under 60 days is frequently state processing lag rather than a short notice. That is why this dataset publishes state-level and year-level shares and never ranks named employers by notice length.

Method and exclusions: notice-period analysis.

Track District of Columbia layoffs without polling this file

• Star the repo or watch releases — GitHub tells you each day the snapshot republishes.
• WARN Watch — $49/year — name up to 500 employers or whole states; every daily refresh matches them and pushes hits to a private page, a calendar (.ics), an RSS feed and your Slack / Discord / Teams webhook. No login. Free 30-day trial — 3 employers or 1 state, no card.
• Full 1988→ archive — free — every state, every year, one schema.

Something wrong in a District of Columbia row? Open an issue — it gets fixed the same day.

---

← all states · repository home · data as of 2026-09-12 · rebuilt daily by an automated pipeline.

A layoff record you can audit, not just download

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

Several projects publish a current WARN scrape and two of them carry more rows than we do. None of them publish what the records used to say:

• 616 observed changes to already-published notices, logged daily since 2026-08-31. data/revisions.csv records every field that differed between two consecutive daily builds — employee counts, effective dates, notice types, company names — with the old value, the new value and the date we saw it. We publish the observation and not the cause: a change is equally explained by the agency amending the notice or by our own parser improving, and we do not guess which (see data/revisions.README.txt). A scrape that starts tomorrow cannot backfill any of it; it only exists if someone was watching.
• 6,799 notices whose state agency page no longer lists them. Agencies take notices down. We keep them, flagged as archive-only, so a count you ran last year still reconciles.
• Point-in-time employer identity. The ticker crosswalk resolves a filer to the company as it existed at the time of the notice — Kmart, Sears Holdings, Symantec — not to whatever is on today's ticker file.

If you have to defend a number to an editor, a referee or a compliance reviewer, that provenance layer is the part you cannot rebuild yourself. How to cite this dataset →

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 →

Need one industry only? The same filings, cut by an auditable employer-name rule (each row keeps the rule that fired): tech companies · hospitals & healthcare · retail store closings · restaurants & hotels · factory & plant closings · banks, insurance & finance · warehouses, trucking & logistics · all 20 sectors.

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

Not deciding today? Join the update list → — one email when a new dataset or tier is published; nothing promotional. A state added or a column renamed ships in the daily release instead, no address needed. The list is shared across APProjects datasets, holds an email address only, is run by Gumroad, and any message unsubscribes you. Rather give no address at all? Watch the repo's releases — GitHub notifies you on every daily republish, and a new state or changed field is in those notes the day it lands.

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

_{Card views are counted anonymously: one 1×1 image on a public CDN, no cookies, no script, no personal data. The count is public: jsDelivr stats.}