When Recruiting’s headcount tracker reaches its limits

TL;DR

You built a spreadsheet or Airtable database to track hires against the plan. It’s a little manual, but the visibility to the business leaders is worth it. Six months in, finance is running their own numbers and they don’t match yours. The CFO is asking questions, and you and FP&A are scrambling to reconcile. You optimized for the question recruiting owns (hiring progress), but the system has to answer the questions finance and the business are asking too. What started as a simple recruiting tracker now has sprawled into 30+ columns that are riddled with errors. The upkeep of the tracker is taking up more and more of your time, and people quickly start to lose trust in the data.

The pride and the blind spot

You know this one. The dashboard that finally connects planned roles to recruiting status. The progress-to-plan views the recruiting leaders take to their business stakeholders. The hiring leaders have visibility into hiring progress.

It’s working well until your FP&A counterpart tries to reconcile your tracker against the finance’s plan. They find discrepancies every month. Changes your team makes in the tracker don’t flow back to the finance model. When a hiring manager wants to uplevel a senior role to a staff role mid-process, it could appear as a comment in the tracker or a Slack DM. It’s impossible to audit.

The business leader starts to ask how these hires in plan tie back to their product areas or sales segments. They ask “are we on track?” and your system says yes (we’ve hit our offer accepts) while finance says no (we’re behind on starts). Both are technically right. The business leader concludes neither team knows what they’re doing.

What happens at the six-month mark

Finance makes changes to the plan, pausing some roles and releasing others. They’re talking to the business leaders directly, and recruiting is the last to know. The discrepancies between their model and your dashboard start to pile up. Now it’s impossible to tell the story of how the original plan morphed into this new plan.

The business leader doesn’t understand why recruiting and finance still give different answers to the same basic questions. They’re starting to lose trust. You’re back to monthly reconciliation calls where the numbers never match, and both teams leave frustrated.

The same pattern everywhere we look

This isn’t specific to your team. Prior to Caro, the Recruiting Ops team at Intercom maintained a spreadsheet to track hiring progress towards an ending headcount target. Finance maintained a separate financial model. The two required reconciliation every month. Changes the recruiting team made didn’t flow back to Workday, Greenhouse, or Adaptive, leading to endless reconciliation cycles. Nobody could see who changed what or how a role had evolved over time.

The structural reason

The tool was built from a recruiting perspective, and finance’s budget management use case was missed because it’s outside of recruiting’s purview.

Recruiting teams focus on offer accepts because that’s what’s in their control. Finance teams focus on the actual start date because that’s when the hire hits payroll. The lag between these events is can be several weeks to several months, depending on the geography. Your dashboard reports against offer accepts because that’s the leading indicator you can control. Finance reports against payroll start because that’s when costs hit the budget. Same week, two different numbers, both correct, but confusing to the business leader who isn’t in the weeds to understand the difference.

The fix isn’t just adding more fields. It’s defining the right workflow for headcount changes and who needs to be in the loop for each change. It’s figuring out how the HCM, ATS, and planning system get updated after the decision is made.

What the cross-functional fix actually looks like

A common view that answers the questions for every stakeholder at once:

• Recruiting can prioritize roles and plan capacity: which reqs are open, pipeline health, recruiter bandwidth, progress against the approved plan.

• Finance can understand the budget implications: the payroll forecast, variance to plan, and the dollar impact of every hiring decision in real time.

• Business leaders can confirm that the right people will land for their initiatives: which roles are approved for hire, who’s in the pipeline, and who’s already accepted an offer.

• HR can advise on org structure: leveling distribution, location strategy, org design.

Same underlying data. Four views. When recruiting closes a role, finance sees the cost impact propagate immediately. When finance approves a budget change, recruiting sees the update without waiting for a reconciliation cycle.

That’s what we built at Caro. A workflow system for headcount that works for recruiting, finance, HR, and business leaders. Integrations with the HCM, ATS, and planning system ensure that all your systems stay in sync. Recruiting operates in the same view as finance. Changes are tracked per-field with a full audit trail: who changed what, when, and why. No more monthly calls where the numbers don’t match.

When Intercom adopted Caro, the finance team went from initial skeptics to the greatest advocates. The recruiting team could finally tell the story of how they managed capacity to a constantly changing plan, and explain the true reason for hiring shortfalls (manager readiness, approval delays) rather than absorbing blame for factors out of their control. That’s what happens when both teams trust the same data.

FAQ

Is this really about the tool, or is it about getting finance to trust recruiting’s data?

Same problem. Finance doesn’t trust recruiting’s data because recruiting’s system doesn’t answer finance’s questions. When the system answers both teams’ questions from the same underlying data, trust follows because the data is defensible. The trust problem and the architecture problem are the same problem.

What about the time I’ve invested in our current tracker?

Your tracker is an important step in getting the business to even think about headcount and setting the foundation. What’s missing is the layer that connects your hiring workflow to finance’s budget model and the business leader’s initiative view. It’s not about walking back from your tracker; it’s upgrading it to meet the needs of your cross-functional partners.

Why can’t we just share the spreadsheet with finance?

Because sharing the data doesn’t solve the definitional mismatch. Recruiting reports offer accepts; finance reports payroll starts. Recruiting counts gross hires; finance counts net adds. Sharing a spreadsheet means sharing one team’s definitions with a team that uses different ones. What’s missing is the mapping of the different definitions, so both can ask their question and get a correct answer without reconciling against each other.