Headcount forecasting: how to forecast where your headcount will actually land

Curious how TeamOhana can help you? Talk to us.
In this article
Never miss new content
Headcount is the biggest line on most companies’ P&L. On average it makes up about 70% of operating expense. So when a headcount forecast is off, everybody feels it. Finance explains a variance it didn’t see coming. Recruiting gets measured against a hiring plan that was never realistic. People Ops hears about attrition at the same moment the budget does.
Most forecasts miss for the same two reasons, and neither one is a math problem. The data lives in too many places, and the plan assumes every approved hire starts on time and nobody quits. This guide covers how to build a headcount forecast with formulas and examples, the six types of headcount models, and how to forecast the gap between your plan and what hiring will probably deliver.
What is a headcount forecast?
A headcount forecast is an estimate of how many people you will employ, and what they will cost, at a future date. It starts with who is in seat today, adds approved hires that haven’t started yet, and subtracts expected departures. The result tells you what your headcount and headcount spend will be at the end of the fiscal year, over the next 12 months, or over the next 24 months.
Forecasting headcount matters for cash flow and burn rate, and it is usually part of the headcount planning cycle. Many companies run an annual plan and then refresh the forecast monthly or quarterly, as Krishna Vallabhaneni, CFO of ProcessMaker, described on our podcast.
Headcount forecast vs. headcount plan vs. headcount model
These three terms get used interchangeably, and mixing them up is how Finance and HR end up arguing about numbers that were never meant to match.
- Headcount plan: the approved intent. Which roles you’ve agreed to hire, in which departments, at what budget.
- Headcount forecast: your best estimate of what will actually happen, based on current data, the plan, attrition and compensation.
- Headcount model: a flexible version of the forecast you use to test what-if scenarios before you commit to a decision.
Our headcount planning process guide covers how the three fit into an annual cycle.
How to forecast headcount: formulas and examples
Before you do any math, you need current headcount and hiring data you trust. The easiest way to get it is a headcount management platform that works alongside your HRIS, ATS and FP&A tools. Without one, you’ll be pulling exports from three systems into a spreadsheet and hoping nothing changed since lunch.
Step 1: Gather your data
Compile these inputs:
- An accurate employee roster with compensation, department and job details
- An up-to-date hiring plan: who has been hired, pending starts, open reqs, and the compensation and target start date for each position
- All known upcoming terminations
- Your average attrition rate, or the department-level rate if you’re forecasting by department
- Upcoming backfills, promotions and internal transfers
Step 2: Calculate your effective current headcount
Take the people in seat today, add pending hires, and subtract known terminations.
Effective current headcount = active employees + pending hire starts - upcoming terminations
.avif)
Say you have 400 active employees, 35 pending new hire starts and 10 anticipated terminations. Your effective current headcount is 425 (400 + 35 - 10).
Step 3: Calculate your burn
Gross burn is your total operating expense: salaries, software, rent and everything else. When you calculate future months, use the start dates of pending hires and the end dates of terminations, because timing changes cash flow. Net burn subtracts operating expenses from revenue for the period.
Net burn = revenue - operating expenses

Step 4: Build the forecast
Add approved roles that haven’t been filled yet, and subtract the departures you expect based on historical turnover. With 425 effective headcount, 30 open approved roles and 15 expected departures by year end, your forecast is 440 (425 + 30 - 15).
Many Finance teams also break the forecast down by department, team or initiative, because a company-wide number can look fine while one department is 12 heads behind.
That 440 is a planned forecast. It is useful, and it also assumes things that rarely happen, which is what the next section is about.
Why headcount forecasts drift from reality
A forecast built on the plan only knows what the plan knows. Four things push actual headcount away from it.
- Start dates slip. Cost hits the books when someone starts, not when the req opens. If a role you planned for March starts in June, that quarter’s forecast is wrong, and so is everything built on it.
- Departures create backfills nobody planned for. Some models subtract expected attrition, which lowers headcount and cost. But every departure also opens a backfill req, and that req has a cost and a recruiting workload the forecast never counted.
- The data doesn’t tie. An employee in your HRIS who isn’t linked to an open role gets missed. A hire who is both in seat and still counted as open gets counted twice. Either way the forecast is off by the number of people it happened to.
- Net and gross don’t match. If your budget is a net number and your hiring plan is gross, the two will never reconcile. If you want 100 people in seat and expect about 5 seats to be vacant at any given time, you need 105 budgeted positions. Pick one basis and label every number with it.
Forecast at the position level, not just the total
A total headcount number can look right while the positions underneath it are quietly slipping. The fix is to forecast from positions: every approved seat gets one record from approval to hire, with a target start date, compensation, department and status. The company forecast is the sum of those records.
That structure does three things for you:
- It keeps approved roles, open reqs and actual hires aligned. The position is the one thing all three systems point back to, so Finance, HR and Talent are looking at the same seat.
- It makes start dates defensible. Instead of a gut-feel date, you can use how long similar roles have taken to fill in the past. As an example, a company’s engineering roles might average around 45 days to fill and its sales roles around 60.
- It shows where the gap is. You can see which department, which role and which stage is behind, rather than discovering a total that’s off.
This is the idea behind position management: the position, not the person, is the system of record. It works alongside your HRIS rather than replacing it.
Predicted Forecast: where headcount will probably land
A planned forecast says where headcount lands if everything goes as intended. A predicted forecast adjusts for what your own history says usually happens. TeamOhana’s Predicted Forecast adds three outputs next to your planned values:
- Predicted Forecast: where headcount will likely land at period end, accounting for expected attrition that hasn’t been logged yet, backfills that can realistically close before the period ends, and planned hires that may slip.
- Predicted Terminations: the total expected departures between now and period end, combining terminations already logged with the departures the model expects for the remaining months.
- Predicted TBH: the revised hiring target once attrition-driven backfill demand is added to your planned hires.
The predictions come from your own data. Predicted attrition is based on your termination history over the last 12 completed months, applied to expected headcount in each remaining month of the period.
An illustrative example
These numbers are made up to show the mechanics. Start with 425 effective headcount and 30 approved hires still to come.
- Planned Forecast (425 + 30 hires, every hire on time, only logged departures): 455
- Expected departures not yet logged, based on 12 months of history: -12
- Planned hires that start after year end, based on past fill rates: -4
- Backfills that can realistically close before year end: +3
- Predicted Forecast: 442
The 13-person gap between 455 and 442 is your execution risk. Finance can use it to anchor scenario planning and budget reserve conversations before the quarter is over. Recruiting gets something useful too: the 12 expected departures turn into backfill demand, so the hiring target for the period is 42, not 30.
Predicted Forecast sits alongside your plan and doesn’t replace it. Your administrator can enable it in org-level settings, and role-level permissions control who sees the predicted outputs.
How to model the cost impact of a delayed hire
A delayed start changes this year’s cost, and it can change what the team can deliver. To put a number on the cost side, prorate the role’s annual compensation by the months of delay.
Cost deferred in the fiscal year = annual target compensation x (months delayed / 12)
If a role has $180,000 in target compensation and the start slips three months, the fiscal year cost drops by $45,000 ($180,000 x 3/12). Two cautions. First, that is timing, not savings: the annualized cost of the role is unchanged, and it shows up in next year’s budget. Second, the work that role was supposed to do still isn’t getting done, so look at what the delay costs in capacity, recruiter workload and missed targets as well.
In TeamOhana, the Variance Tracker shows both views. The fiscal year impact view reflects timing, so hiring later than planned gives a positive fiscal year variance. The annualized view removes timing and shows full-year cost. Variance is split into date variance (hired earlier or later than planned) and compensation variance (pay differs from budget).
Types of headcount forecasting models
There are six main types of headcount models: as-is, supply, demand, sales capacity, what-if scenarios and succession planning.
1. As-is headcount model
An as-is model is a detailed picture of your current headcount, pending and planned hires, terminations, and org structure. It’s the foundation. You need it before you can forecast or model anything else.
2. Headcount supply model
A supply model asks what your current workforce can deliver and when you’ll need to add employees or contractors. It can be tied to revenue or output. An ad agency, for example, could use one to check it has enough designers and writers for current clients, and to see how many new clients it could take on if it added people.
3. Headcount demand model
A demand model works backwards from business goals. If the company wants to close $300K in new MRR next quarter, how many more people does it need, in which roles, and when? Factor in time to hire for your market. If you need an engineer starting June 15, you have to open the role well before that.
4. Sales capacity model
A sales capacity model is a demand model for the sales team. It uses typical rep ramp time, average closed-won deals per rep and expected demand to work out when to hire. Ramp time and quota attainment can vary a lot by market, so large teams should factor in location.
5. What-if scenario analysis
What-if models test the impact of decisions before you make them: a reorg, a new department, a hiring freeze, a budget cut. The usual set is a best case, a worst case and a most likely case. In TeamOhana, a scenario is a sandbox copy of the hiring plan, so you can model changes and see the effect on budget, forecast and variance without touching the live plan. Nothing goes live until the scenario is approved and merged, and you can clone a scenario to compare versions.
6. Succession planning model
A succession model helps you fill leadership and key roles quickly. It identifies who could grow into senior roles and when the company will need to create new ones. A 50-person company might have two account executives reporting to the CEO, while a 500-person company needs a Head of Sales or a VP, and the model shows the timeline and whether the role is filled by promotion, transfer or an outside hire.
Common challenges of headcount forecasting
Teams run into three problems again and again: unreliable data, inefficiency and lack of control.
Unreliable data. If the inputs live in your FP&A tool, HRIS and ATS, you have to pull them into a spreadsheet, and the minute you do, the data is a snapshot. Can you be sure what you exported a few hours ago still matches what’s in your HRIS or ATS?
Inefficiency. Spreadsheets don’t support collaboration across Finance, HR and Talent. Everyone extracts, formats and reconciles by hand, and each handoff is another chance for a mistake.
Lack of control. Compensation and headcount data is sensitive, so some people need to see it and others shouldn’t. You need to restrict access without making collaboration harder.
How TeamOhana helps you forecast headcount
TeamOhana connects to your HRIS, ATS and FP&A tools so the forecast runs on live data instead of last week’s export. A few of the pieces that matter for forecasting:
- Forecast tile on the Headcount page: projected headcount at the end of the period you pick, which defaults to the end of the current fiscal year.
- Variance Tracker: compares budget with forecast and shows whether variance comes from timing or compensation.
- Scenarios: model hiring changes, mid-year budget cuts or a reorg before they touch the live plan.
- Predicted Forecast: adds expected attrition, backfill demand and hiring slippage on top of the plan.
- Exports and feeds: export the headcount forecast or a monthly burn report, or feed the data to your FP&A platform. TeamOhana supplies headcount data to your FP&A tool. It doesn’t replace it.
Here’s a quick peek at how headcount forecasting works in TeamOhana:
Customers like SeatGeek and Docker use TeamOhana to streamline headcount management. Daniel Fulmer, Director of Finance at FusionAuth, described what it replaced on our podcast: forecast work that used to take “hours and hours a month” and still wasn’t quite right.
If you want a starting point, the headcount plan template is free. If you’d rather see the forecast run on your own data, request a demo.
Simplifying TeamOhana: your questions, answered.
Headcount forecasting is estimating how many people your company will employ, and what they will cost, at a future date. It combines current headcount, approved hires still to come, expected departures and compensation, usually through the end of the fiscal year or for the next 12 to 24 months.
Start with effective current headcount (active employees plus pending hire starts minus upcoming terminations). Add approved roles you haven’t filled yet, then subtract expected departures based on your historical attrition rate. For example, 425 + 30 - 15 = 440.
A headcount plan is the approved intent: the roles and budget you’ve agreed to. A headcount forecast is your best estimate of what will actually happen given current data, hiring pace and attrition. The gap between them is where variance comes from.
Many companies plan annually and refresh the forecast monthly or quarterly. Start dates move more often than that, so teams also review past-due start dates each month, since cost hits the books when someone actually starts.
Expected departures lower headcount and cost, and each one also creates a backfill that adds recruiting workload and cost. A forecast that only subtracts attrition understates the hiring needed to stay on plan.
Multiply the role’s annual target compensation by the months of delay divided by 12. That gives the cost deferred in the current fiscal year. It’s a timing difference, not a saving, because the full-year cost still arrives later and the work still has to be done.
Yes. Predicted Forecast is a probabilistic forecasting layer that shows where headcount will likely land at period end, accounting for hiring slippage and attrition that isn’t yet in the plan. It is built from your own termination history and hiring patterns.
No. TeamOhana provides current, accurate headcount and cost data, and exports it or integrates with your existing FP&A tools.



