OWBPA group exits: 21 vs 45 days and the disclosure requirement

When the 45-day window applies — “group” defined#

The OWBPA establishes two parallel tracks for the review-period requirement. For an individual termination, 29 U.S.C. § 626(f)(1)(F)(i) requires the employer to give the employee at least 21 days to consider the agreement before signing. For a group exit, § 626(f)(1)(F)(ii) requires at least 45 days. The statute uses the phrase “exit incentive or other employment termination program offered to a group or class of employees” — the two key terms being “program” and “group or class.”

The EEOC’s procedural regulations at 29 C.F.R. § 1625.22 elaborate. A “program” under OWBPA exists when an employer offers additional consideration (above what employees would otherwise receive) in exchange for a release of claims to two or more employees. The phrase “group or class” turns on whether the offer is being made to a defined population rather than to a single individual. There is no statutory minimum number of employees that triggers the program designation — two is enough if the offer is made on standard terms to both, with the § 626(f)(1)(H) disclosure attached.

In practice, three patterns commonly trigger the group-exit rules: (1) a reduction in force or mass layoff where the employer offers severance in exchange for releases from all affected employees; (2) an “exit incentive program” or voluntary separation program where the employer invites employees in a defined population (often defined by age, tenure, salary band, or organizational unit) to volunteer for separation in exchange for enhanced severance; and (3) staggered or rolling reductions that are administratively structured as separate “waves” but that are part of a single overarching plan. The third pattern is where employers most often get OWBPA wrong — treating each wave as a series of individual terminations to avoid the 45-day window and the disclosure requirement, when the reality is a single program with a single decisional unit.

If you are 40 or older and were laid off as part of a reduction that affected more than one employee on your team, in your function, or in your business unit, ask explicitly whether the 45-day window and § 626(f)(1)(H) disclosure apply. A separation packet that provides only 21 days and no disclosure, when the reduction was in fact a group exit, is procedurally defective on the ADEA portion of the release. See the tech-layoff negotiation guide for how to use this leverage.

The § 626(f)(1)(H) disclosure requirement#

The substantive content of the OWBPA group-exit disclosure is defined by statute and elaborated by the EEOC procedural regulations. 29 U.S.C. § 626(f)(1)(H) requires that the employer inform the individual in writing, in a manner calculated to be understood by the average individual eligible to participate, of: (i) any class, unit, or group of individuals covered by the program, any eligibility factors for the program, and any time limits applicable to the program; and (ii) 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 for the program.

The 29 C.F.R. § 1625.22 regulations expand on each requirement. The eligibility factors must be specific enough that the recipient can understand who was eligible and on what basis. Time limits must include the deadline for accepting the offer. The job-title-and-age listings must be sufficient to permit the recipient (or their counsel) to assess whether the selection pattern shows a disparate impact on older workers. The regulations are explicit that the lists must reflect the decisional unit — not a smaller artificially-defined subset chosen to obscure the age distribution — and that ages must be presented in a way that is meaningfully comparable (e.g., individual ages or age bands narrow enough to permit statistical analysis).

The disclosure is the OWBPA’s most consequential structural feature. The point is to give older workers the information they need to identify a potentially discriminatory selection pattern before they sign away their ADEA claims. When the disclosure shows that the selected group skews materially older than the not-selected group within the same decisional unit, the recipient has direct evidence of potential disparate impact. The statute reasons that an employee asked to release age claims should not have to rely on the employer’s representation that no age discrimination occurred — the data should be on the table.

Three frequent disclosure defects: (1) the employer provides the “selected” list but not the “not-selected” list (a clear violation); (2) the employer provides job titles but only age bands too broad to detect a pattern (e.g., “over 40” vs “under 40” rather than individual ages); and (3) the employer defines the decisional unit too narrowly (e.g., listing only the laid-off team rather than the broader organizational unit from which the selection was actually made). All three are common, all three are challenged in litigation, and all three are appropriately raised with counsel before signing.

What “decisional unit” means — and why employers get it wrong#

The decisional unit is the portion of the employer’s organizational structure from which the employer chose the persons who would be offered consideration for signing the waiver. The EEOC procedural regulations at 29 C.F.R. § 1625.22(f)(3)(ii) define the concept, and its scope drives everything about the disclosure’s usefulness. A correctly defined decisional unit produces a disclosure that lets the recipient see the age distribution of the population from which selections were made; an incorrectly defined unit produces a disclosure that conceals the pattern.

The unit can be an entire facility, a department, a division, a job classification across multiple facilities, or some other organizational subunit. The defining question is operational: where did the selection actually happen? If a VP-level decision-maker compared all engineering managers across three divisions and selected which ones to lay off, the decisional unit is the full population of engineering managers across the three divisions — not the division-specific subsets, and not the laid-off employees alone. If a department head compared all engineers within a single product team and selected which to lay off, the decisional unit is the engineering population of that product team.

Employers get this wrong most often by defining the unit downward. Common patterns include defining the unit as the laid-off employees plus their immediate manager’s remaining direct reports (excluding the rest of the function); defining the unit by sub-team rather than by the organizational level at which the selection was made; and defining the unit by tenure or salary band rather than by organizational position. Each narrowing reduces the visible pattern. If the larger population from which selections were actually made skews younger than the subset disclosed, the disclosure understates the disparate-impact signal that the OWBPA was designed to surface.

The remedy for a too-narrow decisional unit definition is the same as for any OWBPA defect: the ADEA waiver is unenforceable to the extent the disclosure failed to comply with the statute. If you suspect the disclosure understates the actual decisional unit, document the organizational structure as you understood it during employment, preserve any internal communications about the layoff selection process, and consult counsel before signing. The information needed to challenge the unit definition is usually documented in the very materials the employer distributed during the reduction process.

When the 7-day revocation clock starts#

The OWBPA’s seven-day post-signing revocation period is established by 29 U.S.C. § 626(f)(1)(G) and is non-waivable. It applies to both individual (21-day) and group (45-day) OWBPA tracks. The clock starts on the day after the employee signs and runs for seven calendar days. During the revocation window, the employee may revoke the agreement in writing for any reason; revocation undoes the ADEA waiver and, depending on the agreement’s severability language, may unwind the entire release.

The agreement is not legally effective until the revocation period closes. Employers occasionally pay the severance immediately upon receiving the signed agreement; if so, and you revoke during the seven-day window, you must return the consideration. Most employers withhold payment until day 8 to avoid this complication. Either way, the revocation right is real and operative.

Two operational points. First, “in writing” means in writing — not orally, not by inference, not by failing to perform. A clear written revocation delivered by traceable means (certified mail with return receipt, or a formal email to HR and legal) within the seven-day window is the safe practice. Second, any material change to the agreement during the review window restarts the 21-day or 45-day consideration clock under the EEOC procedural regulations — but it does not necessarily extend the seven-day revocation period that begins on signing. The two clocks are governed by different statutory subsections and operate independently.

Defects that void the release#

The OWBPA is unusual among federal employment statutes in establishing a precise procedural checklist for a valid waiver. Failure to comply with any of the listed requirements voids the ADEA waiver as to the employee. Common categories of defect:

Failure to allow the full review window. A 21-day window that is in fact a 14-day window (because the employer presented the agreement with an earlier signing deadline) is procedurally invalid as to ADEA. The same applies to a group exit presented with only 21 days when 45 are required.

Failure to provide the § 626(f)(1)(H) disclosure for group exits. No disclosure at all, an incomplete disclosure (missing the not-selected list), or a disclosure that defines the decisional unit too narrowly all create the same OWBPA-validity question.

Plain-English failure. The statute and regulations require that the waiver be written in a manner calculated to be understood by the average individual eligible to participate. Agreements drafted in dense legalese, in font sizes that obscure key terms, or that omit a clear explanation of what the employee is giving up are vulnerable on this ground.

Failure to advise consultation with counsel. &Sect; 626(f)(1)(E) requires the agreement to advise the employee in writing to consult with an attorney before signing. Agreements that omit this advice are non-compliant.

Waiver of post-signing claims. &Sect; 626(f)(1)(C) prohibits the waiver of claims that arise after the signing date. An agreement purporting to release future ADEA claims is invalid to that extent.

Failure to provide consideration above what is already owed.&Sect; 626(f)(1)(D) requires the waiver to be in exchange for consideration in addition to anything to which the individual is already entitled. If the only “consideration” is the payment of wages already owed under a pre-existing severance policy, ERISA plan, or employment contract, the waiver fails for lack of consideration.

ADEA implications when OWBPA defects are present#

A defective OWBPA waiver does not bind the employee on ADEA claims. The Supreme Court’s 1998 decision in Oubre v. Entergy Operations, Inc., 522 U.S. 422, settled the most important question about the remedy: the employee need not return the severance consideration before suing under the ADEA. The non-compliant release is unenforceable as a defense to an ADEA suit, and the employer cannot condition the suit on tender-back of the payment. The ADEA — codified at 29 U.S.C. § 623 — prohibits age discrimination in employment, including discriminatory selection in a reduction in force.

The practical implications. First, the OWBPA disclosure is itself the document on which an ADEA disparate-impact analysis is built. If the § 626(f)(1)(H) disclosure shows that the selected group’s mean age materially exceeds the mean age of the not-selected group within the same decisional unit, the employee has direct evidence relevant to an age-discrimination claim. The EEOC has historically scrutinized disclosures with this pattern. Second, the combination of an OWBPA defect (procedural) and a disparate-impact pattern in the disclosure (substantive) is often the predicate for class or collective action under the ADEA, where the affected employees pool their claims and litigate together.

Third, even where the OWBPA disclosure is procedurally compliant, the data it contains may itself be evidence in a discrimination claim. The OWBPA is structurally designed to put age data on the table at the moment of separation, when the employee has the practical opportunity to assess whether to release age claims or to investigate further. Treat the disclosure as the document it is, not as boilerplate.

For the broader negotiation context, see the tech-layoff negotiation guide; for the operative review-window mechanics, see the reading your severance agreement guide; and for the federal and state UI implications of severance structure, see the severance and unemployment by state guide. The scenarios index documents related fact patterns, and the methodology page sets out the underlying statutory citations the calculator uses.