Headcount Planning TemplateHow to build a hiring plan finance will actually approve
Most headcount plans are wish lists in a spreadsheet costume. They list roles nobody has priced, start dates nobody believes, and approvals nobody can trace. Then the first bad quarter arrives and the whole thing gets frozen at once. This is the template I use instead, plus the math and the operating rhythm that keep it honest.
A headcount plan is a loop, not a January document
Operating model
What the business must deliver
Role list
Named roles, not FTE blobs
Cost model
Fully loaded, by month
Approval
Trigger unlocks the req
Reconcile
ATS versus plan, monthly
I have sat on both sides of this meeting. The recruiting side arrives with a tab called Hiring Plan FINAL v4 that has 38 rows and a total at the bottom. The finance side arrives with a payroll export and one question: which of these people actually start, and in which month. Those two documents almost never agree, and the gap is where hiring plans go to die.
The fix is boring. Build the plan so it can be reconciled. Every role gets a name, a price, a month, an owner, and a condition that has to be true before recruiting is allowed to open the req. That last column is the one most teams skip, and it is the one that keeps you out of a blanket hiring freeze later.
This guide covers what to put in the template, how to price a role properly using BLS employer cost data rather than a guess, and the monthly reconciliation that keeps the file from rotting. If you want the strategic layer above this, read our workforce planning guide first, then come back here to build the actual sheet.
Definition
What headcount planning actually is
Headcount planning is the process of deciding how many people you will hire, when each one starts, what each one costs fully loaded, and what has to be true for the role to be approved. It is the bridge between a finance budget and a recruiting pipeline.
People confuse it with workforce planning. Workforce planning asks what capabilities the company needs over the next two or three years. Headcount planning asks a much narrower question: which specific roles get filled in the next four quarters, and can we afford the payroll run that results. One is strategy. The other is a budget you sign your name to.
The distinction matters because the two documents fail differently. A weak workforce plan makes you build the wrong team over years. A weak headcount plan blows up your operating expense line in a single quarter, usually because six roles all started in month one when the plan assumed a smooth ramp.
Since 2020, US public companies have had to disclose human capital information in their annual filings under the SEC modernization rule for Regulation S-K. That pushed headcount from an HR side conversation into something the board reads. Private companies inherited the same expectation through their investors, which is why your plan now gets the level of scrutiny a revenue forecast gets.
The template
The twelve columns worth having
You do not need a 40-column model. You need twelve columns that each answer a question somebody will ask out loud in a budget review. Anything beyond that is decoration, and decoration is what makes people stop updating the file.
Build it in whatever tool your finance team already lives in. Google Sheets is fine. The tool matters less than the discipline of one owner and one version.
Twelve columns. Every one of them gets used in a real budget review.
Identity
Role title
Senior Backend Engineer, not Eng Hire 4
Department
Maps to the GL cost center
Level / band
Links to your comp bands
Hiring manager
One named human
Money
Base salary
Midpoint of the band, not the hope
Fully loaded cost
Base times your loading factor
Start month
Month, not quarter
In-year cost
Loaded cost prorated from start
Control
New or backfill
Backfills need no growth case
Trigger
The condition that unlocks the req
Approval status
Planned, approved, opened, filled
Req ID
The join key to your ATS
Two of these deserve extra attention. The Req ID column is your join key. Without it you cannot compare the plan to what recruiting is actually working on, and reconciliation turns into a manual name-matching exercise every month. Pull the ID from your applicant tracking system the moment a req opens and paste it back into the row.
The Trigger column is the one that changes behaviour. More on that below, because it is the difference between a plan that flexes and a plan that gets frozen.
Step 1
Start from the operating model, not the org chart
The wrong way to start is to ask each manager what they need. You will get a list. The list will be longer than the budget, every item on it will be urgent, and you will spend three weeks negotiating it down while everyone quietly resents the process.
Start with what the business has committed to deliver next year and work backwards to capacity. If sales has to close 12 million in new bookings and a fully ramped account executive closes 900,000, you need roughly 15 ramped reps in seat. Then apply attrition and ramp time, and the hiring math writes itself. Same logic in support: ticket volume divided by tickets per agent per month gives you a number nobody has to argue about.
Capacity-driven roles are the easy half. The hard half is functions where output does not divide cleanly, which usually means engineering, design, and most of G&A. For those, use ratios against the capacity-driven teams and defend them as ratios. One recruiter per roughly 40 to 60 hires per year. One designer per four to six engineers. These are conventions rather than laws, but a convention you can state is much easier to approve than a number you cannot explain.
Write the logic in a comment on every row. Six months later nobody remembers why row 23 exists, and an unexplained row is the first thing cut when budgets tighten.
Step 2
Price every role fully loaded
Base salary is not what an employee costs. This is the single most common error in headcount plans, and it produces budgets that miss by 25 to 40 percent on the people line.
The BLS Employer Costs for Employee Compensation series is the right anchor. It reports that benefits make up roughly 31 percent of total compensation for civilian workers, with wages carrying the remaining 69. That gets you in the neighbourhood. Then layer in the things BLS does not count as compensation at all: laptops, software seats, and the recruiting cost to land the person.
One US software engineer at a $140k band midpoint
Base salary
$140,000
Employer payroll taxes
+ $10,700
Benefits and insurance
+ $21,000
Equipment and software seats
+ $4,800
Recruiting cost, amortized
+ $6,000
Year one fully loaded
$182,500
Illustrative. Your loading factor here is 1.30. Run your own payroll export before trusting anyone else's multiplier.
A few notes on that stack. Employer payroll taxes in the US are the 6.2 percent Social Security portion up to the annual wage base, 1.45 percent Medicare with no cap, plus federal and state unemployment. The IRS guidance on Social Security and Medicare withholding has the current rates and wage base, and both move, so check them rather than reusing last year's cell.
Recruiting cost belongs in the row too. SHRM benchmarking has long put average cost per hire near 4,700 dollars, and that number climbs fast for senior or agency-filled roles where a 20 to 25 percent placement fee can add 30,000 to a single hire. Our breakdown of cost per hire shows how to calculate yours instead of borrowing an average.
Do not skip equity dilution either. It does not hit cash, so it will not show up in your operating expense line, but it hits your cap table and it is real compensation. Track it in a separate column so the board can see both numbers.
One practical trick: derive your own loading factor rather than adopting a rule of thumb. Take last year's total people cost from the general ledger, divide by total base salary paid, and you have a multiplier calibrated to your actual benefits plan and state mix. Most US software companies I have worked with land between 1.25 and 1.35. If yours comes out at 1.5, you have either generous benefits or an accounting problem, and both are worth knowing about.
Step 3
Phase start dates by month, and be pessimistic
Quarterly start dates are a lie that costs money. When every role in Q2 is modelled as starting April 1, you have quietly assumed your recruiting team can deliver a quarter of your annual hiring in a single month, and you have overstated in-year cost for every role that realistically starts in May or June.
Use months. Then work backwards from the start date using your actual cycle time. If your median time to fill is 45 days and notice periods run two to four weeks, a June 1 start means the req opens in early April. Put that req-open date in the sheet as a derived column. Suddenly the plan tells recruiting what to do this week rather than what to achieve this year.
The other reason to use months: it forces you to confront capacity. A plan with 24 hires and four recruiters is fine. A plan with 24 hires where 11 start in the same month is not, and the month view makes that obvious before you commit to it. BLS JOLTS data is a useful reality check here on how competitive the market is for the months you are planning into.
My rule: push 55 to 60 percent of planned starts into the back half of the year. Hiring always slips. A plan that is front-loaded fails on day one and then spends the rest of the year in apology mode.
Step 4
Give every growth role a trigger
This is the column that separates a plan from a wish list. A trigger is the condition that has to be true before recruiting is allowed to open the requisition. Written in advance. Agreed by finance and the hiring manager. Checked at the monthly review.
Real examples I have used: open the second solutions engineer req when qualified pipeline passes 4 million. Open the third support hire when weekly ticket volume holds above 850 for four straight weeks. Open the data engineer req when the warehouse migration ships. Each one is verifiable by someone other than the person asking for the hire.
The payoff shows up in a bad quarter. Without triggers, a revenue miss produces a company-wide freeze, because a freeze is the only lever an exec team has when nothing is conditional. With triggers, the plan self-adjusts. The roles whose conditions were not met simply do not open, and the roles supporting the parts of the business that are working keep moving. You get a scalpel instead of a hammer.
Backfills are the exception. A backfill for an approved, budgeted role does not need a business case, and making managers rebuild one every time someone resigns is a good way to lose the manager next. Flag it as a backfill, confirm the role is still needed, and open it. Keep the paperwork light with a standard job requisition form.
Step 5
Reconcile against the ATS every month
Here is the honest answer about why headcount plans go wrong: it is almost never the forecast. It is the drift between what the plan says and what recruiting is doing, accumulating quietly for five months until somebody opens both files at the same time.
The monthly pass takes 30 minutes if the Req ID column is populated. Export open reqs from your ATS, join to the plan, and look at four things. Which planned roles have no req open. Which open reqs have no plan row, because those are the ones that appear when a manager goes around the process. Which start dates have slipped, and by how many weeks. Which filled roles came in above or below the planned salary.
That last one compounds. A single hire landing 15,000 above the band midpoint is noise. Twelve of them is 180,000 of unplanned annual cost and a comp band problem you now have to fix retroactively, which is far more expensive than fixing it in advance. Our guide to salary banding covers how to keep offers inside the model.
How a CFO reads your plan in the first 90 seconds
Reads as credible
- Every row has a named hiring manager
- Start dates are months, and roughly half sit in the back half of the year
- Backfills are separated from growth roles
- Each growth role names the metric that justifies it
- The file reconciles to payroll within about 3 percent
Reads as a wish list
- Rows labelled Eng Hire 1 through Eng Hire 6
- Every start date is the first day of a quarter
- Cost column is base salary only
- Nobody can say who approved a req
- Plan has not been touched since the board deck
If your plan reconciles to payroll within about 3 percent each month, you have a working system. Past 10 percent, the file has become fiction and people have already started keeping their own private versions.
Keep the plan and the pipeline in the same system
Prepzo connects requisitions, pipeline stages, and hiring analytics so your headcount plan reconciles against real recruiting activity instead of a stale export.
Try Prepzo freeSanity checks
Revenue per headcount and the other ratios that catch bad plans
Once the plan is built, test it from the outside. Four ratios catch most of the problems before a board member does.
Revenue per headcount is the first. Divide annual revenue by average full-time equivalents. Private B2B software companies commonly plan around 150,000 to 250,000 dollars per employee, though the range is wide and the model matters more than the benchmark. Watch the direction of travel. If the ratio falls two quarters running while you keep hiring, the plan is ahead of the business and you are buying capacity you cannot yet feed.
Second, the ratio of individual contributors to managers. Below about five reports per manager in a company under 300 people, you are usually paying for coordination you do not need yet. Third, the share of total headcount growth going to revenue-generating functions. If G&A grows faster than sales and product two years in a row, someone should ask why out loud.
Fourth, recruiter capacity. Divide planned hires by recruiters. Past roughly 40 to 60 hires per recruiter per year, quality drops before volume does, and you start paying for it in bad hires that cost far more than the recruiter you did not add. A rushed process is also where structure disappears, which matters given Google's re:Work research on structured interviewing and how much predictive power an unstructured loop throws away.
Track these on a live recruiting dashboard rather than recalculating them the night before a board meeting.
Tooling
When a spreadsheet stops being enough
Headcount planning software exists as a category, and vendors will tell you spreadsheets are the problem. My view is more boring: the spreadsheet is fine for longer than most people expect, and the trigger to move is version control, not sophistication.
Three conditions together mean it is time. More than roughly 40 open or planned roles. More than one person editing the file. And a finance team that needs plan-to-payroll reconciliation every month rather than every quarter. Hit all three and you will lose more hours to reconciling versions than a tool costs.
Before buying a dedicated planning tool, check what you already own. Most modern ATS platforms hold requisition status, approval chains, offer amounts, and stage timing, which is the majority of what a planning tool wants to ingest. If your ATS already has that data and can export it cleanly, the gap you are filling is a join and a chart, not a product. Our overview of recruiting analytics software covers what to look for.
One genuine warning about spreadsheets: they hold salary data for named individuals, which is sensitive in every jurisdiction and regulated in several. If your plan lives in a shared drive that half the company can open, fix that today. Restrict the file, or split identifying information into a tab with separate permissions.
Failure modes
Five ways headcount plans break
The plan is written once and never touched
January plans built for a board deck get abandoned by March. If nobody owns the file, nobody updates it, and within a quarter every function is running a private copy that disagrees with the others.
Roles are generic placeholders
A row called Eng Hire 3 cannot be sourced, priced against a band, or defended. Name the role and the level before it goes in the plan, even if the exact scope shifts later.
Only base salary is modelled
This understates the people line by roughly a quarter to a third. It is the most predictable budget miss in the entire exercise and the easiest to avoid.
Attrition is left out entirely
If you plan 20 new roles and run 15 percent annual attrition on a team of 100, you are actually hiring 35 people. Budget the backfills or your recruiters spend the year on unplanned work.
Location and entity are ignored
The same role costs materially different amounts in New York, Austin, and Lisbon, and hiring in a country where you have no legal entity means an employer of record and a different cost structure. Put location in the sheet.
Operating rhythm
A cadence that keeps the plan alive
The template is the easy part. What makes it work is a schedule nobody has to be reminded about.
Two meetings a month and one real re-plan a quarter. That is the whole system. Teams that keep this rhythm rarely need an emergency freeze, because the small corrections happen early enough to matter. If you are starting from nothing, our guide on how to create a hiring plan is the right first step, and the recruitment metrics worth tracking tell you whether it is working.
Frequently Asked Questions
What is headcount planning?
Headcount planning is the process of deciding how many people a company will hire, when each hire starts, what each one costs fully loaded, and which business trigger justifies the role. It sits between the finance budget and the recruiting pipeline, and it produces a dated, priced list of roles rather than a general growth target.
What should a headcount planning template include?
At minimum: role title, department, level, hiring manager, backfill or new, target start month, base salary, fully loaded cost, the trigger that unlocks the req, approval status, requisition ID, and current pipeline stage. Anything less and the plan cannot be reconciled against your ATS or your general ledger.
How do you calculate fully loaded cost per employee?
Start with base salary, then add employer payroll taxes, benefits, equipment, software seats, and amortized recruiting cost. BLS Employer Costs for Employee Compensation data puts benefits at roughly 31 percent of total compensation for civilian workers, so a common planning multiplier lands between 1.25 and 1.4 times base for US salaried roles.
What is a good revenue per headcount number?
It depends heavily on the model. Private B2B software companies often plan around 150,000 to 250,000 dollars of ARR per employee, while services businesses run much lower and marketplaces much higher. The number matters less than the trend. If revenue per headcount falls two quarters in a row while you keep hiring, the plan is outrunning the business.
When should you replace a headcount spreadsheet with software?
Roughly when three things become true at once: more than about 40 open or planned roles, more than one person editing the plan, and a finance team that needs the numbers to reconcile with payroll monthly. Below that, a well built spreadsheet plus an ATS that exports requisition data is usually faster than buying a tool.
How often should you update a headcount plan?
Monthly for actuals, quarterly for the plan itself. The monthly pass reconciles filled roles, slipped start dates, and cost variance. The quarterly pass is where you actually move, cut, or add roles based on what the business did in the last 90 days.
Who owns headcount planning, finance or HR?
Finance owns the dollars, the hiring manager owns the business case, and recruiting owns the delivery date. In practice one person should own the file itself. When ownership is shared equally, the plan goes stale within a quarter because nobody feels responsible for the version everyone is arguing about.
Resources & Further Reading
Related Guides
- Workforce Planning: The Strategic Layer Above Headcount
Capability planning across a two to three year horizon
- How to Create a Hiring Plan
The starting point if you have no plan at all
- Cost Per Hire: How to Calculate It Properly
The recruiting cost line in your fully loaded model
- Salary Banding: Build Ranges That Hold Up
Keep offers inside the plan instead of above it
External Sources
- BLS: Employer Costs for Employee Compensation
Wage and benefit cost breakdown for US employers
- BLS: JOLTS Job Openings and Labor Turnover
Market conditions and turnover rates by industry
- IRS: Social Security and Medicare Withholding Rates
Current employer payroll tax rates and wage base
- SEC: Human Capital Disclosure Modernization
Why headcount data became a board-level reporting item
