Ask The Recruiter
Adapt my resume

AI Layoff Tracker

Every entry links to the filing, notice or report it came from.

Search the record How we count For press Press kit and soundbites Weekly or daily Email digest

At a glance: today, this week, this month, the last completed month and quarter, and this year

An entry is one layoff reported by one employer. Workers counts people.

Date
Count Layoffs By
Quick Views
Results summary
… Verified job cuts
iCounted on the day each cut was filed or announced. This is the basis layoffs are reported on elsewhere, so this figure can be set beside a national estimate for the same month. It is not the same measurement: we count only cuts with a public filing or named report behind them. Every row behind it links to its source.
 counted by filing date
… Announced job cuts (planned)
iCompany plans at announcement stage, not yet in Verified.
…Companies
iCoverage in this view: how many distinct employers, industries, countries and US states the current filters return.
 … industries … countries with reported layoffs … US states
… 🤖 AI cuts, verified (specific)
iVerified-tier cuts where the employer named AI, in words we hold and can quote. We report the stated reason. We do not decide the cause. Examples: “AI now handles this work” or “replaced by AI.”
… 🤖 AI cuts, announced (planned)
iAnnounced-tier plans that name AI, like “cutting roles as we adopt AI.”

Derived totals, and why they do not add up with the tiles above

Each of these is built from the tiles above rather than counted separately, so adding one of them to those tiles would count the same cuts twice.

… Verified + announced job cuts
Both tiers together. One cut can appear in both stages (an announced plan often becomes a verified filing later), so this is not a count of distinct people.
… 🤖 AI cuts, total (specific) The two AI tiles above, summed: cuts the employer or plan explicitly named AI for.
… 🤖 AI-linked, broad (wider lens)
A separate, looser measure. Counts press framing like “amid AI push” as well as employer statements, so it is wider than the strict AI figure by design and never sums with it.

Looking for who is hiring instead? Hiring signals are tracked separately. Talent Intelligence Tracker

Why our number is lower, and why it’s the one to cite

Announcement surveys count what companies say. We count what you can prove. Every figure on this page clicks through to a legal filing or a named report. So our total is a documented floor: smaller than the headline estimates by design, and verifiable by design.

They book multi-year plans on day one. A “20,000 over two years” announcement lands in their total instantly. We add each cut as its WARN notice or SEC filing actually appears.
They fold in receiptless separations. Buyouts, attrition, and federal-workforce reductions that name no company and file nothing. Hundreds of thousands of jobs with no document to link. We don’t claim what we can’t source.
We don’t pad to match a bigger headline. A number a journalist can verify is worth more than a bigger one they can’t. Nothing here is estimated into existence.
On AI, the thing this tracker exists for. Every flagged cut carries the employer’s own words naming AI. Those words are quotable and clickable, and we hold them to a standard the estimates don’t apply to themselves.

Every figure links to a primary source, and every correction and merge is disclosed in the open log. Nothing is quietly edited. How we count →

Where the cuts are

Geography first: the map plots every cut with a named place, then the state and country rankings below it.

The map of job cuts blue = all job cuts · red = AI-attributed cuts, the employer’s own words (sits inside; small red dots are kept visible even when the share is tiny) · circle size = number of jobs · tap a bubble to filter, tap the map to zoom · hover for exact numbers, expand ⤢ for a bigger view · only cuts with a named country or state are plotted; the rest are counted in the totals but not on the map

Layoffs by US state AI share · tap to filter · our documented cuts, not jobless claims
Layoffs by country AI share · tap to filter

How it is trending

The same filtered data over time: monthly totals with jobless-claims context, this year against last, and how often employers name AI.

Jobs cut per month Verified job cuts we can document, dated to the month each cut takes effect. Tap a month to filter the whole page to it; tap again to clear. ·
iThe solid line is verified cuts; the dashed line is announced plans, never mixed into the verified line. The small strip under the chart shows the whole record and where the charted window sits. The optional grey overlay is official US jobless claims on its own right-hand axis, for scale only.
This year vs last year verified cuts · select 2+ years to compare more
AI share of verified cuts, monthly how attribution is trending · tap a month to scope the page, again to clear
Cumulative AI-attributed cuts

Who is cutting, and why

Industries, stated reasons, the biggest single layoffs and repeat cutters, plus which data source each figure came from.

By industry AI share · tap to filter
Reasons cited tap to filter
Largest single job cuts AI share · tap to filter
Repeat layoffs companies with 2+ rounds in this period · tap to filter
By data source AI share · tap to filter
AI intensity by industry share of each industry’s cuts the employer attributed to AI · tap to filter · industries under 1,000 cuts excluded

Each share is the employer’s own words, not our inference. See the verbatim quotes and their sources →

Roles most impacted Each bar is total job cuts for that team; the orange part and 🤖 number are the AI-attributed share. From only the reports that named which teams were cut.
Loading…
CSV JSON

    Covering Jan 2002 to Aug 19, 2026 · 72 countries · 46 US states + DC Sources · How complete, measured · Corrections · Hiring is tracked separately

    Cite this tracker · CSV · JSON · API

    ★ Monthly report (1-pager) · AI layoffs, in the employer's own words · Embed this tracker

    Frequently asked questions
    What is the AI Layoff Tracker?

    A free, continuously updated layoff tracker covering verified job cuts worldwide across all industries and causes. It flags which layoffs companies explicitly attribute to AI or automation. Every entry links to a primary source: a SEC 8-K filing, a US state WARN notice, or a named news outlet with the exact quote.

    How many layoffs have there been in 2026 so far?

    So far in 2026 the tracker holds 2,947 verified layoff entries totaling 522,255 job cuts worldwide, counted by effective date: the day each cut takes effect, with anything dated later than today left out. Companies explicitly blamed AI for 42,953 of those cuts. The totals on the tracker page itself are counted by filing date by default, which is a different question and a different number for the same year, so the two are not meant to match; the date basis switch on the page moves between them. Totals update daily as new filings and reports are verified.

    Where does the layoff data come from?

    Four kinds of sources. SEC 8-K filings, searched twice daily. Official WARN notices from 46 US states and DC, imported daily with no AI processing. The European Restructuring Monitor, Eurofound's per-company database of announced restructuring across the EU27, Norway and historically the UK, which its national correspondents compile from media reports rather than from government filings (imported daily and credited to Eurofound; because these are announcement-stage figures, they feed the separately labeled "Announced" tier and never the verified totals). And worldwide press coverage in 65+ languages through the GDELT news index plus Google News, read across 45 national editions. The dataset spans 2002 to the present across 72 countries, 65,034 entries in total.

    What sources do you use?

    Official government filings and legally required notices first: every SEC 8-K/6-K filing and official WARN mass-layoff notices from 46 US states and DC (each a live link on our Data Sources page). For the EU we read Eurofound's European Restructuring Monitor, an EU agency database compiled by national correspondents from media reports rather than from the confidential notifications employers file with labour authorities. Worldwide, we add named news coverage in 65+ languages from an editorially maintained trusted-outlet allowlist. Nothing is estimated; every number links back to one of these. The Data Sources page lists each one, with links to check the raw source yourself. See the full Data Sources page →

    How is this different from other layoff trackers?

    Announcement surveys count corporate intentions on the day of the announcement. This job layoff tracker counts what has a verifiable document or quoted primary source behind it, so it is a documented floor rather than an estimate. Announcement-stage cuts are also tracked, but in a separately labeled tier that is never mixed into the verified totals.

    Why is our number different from other layoff trackers?

    Three reasons, and all of them point toward a number you can check. First, we require a document behind every row, so a cut with no filing and no named report never enters the total. Second, we are deliberately conservative and land within about 10 percent of independent WARN trackers, so our figure is a floor you can trust rather than a high estimate. Third, we never inflate a total by counting a company-wide headcount on every state filing: when one notice lists a nationwide figure, we count only the jobs in that state, so one layoff is never summed several times. A tracker reporting several times higher is usually doing exactly that.

    What if a source only says "up to" a number?

    We record the figure the source states and keep its qualifying words with the entry, because inventing a lower number would be a guess and dropping the entry would hide a real cut. So a report of "up to 600 roles" is stored as 600 with that wording retained, which makes it a ceiling rather than a measured total. This is the one place our figures can read high, so we name it rather than bury it. Where a source gives a true range ("400 to 500"), we take the lower bound and keep the upper bound in the data as well.

    How do you check your own accuracy?

    By auditing ourselves against our own sources. Every month an automated audit draws a random, stratified sample of published entries and re-opens every cited source to confirm the company, the number and the date. Entries from official filings and notices consistently match exactly; anything that fails is corrected or removed, usually the same day, and the correction is disclosed in the log below. The latest audit result is always published live on the Tracker Health page, so the number you see there is current, not a snapshot. See the latest audit result →

    Can journalists and researchers use this data?

    Yes, free with attribution to asktherecruiter.com (CC BY 4.0). Filtered or full CSV and JSON downloads are on the page, and a public REST API serves the same data. Corrected entries are publicly flagged, and every correction to published figures is disclosed in the on-page corrections log.

    How often is the tracker updated?

    Continuously. News and SEC filings are collected twice daily (morning and after US market close, ET); official WARN notices and Eurofound ERM records import daily; and the daily summary, stats, charts and table read live data on every page load. The Tracker Health page shows every collector's latest run in real time.

    What is the difference between "verified" and "announced" job cuts?

    Verified cuts have a filing or independently reported source behind them: a WARN notice, an SEC filing, or a named outlet's report of cuts taking place. Announced cuts are company plans reported at announcement stage, tracked in their own labeled tier and never mixed into the verified totals, because announced plans can shrink, stretch over years, or partially happen through attrition.

    How do I report an error?

    Use the contact page and corrections get priority. Every entry links to its primary source, so you can check any number against the underlying document.

    Methodology & sources (for journalists & researchers)

    The short version. Verified job cuts are cuts with a filing or named source behind them; the main figure. By default we count each on the day it was filed or announced, the basis used elsewhere. The “Count layoffs by” control recounts the page on the effective date instead. AI-attributed is the subset where the employer named AI in words we can quote. Announced is a separate, labeled tier of announcement-stage plans, never mixed into the verified total. Nothing is estimated; every number links to a legal filing or named report, and country/US-state filters describe where the jobs were, not an employer’s headquarters.

    How the AI tag works. Only a primary or contributing cause counts, and each one needs an exact supporting quote. Investment in AI, future projections, or AI used to pick who goes do not qualify. A separate broader measure is labeled and never merged in.

    Read the full methodology and sources → · extraction, dedup, coverage limits, why our totals differ, and API access, all in detail.

    Where do we get this data? Every source, by country

    We collect official government filings and notices directly: SEC EDGAR, including Item 2.05 exit-cost filings, and WARN notices from 46 US states and DC. For the EU we read Eurofound ERM. It is the EU agency’s own restructuring database, but its national correspondents compile it from media reports. The filings employers make to labour authorities stay confidential. We also monitor press-release wires and reviewed company investor-relations feeds. And 705 reviewed news outlets across 180 countries surface coverage through GDELT’s 65-language index and Google News. We work from an allowlist and never crawl those outlets directly. Every published entry links to its source. A handful of US states publish no usable WARN register: Arkansas, Wyoming, New Hampshire, Missouri, Hawaii and Oklahoma. For those states we also show the official monthly unemployment rate from the US Bureau of Labor Statistics, sourced and dated. It is a clearly separate context metric, and we never mix it into the layoff counts. See the full source directory.

    How complete is that, measured? We enumerated every SEC 8-K filed between 1 July 2025 and 30 June 2026 that qualified for this test. A filing qualified if its structured filing header carries Item 2.05 and it states an absolute number of affected employees. Then we checked how many appear here. 56 of 57, or 98% (95% confidence interval 91% to 100%). So this is a floor and not a census, and it is why the page does not claim to hold every filing. Where a count is published, it is accurate: 39 of 40 checked figures appear verbatim in the cited source. That measurement covers one source family over one year. It says nothing about private employers, non-US layoffs, or the WARN and news routes, which we count separately. We re-measure it weekly against the same frozen filing list, so this paragraph updates as capture improves.

    The full outlet directory, every country and every reviewed outlet we scan with each country’s official register, lives on the Data Sources page, generated straight from the collector’s own allowlist.

    Do announced cuts actually happen?

    Share of each month’s announced job cuts that show verified records (filings or sourced reports) from the same company within 6 months. Matches are capped per announcement, so a month can never exceed 100%.

    Which countries are in which region tab?

    The region tabs are views over the worldwide data. The full country list for each tab loads here.

    Why our numbers differ from other trackers

    Every tracker measures a different thing, so the numbers should differ. We count verified entries: cuts with a filing or named-outlet source behind them, each one clickable. The big announcement trackers count corporate intentions. Neither is wrong; they answer different questions. Our total sits below the headline announcement estimates, and the gap is fully explainable, here is exactly why, and why we treat it as a feature, not a shortfall.

    1 · They book multi-year plans on day one; we count cuts as they happen. When a company announces “20,000 cuts over two years,” the announcement trackers record all 20,000 that day. We add each cut as its WARN notice or SEC filing actually appears. Over a year that is a large, permanent gap, their figure is a forecast, ours is an execution ledger.

    2 · They include separations that name no employer. Announcement totals fold in voluntary buyouts, deferred resignations, and attrition programs, including large federal-workforce reductions that file no WARN notice and name no company. In 2025 that was roughly 250,000 to 300,000 jobs of the announcement total alone. There is no document or named source to link, so we do not claim it.

    3 · They count cuts no outlet ever named. Announcement surveys aggregate press mentions and estimates we cannot reproduce. We only publish what traces to a source, so an unsourced cut never enters our total.

    4 · We count each cut on the day it was filed, and you can recount it on the day it takes effect. Layoffs are reported nearly everywhere on the filing date. The US national survey counts announcements made during a month. Our default counts each cut on the day its notice was filed or the cut was announced, which is the same question. So the figure at the top of this page is dated the way a national estimate for the same month is dated. The two are worth setting side by side. They are not the same measurement. We count only cuts with a filing or a named report behind them. A national survey also counts federal job cuts, buyout offers and employer estimates that never produce a public document. So in any given month our total can land above or below theirs. The effective date answers a different and equally real question: when the jobs actually ended. That is what a worker lives through, and what a labour-market reader often wants. Neither basis is the true one. When it was filed is the default, and the one that lines up with the survey. Set “Count Layoffs By” to When it takes effect and every figure, chart and table here is recounted on it. The gap between the two is not noise. A notice filed in May for a July closing sits in May on the default and in July on the other. In any given month the two totals can differ widely. The line under the headline figure shows how they split. On either basis, every row we count has a filing or a named report behind it.

    The bottom line, stated plainly. Our verified figure is a documented floor. It is smaller than the estimates, but every single number clicks through to a legal filing or a named report. We deliberately do not pad it to match a headline estimate. A number a journalist can verify is worth more than a bigger one they cannot. That holds on the measure this tracker exists for too, layoffs companies attribute to AI. Compared like for like against an announcement survey’s AI figure, ours is much smaller, and we would rather say so than pick the widest slice we have. A survey codes a reason from what an employer reports to it. We require the employer’s own words, with the source behind them. So what we offer there is not a bigger number. It is that every attribution can be read back to the sentence the employer actually said.

    Where we lead, and where we don’t, stated honestly. Because our figure is built from receipts, it is not always smaller. Measured like-for-like against the public trackers by category:

    • Against WARN-only aggregators (the legally-filed US floor), we come out higher. We import the same WARN notices, then add SEC filings and named-news reports on top. Our US verified total clears the WARN floor rather than stopping at it.
    • Against tech-event trackers, our worldwide technology job-cut total is at or above the largest of them by volume. We carry fewer tiny private-startup events, but more total tech job losses. We catch the big filed cuts they sometimes miss.
    • On AI attribution, we run lower than an announcement survey’s AI figure, and that is the one place readers most expect us to claim otherwise. A survey codes a reason from what an employer reports to it privately. We require a quote we can show you. So we only ever hold the subset that was said in public. Our broader AI-linked tier is wider than our strict one, and neither is a claim to have found more AI-driven cuts than a survey counted.
    • Against announcement surveys’ all-industry total, we run lower, on purpose: the gap is receiptless cuts (federal-workforce reductions, buyouts, attrition, and small closings that file nothing). We do not claim what we cannot source.
    • On coverage no one else offers, we are the only one of these measuring the global, all-industry, source-linked universe. Everyone else is US-only, tech-only, or a survey.

    Where each kind of tracker fits:

    • Announcement surveys, monthly totals of announced US cuts from press reports and company statements, including estimates and multi-year plans. Typically published as press releases; no per-layoff public database.
    • Editorial newsroom trackers, selected major announcements with newsroom verification. No downloadable dataset; selective by design.
    • Sector trackers, technology-focused trackers built from announcements and crowdsourced reports. Their scope matches our Technology filter, not our all-industry total.
    • Official statistics, US BLS JOLTS, UK ONS, Eurostat count all separations economy-wide (millions/month) with no company detail. A different universe entirely.
    • This tracker, verified entries in the headline, announcement-stage figures in a separate labeled tier, corrections logged openly, data and code public. When our number differs, the difference is definitional, and both definitions are stated here so either can be cited correctly.
    Known gaps & why the country count changes

    The full directory of every pipeline, the SEC, all state WARN registries with live links, Eurofound ERM, and the news index, lives on the Data Sources page. The disclosures below cover what is not yet included.

    Why the country count grows over time. The number of countries is not a setting we can raise; it reflects where large, press-covered layoffs have actually happened in our window. GDELT already searches every country on earth in 65+ languages, so a country appears the moment a credible outlet there covers a qualifying layoff. As layoffs occur and as we add more trusted local outlets, the count rises on its own. This is honest by design: we show the countries where verifiable layoffs exist, not a padded list.

    Known gaps, stated plainly. We do not yet operate direct connectors for Canada SEDAR+, UK RNS, ASX, TDnet/EDINET, NSE/BSE, HKEXnews, SGXNet, SENS, DART or TASE. We maintain them as official-source research candidates. We will name one as live only after a stable public interface, tests and source-health monitoring exist for it. A few countries also publish official per-company redundancy records we do not ingest yet, including Belgium’s FPS Employment collective-dismissal reports, Italy’s weekly CIGS decree lists, and Sweden’s varsel statistics. Most countries, including Germany and Mexico, treat employer identity in redundancy filings as confidential, so press coverage through GDELT in local languages is the primary source there. Layoffs too small for any press coverage, any WARN threshold, or the ERM threshold of 100 jobs will not appear in any tracker, including this one.

    Data notes & corrections log

    Corrections are dated and described here, newest first, and corrected rows carry edited: true in the API. Nothing is quietly edited. Each entry has its own anchor link, so a correction can be cited by URL.

    Origin, computed from the log entries themselves. Of the 200 machine-written entries below, 140 name an internal audit or automated check as the trigger. Another 3 name an external report. The remaining 57 do not record an origin, so they are counted as unrecorded, not assigned one.

    For reproducible monitoring, the machine-readable quality status endpoint reports dataset revision, recent corrections, collector health, retained-source integrity and the status of each coverage workstream. Pending work is shown as pending, not silently treated as coverage.

    • 2026-08-19: 3 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-19: 1 entry corrected (fields: ai_explicit, ai_causation, updated_at). Methodology #m-ai AI-skills-swap rule: cuts made in order to hire people with stronger AI skills do not earn the strict AI tag, because the test is whether the work went away or the required skill changed. The GM IT work continued and only the skill profile demanded of the people doing it changed. The GM statement named no AI – "GM is transforming its Information Technology organization to better #
    • 2026-08-19: 1 entry corrected (fields: ai_explicit, ai_causation, updated_at). Methodology #m-ai speaker rule: the strict AI tag requires the employer to have attributed the cuts to AI. This stored source text is a sources-say headline – "cuts hundreds of jobs in shift towards AI content moderation" – and the company confirmed only the number affected, not the reason. Reclassified to the broad AI-linked tier. Job count, date and source are unchanged. #
    • 2026-08-19: 1 entry corrected (fields: ai_explicit, ai_causation, updated_at). Methodology #m-ai speaker rule: the strict AI tag requires the employer to have attributed the cuts to AI. This stored source text carries the reporter own generic line – "Driverless technology is only just starting to cause layoffs" – while the headline attributes the complaint to a union. The Suncor statement quoted in the text announces a driverless truck fleet, not job cuts. Reclassified to th #
    • 2026-08-19: 1 entry corrected (fields: ai_explicit, ai_causation, updated_at). Methodology #m-ai speaker rule: the strict AI tag requires the employer to have attributed the cuts to AI. This stored source text carries only the reporter framing – "The layoffs are part of a bigger push by Microsoft to rely on artificial intelligence to pick news and content" – with no statement from Microsoft. Reclassified to the broad AI-linked tier. Job count, date and source are unchanged. #
    • 2026-08-19: 1 entry corrected (fields: ai_explicit, ai_causation, updated_at). Methodology #m-ai speaker rule: the strict AI tag requires the employer to have attributed the cuts to AI. In this stored source text the AI claim belongs to a third party – "It also claims that TikTok is looking to replace the moderators with artificial intelligence-driven systems" – and not to TikTok. Reclassified to the broad AI-linked tier. Job count, date and source are unchanged. #
    • 2026-08-19: 305 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-19: 400 entries corrected (fields: reason_tags, updated_at). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-19: 10 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-19: 1 entry removed. 'laid off 14,000 employees last fall' – a retrospective mention in a 2026 Fortune article about AI, floored to 2025-01-01; not a January 2025 event #
    • 2026-08-19: 2 entries corrected (fields: country, updated_at). Revert of an incorrect automated country fill (2026-08-19). Row 68454 (Zepz): the source says the closure covered business units in Kenya AND Poland, so a single country is wrong; the layoff itself is 200 IT roles at a London-based company. Row 177396 (Cineverse): the quoted sentence is a total-headcount breakdown (145 in the U.S., 155 in India), not the location of the cut. Both return to blank, #
    • 2026-08-19: 3 entries corrected (fields: country, updated_at). Source re-read: the cited article states where the cut jobs were, and the stored excerpt did not carry that sentence. Country filled from an exact quote in the source body; no count, date, source or AI label changed. #
    • 2026-08-19: 27 entries enriched. SEC EDGAR filer-record domicile backfill (each filer's own principal executive offices, not the filing venue) #
    • 2026-08-19: 20 entries enriched. Curated employer-domicile registry backfill (deterministic public HQ facts for the largest multi-country events) #
    • 2026-08-18: 1 entry corrected (fields: country, updated_at). Country column held a US state name ("Kentucky"). Row is an NC WARN notice for a site in Lexington KY; the job-location country is the United States and the state is already recorded separately. Published as a country in the 2026-08-18 digest and in the tracker country filter. alt_normalize_country now folds US state names, so this class cannot recur. #
    • 2026-08-18: 1 entry corrected (fields: country, updated_at). Automated classification audit: a label mismatch flagged by a model and re-checked by a second pass of the same model (DeepSeek). Applied only to entries below 5,000 jobs; larger relabels are held for a person to review. #
    • 2026-08-18: 24 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-18: 400 entries corrected (fields: reason_tags, updated_at). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-18: 6 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-18: 1 entry reclassified. Automated source-evidence reassessment #
    • 2026-08-17: 1 entry corrected (fields: country, updated_at). Automated classification audit: a label mismatch flagged by a model and re-checked by a second pass of the same model (DeepSeek). Applied only to entries below 5,000 jobs; larger relabels are held for a person to review. #
    • 2026-08-17: 2 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-17: 33 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-17: 400 entries corrected (fields: reason_tags, updated_at). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-16: 1 entry removed. Undated duplicate cleanup: news/SEC rows with no date that duplicate a dated event of the same company and headcount (they had bypassed the date-gated dedup guard). #
    • 2026-08-16: 5 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-16: 10 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-16: 401 entries corrected (fields: reason_tags, updated_at). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-16: 2 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-15: 4 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-15: 50 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-15: 401 entries corrected (fields: reason_tags, updated_at). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-15: 11 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-14: 6 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-14: 1 entry corrected (fields: ai_causation, updated_at). Cloudflare tied the 1,100 cuts directly to AI. The CEO said the company is restructuring for the agentic AI era and that these are not the roles it needs for the future. #
    • 2026-08-14: 1 entry corrected (fields: country, employer_country, updated_at). Angi divested its international segment in 2024, so the roughly 350 person reduction falls on its North American workforce. US employer domicile. #
    • 2026-08-14: 1 entry corrected (fields: country, employer_country, updated_at). Coverage reports the 500 cuts fell across India and North America. Freshworks Inc. is a US company headquartered in San Mateo. #
    • 2026-08-14: 1 entry corrected (fields: country, employer_country, updated_at). The 8-K describes reductions across the company's operations, which span multiple African markets. Jumia Technologies AG is incorporated in Germany. #
    • 2026-08-14: 1 entry corrected (fields: job_count, layoff_date, country, employer_country, source_url, excerpt, updated_at). The stored 7,000 counted workers reassigned to AI roles, not the layoff. The same coverage reports roughly 8,000 employees notified of layoff on 2026-05-20. Corrected to the layoff figure. #
    • 2026-08-14: 1 entry corrected (fields: country, employer_country, updated_at). The 3,200 role Xbox reduction spans studios in the US, UK, Sweden and elsewhere. Microsoft disclosed no country breakdown. #
    • 2026-08-14: 1 entry corrected (fields: country, employer_country, updated_at). Nine Entertainment cuts at The Age and The Sydney Morning Herald, both Australian mastheads. #
    • 2026-08-14: 1 entry corrected (fields: country, employer_country, updated_at). Visa disclosed no geographic breakdown for the 2,600 cuts and a majority of its workforce is outside the US. Labeled Multiple countries with US employer domicile. #
    • 2026-08-14: 1 entry corrected (fields: country, employer_country, ai_causation, updated_at). Patreon is a San Francisco company and no non-US location was reported for the 93 cuts. CEO Jack Conte said AI has an impact on how the company operates and organizes. #
    • 2026-08-14: 1 entry corrected (fields: country, employer_country, updated_at). About 350 of the 620 cuts were in Israel, the rest across US and European offices. Labeled Multiple countries with Israeli employer domicile. #
    • 2026-08-14: 1 entry removed. Multi-company roundup article. The Visa, Intel, Uber and Patreon events are held as their own rows, so a combined 3,000 row counts them twice. #
    • 2026-08-14: 1 entry removed. The bank says AI could replace the work of 1,000 employees by 2028 through attrition, and states there is no plan for large-scale cuts. A projection, not a layoff event. #
    • 2026-08-14: 1 entry removed. The cited interview describes a projected headcount decline to below 2,000 employees by 2030, not a layoff event. #
    • 2026-08-14: 1 entry removed. The company disclosed only a percentage, approximately 7 percent of its workforce. The stored count of 7 jobs is a misparse and no primary source states an absolute figure. #
    • 2026-08-14: 1 entry removed. Duplicate of the Microsoft Xbox 3,200 role reduction announced 2026-07-06, held as its own row. This later article re-reports the same event. #
    • 2026-08-14: 1 entry removed. The cited article reports a fiscal year headcount decline from about 108,000 to about 97,000, which includes attrition. It is not a layoff announcement. Removed as unsupported. #
    • 2026-08-14: 1 entry removed. The cited article reports a cumulative IRS staffing decline of more than 31,000 since 2025, an aggregate attrition total. It is not a January 2026 layoff event. Removed as unsupported. #
    • 2026-08-14: 2 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-14: 2 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-14: 400 entries corrected (fields: reason_tags, updated_at). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-13: 1 entry removed. Undated duplicate cleanup: news/SEC rows with no date that duplicate a dated event of the same company and headcount (they had bypassed the date-gated dedup guard). #
    • 2026-08-13: 1 entry corrected (fields: industry, updated_at). Automated classification audit: a label mismatch flagged by a model and re-checked by a second pass of the same model (DeepSeek). Applied only to entries below 5,000 jobs; larger relabels are held for a person to review. #
    • 2026-08-13: 3 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-13: 400 entries corrected (fields: reason_tags, updated_at). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-13: 12 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-12: 4 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-12: 401 entries corrected (fields: reason_tags, updated_at). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-12: 18 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-12: 4 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-12: 3 entries corrected (fields: country, updated_at). ERM country reverted to the value Eurofound records. All three factsheets state Country = World, which this importer maps to Multiple countries. The rows had been edited to United States, putting 144,000 jobs into the US headline that Eurofound does not place there. #
    • 2026-08-11: 1 entry merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-11: 401 entries corrected (fields: reason_tags, updated_at). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-11: 19 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-11: 4 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-10: 2 entries corrected (fields: country, industry). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-08-10: 1 entry merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-10: 6 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-10: 402 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-10: 8 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-09: 1 entry corrected (fields: country). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-08-09: 2 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-09: 6 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-09: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-09: 10 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-08: 14 entries corrected (fields: country, industry). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-08-08: 3 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-08: 35 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-08: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-08: 5 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-07: 2 entries corrected (fields: country, industry). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-08-07: 5 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-07: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-07: 15 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-07: 3 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-06: 33 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-06: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-06: 8 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-05: 3 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-05: 11 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-05: 405 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-05: 4 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-04: 2 entries removed. Undated duplicate cleanup: news/SEC rows with no date that duplicate a dated event of the same company and headcount (they had bypassed the date-gated dedup guard). #
    • 2026-08-04: 4 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-04: 38 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-04: 403 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-04: 10 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-03: 9 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-03: 31 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-03: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-03: 6 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-02: 1 entry corrected (fields: industry). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-08-02: 13 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-02: 42 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-02: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-02: 8 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-01: 9 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-08-01: 16 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-08-01: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-08-01: 6 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-08-01: 2 entries removed. Undated duplicate cleanup: news/SEC rows with no date that duplicate a dated event of the same company and headcount (they had bypassed the date-gated dedup guard). #
    • 2026-07-31: 6 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-31: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-31: 20 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-31: 2 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-30: 22 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-30: 19 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-30: 416 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-30: 8 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-30: 1 entry removed. NV WARN parser glued city and county; parser fix deployed, next 9am ET import re-creates it correctly #
    • 2026-07-30: 3 entries removed. Undated duplicate cleanup: news/SEC rows with no date that duplicate a dated event of the same company and headcount (they had bypassed the date-gated dedup guard). #
    • 2026-07-29: 12 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-29: 1 entry enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-29: 2 entries removed. Undated duplicate cleanup: news/SEC rows with no date that duplicate a dated event of the same company and headcount (they had bypassed the date-gated dedup guard). #
    • 2026-07-29: 402 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-29: 7 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-29: 1 entry enriched. Automated source-evidence context enrichment #
    • 2026-07-28: 2 entries corrected (fields: country, industry). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-07-28: 3 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-28: 401 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-28: 5 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-28: 3 entries removed. Undated duplicate cleanup: news/SEC rows with no date that duplicate a dated event of the same company and headcount (they had bypassed the date-gated dedup guard). #
    • 2026-07-28: 73 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-27: 3 entries corrected (fields: country, industry). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-07-27: 1 entry merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-27: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-27: 6 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-27: 1 entry reclassified. Automated source-evidence reassessment #
    • 2026-07-27: 54 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-26: 2 entries removed. 2025 historical-year backfill honesty correction: phantom/double-count rows (Meta 8k = lawsuit allegation in a Fortune macro roundup; US-federal 5k = Benzinga commentary on Nov BLS drop; DOGE 10k = cross-agency aggregate double-counting VA/NOAA/IRS). -23,000 jobs. Per TECHLOG backfill #1. #
    • 2026-07-26: 6 entries removed. Undated duplicate cleanup: news/SEC rows with no date that duplicate a dated event of the same company and headcount (they had bypassed the date-gated dedup guard). #
    • 2026-07-26: 23 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-26: 407 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-26: 12 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-26: 134 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-25: 6 entries corrected (fields: industry, country). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-07-25: 5 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-25: 9 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-25: 390 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-25: 1 entry removed. ghost row: wiped meta (empty company + job_count 0) inflating entry/distinct counts #
    • 2026-07-24: 4 entries removed. FL WARN W-1511 test/sandbox notice: one WARN# spans AT&T+BOEING+BOEING test, fabricated counts (78788 fake) #
    • 2026-07-24: 2 entries removed. Undated duplicate cleanup: news/SEC rows with no date that duplicate a dated event of the same company and headcount (they had bypassed the date-gated dedup guard). #
    • 2026-07-24: 9 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-24: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-24: 6 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-24: 18226 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-23: 41 entries corrected (fields: country). Legacy repair: country filled from deterministic evidence (a US state code on the row, or a US state government WARN source). Rows without such evidence were left blank rather than guessed. #
    • 2026-07-23: 54 entries corrected (fields: company). Legacy repair: the notice's site address was stored inside the employer name, which split the company from its own other rows. Name normalized; no count, date or source changed. #
    • 2026-07-23: 1 entry corrected (fields: industry). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-07-23: 17 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-23: 4 entries removed. Undated duplicate cleanup: news/SEC rows with no date that duplicate a dated event of the same company and headcount (they had bypassed the date-gated dedup guard). #
    • 2026-07-23: 23 entries removed. Audit 2026-07-23: WARN notices the state later RESCINDED or CANCELLED. A withdrawn notice is a layoff that did not happen, so counting it added 5,050 jobs nobody lost. The importer now drops these at the boundary; these 23 stored rows are removed and their hashes suppressed. #
    • 2026-07-23: 1 entry removed. Audit #1 (2026-07-23): the cited Times of India source states Starbucks has not confirmed how many jobs will be lost; the ~1,000 figure in the stored excerpt is an earlier Seattle/Kent retail event already covered by WA WARN rows. Count unsupported by its own source. #
    • 2026-07-23: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-23: 21549 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-22: 22 entries removed. Undated duplicate cleanup: news/SEC rows with no date that duplicate a dated event of the same company and headcount (they had bypassed the date-gated dedup guard). #
    • 2026-07-22: 4 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-22: 309 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-22: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-22: 1 entry enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-21: 3 entries corrected (fields: industry, country). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-07-21: 11 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-21: 202 entries enriched. Curated employer-domicile registry backfill (deterministic public HQ facts for the largest multi-country events) #
    • 2026-07-21: 809 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-21: 1 entry enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-21: 1 entry enriched. Automated source-evidence context enrichment #
    • 2026-07-21: 77 entries reclassified. Automated source-evidence reassessment #
    • 2026-07-21: 15727 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-20: 29 entries enriched. Automated industry classification: company identity + retained excerpt, double-confirmed by two model passes, fixed vocabulary, blank fields only #
    • 2026-07-20: 1 entry corrected (fields: industry). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-07-20: 3 entries enriched. Automated source-evidence context enrichment #
    • 2026-07-20: 4 entries reclassified. Automated source-evidence reassessment #
    • 2026-07-20: 37 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-20: 2 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-20: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-19: 2 entries enriched. Automated role-category extraction from stored source evidence #
    • 2026-07-19: 1 entry corrected (fields: company). Company-name alignment: id 70595 (2026-07-13 Volkswagen 50,000) renames to Volkswagen Group so both statements group as one company. #
    • 2026-07-19: 400 entries corrected (fields: reason_tags). Reason-tag backfill: fixed-vocabulary tags classified only from the row's stored excerpt (ERM rows: Eurofound's own recorded restructuring type) #
    • 2026-07-19: 59 entries corrected (fields: reason_tags). Reason-tag backfill for 2026 seeded announcement events: ai_automation for employer-stated AI, possible_ai for broad press links, restructuring baseline. Aligns the Reasons filter and chart with the seeded rows. #
    • 2026-07-19: 1 entry corrected (fields: job_count, source_url, excerpt). 2025 audit batch 2: Nissan row 70233 stored the cumulative 20,000 figure; CBT News states 11,000 NEW cuts announced 2025-05-13 on top of the separately-recorded 9,000 from Jan (row 60932), storing both 20,000 and 9,000 double-counts #
    • 2026-07-19: 2 entries merged. 2025 audit batch 2: Recruit Holdings/Indeed/Glassdoor July 11 announcement of 1,300 cuts is triple-counted (rows 70339 Jul-10, 70341 Jul-11, 26457 Jul-11 all 1,300); keeper 26457 carries the AI attribution #
    • 2026-07-19: 4 entries corrected (fields: job_count, source_url, excerpt). 2025 historical-year audit: conservative-count corrections to the employer's own announced figures (Amazon press release states ~14,000 corporate roles vs the Reuters up-to-30,000 estimate; GM announced 1,750 indefinite layoffs vs the 1,200 Factory Zero slice; Target confirmed ~1,000 layoff notices with 800 vacant roles inside the 1,800 headline; Blue Origin ~1,400 = 10% of ~14,000 per Reuters/Via #
    • 2026-07-19: 20 entries merged. 2025 historical-year audit: confirmed duplicate rows of the same announcement (dossier: UPS Oct-28 48K disclosure duplicated by a Challenger-roundup row and superseding the Apr-29 20K stage; IRS Apr-5 same-day pair; HHS Mar-27 RIF quadruplicated plus FDA/agency sub-slices of the announced 10K breakdown; State Jul-11 pair (keep conservative 1,300); Education Jul SCOTUS row re-reporting the Mar RIF; #
    • 2026-07-19: 7 entries corrected (fields: industry). Industry precision pass on batch-3 seeds: e-commerce, travel and media companies had defaulted to Technology; corrected through the fixed vocabulary. #
    • 2026-07-19: 251 entries enriched. Curated employer-domicile registry backfill (deterministic public HQ facts for the largest multi-country events) #
    • 2026-07-19: 3 entries corrected (fields: industry, country). Automated classification audit: label mismatch flagged and independently confirmed by two LLM passes (DeepSeek) #
    • 2026-07-19: 15 entries merged. Daily cross-source dedup: same layoff event reported by multiple sources, confirmed by DeepSeek #
    • 2026-07-15: Florida test rows removed, 87,600 jobs. Florida’s official WARN export contains internal test entries, which are fictitious notices sharing one WARN number and using non-existent zip codes. Eight such rows were removed, the largest a fake 78,788-worker “AT&T” notice that briefly ranked as our biggest entry. Our importer now skips test-named rows, and each removed row is permanently blocked from re-import. #
    • 2026-07-15: Country assigned to 88 news and SEC entries. These rows had no country recorded, which hid them from the regional views and country charts, though they were always in the worldwide totals. Each was resolved from its own source article. The largest were Oracle (30,000, spanning the US, India, Canada, Mexico and Uruguay, so “Multiple countries”) and BBC (2,000, United Kingdom). #
    • 2026-07-15: Ideal US Talent Systems RI corrected from 9,891 to 2. The Rhode Island notice states the company-wide figure, but only 2 RI employees are affected. The per-state filings for DC, GA, IL and VA are already separate entries. Counting the company-wide total under RI double-counted the layoff. #
    • 2026-07-15: Ten non-layoffs removed. These were SEC-filing extraction mistakes. Some were severance dollar figures and job-cut percentages misread as headcounts. Some were WARN Act boilerplate clauses from acquisition agreements. Three were duplicate rows of one Meta story carrying wrong dates. #

    Spotted something off? Every entry links to its primary source so you can check us. Send corrections through the contact page and they get priority.

    Cite this tracker AI Layoff Tracker, AskTheRecruiter.com. Accessed Aug 19, 2026. https://asktherecruiter.com/blog/ai-layoff-tracker/ Data from SEC EDGAR 8-K filings, US state WARN notices, and credible news outlets. Licensed CC BY 4.0.

    Browse the record

    Every page below lists the source-linked entries behind its own figure. Counts are entries, not jobs.

    By country

    By US state

    By industry

    By employer

    All 7,500 employers, A to Z

    Built for journalists & researchers

    Free to use with attribution to asktherecruiter.com. Every figure links to a primary source. Query the full dataset live through our API, and reach the editors at our contact page, where corrections get priority.

    GET /blog/wp-json/layoffs/v1/query

    Email digest

    A plain email summary of what changed on these trackers: headline numbers, the largest new entries, and links to the sources. You confirm your address by clicking a link we email you, and one click unsubscribes.

    What would you like?
    How often for the digests?

    Our mail provider records whether you open an email and which links you follow, including the confirmation email, which is measured before you have agreed to anything. Unsubscribing stops the sending and the recording together.

    You can read every past edition first. Each one is kept permanently, exactly as it was sent.

    Privacy note: what we store and how to erase it

    What we store: your email address, the choices above, and timestamps (signed up, confirmed, last sent). Nothing else about you.

    What our mail provider records: whether you opened an email and which links you followed, tied to your address. That is Brevo, the service that delivers these emails, and it works by adding a small invisible image and by routing links through its own address. We read it to see which sections people use. Unsubscribing stops the sending and the measuring at the same time, and erasing your row removes it from our side.

    The confirmation email is measured too: the same invisible image is in the one message that asks your permission. If you open it, Brevo records that against your address before you have agreed to anything, and it records it even if you then never confirm. We would exempt that message if we could. Brevo offers no way to switch its measuring off for a single email, and the one setting that exists covers every email we send or none of them. If you would rather not be measured at all, do not open it. Nothing else is ever sent to an unconfirmed address, and the signup is deleted from our side after 30 days.

    About the links: links in the digest pass through a counter on this site that adds 1 to a total for that link and sends you straight on. It records no identifier, no IP address and no browser details, so it counts how many times a link was followed and can never say who followed it.

    What it is used for: sending you exactly the emails you ticked, nothing else. The address is never shared, sold, or used for any other purpose.

    How to erase it: click the unsubscribe link in any email. That stops all sending immediately, and unsubscribed addresses, along with signups that were never confirmed, are hard-deleted automatically after 30 days. You can also ask via the contact page.