Internal Mobility Doesn't Save Money. Here's the Business Case That Actually Works

A reply to someone with a paper due in three weeks, a finance director waiting at the end of them, and an industry statistic in paragraph two they should probably delete.

So: three weeks, and a finance director at the end of them. Plenty, provided you spend the first week on the phone rather than in the document. Which is the opposite of how these usually get written. Mine included, years ago.

Here's what I'd do if it were me.

Start by finding the slide. There's almost always one, in a deck that predates you, saying internal mobility reduces recruitment costs. Don't build on it. It isn't wrong, exactly, it's just very easy to take apart, and the person you're presenting to takes things apart for a living.

You'll get one question: if we promote her, who does her job?

That isn't hostile. It's the correct question, which is worse. Once it's asked and you haven't got an answer built in, everything after it gets read with suspicion — the timeline, the resourcing ask, the bit where you need a decision.

Start your internal mobility business case by conceding the saving

The sentence I'd want on your first page, in your own words:

Internal mobility doesn't reduce headcount cost; it relocates the vacancy.

Promote someone into the senior role you can never fill and you haven't closed a gap. You've moved it down a level. It's as real as it was this morning, only now it belongs to a different manager.

Concede that early and two things happen. Your finance director stops reading for the flaw, because you handed it over unprompted. And everything after it reads as measured rather than hopeful, which is what a paper from HR most needs and rarely has. If they find the weakness, your paper is optimistic. If you find it, it's honest.

While I think of it: be careful with the word saving. Across that table it isn't a general good, it's a budget line lower next year than this year with somebody's name against it. Use it without being able to point at that line and you've misused their vocabulary in their own meeting. Anyway.

So what do you claim instead

Three things change when a role is filled from inside, and not one of them is a headcount saving.

Which seat is empty. The vacancy moves from the role that's hardest to fill to one that's easier, and that isn't a neutral swap. Cost, difficulty and operational risk vary enormously between roles. Moving the emptiness downhill is a real gain even when the establishment sheet is unchanged.

How long it stays empty. Internal moves start sooner. No search, no shortlist, no three months' notice elsewhere, no candidate who accepts on the Friday and goes quiet on the Monday.

And how quickly the person is any good in the job. This is the one that matters most and the one nobody measures. Someone who knows your systems, your customers and which committee genuinely decides things reaches full effectiveness on a different timescale from an external hire who is competent and starting from nothing.

So the claim is: your most critical seat is productive sooner, and the vacancy left over is one you're good at filling. The cost-saving version falls over at the first push.

#The backfill question, answered before anyone asks it

Somebody will ask, so build the answer in rather than waiting for it.

Yes, moving someone internally starts a chain. One person moves up, their role opens, somebody moves into that. At a glance, three vacancies where you had one.

Two things are true about that chain. It terminates. And it gets cheaper as it descends — each link easier to fill, quicker to recruit for, faster to productivity, less costly left open.

So the framing isn't *we avoided a vacancy*. It's that you moved one out of a seat that was hurting into a seat that isn't, in the time it takes to have a conversation rather than run a search. Good thing to have done. Not a saving, and calling it one loses you the room.

Why the cost of an internal vs external hire shouldn't come from a benchmark

The second place these papers go wrong is the industry figure in paragraph two. Average cost of replacing an employee. Percentage of salary. The multiplier. Easiest paragraph in the document to write, first one discounted.

Not because it's wrong. Because it isn't about you. Anyone can say *that's not our experience*, and now you're arguing about whether a statistic applies rather than whether your proposal is right. Ground you never wanted, defending research you didn't do.

Your own numbers don't have that weakness, because nobody argues with their own data.

Before the list: assume some of it doesn't exist. Three of the five, commonly. Normal, and still not a reason to borrow.

The five numbers your business case needs, and who is holding each one

None of these needs a system you don't have. All of them need you to ask someone.

| The number | Who has it | What to ask |

|---|---|---|

| What a hire actually costs you | Talent Acquisition; Finance for the invoices | Agency fees, job board spend and advertising, last twelve months |

| How long roles sit vacant | Whoever owns the ATS; otherwise hiring managers | Median days from vacancy approved to first day |

| Internal versus external fills | People analytics, or whoever runs headcount | Of all roles filled last year, how many went to someone already here? |

| Why people left | HR Business Partners; exit interview records | Stated reasons, grouped, and how many mentioned progression |

| Time to full productivity | Hiring managers. No system holds this | For a similar role: months before an external hire and an internal move were each doing the whole job |

Get the third one first. Single question, answer usually back the same day, and it reframes everything else. Low proportion filled internally: there's your problem statement. High: a strength worth protecting, and a different paper to write, irritating in week one and a relief by week three.

The fifth wins it, and it lives nowhere at all. Ask six managers. Write down what they actually say. Present it as a range rather than averaging six estimates into a false precision the first question will take apart. Six managers in your own building carry more weight in that room than any published figure, because everyone there knows them.

If the numbers genuinely aren't there

Then propose something smaller. Properly smaller, not the same paper with more hedging in it.

Pick one job family, the one where filling roles hurts most. Baseline whatever you *can* measure today, before anything changes; a rough baseline written down now beats a better one reconstructed a year later. Run it for two or three recruitment cycles, then ask for a decision date rather than promising an outcome.

A small proposal that generates evidence is easier to approve than a large one that assumes it. And the second business case, a year on with your own figures in it, is the one that gets real investment signed off. Not a consolation prize. Usually quicker, because it never has to survive the question you couldn't answer today.

What I'd take into the room

You are not proposing a saving. You're proposing that your hardest roles get filled sooner by people who are useful faster, and that the vacancies left over are ones you're good at filling.

Concede first. Use your own numbers. Name the chain before anybody else does.

Three weeks is enough for that. Send the concession paragraph to your most sceptical colleague first. If they can't find a flaw you haven't already named, you've written it properly.

In CareerPaths, Career Pathways makes the routes between roles visible so movement can be seen rather than inferred, and Strategic Gap Analysis gives you the organisation-wide