Headcount planning template: turning growth targets into approved roles
On this page
- What a headcount plan has to answer
- The headcount planning template
- The fully loaded cost math, worked through
- A filled quarterly example
- Building the attrition estimate and sequencing roles
- Turning the plan into requisitions, and reforecasting
- Contractors, contingent workers and the recruiting budget
- Common mistakes, and a checklist before the plan goes to finance
- Questions people ask
A headcount plan is the document that turns a growth target and an attrition estimate into a specific list of approved roles, their cost, and when each one is allowed to start recruiting. It sits upstream of a hiring plan: a hiring plan assumes the role is already approved and works out how to fill it, while a headcount plan is what produces that approval in the first place. Below is a copy-ready planning sheet, the fully loaded cost math worked through, and a filled quarterly example for one department.
What a headcount plan has to answer
Four questions, in this order, for every department or team covered by the plan:
- How many people will we lose? An attrition estimate based on the team's own recent history, not an industry figure you cannot verify for your organization.
- How many people do we need to add for growth? Tied to a specific business plan (new product, new territory, a committed volume increase), not a round number picked because it sounds ambitious.
- What does each role cost, fully loaded? Salary is the visible part; benefits, payroll tax, equipment and overhead usually add 25 to 45 percent on top, and the plan should show that math rather than hide it in a lump budget line.
- In what order do approved roles open? Even a fully funded plan should sequence roles, since recruiting and onboarding capacity is finite regardless of budget.
The headcount planning template
Department: [name] Planning period: [quarter/year]
Plan owner: [name] Finance approver: [name]
Starting headcount (beginning of period): [ ]
Attrition-driven replacements
Role Level Est. departures Replace? (Y/N) Target open date
[role] [level] [ ] [ ] [ ]
Growth-driven additions
Role Level Business driver Priority (1-5) Target open date
[role] [level] [tied to a specific plan] [ ] [ ]
Cost summary (see worked example below for the math)
Role Base salary Loaded cost (base x [factor]) Annualized total
[role] [ ] [ ] [ ]
Ending headcount (end of period): [starting + replacements + growth]
Total fully loaded cost added this period: [sum]
Sequencing notes: [why roles are ordered this way — recruiting capacity, onboarding capacity, seasonal timing]
The fully loaded cost math, worked through
An invented example: a customer success role with a base salary of $80,000. "Fully loaded" means the base plus the costs that come with employing someone, shown here as a worked example, not a benchmark to copy without checking your own numbers.
| Cost component | Example rate | Amount |
|---|---|---|
| Base salary | — | $80,000 |
| Payroll taxes (employer share) | 7.65% | $6,120 |
| Health and other benefits | 18% of base, example rate | $14,400 |
| Retirement match | 4% of base, example rate | $3,200 |
| Equipment and software licenses (year one) | flat example | $2,500 |
| Fully loaded cost, year one | $80,000 + $6,120 + $14,400 + $3,200 + $2,500 = $106,220 | |
As a loading factor: $106,220 ÷ $80,000 = 1.33, so this role's fully loaded cost is roughly 1.33 times base salary. That factor is specific to this invented example's benefit rates and one-time equipment cost; your own factor will differ, and the point of writing the math out like this is that anyone reviewing the plan can check it, not that 1.33 is a number to reuse elsewhere.
A filled quarterly example
An invented customer success department, planning Q1:
Starting headcount: 12.
Attrition-driven replacements: historical attrition for this team has run about 2 departures per quarter over the last year. The plan books 2 replacement roles at the same level as the departures, both approved to open as soon as a departure is confirmed rather than waiting for the position to sit empty.
Growth-driven additions: the business plan adds a new product tier launching in Q2 that is expected to add 15 percent more support volume. One additional mid-level role is approved, sequenced to start recruiting 6 weeks before launch so onboarding finishes in time.
Cost: 2 replacement roles at $106,220 fully loaded each = $212,440. 1 growth role at a fully loaded cost of $98,000 (lower base for this level). Total added cost for the quarter: $212,440 + $98,000 = $310,440.
Ending headcount: 12 + 2 + 1 = 15.
Sequencing: replacements open immediately since the team is already down two people; the growth role is sequenced to start recruiting in week 4 of the quarter so the estimated 8-week fill time lands before the product launch.
Building the attrition estimate and sequencing roles
Building the attrition estimate honestly
Use your own team's departures over the last 12 to 24 months, broken down by whether they were regretted (you would have kept the person) or not, and by level. A plan that assumes zero attrition is optimistic in a way finance will not believe; a plan that assumes a flat percentage copied from an article is precise in a way your own data cannot support. If the team is too small or too new to have a reliable history, say so on the plan explicitly and use a placeholder that gets revisited at the first quarterly reforecast rather than treated as settled.
Sequencing roles when the budget covers all of them
Even a fully approved plan should not open every role on day one. Two constraints usually matter more than budget at that point:
- Recruiter and hiring manager capacity. A hiring manager running six simultaneous searches fills all of them slower than three run in sequence. See how to prioritize open requisitions for a scoring method once roles are open.
- Onboarding capacity. A team that can train two new hires well in a month often cannot train five, regardless of budget. If the plan does not account for this, the roles fill but the new hires ramp slowly, which shows up as a headcount number that looks right and a team that is not actually more productive.
Turning the plan into requisitions, and reforecasting
Turning an approved plan into open requisitions
Once a role is on the headcount plan, it still needs an individual requisition before recruiting starts, which is where the budget, level and pay range get locked in formally. See job requisition form template for that step, and hiring plan template for working out the actual recruiting timeline once the requisition is open. Keep the fully loaded cost figure consistent between the headcount plan and the requisition; a mismatch here is one of the most common reasons finance sends a requisition back for correction.
Reforecasting during the period
Set a fixed cadence, usually monthly, to compare the plan against what actually happened:
| Check | What to do if it is off |
|---|---|
| Actual attrition versus planned | If departures are running ahead of plan, flag which replacement roles need to move up in sequence rather than waiting for the next planning cycle. |
| Time-to-fill versus assumed | If roles are taking longer to fill than the plan assumed, growth roles further down the sequence may need their target start dates pushed, and that should be visible to the business owner waiting on them. |
| Approved roles not yet opened as requisitions | A gap of more than a few weeks between approval and posting usually means the hiring manager is not ready, which is worth surfacing before the quarter ends rather than after. |
| Spend versus budget | Compare actual fully loaded cost of filled roles against the plan's estimate; a consistent gap in either direction means the loading factor used in planning needs updating. |
Contractors, contingent workers and the recruiting budget
Contractors and contingent workers on the same plan
A headcount plan that only counts full-time employees hides real cost and real capacity. If a department is running on a mix of full-time staff and contractors, add an employment-type column to the template above rather than tracking contractors on a separate, informal list. Two reasons this matters in practice: first, a team's actual delivery capacity depends on everyone doing the work, not just the employees; second, a contractor role that quietly becomes permanent is a conversion decision finance should see coming, not a surprise headcount increase discovered at renewal time.
| Employment type | What changes on the plan |
|---|---|
| Full-time employee | Fully loaded cost as shown above; counted against permanent headcount. |
| Contractor or temp | Bill rate instead of a loading factor; tracked separately from permanent headcount but on the same sheet, with a planned end date or conversion review date. |
| Backfill for leave | Time-bound by definition; do not count against net headcount change, but do count against recruiting and onboarding capacity for the quarter. |
Linking the plan to the recruiting budget
The fully loaded cost figures on a headcount plan are the input to a recruiting budget, not a substitute for one: the headcount plan says what the new hires will cost once they are employed, while a recruiting budget also covers what it costs to find them (agency fees, job board spend, sourcing tools, referral bonuses). Keep the two documents separate but consistent, and reconcile them at the same reforecast cadence. See recruiting budget template for the cost-per-hire math that sits alongside this plan.
Common mistakes, and a checklist before the plan goes to finance
Run through this before submitting the plan. Each line maps to a mistake in the table below it.
- Every replacement role is tied to an actual departure pattern from this team's own history, not an assumed rate.
- Every growth role names the specific business driver behind it.
- Costs are fully loaded, with the loading math shown rather than a single lump figure.
- Roles are sequenced by recruiting and onboarding capacity, not only by approval date.
- Contractor and contingent roles are on the plan, not tracked separately or left off.
- A reforecast date is already on the calendar before the plan is approved.
| Mistake | Why it fails | Fix |
|---|---|---|
| Planning only base salary, not fully loaded cost | Finance approves a number that understates the real cost by 25 to 45 percent | Show the loading math, per the worked example above |
| Growth roles with no specific business driver named | The plan cannot be defended when budget gets tight and something has to be cut | Tie every growth role to a specific plan, launch, or committed volume |
| Attrition assumed at zero or at an industry average | Either understates cost or overstates it against your own team's real pattern | Use the team's own trailing history, and say so when history is too thin to trust |
| No sequencing, every role opens at once | Recruiting and onboarding capacity gets overwhelmed even when budget is fine | Sequence by capacity, not just by approval date |
| Plan never revisited after the quarter starts | Actual attrition and fill times drift from the plan within weeks | Set a monthly reforecast cadence, per the table above |
Questions people ask
What is the difference between headcount planning and a hiring plan?
Headcount planning decides which roles get approved and funded, department by department, before recruiting starts. A hiring plan takes an already-approved role and works out how it gets filled: timeline, sourcing, interview stages and owners. Headcount planning answers 'should we open this,' a hiring plan answers 'how do we fill it.'
How often should a headcount plan be updated?
Most organizations set it once a quarter or once a year and then reforecast monthly against actual attrition and hiring progress. A plan that is never revisited between planning cycles usually falls out of date within a quarter, since attrition rarely tracks the assumption used to build it.
Should contractor and contingent headcount be on the same plan as full-time roles?
Track them on the same plan with a separate column for employment type, even if the budget lines are different. Leaving contractors off the plan entirely hides a real cost and makes it look like a team is smaller than the work it is actually running on.
Who owns the headcount plan: finance or talent acquisition?
Ownership varies, but the plan works best as a joint document: finance owns the budget constraint and approval, talent acquisition owns the feasibility of the timeline and the labor market reality behind it. A plan built by one side without the other tends to be either unaffordable or unfillable.