Planning question and workforce baseline · Lesson 1
Frame the workforce decision
7 min read
Lesson objectives
Turn a service goal into a testable capacity question with a unit, denominator, period and decision.
Reading tools
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
Workforce planning starts with a defined business decision, not an isolated vacancy count. Ask what service must be delivered, how often, to what time or quality standard, by whom and over which horizon. If a manager at a hypothetical service centre says, ‘We need five employees,’ that is an answer before the question. The underlying issue might be more transactions, longer handling time per transaction, scarce skill for complex cases or uneven shifts. Planning relates work demand to available capacity and skills, then selects a response that can be reviewed. CIPD's workforce-planning factsheet recommends linking the plan to organisational strategy, relevant data, supply and demand, and periodic review. We use that sequence as a reasoning frame, not as a universal staffing formula.
Fix the demand unit before calculating. An incoming request is not necessarily a completed case: one case may be reopened, transferred or require two contacts. Define the work unit as a unique case completed to a stated standard, or separate its stages if their handling time differs. Then define the period: an operating week, a calendar month or peak hours. The denominator of a productivity rate may be productive hours rather than paid hours; breaks, training and meetings do not process cases. Show that difference instead of burying it in a vague rate. For a first plan, separate three kinds of constraint: a service target such as 90% within two working days, a resource limit such as contracted hours and budget, and a skill constraint such as an internally qualified reviewer for sensitive cases. The last is a hypothetical internal condition, not an external professional licence. Each constraint changes feasible options; an adequate average headcount does not make it disappear.
Build a six-field decision card:
(1) service outcome and measure
(2) demand unit and period
(3) baseline volume and handling time by case type
(4) available capacity and its time definition
(5) quality, skill and budget constraints
and (6) decision option plus review date
When the data are weak, use a range and a testable assumption instead of a falsely precise point estimate. Distinguish sustained capacity need from a temporary peak: permanent recruitment is slower and has continuing cost, while shift redesign or cross-training may resolve a short bottleneck. Do not choose a response before estimating the size and duration of the gap. Nor can a request count become a person count without handling time and productive hours. Retain each number's source and date, marking manager estimates separately from operating records. A decision made today can fail when volume or the service standard changes.
Lesson summary
Turn a service goal into a testable capacity question with a unit, denominator, period and decision.