Reductions in force

A reduction in force is the workspace's most legally fraught HR event: every selection is reviewed for protected-class disparate impact, every notice deadline is statutory, and every release requires precise ADEA / OWBPA language to be enforceable. The RIF file gives you the planning workspace, the selection-criteria worksheet, the adverse-impact analyzer, the WARN-Act timeline, and the release-packet generator — with every step gated by a documented audit trail so the workspace's defense is built into the file as you go.

TL;DR — Open ELR → RIFs → New plan. State the business justification, pick the affected unit(s), define objective selection criteria, score employees, run the adverse-impact analyzer, generate the WARN timeline, draft the release packets, transmit notifications on the calendar the file built. Every step is signed by two reviewers; the file is the defense record.

Before you start

• Counsel is non-optional. The RIF file walks the workspace through best-practice steps, but counsel must review the business justification, the selection criteria, the adverse-impact analysis, and the release language.
• Confirm the scope — single site, multiple sites, business unit, function — and the expected headcount + threshold for WARN.
• Confirm whether any collective-bargaining unit is in scope. RIFs in a represented unit have effects-bargaining obligations and may have CBA-specified selection criteria (seniority, classification).

Define the plan

1. 1

   Open ELR → RIFs → New plan

   A multi-section plan form opens.

2. 2

   Write the business justification

   Why is the reduction necessary, what alternatives were considered (hiring freeze, attrition, voluntary separation program), why each was insufficient. This narrative is the foundation of every later legal defense.

3. 3

   Define the scope

   Affected sites, business units, functions, headcount targets. Workforce data is pulled from HCM at the moment of definition and snapshotted on the file (so later changes don't drift the analysis).

4. 4

   Pick the selection methodology

   Performance-based / skills-based / seniority-based / role-elimination / hybrid. Each carries different evidentiary requirements. Role-elimination is cleanest legally; seniority is required by most CBAs; performance-based requires the strongest documentation.

5. 5

   Define the selection criteria

   Each criterion is one row: what it measures, how it's scored, weight in the composite, and the source of the data. Subjective criteria ("cultural fit") are red flags — replace with observable behaviors and documented records.

6. 6

   Pick the calibration committee

   A multi-person committee (typically 3-5) that scores each employee against the criteria independently before averaging. Single-scorer selections are highly vulnerable on review.

Score the workforce

1. 1

   Open Scoring → Workforce list

   Every employee in scope appears with their HCM record loaded (role, level, tenure, last performance rating).

2. 2

   Each committee member scores independently

   Members can't see each other's scores until all have submitted. The form locks once all scorers have completed.

3. 3

   The composite is computed

   Each criterion is averaged across the committee; the weighted composite produces the rank-order.

4. 4

   Apply the cut line

   The selection list is the lowest-composite employees down to the headcount target. The file shows the boundary scores explicitly so you can see how close the cut is.

5. 5

   Hold a calibration session

   Committee meets, reviews edge cases (employees on or near the cut line), captures the discussion. Calibration is recorded — the discussion is part of the defense record.

Adverse-impact analysis

The 4/5ths rule (29 CFR § 1607.4) is the EEOC's screening test for disparate impact: a selection rate for a protected group that's less than 4/5ths (80%) of the rate for the comparison group triggers an adverse-impact inquiry. The file runs the analysis automatically.

WARN Act timing

The federal WARN Act requires 60 calendar days' notice for plant closings or mass layoffs at single sites with 50+ affected workers (thresholds vary; state mini-WARN acts may be stricter — CA, NY, NJ, HI in particular).

1. 1

   The file computes WARN coverage

   Federal WARN triggers (50+ at single site for plant closing, 50+ and 1/3 of workforce OR 500+ for mass layoff at single site). State mini-WARN triggers per affected state.

2. 2

   Notice list assembles automatically

   Federal WARN notices go to affected workers, their union (if any), the state dislocated-worker unit, and local elected officials. State mini-WARNs may add more.

3. 3

   Generate notice templates

   Each template is pre-filled per worker / per recipient with the statutory content. Review before sending.

4. 4

   Schedule the transmission calendar

   The 60-day clock runs from notice receipt, not notice send. The calendar bakes in the buffer for receipt + return.

5. 5

   Document any exception relied on

   Faltering-company / unforeseen-business-circumstance / natural disaster exceptions exist but are narrow. Document the basis if relying on one — they're commonly tested in litigation.

Release packets (ADEA / OWBPA)

If the RIF includes employees aged 40 or over, a release of ADEA claims must comply with the Older Workers Benefit Protection Act:

Notification day

1. 1

   The file schedules notification meetings

   One meeting per affected employee with manager + HR rep. Sequencing matters — supervisors should learn before their reports; senior leaders before line workers.

2. 2

   Each meeting is logged

   Date, time, attendees, materials delivered, employee's response (signed receipt of notice, took the packet to review, declined to sign, etc.).

3. 3

   System access changes happen on the documented schedule

   Per workspace policy. Cutting access during the meeting is the default; same-day post-meeting is common.

4. 4

   HCM lifecycle transition starts

   The HCM separation flow takes over for final pay, benefits-continuation election (COBRA), equity treatment per plan documents, and final-paycheck timing per state law.

Common gotchas

• "We need to add someone to the list after notification day." Adding affected employees after the cohort definition was finalized invalidates the OWBPA disclosure for the originally noticed group. Either run a separate cohort with a full process, or accept that you must re-issue disclosures + restart consideration periods.
• "The performance data we're scoring on is incomplete." Document the gap and either (a) supplement before scoring, or (b) exclude the criterion. Scoring on incomplete data invites a disparate-impact challenge.
• "The 4/5ths analysis is fine but a single named protected individual was selected." 4/5ths is the screening test for the group; a single selection may still face individual disparate- treatment scrutiny. Document the non-discriminatory basis for that selection particularly carefully.
• "The union wants to bargain over the layoff list itself." Decision bargaining over a RIF is usually not required (it's a business decision), but effects bargaining (severance, recall rights, transfer rights) typically is. Don't conflate.
• "We want to backdate notices to compress the timeline." Don't. WARN penalties are 60 days' back-pay and benefits per affected worker for inadequate notice — and backdating compounds the violation with bad-faith findings.

Troubleshooting

How this is recorded

The RIF file is the workspace's single source of truth and the defense record if any individual selection is later challenged. The ledger captures business justification, selection methodology, calibration committee, individual scores, the adverse-impact analysis at the time of decision, the WARN timeline, every notice transmission, every release packet's status. The file's retention runs for the longer of the workspace's audit-log retention SECURITY floor and any statutory minimum (4 years for ADEA records under 29 CFR § 1627.3).