Was your employer required to give 60 days' notice — and does the rule reach a remote worker?

Sixty is the number everyone knows and the one nobody argues about. What gets litigated is coverage — and a layoff that feels enormous to the people inside it is often outside the Act entirely.

Most layoffs are not WARN layoffs

Two gates. The first is the employer: under 29 U.S.C. § 2101(a)(1), a business employing 100 or more people excluding part-time employees, or 100 or more including part-timers who in the aggregate work at least 4,000 hours a week exclusive of overtime. "Part-time" is broader than it sounds — an average under 20 hours a week or employment for fewer than 6 of the 12 months before notice was due. Everyone under six months’ tenure drops out of the count, so the people most likely to be cut are the least likely to count.

The second gate is the event. A plant closing shuts a single site, or a facility or operating unit within one, causing employment loss for 50 or more employees in any 30-day period. A mass layoff is a reduction in force that is not a plant closing and causes employment loss at a single site in 30 days for at least 33 per cent of the employees and at least 50 of them, or for 500 regardless of percentage.

"Employment loss" is narrower than "the job ended": a termination other than for cause, voluntary departure or retirement; a layoff exceeding six months; or a cut in hours of more than half in each month of any six-month period. A furlough announced as three months is not one when it starts, though § 2102(c) makes it one retroactively if it runs past six.

For a remote worker, the whole case is which site you counted at

Every threshold above is measured at a single site of employment. That is the live question for a distributed company: if thirty engineers in twelve states each count as their own site, nothing aggregates and nothing triggers.

20 CFR 639.3(i) begins geographically — contiguous locations, a campus, buildings across the street; or separate buildings in reasonable proximity that serve the same purpose and share staff and equipment. Locations in different states, hundreds of miles apart, do not aggregate.

None of that reaches a spare room. For remote staff, subsection (i)(6) is the only route: for workers who travel point to point, who are outstationed, or whose primary duties fall outside any of the employer’s regular sites, the single site is the one "to which they are assigned as their home base, from which their work is assigned, or to which they report". The limbs are disjunctive — one is enough.

That second limb is where a modern claim lives or dies, and it splits teams. If your manager sits in an office and reviews your output from there, that office is arguable. If your manager is also remote and head office only runs payroll, there may be no site to attach you to, no aggregation, and no notice owed to anyone. Where you were hired, taxed and insured is a separate question, covered in multi-state remote employment.

New York answered the remote question. Most states have not.

Federal WARN is a floor, and the state statutes stacked on top of it are where the remote-work gap has actually been closed. New York’s regulations count, among those employed at a single site, individuals "who work remotely but are based at the employment site" — the aggregation the federal rule leaves to litigation, written into the headcount.

A minority of states have a statute of this kind, the list has grown recently, and no two are drafted alike — some lower the threshold, some lengthen the notice, at least one attaches mandatory severance. Any roster printed here would rot. Read your own state workforce agency’s WARN page before concluding nothing was owed: identical facts can fail federally and succeed under state law.

Sixty days of severance is not sixty days of notice

This is the most widely held wrong belief about the Act, and employers hold it as often as employees. Section 2102(a) prohibits ordering the closing or layoff before sixty days have run from written notice. There is no pay-in-lieu clause anywhere in the statute.

Money appears only in § 2104, the remedies section, and only as a subtraction from damages already owed. Liability is back pay for each day of violation at the higher of the last three years’ average regular rate or the final rate, plus benefits under an ERISA plan — capped at 60 days and, separately, at half the days the employee worked. Someone dismissed after ninety days recovers at most forty-five.

Section 2104(a)(2) allows exactly three reductions: wages paid for the period of the violation; payments to a third party or trustee, such as health premiums or pension contributions, on the employee’s behalf; and "any voluntary and unconditional payment by the employer to the employee that is not required by any legal obligation".

The word doing the work is unconditional, and courts take it literally. The Ninth Circuit refused the offset where severance was conditioned on employees staying until the casino closed; the Seventh Circuit refused it where payments were tied to settlements in which unions dropped pending lawsuits. Both refusals were recited by the First Circuit in Rivera-Pina v. Luxury Hotels International of Puerto Rico (2024), where genuinely unconditional payments did wipe the claim out.

The exceptions are real, narrow, and easy to forfeit

20 CFR 639.9 puts the burden of proof on the employer and states that the exceptions should be narrowly construed. There are three.

• Faltering company. Plant closings only, never mass layoffs. The employer must have been actively seeking capital or business, had a realistic opportunity to get it, shown it would have avoided or postponed the shutdown, and reasonably believed notice would have precluded it.
• Unforeseeable business circumstances. A sudden, dramatic and unexpected condition outside the employer’s control — a principal client cancelling a major contract, a strike at a major supplier — tested against the commercially reasonable business judgment of a similar employer, not against hindsight.
• Natural disaster. The closing must be a direct result of a flood, earthquake, storm or similar event. This is the only place the Act allows notice after the fact.

The failure mode is structural rather than factual. All three shorten the length of the notice; none removes the duty to give it. Section 2102(b)(3) requires as much notice as is practicable and, at that moment, a brief statement of the basis for reducing the period. An employer that stays silent until the morning of the layoff and produces its explanation for the first time in litigation has usually lost the exception before anyone asks whether the circumstance was foreseeable.

If no notice was given

First check that nothing you received counts. 20 CFR 639.7 requires notice to be specific and based on the best information the employer holds when it serves — which most pre-layoff communication is not.

Two structural facts then shape the next move. Section 2104(b) makes those remedies exclusive and states that a federal court "shall not have authority to enjoin a plant closing or mass layoff" — nobody can stop the layoff, and the claim is only ever for money. And WARN sets no limitation period of its own: in North Star Steel Co. v. Thomas (1995) the Supreme Court held that state law supplies it, so the deadline is borrowed and varies with where suit is filed.

Recovery is back pay and benefits for the period of the violation, capped at sixty days and at half the days you worked, and a court may reduce even that on proof of good faith. The separate penalty of up to $500 a day is payable to local government, not to you. Unpaid final wages are a different claim on a different clock — final paycheck rules apply whether or not notice was owed.

What the Act is actually for

WARN is not a job-protection statute, and reading it as one produces the wrong strategy. Congress wrote a disclosure rule with a capped price attached, then told the courts they could not stop the closure. The most an employer can be made to pay is sixty days, less whatever it already handed over.

Which makes the notice worth more than the damages. Sixty days of warning is a job search run while you are still employed, still insured, still able to open the payroll portal; sixty days of back pay is the same money two years later after a fee-shifted fight. So on the day a layoff is announced the useful question is not whether you can sue. It is which site your job was assigned to, and whether anything was filed with the state — both answerable for free, and both harder to establish every week that passes.