The Stakeholder Map for a Benefits Business Case That Actually Gets Approved

A Reward and Benefits leader spends four months building a proposal. It’s well researched, tightly costed and grounded in real employee data. They present it to the executive team, expecting a straightforward discussion about scope and timing. Instead, the CFO asks how the savings will be tracked once the programme is live and Legal asks whether the vendor's data processing terms have been reviewed. 

Neither question is unreasonable, but the Reward and Benefits leader doesn’t have answers ready. The proposal is deferred, and what follows is six weeks of separate conversations with Finance and Legal that could, with a different sequence, have happened six months earlier and shaped the proposal rather than stalled it.

This isn’t a story about a weak business case. It’s a story about a business case that was built by one team and shown to everyone else only once it was finished.

Read the full guide: How to build a compelling business case for employee benefits

Why HR-siloed business cases fail

A benefits investment at enterprise scale rarely clears the line on the strength of the argument alone. It clears the line because the people with sign-off power, or the influence to block sign-off, have had their concerns addressed before the room is asked to make a decision. Finance, Legal, Operations and the country teams that will implement the programme locally all have a stake in the outcome, and in most organisations at least one of them can stop a proposal outright.

The problem is timing, not personality. A stakeholder who meets a fully formed proposal for the first time at the approval stage isn’t being asked to help build something. They’re being asked to review something someone else has already decided. Reviewers look for reasons to withhold approval, because that’s what the review function is for. The same person, brought in six months earlier while the model was still being built, is answering a different question: not “should this go ahead” but “what needs to be true for this to work.” Co-ownership isn’t a courtesy extended to stakeholders. It’s what converts a review into a decision that has already, in effect, been made.

It also changes what a stakeholder's questions are for. A Finance lead who has helped set the cost modelling assumptions is asking questions to sharpen a case they already have a stake in. A Finance lead seeing the model for the first time in the approval meeting is asking questions to find out whether the case can be trusted at all. Both conversations can look identical from the outside, a Reward leader fielding queries from the front of a room, but only one of them tends to end in approval on the day.

Who your stakeholders are and what each one is actually asking

None of this is news to a Reward leader who’s taken a case through approval before. What’s worth setting out plainly is the specific set of questions each stakeholder is likely to bring, because a proposal that answers them before they are asked has already done most of the work of securing buy-in.

Finance wants to know the total cost of ownership, not just the headline investment: implementation costs, ongoing fees and the administrative burden the programme adds. They want a payback period, and they want to know whether the savings the case promises can actually be audited once the programme is live, rather than asserted once and never revisited. Budget implications by financial year matter as much as the total figure, because a case that lands well against a three-year total can still fail if the first-year number breaks the current budget cycle.

Read more on how to build the numbers Finance will test.

Legal wants to know whether the current programme carries compliance risk that this investment addresses, and what exposure remains if the organisation does nothing. Classification risk is a live concern for any global workforce that includes contractors or cross-border employees. It’s not a theoretical one: in one widely reported case, Spanish regulators fined the delivery platform Glovo €79 million over employment status determinations, and enforcement of this kind is increasing rather than easing off. Legal also wants to understand how the proposed programme handles statutory requirements across every market the organisation operates in, and what the liability picture looks like if the business chooses to stay as it is.

Read more on building compliance in from the start.

Operations and Country Leads want to know what the rollout actually requires of them: the implementation burden on regional teams, how much local variation the programme allows, what the employee communication plan looks like, and how long rollout takes before it stops needing their attention. Their concerns are practical rather than strategic, which is exactly why they’re easy to overlook until the build phase, when it’s too late to plan around them.

The CPO or CHRO wants the connection to the wider people strategy and any board-level commitments the organisation has already made. They want the story that will be told to employees, and they want a clear answer on how success will be measured, because they’re the one who will ultimately have to stand behind the programme's results.

Co-ownership vs consultation: when to bring each stakeholder in

The distinction that matters is between a co-owner and a consultee. A co-owner helps shape the proposal while it is still being built, and their fingerprints are on the assumptions the case rests on. A consultee reviews a proposal that already exists, and their only real lever is to slow it down or send it back. Most benefits business cases treat every stakeholder outside the People team as a consultee. The ones that get approved on the first attempt tend to have turned at least two of them into co-owners well before the proposal reached its final form.

In practice, this maps to three phases:

1. During design, Finance and Legal should be in the room agreeing the cost modelling assumptions and the compliance requirements the programme has to satisfy, not receiving a finished model to react to. 
2. During build, Operations and Country Leads should be shaping the implementation plan and flagging regional feasibility issues while there’s still time to adjust the approach. 
3. By the time the proposal reaches approval, it should be a document Finance and Legal have already helped shape, not one they’re seeing cold for the first time.

A short working session at the design stage, where Finance sets out what a credible payback model needs to include and Legal flags the compliance questions it will ask regardless of what the proposal says, costs a Reward leader an afternoon. Discovering the same requirements for the first time in a deferred approval meeting costs weeks, and it costs something harder to get back: the sense, for Finance and Legal, that the proposal was built without them in mind.

Same strategy, different framing for each audience

The underlying strategy doesn’t change from one stakeholder to the next. The framing has to. 

• Finance responds to the savings case, the payback period and the ability to audit results, so the proposal should lead with ROI and risk reduction when Finance is the audience. 
• Legal responds to compliance risk quantification, so the same investment should be framed as risk mitigation when Legal is reading it. 
• Operations responds to a clear implementation plan and a reduced admin burden over time, not to the strategic narrative that will land well with the CPO. 
• The CPO, in turn, wants the strategic connection and the employee experience story that the other three audiences do not need.

None of this means writing four different documents. It means knowing which section of the same document each reader will actually stop and read closely, and making sure that section speaks their language rather than HR's.

Full launch, phased launch or pilot: structuring the rollout to reduce approval risk

Offering a choice of implementation approach reduces the risk a proposal is asking the business to accept, and that in turn reduces the risk of the proposal being rejected outright. 

• A full launch, covering every country and every benefit on the same timeline, is the fastest route to complete coverage and carries the highest implementation risk. 
• A phased launch starts with the highest-impact or lowest-complexity markets and extends from there, which spreads the implementation burden and gives the business a working proof of concept to evaluate before committing further. 
• A pilot, run in a single market or employee segment, carries the lowest risk and the slowest path to full coverage, but it generates real operating data that strengthens the wider case rather than asking the business to take it on faith.

Finance in particular tends to respond better to a phased approach, because the cost profile is more predictable than an ambitious single-year commitment. A proposal that names this trade-off explicitly, rather than presenting one option as the only option, gives Finance a decision to make instead of a demand to accept.

A global organisation weighing a new wellbeing benefit, for example, might present a full launch across twelve markets alongside a phased option that starts with its three largest markets by headcount and extends over the following two years. Laying both options side by side, with the cost and risk profile of each made explicit, tends to move the conversation away from whether to approve the programme at all and towards which version of it the business is ready for now.

Communications planning belongs in the business case, not after it

A benefits programme that employees don’t know about, or don’t understand, doesn’t deliver the value the business case promised. This isn’t a minor operational detail to be handled once the programme has launched. Comms planning belongs at the design stage, alongside the cost model and the compliance review, because the quality of communication has a direct bearing on the return the business case is claiming.

The size of the gap is easy to underestimate. Research from SHRM has found that only 9% of HR professionals rate their employees as “very knowledgeable” about the benefits available to them, with most describing awareness as merely “somewhat” there. The effect of closing that gap is measurable rather than assumed: one analysis of HSA enrolment found that employees who received proper education on how the benefit worked were nearly three times more likely to enrol than those who didn’t. Good communication is specific, timely and delivered across more than one channel. It’s also, directly, the mechanism that connects a benefits investment to the utilisation rate Finance will be watching once the programme is live.

Approval isn’t the finish line. It’s the point where the measurement phase begins, and the proposal that gets signed off is, in effect, a promise about what will be tracked and reported from here. A stakeholder map built well in advance of approval is what makes that promise credible in the first place, because the people who will hold the business to it have already had a hand in setting the terms.

Read the full guide: The measurement framework that makes your next business case easier to win