Hiring authority is the mandate conversation nobody has upfront

On paper, the GCC head owns the centre and everyone in it. The charter reads well: build the team, own the roadmap, run the P&L. In practice, the moment a hire crosses a certain seniority, the decision drifts back to a function head at the parent who has never met the candidate and has three other centres to think about. The charter says one thing. The approval chain says another. The head is left running a search they can’t actually close.

This is the mandate conversation nobody has upfront, and there’s a reason it gets skipped. At the moment the charter is signed, no senior hire is live. The ambiguity costs nothing that day. The sponsor is optimistic, the head is new, and pressing on where exactly the parent stops signing off feels like distrust before the relationship has even started. So the question that most needs settling is the one both sides are least inclined to raise.

The gap hides in the space between two documents that are never read side by side. The charter describes intent. The delegation-of-authority matrix, the finance-owned grid that says which spend needs whose signature, describes what actually happens. Those two rarely agree on where a senior hire sits, and no one reconciles them until a live offer forces the question.

The authority gap is invisible for the early hires. Filling out the second tier, engineers, analysts, individual contributors 2 or 3 bands down, sits comfortably inside whatever the head can approve without asking. Nobody tests the ceiling because nobody has reason to reach it yet. The org chart fills in, the centre looks healthy, and everyone assumes the mandate is working.

Then comes the first hire that matters at the top of the house: a functional lead, a senior director, the person who will run a pillar of the centre. That’s the hire that crosses the line where the parent still wants a say. And it’s exactly the hire where the process can’t afford to stall, because the candidates in that tier have options and short patience. The gap and the stakes peak at the same moment, which is the worst possible design.

What surfaces first is a pause. The head extends a verbal, the candidate is warm, and then the offer goes quiet for 2 or 3 weeks while it routes to a function head at HQ who is in a different time zone and a different set of priorities. The head can’t explain the delay without admitting the limit of their own authority. The candidate reads the silence and starts taking other calls.

When the decision is divided, the process slows, and senior candidates read a slow process as a signal about how the place is run. Someone weighing a leadership move is judging the role and, just as hard, whether this organisation can act. A hidden approval chain tells them it can’t, at least not for them, and the strongest people, the ones with other offers in hand, tend to disengage first. What’s left is a hire made under time pressure, often a compromise, and a new leader who has learned on day one that their authority carries an asterisk.

The deeper cost is that everyone watching the search now knows exactly how much authority the head really has. The team they are trying to lead saw the offer stall. The candidate who walked will mention it to peers in a small market. And the head themselves has absorbed a lesson they will carry into the next search: don’t promise what the chain above me might not deliver. That caution makes the next hire slower still.

We have watched genuinely good centres lose multiple senior finalists to nothing more than an approval chain that couldn’t move at the speed of the market. Every one of those losses came down to a yes that no one in the room was empowered to give.

The remedy is unglamorous and almost always skipped: an explicit agreement, before any senior search opens, about where the head decides alone and where the parent stays involved. Vague reassurance, “you own hiring, obviously,” is worse than nothing, because it feels like a settlement without being one. What holds up under a live offer is three specific thresholds, named and written down.

The first is band: the compensation ceiling the head can approve without a second signature. Set it against the market, not against the parent’s domestic pay logic, because a threshold pegged to HQ salary bands will trip on every senior GCC hire by design. The second is level: which seniority the head owns end to end and which still requires the parent’s function head in the loop, and if the parent must be involved, whether they consult or they approve, because those are different powers and blurring them is how the gap re-opens. The third is headcount sign-off: whether the head can open a role against an agreed plan or has to re-justify each requisition upward, which is the difference between running a centre and requesting one.

Written thresholds convert an implicit gap into a stated boundary. A boundary is something a leader can work with and a candidate can trust. It also protects the parent: a clear band and level tells them precisely which hires they will still see, so they can let go of the rest without anxiety. Clarity here removes the guessing on both sides, and leaves the balance of power exactly where it was.

There’s a downstream cost that sponsors rarely connect back to the mandate. 12 months in, the review question is whether the head built the right team. But if the parent held veto over every senior hire, the head didn’t fully build that team, they assembled it from the candidates the chain above them was willing to approve, at the speed that chain could move. Judging the outcome as though the authority had been complete is judging the wrong person.

This is where the settled thresholds pay off a second time. When band, level and headcount are agreed in writing, the line of accountability is clean: inside those thresholds, the bench is the head’s, and so is the result. Outside them, the parent shares the outcome, because the parent shared the decision. Ambiguity about who chose the team becomes ambiguity about who is answerable for it, and that ambiguity always resolves against the head, who is closest and easiest to hold.

The sponsors who get this right treat the mandate conversation as the first act of holding the head accountable. You grant a real hiring mandate so that in a year you can point to the bench and have a fair conversation about it. Withhold the mandate and you forfeit that conversation before it starts.

The best moment to settle all of this is the one moment both sides are motivated to be honest: before the head signs. The candidate has the upper hand and wants clarity; the sponsor wants the hire and is willing to define terms to get it. Once the head is in seat, raising the authority question reads as a complaint about the job, and the incentive to be specific evaporates.

So the ask, for a CHRO or a GCC sponsor, is concrete. Put band, level and headcount thresholds into the offer conversation the way you would put compensation or title. Reconcile the charter against the delegation-of-authority matrix on paper, and fix the disagreement before it becomes a stalled offer. Name what the parent will still touch and commit to the speed at which it will touch it, because an approval right with no service level is just a delay with a signature on it.

Centres that do this hire faster and keep better people, because everyone stopped guessing where the power sat. The head can close. The candidate can trust the yes. And a year on, the sponsor gets the accountability conversation they wanted, about a bench the head was actually allowed to pick.