Back to Video Hub

The Approval Flow That Turns Three Hiring Plans Into One Source of Truth

Key Highlights

Where Unapproved Headcount Spend Actually Comes From

Hiring plans live in three places at once, and small changes fall through the cracks. An up-level, a pushed start date, a quiet backfill. Without one approval path for budget-impacting changes, roles get modified and opened without any budget owner ever seeing them. That's the source of the variance Finance discovers after the quarter closes.

One Approval Desk, Configurable to Your Rules

Every new hire request, backfill, change request, and scenario routes through one hub. Approvers see the exact budget impact before they click approve. Chains can be driven by department, cost center, location, or dollar threshold. High-volume backfills can auto-approve. Up-levels trigger review. Approvers act inside Slack without switching tools.

An Audit Trail That Ends the Retrospective Guessing

Every change on every headcount is logged. Who made it. What changed. When it happened. Finance never has to reconstruct when a role went from IC2 to IC3 or why a start date moved from July to August. Nothing reaches the hiring plan without approval. Nothing changes on the plan without a record.

Most companies don't have a hiring plan. They have three. Finance keeps one version. Talent keeps another. Department leaders track their own. When budget-impacting changes happen without a single approval path, they happen anyway. An up-level here. A pushed start date there. A backfill opened by someone with no budget authority. That's how unapproved headcount spend spirals into millions of dollars of variance nobody planned for. In this walkthrough, we show how TeamOhana routes every new hire, backfill, change request, and scenario through one centralized approval desk, with configurable chains, Slack-native approvals, and a full audit trail on every change.

What you’ll learn

Why unapproved headcount spend is a governance problem, not a spreadsheet problem
How to route every new hire, backfill, and change request through one approval desk
How to configure approval chains by department, cost center, location, or dollar threshold
How Slack-native approvals cut review time without cutting oversight
How to skip approvals for one-to-one backfills while still gating budget-impacting changes
How a versioned audit trail retires the question "who changed this and when"
How compensation bands and midpoints get enforced at the request moment, not after the offer

Takeaway #1: Unapproved Headcount Spend Is a Structural Problem

Most companies treat headcount overruns as a discipline issue. It isn't. When Finance, HR, and Talent each maintain their own version of the plan, budget-impacting changes route through whichever spreadsheet the requestor happens to have open. There is no single desk to say yes or no. The variance shows up after the money is committed.

Takeaway #2: The Approval Moment Is Where Governance Has to Live

A budget number is only as strong as the point where it gets committed. TeamOhana puts the approval at the moment of decision, not after it. Requestors see the compensation band and midpoint pulled from the job catalog before they submit. Approvers see the exact budget impact before they click approve. Every stakeholder acts on the same number.

Takeaway #3: Configurability Is What Makes Governance Survive Contact With Reality

Rigid approval chains get bypassed. TeamOhana lets you route approvals by department, cost center, location, or dollar threshold. Auto-approve one-to-one backfills. Require sign-off on up-levels. Route high-dollar requests to the CFO. Route low-risk ones to the department head. Approvers act inside Slack, so review time doesn't become a bottleneck.

Takeaway #4:The Audit Trail Ends the Retrospective Reconciliation Cycle

Every change to every headcount is logged with who, what, and when. This retires an entire category of work. Finance stops reconstructing why a role changed levels. HR stops chasing down who moved a start date. Talent stops explaining why a req looks different than it did last week. The record is already there.

"Every budget-impacting change runs through one approval desk, routed to the right approvers by your own rules, and logged in an audit trail you can retrace at any time. Nothing reaches your hiring plan without approval." — Virginia Hyland, Head of Solutions Engineering, TeamOhana

Frequently asked questions

Unapproved headcount spend is any budget-impacting change to your workforce that goes live without a budget owner authorizing it. It happens because most companies run three parallel hiring plans across Finance, HR, and Talent. Changes get made in one system without routing to the people accountable for the budget. Up-levels, start date shifts, and backfills accumulate quietly until Finance sees the variance after the fact.

Every budget-impacting change. New hire requests, backfills, change requests to existing roles, and larger modifications submitted as scenarios. Each one routes to a preset group of approvers and only goes live once they've approved it.

Yes. Approval chains can be driven by department, cost center, location, or dollar threshold. You can auto-approve one-to-one backfills, require review on up-levels, route high-dollar requests to executive approvers, and keep low-risk requests at the department level. You have full control over who reviews what.

Approvers can review and approve headcount requests directly inside Slack. They see the role details, the budget impact, and the approval status without leaving the tool they already work in. Requestors can follow their submission as it moves through the chain, with each approver's status visible in real time.

Every change to every headcount. Who made the change, what changed, and when. This includes level changes, start date moves, compensation adjustments, and status updates. You can retrace the full history of any role at any time, which retires the manual reconciliation work Finance and HR do today to explain variances after close.