Silent WARN Notices: How to Set the Floor on Chime and Veritone

In mid-September 2026, Chime Financial and Veritone both filed WARN notices that skipped the one field every sourcer actually reads: how many people. They join a wider September pattern of filings from Kroger, FedEx, Chick-fil-A and Compass Group, with count fields that range from precise to blank. If you wait for the number to appear, you lose the 60-day window; if you treat "count: N/A" as unusable, you cede the flight-risk list to whoever knows how to bracket it.

What a silent WARN actually is, and why the floor is not zero

A silent WARN is a Worker Adjustment and Retraining Notification Act filing that discloses the employer, location, and effective date but omits the headcount. Legally, it still had to clear a statutory trigger to be filed at all, which means the floor is never zero.

The federal WARN Act applies to employers with 100+ employees and requires 60 days of notice before a mass layoff. The federal trigger is 50 workers at one site, 500 total, or 33% of the workforce (29 USC §2101). California's Cal-WARN is stricter: 75 workers at a covered establishment, with the only statutory excuse being "a physical calamity or an act of war" (Cal Labor Code §1401).

That last point matters more than sourcers realize. Because Cal-WARN has almost no exception, any California employer who files a silent-count notice did so as a deliberate legal or PR choice, not an oversight. The absence of a number is itself a signal that at least 75 people are affected. In practical terms:

• Federal silent WARN, single site: floor of 50.
• California silent WARN, single site: floor of 75.
• Silent WARN from a serial filer: floor is at least the size of the previous round.

That is the rule. The rest of this piece walks Chime and Veritone through it.

Chime: a silent SF filing on top of a 135-person baseline

Chime Financial's September 2026 WARN in San Francisco County reports no count, effective date September 30, 2026. Read against Chime's own filing history and the Stride Bank deal announced the same month, the defensible floor is 75 and the working estimate is closer to the prior 135.

Here is what is public. Chime already has a California EDD layoff notice on file covering 135 jobs in San Francisco County, published to the state's list since July 2025 (jsilvermanlaw.com/layoffs/chime-financial/). The September filing is a separate notice with the same employer, same county, no disclosed count, and a September 30 last day of work. In the same month, Chime agreed to acquire Stride Bank, N.A. for $590 million in cash.

The mechanism behind an M&A-adjacent silent WARN is not mysterious. Integration-driven redundancies hit G&A, compliance, risk, legal ops, product management and duplicate engineering leadership first. A quiet filing is how a public-facing fintech avoids stacking a layoff headline on top of an acquisition headline in the same news cycle. That is why the Chime pool, if you source only SWE titles, will miss most of it.

Titles to prioritize on the Chime pool

• Compliance and BSA/AML analysts, risk ops, KYC leads.
• Product managers on payments, deposits, and card, particularly duplicated between the acquirer and Stride's stack.
• Engineering managers and staff+ ICs whose org charts stack against Stride's.
• FP&A, GTM ops, and internal tools engineers, the classic G&A trim.

This is the exact gap where plain-English sourcing beats Boolean. Rather than build seven separate LinkedIn strings for "BSA analyst Chime San Francisco" and its variants, ask Refolk for compliance and risk ops people at Chime in San Francisco who joined before the Stride announcement, and get the ranked list back in one pass across LinkedIn, GitHub, and the open web.

Veritone: 31, then 10, then silent is the pattern that matters

Veritone's September filing is the third notice in a rolling RIF that already disclosed 41 jobs across two prior waves, so the operating assumption for the third wave is "at least as large as the last one," not smaller.

Veritone, the Costa Mesa AI company, has 2 California WARN notices on file covering 41 jobs in Orange County, with last days of work between August 10, 2026 and September 28, 2026 (jsilvermanlaw.com/layoffs/veritone/). The staging is 31 in June, 10 in July, and a silent third filing in September. That sequence is the signal.

Why staged filers matter more than one-shot filers:

1. A one-shot WARN reflects a decision that has already resolved. The pool is fixed on the effective date.
2. A staged WARN reflects a plan that is still executing. Each notice tells you the employer is comfortable trimming in small batches, which usually means more batches.
3. A silent notice in a staged sequence signals the employer no longer wants each round counted individually in the press, not that the round shrank.

The Cal-WARN floor of 75 does not cleanly apply to Veritone's smaller batches because prior filings came in under it, which means the September filing may have been aggregated with earlier notices to clear the threshold, or the site count grew. Either way, the working estimate for the September Veritone pool is 30 to 75, biased high.

88

The 2026 WARN wave is wider, not deeper

Through September 2026, 3,562 WARN notices have been filed across 44 states, affecting 313,234 employees, per LayoffAlert. At the same point in 2025, the tracker had logged 3,362 notices affecting 301,891 workers for the full year. 2026 is running roughly 6% ahead on notices and 4% ahead on headcount, but the average notice is 88 workers, not the 500+ single filings that defined the 2022 to 2023 tech cycle.

The implication for sourcing is direct. Alerts pinned to big-name employers will miss the bulk of the pool because the pool is now scattered across facility-level notices. September's list is the shape of things:

The FedEx and Kroger rows are useful contrast. Logistics and grocery employers file with the count because they have no PR reason to hide it. Fintech and AI file silent because they do.

The method, step by step, on any silent WARN

Reverse engineering a silent WARN is a four-step routine you can run in an hour per filing. The output is a defensible floor, a working estimate, and a title cohort worth sourcing.

1. Pull the raw filing. Use jsilvermanlaw.com for California, WARNTracker.com nationally, and each state's labor department portal directly. Confirm employer, county, and effective date.
2. Set the floor from the statute. Federal single-site: 50. Cal-WARN: 75. Read the specific state's threshold rather than assuming federal.
3. Anchor to prior filings. If the same employer at the same site has a disclosed prior notice, use that count as the working estimate. Chime's 135 is the Chime anchor. Veritone's 31 is the Veritone anchor.
4. Overlay the corporate event. M&A in the same 90 days? Assume integration titles. Product sunset? Assume the sunset team plus adjacent PM and design. Cost-out program? Assume G&A and middle management.

Once the pool is bracketed, sourcing is straightforward. You are no longer looking for everyone at the company, you are looking for the intersection of location, tenure, and the specific title cohort the corporate event implies. This is what Refolk does well: describe that intersection in plain English, get a ranked list back across GitHub, LinkedIn, and the open web, without stitching together five different tools.

A silent WARN is not missing data. It is the state minimum, wearing a suit.

Why California silent filings are higher-confidence than most

California silent WARNs are more reliable signals of a real cut than silent filings from states with broader statutory exceptions. Cal-WARN's only carve-outs are "physical calamity or act of war," so a California employer who omits the count did it on purpose.

Compare that to federal WARN's three exceptions: faltering company, unforeseeable business circumstances, and natural disaster. In federal-only jurisdictions, a silent or late filing can plausibly be blamed on "unforeseeable business circumstances," which softens the signal. In California, no such rhetorical exit exists. A silent Cal-WARN from Chime or Veritone is a filing where legal signed off on the omission knowing the statute gives them nowhere to hide, which means the underlying event is real, large enough to trigger 75, and the omission is a PR decision.

Practically, this changes how you rank alerts:

• California silent WARN: high-confidence, pool ≥ 75, source immediately.
• Federal-only silent WARN: medium-confidence, verify against the state portal and press releases before spending sourcing budget.

What sourcers should actually do this week

Three moves, ordered by leverage. Every one of them assumes you have already accepted that sourcing from silent WARN is a repeatable workflow, not a one-off scramble.

• Rebuild alerts at facility level. Employer plus city, not employer alone. The 88-workers-per-notice average means the big-name filter misses most of the pool.
• Pre-load the title cohort for M&A-adjacent silent filers. For Chime, that is compliance, risk, payments PM, and duplicate eng management. Have the search saved before the effective date, not after.
• Treat staged filers as a subscription. Veritone's 31, 10, silent pattern will produce a fourth filing. Build the Costa Mesa AI/ML list once, keep it warm, and refresh weekly.

FAQ

How do I find WARN notices that don't have a headcount?

Every state maintains a WARN portal, and aggregators like jsilvermanlaw.com, WARNTracker.com and LayoffAlert.org normalize them. A "no count" or "N/A" in the headcount field is common enough that most trackers surface it as a distinct filter. Once you have the filing, the state's WARN statute tells you the minimum headcount that could have triggered it, and that is your floor.

Is a silent WARN legally allowed?

In most jurisdictions the headcount field is not strictly required to satisfy the notice obligation, though it is customary. The federal WARN Act and most state analogs require employers to notify the state dislocated worker unit and affected employees, but the public-facing state list can lag or aggregate. Employers exploit that gap for PR reasons. It does not change the underlying legal event: a covered mass layoff still had to occur for the filing to exist.

Why would Chime file silent when it's already publicly known for a prior 135-person round?

Because September 2026 was also the month Chime announced a $590 million acquisition of Stride Bank, and stacking a layoff headline on top of an acquisition headline compounds the PR damage. A silent filing satisfies the statute without giving reporters a fresh number to lead with. For sourcers, the lesson is to always cross-reference silent WARNs against the employer's press releases in the same 90-day window; the corporate event usually explains both the silence and the title cohort being cut.

Should I trust the Cal-WARN 75 floor as a hard number?

Treat 75 as the defensible lower bound and the prior filing as the working estimate. If the employer has never filed before, 75 is the number. If they have filed before at the same site, use whichever is larger. And if the employer is staging cuts across multiple notices, assume the silent one is at least the size of the last disclosed one, because the reason to go silent is almost always that the number got bigger, not smaller.