A workforce planner is judged on three artefacts and spends most of their time on a fourth thing that is not one of them. This page is about what the role owns, what it is actually measured on, and a first ninety days that produces the three artefacts rather than an inbox. It is written for someone taking the role or defining it.
What the role owns
The forecast, the requirement and the plan. Not the schedule, which operations usually owns, and not the hiring, which recruitment does. The planner's product is a number with an argument attached, and the argument is as much of the job as the number.
The three artefacts
A forecast somebody can check afterwards. A requirement with its assumptions stated. A plan with versions. If those three exist and are current, the role is being done, whatever else is on fire. If they do not, no amount of responsiveness compensates.
The fourth thing that eats the time
Answering questions about the number, one person at a time, in different rooms. The cure is publication rather than patience: the assumptions written once where everyone can see them turn twenty conversations into one. This is the single highest-leverage habit in the role.
The first ninety days
Measure shrinkage. Compute last quarter's requirement and compare it to what was rostered. Write down the current plan with its assumptions. Put the three where people can find them. Ninety days is generous for that list and the artefacts outlast whoever made them.
Questions people ask about workforce planner
Is this an analyst role or an operations role?
Both, and the balance depends on whether the organisation trusts the numbers yet. Early on it is mostly persuasion.
What tools does a planner need?
A way to do the arithmetic and a place to keep plans with their assumptions. Spreadsheets do the first well and the second badly.
When does a team need a dedicated planner?
Usually when the requirement is argued more than once a quarter, or when more than one team's plan has to reconcile.