How to Use WARN Act Filings to Find Companies Ready to Buy

Most reps ignore WARN filings because they think layoffs mean a dead account. That’s backwards.

A WARN notice usually shows up before the public narrative catches up. It gives you a 60-day window into a company that is actively restructuring. And restructuring is when teams change tools, budgets move, workflows break, and new vendors get considered.

That matters right now because the volume is high. Intellizence reported that since January 1, 2026, more than 1,621 companies had announced mass layoffs as of March 22. Separately, CNBC, citing Challenger, Gray & Christmas, reported 108,435 announced U.S. layoffs in January 2026, the highest January total since 2009.

If you sell into operations, HR, IT, security, finance, procurement, workplace, cloud, data, or transition-heavy functions, WARN filings are not bad news. They are timing data.

What WARN filings actually tell you

The federal Worker Adjustment and Retraining Notification Act requires certain employers to provide advance notice ahead of mass layoffs and plant closings. In California, the state’s EDD explains that employers generally must provide notice 60 days before a mass layoff, plant closure, or relocation, and California’s rules can apply to employers with 75 or more employees. California also added new 2026 notice requirements around worker support services. See the official EDD page here: edd.ca.gov/en/jobs_and_training/Layoff_Services_WARN/.

That means a WARN filing can give you:

• Date signal: when the change is expected to hit
• Location signal: which office, campus, facility, or state is affected
• Headcount signal: rough size of the disruption
• Function signal: sometimes the roles or teams impacted
• Restructuring signal: whether this is a closure, relocation, or broader reduction in force

That is enough to build a targeted outreach plan.

Where to find WARN data fast

You do not need a paid data vendor to get started.

Use these sources:

• State labor sites: California EDD at edd.ca.gov/en/jobs_and_training/Layoff_Services_WARN/, Washington ESD’s WARN database at esd.wa.gov/.../worker-adjustment-and-retraining-notification-warn-layoff-and-closure-database, Texas Workforce Commission at twc.texas.gov/data-reports/warn-notice, and New Jersey’s 2026 archive at nj.gov/labor/assets/PDFs/WARN/2026_WARN_Notice_Archive.pdf
• WARNTracker: a searchable public-WARN aggregator at warntracker.com
• WARNwise: another searchable WARN notice database at warnwise.org

If you want a simple workflow, use aggregators to spot targets, then verify the notice on the state site.

How to read a filing like a seller, not a job seeker

Most people stop at the company name and layoff count. Don’t.

Pull these five fields every time:

1. Notice date — when the company filed
2. Effective date — when the layoffs or closure take effect
3. Site address — tells you which business unit or office is under pressure
4. Layoff vs. closure vs. relocation — very different buying scenarios
5. Role mix — when available, this is the gold

Then translate the filing into a sales hypothesis:

• If engineering is cut, the company may consolidate platforms, outsource implementation, or prioritize automation.
• If operations is cut, they may need workflow tooling, cost controls, or external services.
• If a site is closing, facilities, logistics, IT asset recovery, compliance, and HR transition work all spike.
• If layoffs hit a specific geography, regional leaders may suddenly own change-management budgets.

Real example: Oracle

Oracle is a clean example because the notices are recent and the filings are specific.

According to recent reporting and WARN data, Oracle filed multiple notices tied to layoffs effective June 1, 2026. USA TODAY network reporting said Oracle laid off 158 workers in Pleasanton and noted many affected employees were software developers, application developers, and product staff.

WARNwise shows Oracle notices for:

• 310 workers at 500 Oracle Parkway, Redwood City, California
• 184 workers at 4230 Leonard Stocking Drive, Santa Clara, California
• 158 workers at 5815 Owens Drive, Pleasanton, California
• 50 workers at 1620 26th Street, Suite 100S, Santa Monica, California
• 491 workers in Washington
• 539 workers in Missouri

See the Oracle notice rollup here: warnwise.org/notices/orwa922025.

Why this matters for sellers:

• The affected roles skew technical, which signals pressure in product, engineering, and delivery
• The locations map to major Oracle operating hubs, which suggests a structured reallocation, not a random trim
• The effective date gives you a clear outreach window before and after the change lands

If you sell cloud cost optimization, security, automation, IT operations, contractor support, or HR transition services, that is not noise. That is an account plan.

Real example: Chevron

Chevron is a good reminder that WARN data is not just for tech.

Intellizence’s 2026 layoff tracker lists Chevron among major companies announcing layoffs, and California WARN records from prior reporting periods have included Chevron notices in Richmond. That matters because energy companies restructuring a site or business unit often trigger downstream needs across contractors, compliance, asset management, field operations, workforce transition, and procurement.

The takeaway is simple: don’t wait for a press release saying “transformation initiative.” If Chevron, Oracle, or any large account appears in WARN data, start mapping the affected site, leadership, and support functions immediately.

The 60-day outreach playbook

This is the part most reps miss.

A WARN notice is not a “pitch them tomorrow” trigger. It gives you a sequence.

Days 1-7 after filing:
Verify the filing, map the site, identify department leaders, HR, IT, operations, finance, and procurement. Read local news for role-level clues.

Days 8-21:
Start soft outreach around transition risk, continuity, and cost control. Do not lead with “saw your layoffs.” Lead with what breaks during restructuring.

Days 22-45:
Push account research deeper. Watch for executive changes, earnings language, office closures, vendor reviews, real estate moves, and new job postings in replacement functions.

Days 46-75:
Now the change is real. Teams are absorbing workload, systems are changing, and outside help gets considered. This is when practical offers land better than generic intros.

A simple opener works better than a clever one:

“We work with teams dealing with site reductions and role consolidation. Usually the pain shows up in handoffs, system access, reporting, and vendor sprawl before leadership fixes it. Worth comparing notes?”

What to sell into after a WARN filing

Not every layoff creates the same opportunity. Match the filing to the category:

• HR / outplacement / benefits: employee comms, career transition, benefits support
• IT / security: offboarding, identity, device recovery, access reviews, contractor backfill
• Finance / procurement: spend controls, vendor consolidation, audit readiness
• Operations: workflow redesign, outsourcing, coverage gaps, service continuity
• Real estate / facilities: closures, moves, lease actions, asset disposition

This is why WARN data is useful. It narrows the “why now” faster than most intent tools.

A simple framework: FILER

Use FILER on every notice:

• Functions affected
• Impact size
• Location
• Effective date
• Restructuring type

If you can fill those five fields, you can write a relevant outbound angle in 10 minutes.

Final point

WARN filings are one of the most underused public buying signals in sales. They are free, current, specific, and tied to real operational change. In a market where more than 1,621 companies have already announced mass layoffs in 2026 and January alone hit 108,435 announced cuts, ignoring WARN data is just leaving signal on the table.

If you want deeper workflows, templates, and account-research systems built around signals like WARN, join SalesInt’s paid tier.