The playbook  /  Before you are told

The notice that never came

California law gives workers in a mass layoff a right most never hear about. Sixty days of written notice, with back pay if it never arrives. The right depends on a count, of people, days and sites, and the count is exactly what a quiet sequence of small departures can obscure.

What it looks like

There is no announcement. A team loses three people one month and four the next, each explained separately: a performance exit here, a restructure there, a role eliminated somewhere else. Departure dates cluster, but nothing is ever called a layoff, and no notice arrives, because each individual event looks too small to require one. By the time the pattern is visible, the site has lost dozens of people and the notice period the law promised has already run, unused.

What it costs you

Sixty days of warning is not a courtesy. It is the period in which you could have looked for work while still employed, priced health coverage, and planned. When the count is missed, or never made, you lose that period entirely, and the back pay the statute substitutes for it is a claim you have to know exists before you can pursue it. The departures also arrive one at a time, which means each worker negotiates alone, with no shared information about the scale of what is happening.

What the law says

California's Cal-WARN Act, Labor Code 1400 to 1408, covers an establishment that employs, or has employed in the preceding 12 months, at least 75 people. A mass layoff of 50 or more employees within a 30-day period at a covered establishment, and qualifying relocations and terminations, require 60 days of written notice under section 1401, to the affected employees, the Employment Development Department, the local workforce development board, and the chief elected official of each relevant local government. Since January 1, 2026, under SB 617, the notice must also say whether rapid response services will be coordinated through the local board, give the board's contact information and a description of those services, and include a description of CalFresh, its food assistance helpline and a link to apply. An employer that fails to give the notice owes each affected employee, under section 1402, back pay at the higher of the employee's average regular rate over the last three years or the final rate, plus the value of benefits, for the violation period, up to 60 days or one half of the employee's period of employment, whichever is smaller, reduced by specified payments the employer made. Section 1403 adds a civil penalty of up to $500 per day for failing to notify the government recipients, avoided if the employer pays all section 1402 amounts within three weeks of the date the layoff was ordered. And section 1407 provides that Cal-WARN payments are not wages for unemployment insurance purposes, and benefits may not be denied or reduced because of them. Federal WARN adds a second counting rule: under the 90-day aggregation rule in 29 U.S.C. 2101 and 20 C.F.R. 639.5, smaller groups of terminations within 90 days are combined into one employment loss unless the employer shows they resulted from separate and distinct actions and causes and were not an attempt to evade the Act. A discharge for cause, a voluntary departure and a retirement are not an employment loss at all under federal WARN, which is why the label attached to each departure matters to the count.

What to do instead

  • Build the timeline yourself: departure date, site, team or job family, headcount and the stated reason, for every exit you know about, over 30-day and 90-day windows. The pattern, if there is one, lives in that table and nowhere else.
  • Ask in writing whether a Cal-WARN or federal WARN notice was issued for your separation, and to whom it was sent. Notices filed with the EDD are a matter of record, and the local workforce board named in them runs the rapid response services the notice describes.
  • Count carefully before concluding anything. Coverage turns on employer size, the single site, full-time status, and the cause of each loss. A cluster of departures is a reason to ask the question, not proof of the answer.
  • If no notice was given and the count reaches the threshold, the section 1402 claim belongs to each affected employee whether or not a separation agreement mentions it. Ask whether any payment you were offered is described as offsetting WARN liability, and get that description in writing.
  • Take advice early. WARN claims are fact-specific, the counting rules differ between the California and federal statutes, and the timeline you build is worth most while departure dates are still easy to establish.

A right that depends on arithmetic

Most rights in this playbook attach to a document. This one attaches to a number. Whether you were owed 60 days of notice depends on how many people lost their jobs, at one site, inside a window of days, and on what each departure was called. Every element of that count is information the employer holds and the worker mostly does not.

That is what makes the pattern worth naming on a site about paperwork. A single layoff of sixty people is an event: it generates a notice, a record, a rapid response team, and a room full of people who know what happened to them. Sixty departures in six quiet groups generate none of that, even where the total is identical. Federal WARN was drafted with this in mind, which is why the 90-day aggregation rule exists: smaller losses add up, unless the employer can show they were genuinely separate events and not an attempt to stay under the line. The rule cuts both ways. It is the worker’s best argument that the count should be made honestly, and it is the reason the label on each departure, laid off, resigned, fired for cause, is worth reading rather than accepting.

Read this entry the way this site asks you to read all of them: as a pattern to check with a timeline, not as a claim that employers commonly evade WARN. Groups of departures have ordinary causes. Reorganisations stagger. Performance processes conclude when they conclude. The check is cheap, and it is the only version of the question that can actually be answered: dates, sites, numbers, labels.

What the notice was supposed to contain

When a Cal-WARN notice does arrive, read it as more than a warning. Since SB 617 took effect on January 1, 2026, a compliant California notice has to do practical work: it says whether rapid response services will be coordinated through the local workforce board, gives that board’s contact information, describes what the rapid response team does, and includes information about CalFresh, the state food assistance program, including its helpline and where to apply. Those contents exist because the notice period is when a worker is best placed to use them. A notice that omits them is missing elements the Legislature added deliberately, for exactly the weeks the notice is meant to cover.

The liability side is just as specific. Back pay under section 1402 is measured at the higher of your three-year average rate or your final rate, with the value of benefits on top, for up to 60 days or half your length of employment, whichever is smaller. Specified payments the employer actually made reduce it. A severance payment described as satisfying WARN exposure does not cure a notice that was never given. Section 1407 keeps Cal-WARN payments from reducing your unemployment benefits.

The ideal

In the ideal process, the count is made before the departures begin, not after a worker makes it. A covered employer gives the full 60 days of notice, to every recipient the statute lists, with the SB 617 service and CalFresh information included, and treats a sequence of related departures as the single event it is. Where an employer genuinely runs separate, unrelated reductions, it can say so and show its work, which is all the aggregation rule asks. The notice period then does the job it was designed for: sixty days of looking for work from inside a job, with the local board’s services already in hand.

Why it works

Aggregation defeats attention one small event at a time. Each departure is below the size that triggers scrutiny, gossip networks lose a few members at a time rather than a team at once, and no single worker ever sees the total. Marc Galanter’s repeat player analysis (1974) describes the structural version of the same point: the employer counts its separations continuously, as a routine metric, while each worker experiences exactly one data point, their own, and has no way to know it was the forty-ninth. Naming the counting rules is most of the countermeasure, because a worker can reconstruct the count from the outside, using the dates and departures they personally witnessed.

What employer-side guides say

The counting rules are not a worker-side theory. The United States Department of Labor publishes an Employer’s Guide to the federal WARN Act that explains the 90-day aggregation rule to employers directly, including the separate and distinct actions defence and the warning that a series of smaller terminations may be combined when they reach a covered event. California’s EDD publishes the Cal-WARN thresholds and notice requirements for employers in the same plain terms used in this entry. An employer is entitled to rely on those guides. A worker is entitled to check the departures they saw against them.

This is why the campaign exists

Three simple rules would remove most of the leverage described on this page. A copy by default, in a format you can open, with every change marked.Help get it introduced in 2027.