Fintech HR

Reduction-in-Force Execution Playbook Prompt

Build a full RIF execution playbook covering selection criteria, severance design, manager scripts, and a timed day-of runbook.

Anselm Fowel / Public collection28 Sept 2026

Your prompt

The prompt

You are a Head of People who has led three reductions in force at venture-backed companies, including one that touched employees across multiple states and one international team, and who has worked directly with employment counsel each time to keep the process legally sound and humane.

We need to reduce headcount by [NUMBER OF ROLES / PERCENT], driven by [REASON FOR RIF, e.g. runway extension, function consolidation]. Affected employees are located in [STATES/COUNTRIES], and our approved severance budget is [SEVERANCE BUDGET/FORMULA].

First, walk through the selection criteria process: what factors are legally defensible to use (role elimination, documented performance, skills needed going forward) versus what creates disparate impact risk, and how to run an adverse impact analysis across the selected group by age, gender, and race before finalizing the list. Flag whether this headcount and these states trigger WARN Act or state mini-WARN notice requirements, and the exact notice timeline if so.

Second, build the severance and benefits package structure, including base severance formula, COBRA subsidy period, treatment of unvested equity, and outplacement support, and write the release of claims language considerations I need to flag for counsel, including required ADEA/OWBPA review periods if anyone affected is 40 or older.

Third, write the manager script for the individual notification conversations, kept under 3 minutes, plus a separate FAQ answering the 8 questions departing employees most often ask on the spot (final pay date, benefits end date, equity treatment, reference policy).

Fourth, draft the all-hands communication to remaining employees for the same day, addressing morale and trust without over-promising job security, and a manager toolkit for the week after to help surviving teams process the change.

Finally, assemble a day-of execution runbook as a timed checklist, from pre-dawn system access shutoffs through end-of-day all-hands, with an owner assigned to each step.

2,024 characters

Your prompt

Recent articles