Upcoming
On demand
30 minutes

After the Annual Plan: Managing Headcount in the Real World

The Plan Is Approved. Now What? Managing Headcount When Everything Keeps Changing

Annual planning is done. Leadership signed off. Finance has the numbers. HR has the headcount list. Everyone is aligned.

For about two weeks.

Then a director decides to swap a senior engineer for two mid-level ones. A backfill comes in that wasn't in the original plan. A new initiative gets greenlit and suddenly there are six roles that need to be opened by end of quarter. And somewhere in the middle of all of this, a hiring manager is asking why their recruiter is working a role that got put on hold last month.

The plan was never meant to be static. But most teams are still managing a living, breathing headcount plan with tools built for a snapshot. So every change kicks off a chain of emails, Slack messages, and spreadsheet updates just to get everyone back on the same page.

This session is for HR and Talent leaders who are good at planning but exhausted by what comes after it.

In this TeamOhana demo, we'll walk through:

  • Headcount Ledger: Every change to the plan, whether it's a new role, a backfill, a level change, or a hold, is tracked in real time and reflected immediately across Finance, HR, and TA. No more chasing down what changed or why.
  • Approval Workflows: When a business leader wants to make a change mid-year, it goes through a structured process before it touches the plan. TA doesn't start recruiting until Finance has signed off. Everyone moves with the same information.
  • Recruiter Workboard: Your TA team always knows exactly which roles are approved, funded, and ready to recruit. No more working roles that are on hold. No more missing roles that quietly opened last week.
  • Scenario Planning: When leadership wants to shift priorities mid-quarter, HR and Finance can model the impact together before anything is committed. You stop reacting to decisions and start shaping them.

Key Highlights

The Spreadsheet Goes Stale on Day Two
The headcount plan starts drifting the moment the fiscal year begins. Up-leveled roles, backfill approvals stuck in Slack, comp changes that only live in the offer letter. By the end of the first month, no one is looking at the same number.
Jump to
2:43
One Hire, Five Systems, Zero Source of Truth
A live walkthrough of how a single headcount moves through the org: leader prioritization, HRBP Slack thread, TA ops spreadsheet update, ATS req creation, HRIS reconciliation. Every handoff is a chance for the plan to fall out of sync, and TA ops ends up stuck in the middle answering to everyone.
Jump to
4:49
Scenario Planning Without the Spreadsheet War
How leaders run what-if modeling, quarterly re-planning, and role-level changes inside a sandbox tied to live budget impact. Down-level a role, see the FY and annualized impact instantly, route for approval, and push to the live plan with a full change log.
Jump to
22:56

What You'll Learn

  • Where headcount plans break down between Finance, HR, TA, and business leaders, and what it costs you
  • How one hire moves through five systems, and where reconciliation fails at every step
  • How to track every change to the plan with a complete audit log of who changed what, when, and why
  • How approvals can run in Slack instead of email threads and screenshots
  • How to bidirectionally sync TeamOhana with Greenhouse, Ashby, and Lever so ATS reqs stay aligned with approved positions
  • How to run scenario planning and quarterly re-plans in a sandbox tied to live budget impact

Takeaway 1: The Plan Is a Photograph. The Reality Is Film.

A spreadsheet captures the plan on the day it was approved. It does not capture the up-level that happened in week three, the backfill request sitting in Slack, or the start date that just slipped a quarter. The cost of that gap is not theoretical. It is variance, missed forecasts, and the quiet erosion of trust between Finance and Talent.

Takeaway 2: Reconciliation Is a Tax, Not a Process

TA ops updating the spreadsheet, Finance maintaining a parallel forecast, HR working out of the HRIS, business leaders asking for a status. Every system holds a version of the truth, and someone is paying the tax to reconcile them. That tax shows up as hours lost, decisions delayed, and forecasts that go stale before the next leadership meeting.

Takeaway 3: Observability Beats Reporting

A hiring plan with no exceptions surfaced is a hiring plan you cannot trust. TeamOhana's "needs attention" layer flags the things that actually matter: 17 terminations with no backfill decision, an unclaimed employee who showed up in the HRIS outside the plan, headcount that has quietly slipped quarters and deferred cost Finance never saw coming.

Takeaway 4: Approvals Belong in the Flow of Work

Finance and HR leaders already live in Slack. Forcing them into another tool to approve a headcount change is friction the org will route around. Approvals that happen in Slack, with full context and a clean audit trail captured automatically in the system of record, are the approvals that actually get done on time.

"A spreadsheet of your hiring plan acts like a photograph, a snapshot in time. TeamOhana is more like the film, watching the ever-evolving and changing aspects of the plan live."— Virginia Hyland, Director of Solution Engineering, TeamOhana

Frequently asked questions

My company already runs headcount planning in our FP&A tool. Why would we need TeamOhana?

FP&A tools are built for Finance to model the plan. They are not built for the four teams that execute it: Recruiters, Hiring Managers, HRBPs, and Finance. TeamOhana sits next to your FP&A tool and runs the operating layer after the plan is approved, so the model stays accurate without Finance chasing updates every Monday.

We have an HRIS and an ATS. Isn't that enough?

The HRIS holds employees. The ATS holds candidates. Neither one holds the plan, the approved budget, or the reconciliation between them. That gap is where ghost reqs, mis-leveled hires, and start-date slippage live. TeamOhana is the layer that connects all three.

Who actually uses TeamOhana day to day?

Finance leaders for budget variance and forecast accuracy. HR and HRBPs for approvals and governance. TA ops for req creation and ATS sync. Business leaders and hiring managers for requesting headcount and running what-if scenarios. Everyone looks at the same number.

How does TeamOhana connect with our ATS?

Bidirectionally. When TA ops is ready to hire an approved position, they create or link the job in Greenhouse, Ashby, Lever, or other ATS with one click, and the headcount ID maps one-to-one with the opening ID. If a hiring manager up-levels a role inside TeamOhana, the ATS opening updates automatically.

Can business leaders model changes without affecting the live plan?

Yes. Scenarios take a snapshot of the live plan and give leaders a sandbox to run what-ifs: down-level a role, change a location, add headcount, model attrition. Every change shows fiscal year and annualized budget impact in real time. When the leader is ready, the scenario routes through approval and updates the live plan with a full change log.