Headcount planning: roles, hiring dates and cost

Headcount planning connects required roles, hiring dates and departures to monthly staffing cost. Start with a position list and a staffing snapshot, then calculate how many people will be active and what their compensation will cost in each month.

Start with approved positions and a clear reporting date

Collect the approved position register, current staffing export, hiring plan and payroll-cost export. Use a position ID to connect the files. A vacant approved role and a filled role are different states of the same position, so do not create an extra position when a replacement is hired.

The Georgia Municipal Association describes position control as ensuring new personnel fill positions authorized in the budget. That control also gives a company a useful starting point: reconcile approved roles before counting proposed hires.

For each role, record department, approval status, planned start, last paid date if known, FTE, annual full-time salary and employer-cost assumptions. Maintain actual dates separately from planned dates.

Define the measures before combining departments:

• Closing headcount: employees active on the reporting date.
• Closing FTE: those employees' scheduled FTE on that date.
• Average annual FTE: the year's FTE-months divided by the months in the year when using a monthly convention.
• Loaded compensation: salary plus the employer costs included in the planning policy.

Show recruiting, equipment and external coverage separately from compensation. For sales-specific workload assumptions, use sales planning; this schedule starts after roles have been proposed.

Build a dated role schedule

An invented US distribution business plans the following full-time roles for 2027. Existing roles are active at the start of the year; proposed hires start on the first day of their listed months. Nobody departs during the year.

The illustrative employer load is 25% of salary for every role. It represents the company's assumed additional employer costs, not a national benchmark or a statutory rate. It excludes paid leave already covered by the annual salary.

Annual loaded compensation = Annual full-time salary × FTE × (1 + Employer load rate)

In-year loaded cost = Annual loaded compensation × Active months / 12

All roles are 1.0 FTE. The annual salary column describes full-year rates; its total is not the year's salary expense because the two hires join later. The analyst's annual loaded compensation is $90,000, but only nine months, or $67,500, belong in this year's plan.

The headcount planning spreadsheet guide covers the workbook-specific layout in more detail. Here, the important decisions are which dates and costs the schedule represents.

Calculate each month from the dates

For a working sheet, use A:G for position ID, department, start date, last paid date, FTE, annual full-time salary and employer load rate. Put the month's first date in H1. Enter this formula in H2 and copy across and down:

=MAX(0,MIN(IF($D2="",EOMONTH(H$1,0),$D2),EOMONTH(H$1,0))-MAX($C2,H$1)+1)/DAY(EOMONTH(H$1,0))*$E2*$F2*(1+$G2)/12

This calculates a monthly salary allocation and prorates partial months by active calendar days. Dates must be real spreadsheet dates, and a blank last paid date means the position continues. Microsoft's EOMONTH documentation confirms that the function returns the month's final date. Covirage is not affiliated with Microsoft.

This is a planning convention, not a payroll calculation. If payroll uses a different proration method, either adopt that method or reconcile the difference explicitly. Split a role into dated segments when salary or FTE changes during the year.

Closing headcount for a single position uses its employment dates, not the salary allocation:

=IF(AND($C2<=EOMONTH(H$1,0),OR($D2="",$D2>=EOMONTH(H$1,0))),1,0)

Sum the flags for headcount. Multiply each flag by its FTE before summing closing FTE.

Check the monthly total against the annual plan

The monthly schedule totals $285,000, matching the position-level total. The staffing roll-forward also closes: two opening employees plus two hires minus no departures equals four closing employees.

Average annual FTE is 39 / 12 = 3.25. Closing headcount is four. Both are correct; they answer different questions.

Finance should reconcile monthly payroll to the ledger separately, including employer costs that may post outside payroll. HR and department leaders confirm staffing completeness and department assignments.

Separate timing variances from staffing decisions

Suppose the analyst instead starts June 1. The two-month delay reduces planned loaded compensation by $15,000: two months at $7,500. The revised annual total becomes $270,000, assuming no temporary cover or other changes.

Keep the original $285,000 approval visible. Explain the $15,000 timing movement in the current forecast rather than quietly rewriting the budget; budget vs forecast covers that distinction.

Ask the department what the vacancy changed. A lower cost does not establish that the work disappeared. Delayed reporting, extra hours or purchased support may explain the apparent saving.

Where headcount planning goes wrong

• Budgeting every hire for a full year. Apply start dates before totaling annual cost.
• Treating headcount as FTE. A person count does not describe scheduled capacity when hours differ.
• Double counting a replacement. Use position IDs and actual employment dates to identify any intentional overlap.
• Using one load without review. Benefits, incentive arrangements and employer costs can differ by role and location.
• Calling vacancy variance productivity. Compare the staffing gap with work delivered and coverage costs.

Check your staffing plan in Covirage

Bring a position-level staffing plan and actual staffing and compensation exports in a file. Covirage maps the columns, and its tools compute and check headcount and loaded-cost differences; the external AI model explains the result with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.

See capacity planning for the supporting business use case.