Finance teams work hard to build a headcount plan. Then reality happens.
A hire that was supposed to close in Q2 slips to Q3. Someone splits a backfill into two roles that weren't in the plan. New hires accepted four offers at 10% above the benchmark rate. Six people leave in the same month, and attrition was budgeted at half that rate. None of these things is a surprise in isolation. But by the time you're reconciling at quarter-end, the variance is bigger than anyone expected. And nobody can agree on why.
The problem usually isn't the plan itself. It's that the plan lives in one place, approvals happen somewhere else, and actuals come from a third system. By the time you pull it all together, you're already behind.
This session is for any Finance leader who has ever stared at a headcount variance and had to reverse-engineer how it happened.
We'll show you what it looks like when your plan, your approvals, and your actuals all live in one place and stay in sync automatically.
In this TeamOhana demo, we'll walk through:
- Variance Tracker: See exactly where your plan drifted from actuals, whether that's a delayed start date, an unplanned backfill, a higher-than-expected offer, or attrition you didn't see coming. No more building a variance explanation from scratch every month.
- Approval Workflows: Every headcount change goes through a structured approval process before it touches the plan. Finance stays in control. Nothing gets added, modified, or removed without a paper trail.
- Attrition Forecasting & Predicted Forecast: Model projected attrition and hiring gaps against your current plan so you can see gaps before they become surprises. Whether you're in a high-growth phase or managing a tighter budget, you'll know what's coming.
- Scenario Planning: When leadership asks "what if we pause hiring in one department and accelerate in another?" you can model the budget impact in real time, not a week later in a spreadsheet.
Key Highlights
What You'll Learn
- Why headcount plans change within days of approval, and which changes drive the biggest variance
- How to stop reconciling plan, approvals, and actuals across three or four separate tools
- How to see the exact drivers of variance (early hiring, higher pay, non-budgeted hires, late hiring, lower pay) in one view
- How approval flows enforce budget control before a change touches the plan
- How to predict attrition and backfill needs so your next plan is closer to reality
- How scenario planning lets finance and business partners test changes before committing budget
Takeaway 1: The Plan Is Supposed to Change. Your System Isn't Built for That.
Every finance leader knows the headcount plan won't survive contact with reality. What they don't have is a system built to absorb changes as they happen. The FP&A tool holds the plan. The ATS holds the reqs. The HRIS holds the actuals. Slack holds the approvals. Reconciling all four is a monthly forensics project, not a management practice.
Takeaway 2: Variance Is a Story, Not a Number
A $2 million variance on its own tells the CFO nothing. What they need to know is what caused it. Was it early hiring pulling costs into the quarter? Offers landing over band? Non-budgeted hires that skipped the planning cycle? Or the opposite: late hiring and lower pay creating room to reinvest? The variance tracker splits the number into drivers so finance can walk into the CFO conversation with the answer, not the question.
Takeaway 3: Approvals Are Where Budget Control Actually Happens
Most companies think of approvals as an HR workflow. Finance should think of them as the moment budget control gets enforced or bypassed. When a hiring manager wants to change a level from IC1 to IC2, or push a start date, or expand a role's scope, that decision has a dollar impact. If it doesn't route through finance before it touches the plan, the plan is already wrong.
Takeaway 4: Predict Attrition Before It Wrecks the Forecast
Backfills are the change type finance can't plan for at the start of the year. You know people will leave. You don't know who or when. Most teams either ignore attrition in the plan or pad it with a flat percentage. Neither reflects reality. Predicted forecasting uses historical attrition by division, expected backfill rates, and TA hiring capacity to give finance a headcount forecast that accounts for what actually happens throughout the year.
"The problem is not really the plan itself. We know that the plan will change. The problem that most finance teams struggle with is that the initial headcount budget lives in one tool, approvals happen all over the place in Slack and email, and the reality of what's actually happening day to day lives in your HRIS and your ATS. At the end of every month, finance is left pulling all of these things together, and the picture is out of date by the time you stitch it together." — Virginia Hyland, Head of Solutions Engineering, TeamOhana
