Workforce planning template: supply, demand, gaps and what to do about each

A workforce plan compares the people and skills you have with the ones your strategy will need over the next one to three years, and decides how to close each gap: train, redeploy, hire, contract or automate. It is broader and longer than a headcount plan. A headcount plan approves and funds roles for the coming period; a hiring plan fills them. The workforce plan sits above both and tells you which roles should exist at all, and which gaps hiring cannot close in time.

Below: the five parts of a workforce plan, a copy-ready template, a worked example for one function, and the scenario step most plans skip.

The five parts of a workforce plan

1. Supply today. Who you have, by role family, level, location and critical skill, plus who is likely to leave or retire.
2. Demand later. What the business plan requires at the end of the horizon, expressed as work and skills, then as roles.
3. Gap. Demand minus projected supply, by role family and skill. Surpluses count too.
4. Actions. For each gap, how it will be closed, by whom, and by when, chosen against lead time and cost.
5. Scenarios and triggers. What changes if growth is faster or slower than the base case, and which signals tell you to switch.

Part 1: supply, current and projected

Start with the roster, not the org chart. For each role family, count people and note the skills that matter for the strategy, not every skill. Then project supply to the end of the horizon using your own history:

• Expected leavers: the team's own trailing departures, split into regretted and not.
• Known exits: announced retirements, fixed-term contracts ending, visas expiring.
• Internal movement: people likely to be promoted out of the role family.
• Flight risk in critical roles: single points of failure, where one departure stops work. Stay interviews are a direct way to find these.

If the group is too small or new for a reliable history, say so and use a placeholder to revisit at the first quarterly check. Do not borrow an industry attrition rate you cannot verify for your own organization.

Part 2: demand, from the strategy

Ask business leaders what will be different at the end of the horizon, then translate it into work. "Launch in two new regions" becomes customer support in two more languages and time zones, a regional sales team, and legal and payroll coverage in new countries. "Move to self-serve" becomes fewer sales-assisted deals and more product, lifecycle marketing and support content. Only then convert the work into roles and headcount.

Demand can shrink too. A plan that only adds roles misses the chance to redeploy people from declining work, which is often the fastest and cheapest way to cover growth elsewhere.

The workforce planning template

WORKFORCE PLAN — [function / business unit]   Horizon: [start] to [end]
Business owner: [name]   HR / TA owner: [name]   Finance: [name]
Strategy assumptions (base case): [3–5 bullets]

A. SUPPLY
Role family   Today  Critical skills held   Expected leavers  Known exits  Projected (end)
[ ]           [ ]    [ ]                    [ ]               [ ]          [ ]

B. DEMAND (base case)
Role family   Needed (end)  New skills required        Driver (from strategy)
[ ]           [ ]           [ ]                        [ ]

C. GAP
Role family   Gap (+ short / − surplus)   Skill gap           Time to close by hiring
[ ]           [ ]                         [ ]                 [months]

D. ACTIONS
Gap   Option (build / buy / borrow / redeploy / automate)   Owner   By when   Cost
[ ]   [ ]                                                   [ ]     [ ]       [ ]

E. SCENARIOS
Scenario     Trigger signal                    Changes to actions
Faster       [e.g. bookings > X for 2 qtrs]    [ ]
Slower       [e.g. launch slips past date]     [ ]

F. RISKS
Single points of failure: [roles / people]   Mitigation: [ ]

G. REVIEW
Quarterly check: [date]   Full refresh: [date]

Choosing how to close each gap

The deciding factor is usually lead time. If a gap has to close in six months and hiring for that skill has taken you nine, hiring alone will not do it; the plan needs borrowing in the meantime or a build path started now. Use your own time-to-fill by role family, from the recruiting forecast model if you keep one.

A worked example: a customer support function

The example shows what a headcount list would miss. Half of the 22 hires are general agents, the role this team fills fastest, because the scarce skills (languages, enterprise, integrations) are partly covered by moving current agents, whose places are backfilled at entry level. The language gap, which hiring cannot close before launch, is bridged by a partner.

Turning the workforce plan into hiring

Each "buy" action becomes a line on the next headcount plan, with a target open date worked back from when the person must be productive. Each "build" action needs its own owner and a date, because internal moves create backfills that also need hiring; see how to hire your replacement for that handover. Each "borrow" action needs a contract end date and a review of whether the work should become permanent.

Common mistakes

A quarterly check, in 30 minutes

• Actual leavers against projected, by role family.
• Any scenario trigger hit, and whether actions switch.
• Build actions on schedule: training started, people moved, backfills opened.
• Buy actions: roles opened on the dates the plan required.
• Borrow actions: contracts ending, and whether any should convert to permanent roles.
• Single points of failure: reduced, unchanged or new.