The three scenarios you need before the next budget meeting
You have four weeks before the executive team reviews next year's headcount plan, and the CFO has already asked a version of the same question twice: what happens to labor cost if we don't backfill the next twelve departures? Your current answer is a spreadsheet of open requisitions and a hiring freeze memo — not a model. That gap is the difference between walking into the room with an opinion and walking in with three fully worked scenarios the executive team can actually choose between.
Headcount scenario planning is the discipline of modeling more than one future staffing state — typically a hiring-freeze case, a redeployment-first case, and an attrition-based reduction case — against the same cost and task-coverage assumptions, so leadership can compare trade-offs before committing budget. Done well, it turns a defensive conversation about cuts into a structured conversation about where capacity is going and why.
This article walks through a repeatable method for building those scenarios: what inputs you need before you touch a spreadsheet, the five-step modeling sequence, a worked example at department scale, and the pitfalls that make most headcount models fall apart under executive scrutiny.
Why headcount planning breaks down when it's just an FTE spreadsheet
Most organizations still treat headcount planning as a counting exercise: how many seats are filled, how many are open, what's the delta to budget. Gartner's 2024 HR Priorities Survey found that 66% of organizations say their workforce planning is limited to headcount planning and that they struggle to demonstrate its ROI to the business — the plan exists, but it doesn't answer the question leadership actually asks, which is "what should we do differently, and what does it cost us either way." Gartner's broader 2024 research also found that 86% of HR leaders have not implemented a strategic workforce planning practice at all, which means most teams are improvising scenario logic under deadline pressure rather than working from a repeatable method.
The fix isn't more headcount data. It's a model that ties staffing scenarios to two things most FTE spreadsheets ignore: what the people in each role are actually doing at the task level, and what it costs — in dollars and time — to move people between roles versus hiring externally versus letting attrition run its course. That's the gap this method is built to close.
Five inputs to gather before you model anything
A credible scenario model needs the same five inputs regardless of which scenario you're building. Skipping any one of them is usually why a model falls apart the first time someone on the leadership team asks a follow-up question.
1. A task-level view of current roles. Headcount counts don't tell you what's replaceable, reducible, or protected — tasks do. Mapping each role to its O*NET occupational match and scoring its underlying tasks is the foundation every downstream scenario depends on. For a primer on how that mapping works, see our guide to workforce scenario planning software.
2. An exposure score per role, not per department. Department-level averages hide the roles that actually carry risk or redeployment potential. The four-dimension exposure rubric — cognitive routine, physical routine, social/judgment, and creative, each scored 0–100 and weighted by O*NET task importance — gives you a role-level number you can roll up, not a department-level guess.
3. A skills-adjacency map. Before you can model a redeployment scenario, you need to know which roles share enough skill overlap to make internal movement realistic. We cover this in depth in our skills gap analysis software guide.
4. Cost benchmarks for each staffing path. Hiring externally, redeploying internally, and letting a role go unfilled all carry different costs. SHRM's 2024 research puts the cost of replacing an employee at 50% to 200% of their annual salary, and SHRM's benchmarking data has separately put the average cost per hire at $4,129. The Josh Bersin Company's 2023 research found that external hiring costs three to five times more than internal placement. These are industry benchmarks, not your organization's actual figures — confirm current numbers against your own finance data before using them in a board deck.
5. A timeline and a trigger. Every scenario needs an "if this happens, by this date" condition — a departure, a budget freeze, a reorganization announcement — or it stays theoretical.
The step-by-step method
Step 1: Establish one shared baseline
Build a single current-state picture — role, headcount, fully loaded cost, O*NET-mapped task exposure, and skill-adjacency tags — that every scenario will modify. If each scenario starts from a different baseline, the comparison between them is meaningless. This is also the point to flag any role whose exposure score lands in the Review or Redeployment Candidate band, since those are the roles most likely to move between scenarios. (Exposure scores are an input to this conversation, not a verdict on any individual's job — they tell you where to look, not what to decide.)
Step 2: Define the scenario levers, not just the scenario labels
"Hiring freeze," "redeployment-first," and "attrition-based reduction" are labels. The model needs levers: which open requisitions are frozen versus filled, which roles are candidates for internal redeployment and into what receiving roles, and what attrition rate you're assuming over the planning window. Write the levers down before you build the math — it's the step most teams skip, and it's why two people building the "same" scenario independently produce different numbers.
Step 3: Run each scenario against the identical roster
Apply the levers from Step 2 to the baseline from Step 1, scenario by scenario, without changing any underlying assumption between them. If scenario A assumes a 5% attrition rate and scenario B assumes 8% without a stated reason, the comparison is no longer fair. Our guide to workforce redeployment walks through how to structure the redeployment lever specifically — matching Redeployment Candidate roles to open or emerging roles by skill overlap rather than by availability alone.
Step 4: Attach cost to each scenario, qualitatively where you lack hard numbers
For every departure a scenario assumes, cost it against the benchmarks from Step 1: an external backfill at SHRM's 50–200%-of-salary range and $4,129 average cost per hire, an internal redeployment at the lower multiple implied by Bersin's 3–5x internal-versus-external finding, or an unfilled seat at its ongoing productivity cost, described qualitatively if you don't have a reliable internal figure. Where you genuinely don't have a number — your own cost-per-hire, your own time-to-redeploy — say so in the model rather than borrowing a number that doesn't apply to your organization.
Step 5: Stress-test the assumptions before you present them
Pressure-test each scenario against the training and reskilling capacity question, because it's usually the first thing a sharp executive asks. The WEF Future of Jobs Report 2025 found that 59 of every 100 workers are expected to need training, with 29 upskilled into their existing role, 19 reskilled or redeployed internally, and 11 unlikely to receive adequate training at all — and 63% of employers cite skill gaps as their biggest barrier to workforce transformation. If your redeployment-first scenario assumes a reskilling timeline your L&D function can't actually deliver, that's a flaw to surface now, not in the quarter you're trying to execute the plan.
A worked example: three scenarios for a 40-person operations department
Assume a 40-person operations department with fully loaded average cost of $70,000 per role (a round number for illustration, not a benchmark figure). Task-level exposure mapping identifies 8 roles in the Review band and 4 in the Redeployment Candidate band, based on their four-dimension scores on cognitive-routine and physical-routine task share.
- Scenario A — Hiring freeze: 6 planned departures over the year go unbacked; no redeployment, no backfill. Direct cost: zero new hiring spend, but 6 seats of unaddressed capacity.
- Scenario B — Redeployment-first: the 4 Redeployment Candidate roles are matched against two open roles in an adjacent department with high skill-adjacency scores; the remaining departures are backfilled externally. Cost, using the Bersin 3–5x internal-versus-external relationship as a directional guide: materially lower hiring cost than full backfill, concentrated in onboarding and reskilling time rather than external recruiting spend.
- Scenario C — Attrition-based reduction: no backfill on any of the 6 departures, with the 4 Redeployment Candidate roles absorbed into existing teams rather than replaced. Lowest direct cost, highest execution risk if the receiving teams lack the skill-adjacency capacity the model assumed in Step 2.
Laid side by side with the same baseline, the same cost benchmarks, and the same exposure data, the executive team isn't choosing between a vague "freeze" and a vague "cut" — they're choosing between three quantified paths with stated trade-offs. That comparison is the actual deliverable of headcount scenario planning, not the individual scenario itself.
Common pitfalls that undermine a scenario model
Modeling departments instead of roles. A department-level exposure average flattens the 4 Redeployment Candidate roles into the same number as the other 36 — exactly the detail a board question will expose.
Borrowing a competitor's or a prior employer's cost figures without re-stating the caveat. SHRM's and Bersin's benchmarks are useful anchors, but they are industry averages, not your organization's numbers — label them as such every time you use them.
Treating exposure scores as a staffing decision. The rubric tells you where cognitive-routine or physical-routine task share is concentrated. It does not tell you who gets redeployed, retrained, or let go — that remains a human decision informed by the data, not replaced by it.
Skipping the reskilling feasibility check. A redeployment scenario that assumes every Redeployment Candidate role can be retrained in a quarter is optimistic in a market where 63% of employers already cite skill gaps as their top transformation barrier.
From model to board-ready narrative
A scenario model earns its place in the budget conversation when it can answer three questions on the spot: what does each path cost, what capacity does it protect or lose, and what does it require from reskilling or recruiting to execute. Build that model once, with a shared baseline and the same cost assumptions across every scenario, and you can re-run it the next time the CFO asks — rather than rebuilding it from scratch under deadline.
If you want a structured starting point rather than a blank spreadsheet, our Workforce Scenario Planning Workbook walks through this exact five-step sequence with pre-built scenario templates, cost-benchmark placeholders, and a redeployment-matching worksheet. For teams ready to run this process against live O*NET-mapped exposure data rather than manual estimates, WorkforceAnalysis generates the task-level exposure baseline in Step 1 automatically — you can see what that looks like against your own role list, or estimate the cost of continuing to model this manually, with our ROI calculator. For the broader strategic context this method sits inside, see our guide to strategic workforce planning with AI.