Laid Off in a Second or Third Round: How Repeated RIFs Affect Your Severance

When a company runs two, three, or four rounds of layoffs over a span of months, the experience for employees in later rounds differs in several ways. The company is smaller by the time you are affected. The people who remain are the people the company worked hardest to keep. The process is often more deliberate than the first wave. And the legal question of whether the WARN Act applies is more complicated than it was in Round 1, because of a rule called the 90-day aggregation provision.

Your severance offer still gets graded the same way as it would have in any earlier round: against benchmarks for your tenure, your role, and your employer's publicly disclosed practices. The round number does not enter that math. But the 90-day aggregation rule, and the OWBPA group disclosure requirements that attach whenever two or more employees are laid off together, can change what you are entitled to ask for and what defects in your paperwork you should know about.

Why companies do layoffs in rounds

Companies stagger reductions in force for several reasons: to manage internal communication costs, to respond incrementally as business conditions evolve, to target different functions in sequence, or to avoid triggering a single large federal notice requirement all at once. The federal WARN Act anticipated this behavior. The statute's 90-day aggregation provision explicitly prevents an employer from defeating WARN coverage by spreading separations across multiple smaller rounds, unless the employer can show each round had separate and distinct causes (29 U.S.C. § 2102(d), Cornell LII, verified May 2026).

For employees, the reasons behind multiple rounds matter less than the legal structure they create. What matters is whether the aggregated headcount crossed the threshold at your site within the 90-day window.

The WARN Act 90-day aggregation rule

The federal WARN Act requires private employers with 100 or more full-time employees to provide 60 days of advance written notice before a plant closing affecting 50 or more workers at a single site, or a mass layoff affecting either 50 to 499 workers who constitute at least 33% of the active workforce at a single site, or 500 or more workers regardless of percentage (29 U.S.C. § 2101(a)(2)-(3), Cornell LII, verified May 2026).

Subsection (d) adds the aggregation rule: "employment losses for 2 or more groups at a single site of employment, each of which is less than the minimum number of employees specified in section 2101(a)(2) or (3) of this title but which in the aggregate exceed that minimum number, and which occur within any 90-day period shall be considered to be a plant closing or mass layoff." The employer has one rebuttal: demonstrating that the losses "are the result of separate and distinct actions and causes and are not an attempt by the employer to evade the requirements of this chapter" (29 U.S.C. § 2102(d), Cornell LII, verified May 2026).

The rebuttal is technically available but difficult to establish in practice. Courts have been skeptical when the rounds occurred close together, involved the same function or department, or were announced in overlapping communications. Separate budget decisions that happened to produce layoffs in the same quarter do not automatically satisfy the "separate and distinct causes" test.

If a WARN violation occurred, the remedy is back pay calculated for the period of the violation, up to a maximum of 60 days but in no event for more than half the total number of days you were employed by that employer. The rate is the higher of your average regular rate over the prior three years or your final rate. Add the value of employer-paid benefits during that period. Wages and benefits already paid during the notice gap reduce the liability dollar for dollar (29 U.S.C. § 2104, Cornell LII, verified May 2026).

What the aggregation rule means if you were in a later round

The analysis starts with headcount at a single site. WARN's thresholds apply to a single site of employment, not the company as a whole. If you worked at a headquarters with 400 employees, and your company ran a round of 30 in February and a round of 25 in April, the April round triggers WARN: 55 workers combined at a single site within 90 days exceeds the 50-worker floor.

If the February employees received no notice and no back pay, and you received no notice in April, you have a WARN claim for up to 60 days of wages and benefits from your separation date. The February employees may also have a claim, depending on whether a prior round (if any) pushed their combined count above threshold.

The single-site requirement is where remote work creates complexity. Court interpretations through 2026 have generally counted remote employees as employed at the site they are assigned to or from which they receive direction, even when they have not physically visited in years. A remote engineer assigned to a San Francisco headquarters is counted as part of that site's headcount for purposes of the WARN threshold (29 U.S.C. § 2101(a)(1), Cornell LII, verified May 2026). The DOL has not issued binding remote-work-specific guidance, so court decisions remain the operative framework.

Document the key dates: when you received verbal notice of the layoff, when you received any written notice, your last day of employment, and the approximate number of employees affected in each round you are aware of. If the employer gave you fewer than 60 days of written notice and the aggregated headcount crossed 50, the WARN back-pay calculation runs backward from your separation date for up to 60 days, subject to a cap of half the total days you were employed by that employer.

Group exit disclosures and OWBPA

Whenever two or more employees are laid off together as part of an exit incentive or other employment termination program, the Older Workers Benefit Protection Act requires the employer to disclose the job titles and ages of all individuals eligible or selected for the program, and the ages of all individuals in the same job classification or organizational unit who are not eligible or selected (29 U.S.C. § 626(f)(1)(H), Cornell LII, verified May 2026). The EEOC refers to this group as the "decisional unit" in its implementing regulations; the statute calls it the "organizational unit."

This disclosure serves two functions. It gives affected employees the data to assess whether the selection criteria disparately affected workers 40 and over. And it is a waiver requirement: an OWBPA-defective release does not bar the affected employee from bringing an age-discrimination claim under the ADEA, even if the employee signed and accepted the severance. Courts have held that the employee does not have to return the severance before pursuing a claim based on a defective waiver. For the full OWBPA framework, including the 7-day revocation window and the complete list of waiver requirements, see The 21-Day OWBPA Consideration Period for Severance Agreements.

If your company ran multiple rounds and treated each as a separate program, each round requires its own disclosure. If the rounds are treated as a single phased program, the disclosure should cover the full group. Check what your separation paperwork calls the program. If the disclosure covers only the employees in your specific round and not employees from prior rounds in the same function or job classification, it may be defective, particularly if the prior round drew from the same organizational unit.

For any group termination program, OWBPA extends the consideration period from 21 days to 45 days. The 7-day revocation window stays the same in both cases (29 U.S.C. § 626(f)(1)(F)(ii), Cornell LII, verified May 2026).

The severance calculation: tenure-based, not round-dependent

Your base severance calculation uses your actual hire date. Surviving prior rounds does not reset your tenure clock or reduce your multiplier. Being caught in a later round means you have more tenure than you would have had if you had been in Round 1, which directly increases your baseline.

The layoff calculator grades your offer against public-company benchmarks using your years of service, your salary, your state, and your employer's size. It does not ask which round you were in, because round number is not a variable in any severance formula. Enter your total tenure at the company. The calculator grades the offer against benchmarks for that tenure and role.

What round number does affect is your WARN analysis (via the aggregation rule) and your OWBPA disclosure rights. Both are surfaced by the calculator when the inputs warrant it.

Negotiating position in later rounds

Employees in later rounds often have more room to negotiate than those in earlier rounds. The first round at a company is typically a broad cut: headcount targets set, functions reduced, swift execution. By the second or third round, the company has cut to the people it most needed to keep. Those employees hold context, relationships, and institutional knowledge that is not documented anywhere else.

Name that concretely when you make a counteroffer. "I'm managing five active client relationships that haven't been transitioned" is a specific negotiating point. "I'm the only person left who knows how this system works" is another. These create real transition costs for the company, and the company knows it. The ask does not have to be larger cash. It can be extended healthcare beyond the standard COBRA window, a longer post-termination exercise window for vested options, a neutral reference letter with agreed-upon talking points, acceleration of unvested equity that would have vested in the next quarter, or removal of a non-compete clause that overreaches.

All of these are negotiable at the later-round stage, when the company has a clear interest in a cooperative transition. The layoff calculator grades your starting offer and surfaces specific items with room to move based on your inputs.

State mini-WARN rules and multi-round layoffs

Several states layer additional protections on top of the federal floor. Thresholds, notice periods, and aggregation windows all vary.

California (Cal-WARN) defines a mass layoff as a layoff during any 30-day period of 50 or more employees at a covered establishment. A covered establishment is any employer with 75 or more employees within the preceding 12 months. Cal-WARN does not include a standalone 90-day aggregation provision comparable to the federal statute, but its lower 75-employee coverage threshold catches companies that fall below the federal 100-employee floor, and its 30-day mass-layoff window is shorter than the federal 30-day period for plant closings (Cal. Lab. Code § 1400 et seq., leginfo.legislature.ca.gov, verified May 2026).

New York's WARN statute imposes a 90-day notice period rather than the federal 60-day floor and covers employers with as few as 50 employees. New Jersey's WARN law adds mandatory severance pay when WARN notice is owed. Illinois requires 60 days of notice and covers employers with 75 or more full-time employees. The full state-by-state comparison with threshold tables appears in The 60-Day WARN Notice Period: What Counts and What Doesn't.

The practical implication for multi-round situations: if your company's rounds were close together and your state has a shorter aggregation window or a lower employee threshold, your state statute may cover you even when the federal statute does not. Check both.

How to use the calculator

Enter your total years of service at the company (counting from your original hire date, not the date of the round you survived), your state, your salary, and the severance offer you received. The calculator grades the offer against public-company benchmarks for your tenure and role and runs the WARN eligibility check based on company size, separation type, and the gap between any notice and your separation date.

If WARN applies to your situation, the calculator surfaces the context. The actual back-pay claim, if you have one, is filed in federal district court directly (WARN does not require an agency filing first). The calculator identifies whether the math suggests a claim worth investigating, not whether the claim will succeed.

FAQ

Does the WARN Act 90-day aggregation rule combine rounds from different company locations?

No. The aggregation rule applies within a single site of employment. A company that cut 30 employees in one city in January and 30 employees in a different city in March has not triggered WARN under the aggregation rule, because the sites are separate. Each site's headcount is analyzed independently against the thresholds in 29 U.S.C. § 2101(a)(2)-(3). Employees at a site with fewer than 50 total affected workers across all rounds do not have a WARN claim based on aggregation (29 U.S.C. § 2102(d), Cornell LII, verified May 2026).

Can my employer defeat the aggregation rule by showing the rounds had different causes?

The statute permits the rebuttal, but it is narrow. The employer must show the losses were "the result of separate and distinct actions and causes and are not an attempt by the employer to evade the requirements of this chapter." Courts have read this strictly: separate budget line items are not enough. The employer needs to show the decisions were made independently, by different decision-makers, for different reasons, without coordination. When two rounds affect the same function, the same department head made both decisions, and the company cited the same economic rationale in both sets of separation paperwork, the rebuttal is unlikely to succeed (29 U.S.C. § 2102(d), Cornell LII, verified May 2026).

Does the round number change the OWBPA consideration period?

No. For any group termination program affecting two or more employees, the consideration period is 45 days regardless of whether this is the first, second, or third round. The 7-day revocation window is the same in all cases. The employer must attach the age-and-job-title disclosure at the start of the consideration period, not at the end (29 U.S.C. § 626(f)(1)(F)-(H), Cornell LII, verified May 2026).

What if my employer did not provide the OWBPA group disclosure?

A missing or incomplete group disclosure is a waiver defect. A defective OWBPA release does not bar an ADEA claim even if you signed the agreement and accepted the severance. You do not have to return the severance to pursue the ADEA claim. To bring an ADEA claim, file a charge at the EEOC within 180 days of the alleged discriminatory act (or 300 days in states with their own anti-discrimination agencies). The EEOC investigates and either pursues the charge or issues a right-to-sue letter (EEOC charge filing, verified May 2026). For the full OWBPA framework, see The 21-Day OWBPA Consideration Period for Severance Agreements.

Does surviving earlier rounds entitle me to a higher severance multiplier?

No calculation adjusts automatically for prior-round survival. Your severance is based on your total tenure at the company. Surviving prior rounds means you have more tenure when the later round hits you, which increases your baseline, but there is no premium attached to the round number itself.

I work remotely in a different state than my company's headquarters. Which state's mini-WARN applies?

The analysis runs on two tracks. Federal WARN coverage is determined by the headcount at your assigned site of employment, which is generally your employer's location rather than where you physically sit. The applicable state mini-WARN is generally the state where your assigned worksite is located. If you are assigned to a California headquarters, Cal-WARN applies even if you have never physically visited California. If your state of residence has its own WARN statute and your employer meets its threshold, that state's law may also apply. Check both the state of your assigned worksite and the state of your residence if they differ.