WARN Act and Layoffs in Security Services — What Security Workers Should Know

Security layoffs look different from factory layoffs. A guard usually works at a site the employer does not own — an airport, a warehouse, an office tower — and the job can end because a client contract ended, not because the security company is closing. Two recent California filings show both patterns: one giant airport contract, and one company shedding guards site by site across a county.

The 60-day rule, applied to security

The federal WARN Act requires employers with 100 or more full-time employees to give 60 days' written notice before a plant closing or a mass layoff of 50 or more workers. The 50-worker threshold is the one that matters most here: a single large site — an airport terminal, a distribution center, a corporate campus — can hold 50 or more guards, so losing one contract can trigger the notice requirement on its own.

California adds its own layer. The state's Cal-WARN law also requires 60 days' notice, but its exceptions are far narrower than federal law's: California recognizes only a physical calamity or an act of war, while federal law also allows exceptions for a faltering company and unforeseeable business circumstances. A short notice period is a fact worth checking, not a conclusion that the law was broken.

Two filings, 1,419 workers

Covenant Aviation Security — 1,279 workers, San Francisco. The aviation-security contractor filed on September 28, 2026, for a layoff effective November 30, 2026 — 63 days' notice, just over the 60-day standard. One filing, one site, 1,279 workers: the largest recent WARN filing in the country at the time.

Constellis, LLC — 140 workers, Los Angeles County. The private-security firm filed 28 WARN notices with California's Employment Development Department, all dated within September 2026, covering 140 jobs across 21 locations including Los Angeles, Whittier, Lynwood, Norwalk, Marina Del Rey, and Pomona. The last days of work run through October 31, 2026, and the employer classified the event as a permanent layoff. The shortest gap between a notice date and the last day of work is 32 days — about half the 60-day standard. All 28 notices arriving in a single month reads as one event reported site by site rather than a rolling reduction.

Together the two filings cover 1,419 workers — about 710 per filing, against a national average of about 90 workers per notice in the current 90-day window (673 notices, 60,744 reported workers).

Why security filings look the way they do

The first pattern is the contract, not the company. When a security firm loses a client, the guards at that site are the layoff — even though the security company itself keeps operating elsewhere. That is why Constellis shows up as 28 separate notices for 21 locations instead of one filing for 140 workers.

The second pattern is the notice-period squeeze. Contract transitions move fast: a new firm takes over a site on a set date, and the outgoing firm's guards are done that day. Constellis's 32-day shortest gap is the result — the contract's end date, not a 60-day planning window, set the schedule.

What to do when your security employer files

First, read the notice itself. It states your effective date, whether the layoff is permanent or temporary, and which site it covers. In a contract loss, the answer is usually permanent for that site, with no bumping rights to another site — but check anyway.

Second, check the notice period against the 60-day rule. Count the days from the notice date to the effective date. If it is short, keep the notice and note the gap; the exceptions are narrow, and in California they are narrower still. No agency enforces the WARN Act — claims are private lawsuits, usually class actions, with back pay capped at 60 days.

Third, use the notice period. Sixty days is time to file for unemployment, check COBRA and marketplace health coverage, and contact your state's Rapid Response team, which coordinates retraining and job placement for workers affected by WARN filings. For guards, it is also the time to check whether the incoming contractor at your site is hiring.

Fourth, keep records. Save the notice, your pay stubs, your license documents, and any written communication about your last day. In a contract transition, the old employer leaves the site; your copy may be the only record of whether the filing happened on time — or did not.

The national picture

Security filings are a small slice of a concentrated national picture. In the 90-day window, California accounts for 21,630 reported workers and Washington for 17,333 — together about 64 percent of the 60,744 total. The weeks ahead stay heavy: 5,788 workers are scheduled effective in the week of November 16, 6,207 in the week of November 23, and 5,962 in the week of November 30. Covenant's 1,279 workers, effective November 30, are part of that week's 5,962.

One caution applies to every figure in this article. These are reported plans, not confirmed job losses. A WARN notice records what an employer told a state agency it intends to do. Filings can be amended, delayed, or cancelled — the numbers describe the paper trail of planned layoffs, not a census of lost jobs.

For security workers, the practical lesson is simple. A WARN notice is not a rumor or a pink slip. It is a dated, public record that starts a 60-day clock — and when the job depends on a contract, that clock may be the only warning that the site is changing hands.

Data source: Layoff Atlas