WARN Act Obligations for Scaling Companies During Layoffs

WARN Act obligations during layoffs are a planning constraint for scaling companies. Compliance depends on how workers are counted, which state rules overlap, what the notice says, and when it is sent. WARN analysis belongs in workforce planning before leadership fixes a separation date.

Why WARN Act compliance has become a live operational risk for scaling companies in 2026

A fast-growing company hits a rough quarter, and its leaders decide to cut costs through layoffs. If the planned separations are only weeks away, the federal 60-day notice requirement may already make that schedule untenable. For founders, finance leads, and people operators at companies with 50 to 500 employees, crossing a coverage threshold can create obligations that the existing reduction-in-force process does not recognize.

That planning risk is increasing in 2026 as elevated WARN filings coincide with changes to state law. Washington’s mini-WARN law took effect on July 27, 2025, and Ohio’s followed on September 29, 2025. California’s SB 617 added notice requirements effective January 1, 2026. Congress has also introduced the Fair Warning Act, H.R. 5761, which would lower federal coverage thresholds if it becomes law. A process built around an earlier understanding of WARN can therefore fail even when leadership follows its established procedure.

What the federal WARN Act actually requires and who it covers

The federal Worker Adjustment and Retraining Notification Act generally covers employers with 100 or more employees, excluding workers with fewer than six months of service in the preceding 12 months and those averaging fewer than 20 hours a week. An alternative test includes part-time employees. Under that test, coverage applies to employers with at least 100 employees who collectively work at least 4,000 hours per week, excluding overtime. Employer coverage and the trigger for a particular workforce reduction are separate determinations.

Employers covered by the law must give written notice at least 60 calendar days before qualifying plant closings and mass layoffs. A plant closing involves a shutdown at a single site that results in job losses for 50 or more employees during a 30-day period. Mass layoffs have distinct numerical and workforce-percentage tests. Smaller reductions across separate 30-day periods can also aggregate over 90 days unless they result from separate and distinct causes.

Notice must go simultaneously to affected employees or their union representatives, the state dislocated worker unit, and the chief elected official of the relevant local government. Required content varies by recipient, including the action’s permanence, timing, affected jobs, bumping rights, union information, and a company contact. Three narrow exceptions can shorten notice, which are faltering company, unforeseeable business circumstances, and natural disasters. The faltering-company exception applies only to plant closings where notice would preclude obtaining capital that could avert shutdown. Even when an exception applies, notice remains required “as soon as practicable,” with a written explanation.

The counting and aggregation errors that trip up scaling companies before a single notice is filed

Counting errors can prevent an operator from recognizing that notice is required at all. Federal exclusions depend on service and hours. The alternative hours-based coverage test also prevents a blanket assumption that part-time workers are irrelevant. State analysis then changes the calculation again. California counts both full-time and part-time employees toward its 75-employee coverage threshold, so a correct federal determination does not settle state coverage.

A company cutting 25 people in January, 20 in February, and 15 in March may trigger a mass layoff obligation when the reductions fall within the applicable 90-day window and lack separate and distinct causes. Smaller rounds are not automatically independent events. Leadership that phases reductions to remain below a threshold can instead create a retroactive violation, depending on the applicable trigger and the reasons for each round.

Location is another input requiring substantive analysis. Federal event thresholds apply at a single site, so one office may trigger WARN while others do not. Consolidating two sites’ functions can complicate the assumption that a small office closure falls below the threshold. Accurate analysis therefore requires current location, tenure, hours, and supervisor-assignment data, together with a rolling record of reductions. Disconnected spreadsheets make those relationships harder to reconstruct before a proposed cut becomes an actual employment loss.

How California, New York, New Jersey, Washington, and Ohio have each raised the bar above federal WARN

California’s Cal-WARN covers establishments with 75 or more employees, counting full-time and part-time workers. Its mass layoff trigger is 50 or more employees at a single establishment within any 30-day period, without a workforce-percentage requirement. The notice period is 60 calendar days. SB 617 added four mandatory content categories for notices issued on or after January 1, 2026. Financial distress does not excuse or shorten California’s notice obligation.

New York covers businesses with 50 or more employees and requires 90 days’ notice. That earlier deadline changes the planning horizon.

New Jersey covers employers with 100 or more employees nationwide, regardless of full-time or part-time status, and counts affected employees statewide. It requires 90 days’ notice and statutory severance of one week per year of service. If the notice falls short, the employer owes another four weeks of severance. Waiver of statutory severance typically requires state or court approval, making it a separate obligation from notice administration.

Washington’s mini-WARN law applies to employers with 50 or more full-time employees. It sets detailed rules for what the notice must say and allows few exceptions.

Ohio requires employers with 100 or more employees to provide 60 days’ advance written notice before a qualifying mass layoff or plant closure. Its mass layoff test includes 50 or more employees at one site during a 30-day period, with a workforce-percentage requirement under federal guidance. Notices must be more detailed than federal notices. Required recipients include the Ohio Department of Job and Family Services and the chief elected officials of both the municipality and county. These differences require jurisdiction-by-jurisdiction analysis.

The content-deficiency trap: why a timely notice can still be a noncompliant notice

A timely notice can still fail on content. California’s SB 617 does not grandfather templates that omit its four new mandatory content categories. An employer that uses a pre-2026 template without those disclosures can send notice on time and still remain in violation. Under California’s penalty structure, each calendar day of content deficiency is treated as a separate violation.

Federal notice preparation also requires recipient-specific review. There is no mandated federal form, so an employer must build a document that addresses whether the action is permanent or temporary, expected timing, affected job titles and counts, bumping rights, union information, and a named company contact. Those details must be tailored to who receives the notice. Employee notices and government notices are not interchangeable, even when they describe the same reduction.

Delivery creates an additional, independent compliance obligation. Under Cal-WARN, incomplete or deficient delivery to a required recipient can constitute a violation, and staggered delivery can also create exposure. New York also has an AI-disclosure checkbox that affects what the notice must say. When job losses involve technological innovation or automation, the required form must name the technology used. Omitting an applicable disclosure is a content failure.

What penalty exposure looks like when WARN is violated — and why enforcement is a class action problem

Federal WARN liability can include up to 60 days of back pay and benefits for each affected employee who did not receive adequate notice. Even a small cut at a company that pays high wages can therefore leave it owing a large amount, with far fewer layoffs than those associated with Meta, Amazon, or Oracle. Those companies provide context only for the workforce-reduction environment.

Failure to notify local government can also create a civil penalty, avoidable through the required payments within three weeks of the closing or layoff. Courts may reduce liability when an employer acted in good faith and reasonably believed it was following the law, and may credit payments made during the violation period. Reasonable attorney’s fees may go to the prevailing party. California adds full benefits value and civil penalties to back-pay exposure, while awarding attorney’s fees to prevailing employees but not prevailing employers. Its content-deficiency exposure accrues from the deficient filing.

Enforcement changes how this exposure must be understood. The federal labor department administers federal WARN through the Employment and Training Administration but has no role in seeking damages. Enforcement proceeds through private litigation in federal district court, with class certification common in large-workforce cases. The same filing error in a reduction across several states can lead to several lawsuits. There is no administrative settlement pathway in which an agency fine resolves federal WARN liability before litigation, and New Jersey’s statutory severance remains an additional entitlement alongside notice compliance.

What a compliant WARN process looks like, built backwards from the 60- or 90-day deadline

The operational response is to work backwards from the planned separation date. An employment attorney should validate the framework against the company’s specific facts. Planning begins with the applicable notice period, including 60 calendar days federally and 90 days in New York and New Jersey. The stricter rule governs employees in the relevant state, regardless of headquarters location. Where those longer-period states are involved, aligning the overall timeline to 90 days may simplify administration.

The next step is a workforce count using the correct jurisdictional rules. The record used for the count should show where each employee works, their tenure and weekly hours, and who their supervisor is. The federal count should use the short-tenure and sub-20-hour exclusions and also check coverage under the alternative hours-based test. State counts require their own treatment. The planned cut should then be checked against earlier cuts within the 30-day and 90-day windows, including whether separate and distinct causes allow the rounds to be treated separately.

Once the company has checked coverage and triggers, it should list everyone who must receive notice. Federal recipients include employees or their representatives, the state dislocated worker unit, and the relevant local official. Ohio also requires notice to the specified state department and to both municipal and county officials. California requires the state employment development agency, the local workforce development board, and the chief elected official of each city and county government. The delivery plan should have all notices, including government copies, go out at the same time.

The notice audit should use current requirements for each recipient and jurisdiction. California templates need review against SB 617, while New York forms require an accurate response to the AI/automation disclosure where applicable. Whether an exception applies should be decided separately and put in writing. The federal faltering-company exception does not cover mass layoffs, and financial distress does not shorten Cal-WARN notice. Any valid basis for reduced federal notice still requires delivery “as soon as practicable” and a written explanation.

Why a fragmented HR and payroll stack makes WARN compliance structurally harder than it should be

WARN readiness depends on employment records that are often maintained in different systems. Payroll records show hours and pay, while HR records show tenure, where employees work, and who they report to. The records must also keep track of earlier cuts within a rolling window. When those records are not reconciled, the company can miss an aggregation trigger or apply the wrong state rule even if its notice template is current.

The maintenance burden is growing as states amend their rules. Connecticut’s change effective October 2026 adds to the sequence of developments in Washington, Ohio, and California. A unified system of record makes continuous threshold analysis more tractable than a reconciliation exercise begun after a reduction is approved. It also gives operators a sounder basis for evaluating a proposed action across jurisdictions. Software supports that analysis but does not replace counsel’s judgment about legal triggers or exceptions.

Among platforms addressing this fragmentation, Warp combines payroll, compliance, benefits, and HR data and monitors payroll and headcount changes across all 50 states in real time. It can flag when workforce changes cross thresholds, helping operators spot aggregation risks before they treat one round of cuts as separate from the next. That is an infrastructure capability. With current data and active monitoring, operators can see a potential trigger while the reduction is still a proposal and act before the notice clock constrains the decision.