Workforce planning matches the people you will have against the people you will need. A practical 6-step process, the data you need, and the models that work.
Workforce planning is the process of forecasting the people an organisation will need against the people it will have, then closing the gap deliberately through hiring, development, redeployment or automation. It answers three questions: what capability will we need, what will we have if we do nothing, and what is the cheapest defensible way to close the difference.
Most organisations do a version of this already. It is usually called budgeting, it happens once a year, and it consists of managers asking for more headcount than they need because they expect to be cut. That is headcount negotiation, not workforce planning. The difference is that real workforce planning starts from capability demand and supply data, not from last year's number plus a percentage.
The two get conflated constantly, and they need different data and different owners.
| Dimension | Operational | Strategic | |---|---|---| | Horizon | 0–12 months | 18 months–5 years | | Unit | Roles and requisitions | Capabilities and skill families | | Question | Can we staff the plan? | Will we have the capability the strategy needs? | | Owner | HR business partner + finance | CHRO + exec team | | Main input | Attrition, time to fill, budget | Strategy, technology change, labour market | | Output | Hiring plan, budget, backfill list | Capability roadmap, build/buy/borrow decisions |
Operational planning failure looks like unfilled roles and blown budgets. Strategic planning failure looks like an organisation that is fully staffed for the business it used to be. Both matter; only one gets attention in most companies.
Start from what the business is committing to, not from the org chart. If the plan is to enter two new markets and ship a new product line, the demand question is which capabilities those commitments require and at roughly what volume.
Translate each business commitment into capability demand:
Be explicit that these are estimates. A planning process that pretends to precision it does not have gets ignored the first time it is wrong.
Supply is what you will have if you do nothing. It is the easier half and the one most often skipped, because it requires attrition data most teams do not segment.
Baseline supply = current headcount − expected exits + expected internal moves in − expected internal moves out
The expected-exits figure should come from your own employee turnover rate segmented by function and tenure band, not a company average. A function running 8% and a function running 26% will produce wildly different supply curves, and averaging them produces a plan that is wrong for both.
Add retirement eligibility where you have age data, and factor in average employee tenure patterns — most organisations have predictable tenure cliffs that make attrition lumpy rather than smooth.
The gap is demand minus supply, expressed by capability rather than by headcount. This is where most planning processes lose their value: a gap expressed as "we are 40 people short" is not actionable. A gap expressed as "we are 40 people short, of which 22 are a single engineering specialism where median time to fill is 74 days" is a plan.
Segment the gap three ways:
Every gap has four possible closures, and most organisations reach for "buy" by default because it is the one with an existing process.
Build — develop existing employees into the role. Cheapest per head, slowest, and it only works where the skills are adjacent. Requires skills gap data to identify who is close enough.
Buy — hire externally. Fastest for common roles, slow and expensive for scarce ones. Check cost per hire and time to fill by role family before assuming this is the default.
Borrow — contractors, agencies, partners. Right for genuine peaks and for capability you do not want permanently. Expensive as a standing answer.
Automate — remove the demand. Frequently the correct answer for high-volume transactional roles, and almost never considered in a planning process owned by HR alone.
The decision is usually a mix, and it should be explicit. A plan that closes every gap by hiring is a plan that has not been thought about.
Build at least three scenarios: base case, high growth, and downside. For each, model headcount, cost, and the capability position you end up in.
The scenarios matter more than the base case. A plan that only works if everything goes as expected is not a plan. Test specifically:
Quarterly review with monthly data. The annual cycle is the single biggest reason workforce plans fail — by the time the plan is reviewed, the assumptions are twelve months old and nobody can remember why the numbers were chosen.
You can run a credible first workforce plan with five inputs. Most organisations already hold all five and simply do not connect them.
| Input | Where it comes from | What it drives | |---|---|---| | Headcount by role, level, location | HRIS | Supply baseline | | Turnover rate by function and tenure | HRIS + exit data | Expected exits | | Time to fill by role family | ATS | How early hiring must start | | Internal mobility rate | HRIS | How much of the gap can be filled internally | | Fully loaded cost by role | Finance | Whether the plan is affordable |
Notice what is not on the list: a perfect skills taxonomy, a competency framework for every role, or an integrated planning platform. Those help. They are not prerequisites, and waiting for them is how workforce planning stays permanently on next year's roadmap.
Planning in headcount instead of capability. Headcount plans survive contact with reality for about a quarter. Capability plans survive reorganisations, because the underlying need does not change when the boxes move.
Using a company-average attrition rate. Supply modelling with a blended rate produces a forecast that is wrong for every function simultaneously. Segment it or do not bother.
Ignoring internal supply. Most organisations model external hiring in detail and treat internal movement as noise. In practice internal mobility closes 20–30% of open roles, and improving it is usually cheaper and faster than improving external hiring.
Building one scenario. A single-point forecast is a guess with a spreadsheet attached. The value of planning is in seeing which decisions are robust across scenarios and which are bets.
Treating it as an HR exercise. Workforce plans that finance and the business have not signed up to become documents rather than decisions. The output should be a set of commitments, not a report.
Pick one function — ideally one with a known capability problem and a manager who cares. Run the six steps on that function alone over about four weeks. Produce a one-page plan with a base case and one downside scenario.
That single worked example does more to establish workforce planning than a two-year programme to build the perfect model, because it produces a decision someone can point at. Expand from there.
What is the difference between workforce planning and headcount planning? Headcount planning allocates a number of people to each team within a budget. Workforce planning starts from the capability the business strategy requires and works out how to get it — which may mean hiring, developing, borrowing or automating. Headcount planning is a subset, and it is the part that happens after the real decisions.
How far ahead should workforce planning look? Run two horizons. Operational planning covers the next 12 months in role-level detail. Strategic planning covers 18 months to three years at capability level. Anything beyond three years in a fast-moving sector is scenario thinking rather than planning, which is still useful but should not be presented as a forecast.
Who should own workforce planning? Jointly: HR owns the supply model and capability data, finance owns the cost model, and the business owns the demand. Plans owned by HR alone are treated as HR's opinion; plans co-owned with finance become the budget.
What is the most common workforce planning mistake? Using a single company-wide attrition rate to model supply. Attrition varies enormously by function and tenure band, and a blended figure produces a forecast that is simultaneously too optimistic for the volatile teams and too pessimistic for the stable ones.
Model your own workforce scenarios. PeoplePilot Analytics builds supply forecasts from your live HRIS data — attrition segmented by function and tenure, time to fill by role family, and internal mobility — so the plan updates when reality does. Start a free trial or browse the HR Metrics Library for the formulas behind every input above.