The hardest thing HR does, done under time pressure

A reduction in force (RIF) is a layoff driven by business need rather than individual performance — a lost contract, a budget cut, a restructure. It is the single highest-risk event a small HR function handles, because it concentrates several legal exposures into one decision made quickly and under stress: who gets selected, how the selection is documented, whether a release is signed, and whether the cut is large enough to trigger advance-notice law. Get the process right and a RIF is a sad-but-clean business decision. Get it wrong and you've handed several former employees a discrimination claim and possibly violated a federal notice statute.

This is a practical framework, not legal advice — and a RIF is one of the genuinely worth-it moments to involve counsel before you act, because the cost of getting it wrong dwarfs the cost of the review. What follows is how to think about it so that conversation is short.

Pick the unit, then the criteria — in that order

The most common RIF mistake is choosing people and then reverse-engineering a rationale. Do it the other way around:

  • Define the selection unit. Which department, location, function, or job level is being reduced, and why does the business case point there? Write the business rationale down before any names are attached.
  • Define objective, job-related selection criteria. Seniority, specific skills the surviving roles need, documented performance, or elimination of an entire role or location. Decide the criteria, then apply them mechanically to everyone in the unit.

The reason for this order is legal defensibility. If you pick names first, you cannot prove the selection wasn't driven by age, race, sex, disability, or another protected trait. If you pick criteria first and apply them uniformly, the selection is explainable on its face.

Run an adverse-impact check before you finalize

Even neutral-looking criteria can land disproportionately on a protected group. Before you finalize the list, compare the demographics of the selected group against the unit they were drawn from. If everyone you're cutting is over 50, or the cut skews heavily by sex or race relative to the pool, you don't necessarily have to change the decision — but you must understand why the criteria produced that result and be able to defend it as job-related. This is the same disparate-impact discipline that governs a pay-equity audit and your knockout screening questions: a neutral rule with a skewed result is exactly what plaintiffs and the EEOC scrutinize. Doing the check yourself, before the layoff, is far cheaper than explaining the numbers in a deposition afterward.

The OWBPA trap when you offer severance for a release

If you offer severance in exchange for a signed release of claims — which most RIFs do — and any affected employee is 40 or older, the Older Workers Benefit Protection Act (OWBPA) imposes strict rules for the age-discrimination waiver to be valid. In a group layoff that typically means:

  • A longer consideration period (often 45 days for a group termination, versus 21 for an individual) to sign,
  • A 7-day revocation window after signing,
  • And a required written disclosure listing the job titles and ages of who was and wasn't selected in the decisional unit.

Botch the OWBPA formalities and the release you paid severance for may not actually waive age claims — you've spent the money and kept the exposure. This is precisely the kind of formality where a quick legal review pays for itself.

When the WARN Act applies

The federal Worker Adjustment and Retraining Notification (WARN) Act requires 60 calendar days' advance written notice of certain large layoffs and plant closings. The headline thresholds:

  • It generally covers employers with 100 or more employees.
  • It's triggered by a plant closing, or a mass layoff affecting a threshold number of workers at a single site (broadly, 50 or more employees where they make up at least a third of the active workforce, or 500 or more outright).

Many small employers fall under the 100-employee floor and never trigger federal WARN — but do not stop there. A number of states have their own "mini-WARN" laws with lower thresholds, longer notice periods, and broader coverage than the federal statute. A cut that's well clear of federal WARN can still trip a state notice requirement. Confirm both the federal threshold and your state's mini-WARN before you assume notice doesn't apply, because a missed WARN notice can mean back pay and penalties for every affected employee.

Run it through your offboarding workflow

The execution risk in a RIF is the same as any termination, multiplied: every selected person needs final pay handled to state timing, benefits and continuation paperwork, equipment and access recovery, and consistent documentation — all on the same day, often for many people at once. This is where a disciplined offboarding process stops being nice-to-have and becomes the thing that keeps a layoff from turning into a string of unemployment and discrimination disputes. Launch the offboarding workflow for each affected employee the moment the list is final, so access is cut cleanly, paperwork is complete, and the documentation is consistent across everyone — the inconsistencies between one person's file and the next are exactly what a plaintiff's lawyer looks for.

The bottom line

A defensible RIF is built backwards from the one you'd have to explain in court: a written business rationale for the unit, objective job-related selection criteria applied uniformly, an adverse-impact check before you finalize, OWBPA-compliant releases if anyone over 40 is signing for severance, and a confirmed answer on both federal WARN and any state mini-WARN. Pick criteria before names, check the demographics before you commit, get the release formalities right, and run the execution through a structured offboarding workflow so nothing is inconsistent across the group. The mechanics are heavy, but every one of them is process you can document in advance — which is exactly what turns the worst day at a company into a clean one instead of a lawsuit.