The core idea
Workforce planning connects organisational needs with the people and skills available to meet them. A useful sequence is to understand strategy, analyse the current workforce, estimate future demand and supply, identify gaps, choose actions and monitor outcomes. It concerns capability, timing and location as well as headcount. Demand and supply are uncertain, so a plan should show assumptions and alternative scenarios rather than one apparently inevitable forecast.
Source and attribution [1]Using it in practice
Define the service or work required, then translate it into capacity using realistic assumptions about productive time and skills. Estimate internal supply, including development, movement and expected departures, without treating every employee as interchangeable. Compare options such as redesigning work, recruiting, developing capability or improving retention. Assign owners and trigger points for revisiting the plan.
An example, not a reported case
Worked example · illustrative
A fictional operation needs 4,000 coverage hours per week. If one full-time equivalent provides 32 usable coverage hours after the allowances included in this example, demand is 125 FTE. Current deployable capacity is 116 FTE, leaving a nine-FTE gap before any further forecast change. The calculation is only as sound as the 32-hour assumption: leave, training, availability and skill coverage must not be counted twice or ignored.
What to watch for
FTE is not headcount, and equal FTE does not imply equal availability or capability. A forecast can become circular if managers enter the staffing number they hope to receive as the demand estimate. Restructuring options require separate consultation and legal assessment. This guide explains planning logic, not a staffing standard for a particular service.
Set the planning boundary
Define the service, locations, roles and time horizon before requesting figures. A plan for next month’s shift cover answers a different question from a two-year capability plan. Record the business decision the work will support and the consequences of being wrong. CIPD’s strategic workforce-planning guide describes a structured planning approach; AIHR also connects future workforce requirements with organisational strategy. The application below is ADM HR’s own worked approach. Use the source guides for their full frameworks rather than treating one local worksheet as a universal model.
Build a demand assumption register
Describe required output, service standard, timing and skill mix. For every conversion from demand to labour, name the unit, evidence, owner and confidence level. For example, a forecast of customer visits needs an assumption about time per visit and the work outside the visit. Record whether travel, documentation and supervision are already included. A service-hour assumption copied from last year may no longer fit a changed service. Keep a low, central and high case where uncertainty matters, and identify the assumption that would change the staffing decision most.
Separate headcount, capacity and competence
Headcount counts people; FTE expresses contracted time against a stated full-time standard; usable capacity reflects the work those hours can support. Competence and availability determine where that capacity is deployable. Do not count the same person’s time in two teams or deduct leave twice. Build the plan at a level that exposes the constraint: a total can balance while a particular shift or qualified role is short. Use aggregate information where possible and record the date of the source data so managers know whether the picture is current.
An illustrative calculation with a sensitivity check
A fictional service needs 3,600 productive hours a month. At 120 productive hours per FTE, the arithmetic requirement is 30 FTE. Available deployable capacity is 27 FTE, leaving a three-FTE gap under those assumptions. If usable hours fall to 112, the same demand requires about 32.1 FTE. Do not round that result into a recruitment instruction: check shift coverage, minimum staffing requirements, skills and affordability. The numbers are invented. Their purpose is to show how one assumption changes the decision, and why a precise spreadsheet result can still be uncertain.
Compare options on the same basis
For each gap, compare recruitment, internal development, redeployment, retention and changes to the work. Record time to effect, one-off and ongoing cost, confidence, dependencies and employee consequences. A trainee may be available quickly but need supervision that reduces another employee’s capacity. Temporary cover may resolve timing without building future capability. Redesign may remove avoidable work but require testing for service quality. Identify which options remain useful in several scenarios and which should wait for a trigger. Any proposed contractual change or restructuring needs its own appropriate process and legal assessment.
Write triggers that can actually be observed
Replace “recruit if busy” with a measurable condition, an owner and a review date. An illustrative trigger could be confirmed additional work above an agreed volume for two review periods, with evidence that existing capacity cannot safely meet it. Define the source of the measure and what happens if it is unavailable. Include a stop or scale-back condition as well as an expansion trigger. A trigger supports a decision conversation; it should not silently automate a consequential employment decision or remove the need to consider changed circumstances.
Review the forecast and the response separately
Compare predicted demand, usable hours and skill availability with actuals. Then ask whether the chosen action arrived on time and improved the service without shifting an unacceptable burden to employees. A poor forecast can accompany a sensible response, and an accurate forecast can accompany ineffective implementation. Preserve previous assumptions and explain material differences. Discuss the result with operations and finance, and seek employee insight into practical constraints. The next planning cycle should inherit the learning, not merely a new version of the same headcount total.
Original ADM exercise: forecast the task mix after an AI pilot
A fictional team currently spends 600 hours a month preparing routine summaries. A pilot predicts a 40% reduction in drafting time, but checking and correction add 90 hours. The provisional saving is 150 hours, not 240. Do not translate it directly into job reductions: check whether demand grows, the saved time is usable on the required shifts, and quality holds for difficult cases. Run low, central and high scenarios with finance and operations. Use the pilot to test the assumption, record employee feedback and assign a stop condition for deteriorating service. These invented figures demonstrate planning logic rather than an estimate of AI productivity.
Member-source update: make the business own the choice
CIPD’s member guide treats the action plan as a comparison of ways to close capability gaps, with business ownership and HR facilitation. Options need costs, timings and the stakeholders who can deliver them. Use the original guide for its complete methodology. Original ADM HR exercise: a service has a temporary shortage of qualified cover. Compare an external appointment, supervised development and a short-term secondment on one page. Show the earliest safe deployment date and the supervision each consumes. Ask the operational sponsor to select and fund an option, with finance confirming the assumptions. Name a review trigger and a fallback if the chosen option arrives late. Keep employment consultation and contractual questions as separate decisions rather than treating the planning worksheet as authority to change someone’s role.
Take it into your next conversation
Three useful questions.
- Which decision will this analysis change?
- Are the population, denominator, time period and assumptions explicit?
- What alternative explanation or unintended effect must we check?
Related terms
Go to the evidence
Sources & attribution
Further reading: Michael Armstrong with Stephen Taylor (2023), Armstrong’s Handbook of Human Resource Management Practice, 16th edition, chapters 26, 28. Edition & reading notes ↗
Further reading: Nadeem Khan and Dave Millner (2023), Introduction to People Analytics: A practical guide to data-driven HR, 2nd edition, PDF pp. 227, 244 and 294–295. Edition & reading notes ↗
[1] CIPD: Workforce planning ↗
[2] CIPD: Strategic workforce planning guide (member access may be required) ↗
[3] Erik van Vulpen, AIHR: Strategic workforce planning ↗
[4] ADM HR: editable Word worksheet ↗
The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.
Expanded on 20 September 2026 for the People Analytics collection; original URL retained. Application guidance expanded on 26 September 2026. These practical suggestions and invented examples are editorial explanations; further-reading sources are not the original authors of the historical models unless expressly identified. Original overview review dates are retained. Reworked on 28 September 2026 to consolidate repeated application notes and add original decision exercises, worked examples and practical guidance. Newly linked CIPD and AIHR resources were checked; existing legal review dates are unchanged. Targeted editorial update on 15 October 2026. New application exercises are original ADM HR illustrations. Public sources were checked for the first update. Member-source follow-up on 15 October 2026: the linked resource was reviewed through authenticated access. The application exercise is original ADM HR content; licensed templates and course materials are not reproduced.
Published 2026-09-20 · Reviewed 2026-10-15. Editorial approach