Workforce planning: distinguish headcount from available capacity
Workforce planning: distinguish headcount from available capacity. A practical HR workflow guide with a worked example, review checklist and implementation checks.
On this page
Workforce planning needs more than the number of employees on a team. Available capacity depends on working patterns, approved time away, required coverage and the skills needed for the work. Keep those inputs visible so a staffing discussion does not treat every person as interchangeable capacity.
Define the planning unit
Choose a period and a useful unit such as scheduled hours or staffed service slots. Identify which work is included and who owns the demand estimate. Avoid mixing monthly headcount with weekly task demand without an explicit conversion.
Separate approved staffing from vacancies and proposed hires. A role that has not been filled does not provide capacity merely because it appears in a budget.
Work through a small example
Three hypothetical employees each have 40 scheduled hours next week. Approved leave removes 16 hours, and agreed internal duties use 14 hours. That leaves 90 hours for the scoped work before other constraints are considered.
| Input | Hours |
|---|---|
| Scheduled hours | 120 |
| Approved leave | -16 |
| Allocated internal duties | -14 |
| Remaining scoped capacity | 90 |
This is an illustration, not a recommended utilisation target. If only one person can perform a specialist task, the team's total hours do not establish enough capacity for that task.
Include coverage and uncertainty
Map the skills and time windows required for essential work. Identify gaps that overtime, rescheduling or recruitment might address through approved processes. Consider a range of demand scenarios rather than presenting one forecast as certain.
Use aggregate planning information where possible and limit personal details to what authorised planners need. The model should support workload decisions, not infer an individual's suitability from sensitive personal characteristics.
Compare plans with observed work
After the period, review demand, available capacity and the main causes of variance. Check whether meetings, rework or unplanned support were omitted from the original scope. Revise the assumptions with evidence.
Keep a short decision record: the gap observed, the action agreed and the next review date. This connects the planning report to operational choices and makes it easier to learn from repeated shortfalls.
Related reading
Explore the Dood payroll and HRMS guide or discuss your implementation.
Product reference
Zoho People: reports. This is background on the related software workflow; the examples and review checklists in this article are illustrative guidance by Dood System.
