WARN Act Exceptions
WARN Act exceptions: UFBC, faltering company, and natural disaster
The three federal WARN Act exceptions are heavily litigated, frequently misapplied, and always interpreted narrowly by courts. This guide covers what each exception actually requires, what case law says about each, and what documentation you need to have any chance of succeeding.
3
Recognized exceptions
Federal WARN recognizes three exceptions: unforeseeable business circumstances, faltering company, and natural disaster. Each has specific requirements courts enforce strictly.
Strict
How courts apply them
Courts interpret WARN exceptions narrowly. The burden of proof is on the employer. Vague or after-the-fact documentation rarely succeeds.
WARN exceptions: what they actually mean
The WARN Act's exceptions are not safe harbors. They are narrow defenses that reduce the required notice period when an employer can prove specific conditions existed. All three exceptions share two features: (1) the burden of proof is on the employer, and (2) notice must still be given "as soon as practicable" regardless of which exception is claimed.
Courts have consistently rejected exceptions claimed retroactively or supported only by vague testimony. The Department of Labor's implementing regulations (20 C.F.R. Part 639) interpret each exception narrowly, and courts have generally followed that interpretation. An employer who wants to invoke an exception must be prepared to prove specific facts, not general conditions.
The exceptions reduce the notice period. They do not eliminate WARN's other requirements: the content of the notice, who receives it, and the penalty structure for violations all remain in effect.
Exceptions reduce the notice period, they do not eliminate it
An employer who claims the UFBC exception must still give whatever notice was practicable, even if that is 14 days instead of 60. Courts have denied the exception entirely to employers who waited weeks after the triggering event before notifying employees.
Unforeseeable business circumstances (UFBC)
UFBC is the most commonly claimed exception and the most commonly rejected. The standard has two conjunctive prongs: the circumstance must be (1) sudden, dramatic, and unexpected, AND (2) caused by some sudden, dramatic, and unexpected action or condition outside the employer's control.
The DOL regulations give concrete examples: a principal customer suddenly and unexpectedly canceling a major contract; a strike at a major supplier. These examples inform the analysis. Courts have treated them as the paradigm cases the exception was designed to cover.
The predictability test is objective, not subjective. Courts ask whether "an employer exercising reasonable business judgment" could have foreseen the event. An executive who was personally surprised is not sufficient. The question is whether the circumstances were objectively foreseeable to a reasonably prudent employer in that industry and position.
What courts have accepted
Sudden loss of a single customer representing 60% or more of revenue with no prior warning (upheld in several circuits when documentation was contemporaneous)
A government contract cancellation the employer had no reason to anticipate, relevant particularly for defense contractors
COVID-19 government-mandated shutdowns in the narrow window of March 2020, when specific closure orders left no operational alternative
What courts have rejected
A general economic downturn or industry-wide recession, which courts treat as foreseeable even if the specific timing was not predicted
A startup running out of funding after a failed fundraising round where the cash runway was clearly limited and disclosed to investors
A customer concentration risk that was known and disclosed but not acted upon
A fast-growing tech company's "strategic reset" layoff where declining growth metrics were visible for months
A retailer closing stores due to ongoing competitive pressure from e-commerce, a trend that had been underway for years
The UFBC exception is not a startup exception
Courts in the Ninth Circuit (California, Oregon, Nevada) have repeatedly rejected UFBC claims from technology companies citing fast-changing business conditions. The exception is narrow and reserved for genuinely sudden events. A company that has been managing a deteriorating runway for months cannot claim that running out of cash was sudden and unexpected.
Faltering company exception
The faltering company exception applies only to plant closings, not mass layoffs. It is the most narrowly applied of the three exceptions. The exception was designed for a specific scenario: a company on the verge of closing is actively trying to save itself, and disclosure of the impending closure would cause a deal to collapse.
The three-part test is conjunctive: all three elements must be satisfied. Satisfying two of three is not enough, and courts have been willing to grant summary judgment against employers who cannot produce evidence on each element.
Mass layoffs cannot use this exception
The faltering company exception does not apply to mass layoffs, only plant closings. An employer doing a large-scale layoff without closing a facility cannot claim this exception even if the company is genuinely distressed and seeking financing. This is a common misconception. If there is no plant closing, the faltering company exception is unavailable.
When it works: the paradigm case
A manufacturing plant actively negotiating a sale to a buyer who has conditioned the deal on the workforce remaining intact, where notice to employees would have caused the buyer to walk away. This is the scenario the exception was designed for. The employer must document the buyer's condition, the timeline of negotiations, and the fact that the deal ultimately failed (or succeeded) before notice could be given.
Natural disaster exception
The natural disaster exception applies when the plant closing or mass layoff was directly caused by a natural disaster: flood, earthquake, drought, storm, tidal wave, or similar catastrophic event. The critical word is "directly." The disaster must be the proximate cause of the employment loss, not a contributing factor or background condition.
The DOL regulations require that the employer give notice "as soon as practicable" and include a statement of the reasons for the reduced notice period. Even in a genuine natural disaster, notice must be given to affected employees, state agencies, and local officials as soon as the employer is able to do so.
COVID-19: not a natural disaster under most courts' analysis
Courts have split on whether COVID-19 qualifies as a natural disaster for WARN purposes. Most courts have treated pandemic-related closures under the UFBC exception rather than the natural disaster exception, requiring employers to satisfy the UFBC standard. The Sixth and Seventh Circuit courts in particular have applied UFBC analysis to COVID-related closures, reserving the natural disaster category for physical property destruction scenarios. Employers who relied on the natural disaster label for pandemic closures without also establishing UFBC have faced litigation exposure.
Documentation requirements
Documentation is where exceptions are won and lost. Courts have rejected well-founded exception claims almost entirely because the employer could not produce contemporaneous records. The burden of proof at trial is on the employer, and without contemporaneous documentation, courts apply exceptions narrowly against the employer.
Retroactive reconstruction of the factual record, through after-the-fact memos or executive affidavits describing what happened months earlier, rarely satisfies the standard. Opposing counsel will argue that the explanation was constructed for litigation, and courts have agreed.
Contemporaneous board or executive records
Board resolutions, executive committee minutes, or written decisions dated at or before the time notice would have been required. For UFBC, these records should reflect when the employer first learned of the triggering event and what decision was made in response. For faltering company, they should reflect the status of financing negotiations and why notice was deferred.
Financial and transactional records
For faltering company: loan applications, term sheets, investor presentations, bank communications, and records from each specific financing source pursued. For UFBC: customer cancellation letters, government orders, supplier notices. These should be dated and authentic. Courts have reviewed metadata on documents to assess whether they were created when claimed.
Timeline reconstruction
A written chronology of events, prepared at the time (not for litigation), showing when the employer first learned of the triggering circumstance, what actions were taken and when, and when the decision to close or reduce was made. If this document was prepared after the fact, be prepared to explain when and why.
Employment counsel opinion at the time
An opinion from employment counsel documenting the exception claim contemporaneously is powerful evidence that the decision was made in good faith and in reliance on professional advice. This does not guarantee the exception applies, but it is strong evidence against a willful violation finding, which affects the penalty calculation.
The employer bears the burden of proof at trial
Without contemporaneous documentation, courts apply exceptions narrowly against the employer. Retroactive reconstruction of the factual record rarely satisfies the standard. The time to build the documentation file is when the decision is being made, not when the complaint is filed.
How circuits differ
Courts do not uniformly apply WARN exceptions. Employers operating across multiple states face different risk profiles depending on where the employment loss occurs. The Ninth Circuit is consistently the most restrictive. State WARN laws introduce additional complexity: some states have no analogue to the faltering company exception at all.
Penalty exposure when an exception fails
WARN exceptions are defenses, not safe harbors. If an employer claims an exception and loses in court, the penalty is calculated as if no notice was given at all from the date notice should have been provided. The employer does not get credit for the notice it eventually gave.
$500/day
Civil penalty per unit of local government
Owed to each unit of local government for each day of violation, up to 60 days. Capped at $30,000 per site.
60 days
Back pay per affected employee
Each affected employee can recover back pay and benefits for each day of violation, up to 60 days. Back pay is calculated at the employee's regular rate of compensation.
Attorneys' fees
Awarded to prevailing employees
Prevailing employees recover reasonable attorneys' fees. WARN cases are frequently brought as class actions, multiplying the attorneys' fee exposure significantly.
Example calculation
A plant closing with 200 affected employees, average salary $80,000/year ($308/day), notice short by 30 days.
Back pay: 200 employees × $308/day × 30 days = $1,848,000
Benefits continuation: estimate 30% of salary = ~$554,400
Civil penalty: $500/day × 30 days = $15,000 (capped at $30,000)
Attorneys' fees: contingency counsel typically takes 25-33% of recovery
Total exposure estimate: $2.4M+ before attorneys' fees
This is a simplified estimate. Actual damages depend on benefits values, whether bumping rights exist, and class certification outcomes.
WARN cases are typically filed as class actions
All affected employees at the same site are automatically in the class. There is no individual damages calculation. Courts award aggregate back pay and benefits across the entire class. The class action structure means that even a small WARN violation can produce material litigation exposure.
Statute of limitations: 3 years
WARN claims must be filed within 3 years of the date of the violation under the applicable statute of limitations. Employees who were not given notice have 3 years from their separation date to sue.
Frequently asked questions
People Plan
WARN exception risk flagged before notice is drafted
People Plan flags WARN exception risk automatically. When a layoff's timeline suggests an exception may be needed, it surfaces the documentation checklist before notice is drafted, so you are not reconstructing the record after the fact.