Workforce planning and the financial plan: building the CHRO and CFO operating model

Two numbers from Mercer’s Global Talent Trends 2026 explain most of what goes wrong between HR and finance. Only 27% of executives say HR advises effectively on workforce risk. At the same time, 81% of investors say embedding HR strategically is fundamental to growth. The demand is there. The supply of credible advice is not.

That gap does not usually open because the workforce plan is wrong. It opens at the handoff. HR plans in headcount and capability. Finance plans in cost and margin. The two get reconciled once a year, in a budget conversation neither side enjoys, and whichever version is denominated in dollars wins. Workforce planning and the financial plan end up as two documents describing two different companies.

This piece is about closing that gap in practice: the numbers your CFO already carries, the sharpest misalignment between pay practice and skills strategy, and then the operating model itself. The shared data spine and who owns which number. How to convert capability plans into cost lines, and how to run headcount and capability budgeting together. A planning calendar that syncs to the financial cycle, the metrics worth putting in front of a CFO, a risk register finance will read, and the mid-year reforecast.

The credibility gap is measurable, and it cuts both ways

Mercer’s Global Talent Trends 2026 draws on roughly 12,000 executives, HR leaders, employees and investors across 16 geographies and 16 industries. Alongside the 27% and 81% figures, it reports that 97% of investors say weak skills-based models would harm investment value. Read those three together: the capital markets already believe workforce capability is a value driver, and they do not believe HR is the function explaining it to them.

HR leaders feel the pressure without always being able to convert it. SHRM’s 2026 research, published January 2026 and based on 1,856 HR professionals including 352 HR executives, found 43% cite rising operational costs as a primary concern and 42% feel pressure to meet financial goals. HR already carries the financial anxiety. What it lacks is the vocabulary to put it into the model finance is running.

The four numbers your CFO already carries

The first is productivity and cost. BLS Productivity and Costs for Q2 2026, released 6 August 2026, put nonfarm business labor productivity up 1.4% annualized in the quarter and 2.2% year over year. Unit labor costs rose 1.3% in the quarter and 1.4% over four quarters. Hourly compensation rose 3.7%, but real hourly compensation fell 0.1% over four quarters. Output per hour is rising faster than the cost of an hour, which is the most benign labor cost environment a CFO has seen in years.

The second is the labor share of output, and it reframes the conversation. BLS reported labor share at 52.9% in Q2 2026, the lowest level in a series that begins in the first quarter of 1947. Not the lowest in a decade, the lowest ever recorded. Productivity has also grown at an annualized 2.1% since Q4 2019, against 1.5% over the Q4 2007 to Q4 2019 stretch.

The third is what that looks like at company scale. Fortune’s analysis of the Fortune 500, published 19 June 2026, showed record revenue of $21 trillion, up 5%, record profits of $2.1 trillion, up 12%, and market capitalization of $55 trillion, up 19%. Employment fell 1% to 30.5 million, a loss of 301,049 workers. Revenue per employee reached $687,094 and profit per employee $68,743. Harvard’s Lawrence Katz attributes the trend primarily to outsourcing of labor-intensive work plus technology productivity gains, not principally to AI. That attribution matters: the decoupling of output from headcount is a structural, decades-long pattern, not a sudden AI event your CFO will treat as speculative.

The fourth is the supply constraint, the one number here that runs in HR’s favor. The Federal Reserve Bank of Kansas City estimated in October 2025 that breakeven employment growth, the monthly job creation needed to hold unemployment steady, has fallen to roughly 77,000 per month, and to 29,000 excluding immigration. In that market, soft payroll prints signal constrained supply, not slack demand. Do not let anyone read weak hiring numbers as evidence that talent has become cheap.

Those four define the frame a CFO operates inside: output can grow while headcount does not, labor’s claim on output is at a record low, and the people you need are harder to source. Argue on that terrain.

Where the financial plan quietly overrules the workforce plan

Mercer’s US compensation planning survey, fielded across 1,013 US organizations in late October 2025, put 2026 merit increase budgets at 3.2% and total increase budgets at 3.5%, flat against 2025. Promotional increases average 8.7%, but the promotion rate is falling to about 9% of the workforce, down from 10%. The same survey found 57% of employers reporting stable hiring volumes despite AI adoption, only 9% planning headcount changes related to AI, and only 2% citing AI or automation as a reason for reduced hiring. Whatever the discourse says, the money is not moving because of AI.

Here is the finding that should stop you: 83% of employers said they would distribute their salary increase budgets equally across the organization, rather than directing more resources toward high-demand skills.

Nearly every workforce plan identifies scarce capabilities. Then more than four in five spread the money flat.

If the workforce plan says scarce skills and the pay plan says uniform, the financial plan has already overruled the workforce plan. Not through argument, through arithmetic. A uniform 3.2% merit distribution states that every capability in the business is appreciating at the same rate. No CHRO believes that. The market certainly does not. But the payroll file says it every cycle, and the payroll file is the document finance trusts.

It is also the most tractable problem here, needing no new technology and no new headcount, only a named percentage of the increase budget directed differentially and defended against the capability plan. The reason 83% distribute evenly is rarely analytical. Uniform distribution is the only allocation nobody has to justify.

Why the numbers do not tie out

First, the honest diagnosis: most organizations cannot produce a workforce plan and a financial plan from the same underlying data.

BearingPoint’s People and Tech study, published 18 March 2026 and covering 414 senior HR and transformation leaders across Europe, found that 45% use AI or analytics platforms to generate insights across systems, but only 14% consistently connect and act on that data. Nearly one third cannot systematically use data across systems at all. Insight generation is not the constraint. Reconciliation is.

The horizon problem compounds it. McKinsey’s HR Monitor 2025, published 3 July 2025 across Europe and the United States, found that only 12% of HR leaders do strategic workforce planning with at least a three-year focus, while 73% conduct full operational workforce planning. Finance runs a multi-year long-range plan as a matter of course. HR mostly does not. When finance asks what the workforce looks like in year three, the honest answer in most organizations is that nobody has modeled it. That is why HR gets invited to the budget conversation rather than the strategy conversation.

The operating model

The shared data spine, and who owns which number

The first rule is that every number has exactly one owner, one system of record and one refresh cadence. Dual ownership is how reconciliation meetings get invented.

A workable split: finance owns the position ledger, the fully loaded cost per position including benefits, employer taxes, equity expense and allocated overhead, and contractor and outsourced spend, because that already sits in the general ledger. HR owns the position-to-person mapping, the requisition pipeline, the capability taxonomy and skills inventory, the attrition forecast, and time to fill and time to productivity. Both sides agree one headcount definition, in writing, covering part-time, fixed-term, contingent and unfilled-but-funded positions.

Then agree the joins. The position ID links the HR system to the general ledger, and without one that survives reorganizations every cost conversation degrades into a spreadsheet argument. If you still reconcile workforce cost by emailing extracts between HR and FP&A, fix that first.

The second rule: the CHRO does not dispute finance’s cost numbers, and the CFO does not dispute HR’s capability numbers. Each side owns its own inputs. What they negotiate is the plan, not the data.

Translating capability plans into cost lines

A capability plan says we need materially more depth in data engineering, regulatory affairs and industrial controls over three years. A CFO cannot carry that sentence. What a CFO can carry is a cost line with a timing profile. The translation runs through four routes, each with a distinct cost signature.

• Buy. External hiring. Recruiting cost, salary at market premium for scarce skills, onboarding, and the ramp period during which you pay full cost for partial output. Fast to start, slow to deliver, priced outside your organization.
• Build. Internal development and redeployment. Training spend, coverage during development time, and the compensation adjustment that follows capability acquisition. Cheaper per unit than buying, but it consumes calendar time.
• Borrow. Contingent, contract and outsourced capacity. It sits in operating expense rather than headcount, which is why it gets overused when headcount is frozen. Flag the substitution, or you will report a flat headcount plan alongside a rising cost plan and lose credibility.
• Redesign. Automation, work elimination or restructuring the job. Technology and change cost now, against a capacity saving later, with a real probability that the saving does not fully land.

Every capability gap should resolve into a mix of those four, with an FTE-equivalent capacity number, a unit cost, and a quarter in which the cost begins. FP&A can consume that without translation, and it makes explicit that “we will upskill” is a spending decision with a delivery date, not an aspiration.

Headcount budgeting and capability budgeting: run both

Headcount budgeting asks how many positions we fund and what they cost. It is a control mechanism, well understood, and it will not go away. Capability budgeting asks which capabilities we are buying more of, at what price, and how that price is moving relative to the market. Most organizations run the first and talk about the second. The Mercer 83% finding is the proof.

Run them as two views of the same plan. The headcount view rolls up by cost center against the position ledger. The capability view rolls up by capability cluster and reports three things: spend directed at that capability, the change in its unit cost, and coverage against the plan. Both must reconcile to the same total, or the capability view is decoration.

The mechanism is a named, ring-fenced portion of the increase and development budgets, allocated by capability scarcity rather than cost center headcount. Named, because unnamed money gets absorbed. Defended annually, because the pull of every compensation cycle is back toward uniform distribution.

A planning calendar that syncs instead of trails

Most workforce plans arrive after the budget is built, which means they can only request exceptions. Fix the sequence and half the friction disappears.

• Q1: baseline and truth. Refresh the capability inventory and the position-to-person reconciliation, and close out prior-year variance in both headcount and capability terms. Nothing here is forward-looking, and that is the point.
• Q2: scenarios, timed to the strategy refresh. Model two or three workforce scenarios against the business scenarios finance is already running for the long-range plan. Same assumptions, same horizons, same currency. This is the highest-value change on the list, because it puts workforce modeling inside the strategy conversation rather than downstream of it.
• Q3: the plan lands before the budget build. Capability plans converted to cost lines, delivered to FP&A before the budget template opens. Include the risk register below.
• Q4: allocation and pay. Increase budget, promotion budget and capability carve-out, decided against the capability plan rather than last year’s distribution.

Finance’s own cycle is getting faster, which raises the cost of trailing it. Deloitte’s CFO Signals for Q2 2026, surveying 200 North American CFOs at companies with at least $1 billion in revenue, found 93% say their organizations use AI across key operations and 44% deploy AI for financial planning and budgeting. It also found 46% name cost uncertainty and transparency as their biggest internal AI concern, and 59% cite balancing quick AI deployment with risk management as their top challenge. So finance is compressing its planning cycles, and cost transparency is where your CFO is anxious. That is exactly where a well-built workforce cost model earns trust.

The small set of metrics worth putting in front of a CFO

Resist the full dashboard. A CFO engages with a short list carrying external comparators, because a number benchmarked against a public source can be audited.

Each has a financial consequence you can state in one sentence. An 18% probation attrition rate means nearly one in five hiring investments is written off before it produces anything. Succession coverage of one third on critical roles is a concentration risk finance would never tolerate in a supplier base.

For the schema, use ISO 30414:2025. Edition 2 was published in August 2025 and supersedes the withdrawn 2018 version. It covers 11 human capital reporting areas, including workforce composition, costs, productivity, mobility and succession planning, turnover, and skills. Its practical value is that it is not yours: when a metric definition is contested internally, an international standard settles it faster than a debate does.

A workforce risk register finance will actually read

Risk registers fail with finance for one reason: they are qualitative. A register that says “key person risk: high” gets read once and never again.

Give every entry six fields. The risk, stated as an event rather than a condition. The exposure, in dollars or months of delay to a named business outcome. The likelihood, as a range you will defend. The time to impact. The mitigation and its cost. The leading indicator you will watch, and its current value.

Four categories earn their place. Concentration risk in critical roles, anchored to your succession coverage against McKinsey’s one-third benchmark. Scarce-skill cost drift, where the market price of a capability rises faster than your increase budget, which translates directly into compensation variance. Supply constraint, using the KC Fed breakeven figures to show that a hiring plan assuming a loose market assumes something the data does not support. And internal supply capacity, now stated CFO strategy: Deloitte’s CFO Signals for Q4 2025, also covering 200 CFOs at companies with at least $1 billion in revenue, found 49% say their organizations will hire or promote internally to keep worker costs in line in 2026. If half of CFOs count on internal mobility as a cost lever, the risk that internal pipelines cannot deliver belongs on the register with a number attached.

Include the risk created by the mitigation too. A hiring freeze that protects this year’s margin while pushing capability acquisition into a tighter labor market is a risk transfer, not a risk reduction. Say so in writing, before the decision.

How to handle the mid-year reforecast

The mid-year reforecast is where workforce plans get quietly dismantled, because it runs as a cost exercise under time pressure. Prepare rather than react. Re-baseline attrition against actuals instead of carrying the annual assumption, since attrition variance is normally the largest single driver of workforce cost variance. Re-price open requisitions at current market rather than the rate they were approved. Retire requisitions open long enough to be evidence that the role, the price or the market assumption is wrong. Then, and this is the part that matters, propose reallocation between the four routes rather than accepting reduction. Moving a capability from buy to build changes the shape of the cost curve without abandoning the plan. Moving it to borrow changes which line of the P&L it lands on.

Protect the capability carve-out explicitly. It is the smallest line and the easiest to absorb, and absorbing it is how you arrive back at uniform distribution without deciding to. Report variance in both views, so a plan that came in on budget while losing ground on scarce skills is visible as what it is.

Reconciling positions, costs, scenarios and capability coverage inside one model rather than across exported spreadsheets is what workforce planning software with organizational modeling and cost forecasting is built for, and it is why the same data should feed your compensation planning cycle. If the capability plan and the pay plan live in different files, the pay plan wins by default.

Frequently asked questions

What is the difference between headcount budgeting and capability budgeting?

Headcount budgeting funds positions and reports cost by cost center. Capability budgeting allocates spend by capability scarcity and reports the changing unit cost of skills you need. Both views must reconcile to the same total. Running only the first is why 83% of employers spread merit budgets evenly (Mercer, 2026).

Which workforce metrics do CFOs actually trust?

Metrics with public external benchmarks. Compensation share of output against the BLS labor share of 52.9% for Q2 2026, unit labor cost change against +1.4%, revenue per employee against the Fortune 500 figure of $687,094, and increase budgets against Mercer’s 3.5% for 2026. Benchmarked numbers can be checked, so they get believed.

How do we align workforce planning with the financial planning calendar?

Move the workforce plan upstream of the budget build. Baseline in Q1, run workforce scenarios alongside finance’s long-range planning scenarios in Q2, deliver capability cost lines to FP&A in Q3 before the budget template opens, and allocate pay and capability budgets in Q4. A plan delivered after the budget can only request exceptions.

What is ISO 30414 and why does it matter to finance?

ISO 30414:2025, Edition 2, published August 2025, supersedes the withdrawn 2018 version. It defines 11 human capital reporting areas including workforce composition, costs, productivity, mobility and succession planning, turnover, and skills. It gives you externally defensible metric definitions, which shortens internal arguments about what a number means.

Why do most workforce plans fail at the handoff to finance?

Because the two functions plan in different units, on different horizons, from different data. Only 12% of HR leaders plan on a three-year-plus horizon while 73% do operational planning (McKinsey, 2025), and only 14% of organizations consistently connect and act on cross-system data (BearingPoint, 2026). The plan does not fail. The translation does.

Where to start

You do not need a new operating model to make progress this quarter. You need three things, in sequence.

First, agree the data spine: one headcount definition, one position ID linking HR to the general ledger, one owner per number, signed by both functions. Second, name the capability carve-out in the next increase budget and defend it, since even a small directed allocation breaks the uniform-distribution default Mercer found in 83% of employers. Third, get workforce scenarios into finance’s long-range planning conversation before the budget build begins.

Then make the numbers visible continuously rather than annually. A shared view of workforce cost, capability coverage and risk, built on business intelligence dashboards that both HR and finance read from, changes the conversation more than any model does. Pair it with the numbers that measure bench strength and pipeline health, since succession coverage is the workforce risk finance grasps fastest, and with our guide to integrating demographic trends and economic forecasts into workforce planning.

The 27% figure is not a verdict on HR’s competence. It is a verdict on translation. Investors are already convinced that workforce capability drives value. The work left is arithmetic.