A workforce plan says how many people are needed, in which roles, starting when, and what that costs. Most of what gets called a workforce plan is a headcount list with a total at the bottom, and the difference between that and a plan is whether the assumptions behind each number are written next to it. A list gets argued about; a plan gets interrogated, which is what you want, because an interrogation is a conversation about assumptions rather than about your judgement.
The five lines
Roles and the headcount each needs, start dates by month rather than by year, attrition you expect to replace, the cost per role fully loaded, and the assumption each of those rests on. The fifth line is the one usually missing and the only one that makes the other four defensible. Written down, it turns every challenge into a question about a stated assumption, which is a question you can answer.
Start dates are where plans go wrong
A plan that adds twelve people is really a plan about when twelve people are productive, and the gap between an approval and a productive person is the hiring time plus the ramp. Counting from approval rather than from productivity is the single most common error, and it is the one that makes a plan look affordable in the spreadsheet and short-staffed in the quarter.
Attrition is a replacement line, not a discount
Expected leavers do not reduce the hiring number, they increase it, because each one has to be replaced before the position is refilled and productive. Plans that net attrition against growth consistently understate the recruiting load, and recruiting load is the constraint that actually binds in most years.
Version it, because it will be wrong
The value of a plan is not that it predicts the year, it is that it records what was believed when the decision was made. Keeping versions with dates means a mid-year variance is a readable difference rather than an argument about what anybody said in the autumn, and it is the half of planning that spreadsheets lose first.
Questions people ask about workforce plan
How far out should a workforce plan run?
Twelve months at monthly grain is what most organizations can actually defend. Longer horizons are worth sketching at role level, but the month-by-month detail stops being real somewhere past a year.
Is a workforce plan the same as a headcount budget?
The budget is the money line. The plan is the roles, the timing and the assumptions that produce it, which is why a plan can survive a budget change and a budget cannot survive a plan nobody wrote.
Who owns it?
The manager who owns the work owns the roles and the timing; finance owns the cost; HR owns the attrition and hiring assumptions. A plan with one owner is usually one of those three views written as if it were all of them.