Headcount planning model: process, structure and best practices

People are the largest cost line for most companies, and the one most often planned in a spreadsheet that only one person understands. A good headcount planning model gives HR and finance one number for headcount and one number for people cost, and lets leaders see the effect of hiring decisions before they are made.

What is headcount planning?

Headcount planning is deciding how many people the business needs, in which roles, teams and locations, and when they need to start, then turning that into a cost forecast. It sits at the centre of the annual operating plan, because almost every other budget depends on it.

The headcount planning process

1. Start from the current roster. Load employees and positions from the HR system as the opening balance.
2. Collect requests. Department leaders propose new roles and backfills with target start dates.
3. Apply assumptions. Time-to-hire, attrition by team, merit timing and benefit rates.
4. Cost the plan. Salary, bonus, benefits, payroll taxes and any allocations, by month.
5. Review and approve. Finance checks the plan against the budget envelope; leadership approves or trims.
6. Track and re-forecast. Each month, compare actual hires and leavers with plan and roll the forecast forward.

What a headcount planning model should include

• Positions, not just people. Each position has a department, location, level and status: filled, open or proposed. Employees are linked to positions.
• A monthly roll-forward. Opening headcount plus hires, minus leavers, plus or minus transfers equals closing headcount, every month, by team.
• Hiring timing. Proposed roles with start dates and a time-to-hire assumption so cost does not start the day the role is approved.
• Attrition. An attrition rate by team or role family to forecast leavers and backfills.
• A cost engine. Base salary by level and location, plus benefits, taxes, bonus and merit, giving fully loaded cost per position per month.
• Views by owner. Each leader sees and edits only their own team.

A simple structure

Think of the model in three layers:

1. Data: employees, positions, compensation bands and actual payroll from HR and payroll systems.
2. Planning: the roll-forward, new roles, attrition and merit assumptions.
3. Outputs: headcount and people cost by department, location and month, feeding the opex plan and the P&L.

Headcount forecasting vs headcount budget

The headcount budget is the approved plan for the year. The headcount forecast is the latest expectation, updated as hires slip, people leave and new roles are approved. Keep both as separate versions so you can explain the variance between them, usually in terms of hiring delays, unplanned attrition and roles added mid-year.

Best practices

• Plan by position so open roles and backfills are visible and budget does not disappear when someone leaves.
• Agree definitions early: what counts as headcount (FTE or heads, contractors or not) and when a hire counts (offer accepted or start date).
• Reconcile to HR every month. Closing headcount in the model should tie to the HR system, and any differences should be explained.
• Feed people cost into opex once, from the workforce model, instead of asking budget owners to re-enter it.
• Restrict access so compensation data is only visible to those who need it.

Building it in Pigment

In Pigment, positions and employees are dimensions, the roll-forward is a set of metrics over time, and compensation uses lookups by level and location. Access rights restrict salary data by department. The workforce planning blueprint shows a full design, and How to structure workforce planning in Pigment goes deeper on the modeling choices.

Frequently asked questions

What is the difference between headcount planning and workforce planning?

Headcount planning focuses on the number of people and their cost over the planning horizon. Strategic workforce planning is broader and longer term, covering skills, capabilities and organisational design over several years.

Should headcount be planned in FTE or heads?

Plan in whichever unit the business manages to, but store both if you have part-time staff. Cost should always be calculated from FTE.

Is a headcount planning template in Excel enough?

For a small, stable team it can be. Once several leaders contribute, compensation needs protecting and the plan must tie to HR data monthly, a connected planning model saves time and errors.