Headcount Planning

Headcount planning is the exercise of turning a workforce plan into a funded, dated list of positions. It establishes how many roles exist, which are paid for, which are authorized to be recruited, and what the cost is by period.

It sits between workforce planning, which decides what capability is needed, and recruiting, which fills specific requisitions. Its output is a plan that finance, the business, and HR all read the same way, which is harder than it sounds because the same word means different things to each of them.

Approved, budgeted, open, filled: four different numbers

Most headcount disputes are vocabulary disputes. These states are not interchangeable, and a plan should state which one any given number refers to.

FTE math and why the count and the cost differ

Headcount counts people. FTE, full-time equivalent, counts capacity. One FTE is one person working the organization's standard full-time schedule, commonly forty hours per week in the United States. A person scheduled for twenty hours is 0.5 FTE. Two such people are two heads and one FTE.

The number that drives budget is usually neither of those, because cost depends on how much of the period the position is actually occupied. A position that starts on the first of July in a calendar-year plan is one head and, if full time, one FTE, but it consumes roughly half a year of salary. Planning teams handle this with a start-date weighting: multiply the annual fully loaded cost by the fraction of the period the position is filled. Ten roles all planned for the fourth quarter add ten to the ending headcount and roughly two and a half FTE-years to the budget.

The reverse error is equally common. A team that hits its FTE-year budget by hiring late has not delivered the capacity the plan assumed, it has only delivered the cost. Reporting both numbers, ending headcount and average FTE for the period, keeps that visible.

Two further adjustments matter in practice. Attrition backfills should be modeled with a vacancy gap, because the position is empty between the departure and the replacement start, and the plan that ignores this systematically overstates cost and understates disruption. And FTE should be computed from scheduled hours, not from hours worked, or overtime will inflate apparent capacity that does not exist.

Backfill versus incremental headcount

The distinction determines who approves the role and whether it is new money.

• A backfill replaces someone who left a position that already exists and is already funded. It usually needs less approval because the budget impact is neutral, and it is often the largest share of annual hiring.
• Incremental or net-new headcount adds a position that did not exist. It requires new funding and normally a heavier approval path, because it changes the run rate permanently.
• A backfill is not automatically the same job. Departures are the natural moment to reconsider level, location, and scope, and treating every backfill as a like-for-like replacement wastes the one chance to reshape a team without a reorganization.
• Backfills triggered by internal promotion cascade. One external hire at the top of a chain can create two or three vacancies below it, and plans that count only the top role understate the recruiting load.
• A position held vacant deliberately to fund something else should be recorded as such. Otherwise it reappears as an expected backfill in the next cycle.
• Contingent and contract workers are usually excluded from headcount but consume real budget. Excluding them from both is how a department appears under plan while spending over it.

Running the cycle

A repeatable headcount cycle keeps the plan and the ledger reconciled.

1. 1Freeze a baseline. Take actual headcount from the system of record on a stated date and reconcile it to payroll before anything else. If the baseline is wrong every downstream number is wrong.
2. 2Layer in known changes: accepted offers with start dates, resignations already notified, planned transfers, and any position already committed.
3. 3Apply the workforce plan gaps as requested positions, each with a role, a level, a location, and a proposed start month.
4. 4Cost each position fully loaded, including employer taxes, benefits, equipment, and location differential, then weight by the fraction of the period it is filled.
5. 5Separate the request into backfill and incremental, since the two travel different approval paths.
6. 6Review and approve, producing a plan of record with an explicit approved position list rather than a total number.
7. 7Release positions to recruiting on the agreed schedule, so requisitions open in the month the plan assumed rather than all at once in January.
8. 8Track plan against actual monthly on four measures: positions approved, positions open, positions filled, and cost to date.
9. 9Reconcile quarterly with finance and reforecast, explicitly handling positions that will not be filled in period rather than silently carrying them.

Where the plan comes apart

These are the recurring reconciliation problems.

• Counting heads and FTE interchangeably. A part-time-heavy population makes the two diverge sharply, and the wrong one will be used for the wrong purpose.
• No as-of date on reported numbers, which makes two correct reports look contradictory.
• Approving positions outside the planning cycle without recording them, so the approved list drifts away from the budget.
• Assuming every planned role starts on the first of the month it was planned for. Real start dates slip, and the cost forecast should reflect a realistic lag.
• Forgetting the vacancy gap on backfills, which overstates cost and hides the coverage problem the gap creates.
• Leaving requisitions open after a hire or a cancellation, which corrupts both the pipeline view and the vacancy count.
• Ignoring the promotion cascade, so recruiting is measured against a plan that never counted the roles it will actually have to fill.
• Managing headcount only at the total level. A department at plan in aggregate can be badly wrong by function, level, and location all at once.

Why it matters

Headcount is usually the largest controllable line in an operating budget, and it is the slowest to change direction. A hiring decision made in one quarter shows up in cost for years, and reversing it is expensive in money and in trust.

A headcount plan that everyone reads the same way also removes a specific and corrosive failure: the argument in which a manager believes a role was approved, finance believes it was only budgeted, and a candidate is already in final interviews. Shared definitions, one approved position list, and an as-of date on every number prevent almost all of it.