Every Other Large Spend Needs a Business Case. Pay Decisions Are Made on a Deadline

Compensation makes up a substantial share of total operating cost at most companies. It is also, uniquely among large expenditures, decided without the machinery that governs the others.

Any comparable capital decision requires a business case, an approval chain and a formal review. A pay decision is made by a hiring manager or a recruiter against a deadline, using whatever context happens to be on the screen.

Maria Colacurcio, whose company Syndio works on how enterprises govern pay, offers a domestic analogy for what that produces. It is a diet in which every meal is counted, except the bites of the children's macaroni cheese eaten standing up each evening. Individually negligible. Cumulatively, the whole problem.

The number

Syndio's research team has attempted to size it, and the figure is specific.

A single unmanaged pay decision runs to at least 5,257 dollars.

That is one decision. Multiply it across a hiring year in a company of any size and the aggregate is not a rounding error. It is a material sum being committed without the review any other spend of that magnitude would attract.

Every other capital decision requires a business case. A pay decision requires a deadline

The two functions that own it, separately

In every company, two functions guard this line most closely, and they are not the same function.

Finance and HR, usually represented by the chief revenue officer and the head of total rewards, are jointly responsible for what happens when things depart from the plan. The gap tends to open between strategy and execution, which is where both of them are holding different halves of the same problem.

The deeper issue is that their collaboration is episodic rather than continuous. Each year the teams set the operating plan and headcount, run the merit cycle, analyse pay equity, and work through remediation and any global pay reporting that is required.

Between those moments, the shared strategy lives in a series of static documents.

What static documents produce

The consequences are concrete, and anyone who has worked inside a large compensation function will recognise all of them.

Patchwork range widths, where different parts of the organisation are operating on bands that were set at different times to different logic. Inconsistent pay progression, so that two people on similar trajectories arrive at materially different places. Incomplete or outdated survey data, as leaders move between survey providers trying to compensate for low sample counts in particular roles.

Each of those makes day-to-day management harder, and each of them is the residue of a plan that was correct when it was written down and has not been touched since.

Why the framing matters

The useful reframing here is to stop treating pay as an HR process and start treating it as a capital allocation problem, which is what it is.

Capital allocation has an established discipline: a case, a review, a decision log, and a way of checking afterwards whether the money did what it was supposed to. None of that is exotic, and none of it is currently applied to the largest recurring commitment most companies make.

The reason is partly speed. A hiring manager with a candidate and an offer deadline cannot wait for a committee, and any governance model that ignores this will be routed around within a week.

Which means the answer is not more approval. It is better context at the moment of the decision, so that the person making it under time pressure is working from something more current than last year's document.