The expensive part of replacing someone is not the hiring. Advertising a role, paying an agency, running interviews — those costs are real, they land on a budget line, and somebody above you usually approves them without much argument. The much larger cost is paid quietly by your team over the months either side of the departure: work that gets covered badly, work that gets dropped, and a new person who is on the payroll long before they are producing what the last one did. None of that appears anywhere, which is exactly why it never gets managed.
So the honest answer to "what does it cost?" is: mostly hours, mostly your team's, spread over longer than you expect. The useful version of the question is not the total but the shape — which parts you can actually influence, and which you cannot.
Why the figure you find online won't match your team
Search this question and you will be handed a multiple of salary, quoted with great confidence. Treat those numbers carefully. They come from models built on particular assumptions — a particular sector, a particular seniority, a particular definition of what counts as a cost — and the assumptions do far more work than the arithmetic does.
The reason a single figure cannot travel is that the biggest component varies enormously between roles. Replacing someone in a well-documented, well-staffed role where three colleagues do similar work is a different event from replacing the only person who understands a system, holds a client relationship, or knows why something was built the way it was. Same salary, wildly different bill.
Which means a borrowed statistic is a weak argument and an easy one to dismiss. An estimate built from your own team's hours is harder to wave away, and this article is really about how to build one.
What shows up on a budget line
Start with the visible costs, because they are the easy part and they are usually the smallest part.
- Sourcing the replacement — advertising, agency or recruiter fees where you use them, referral bonuses, and any assessment tools.
- Interviewing time — every hour spent by you, by the panel, and by whoever screens applications, none of which is being spent on the work.
- Overlap and cover — notice-period handover, temporary or contract cover, or overtime for the people absorbing the gap.
- The pay correction — often overlooked and frequently significant. If the market has moved since the leaver was hired, the replacement is priced at today's rate, not the one you had budgeted.
- Setup — equipment, access, licences, training, and whatever induction the organisation requires.
Add these up honestly, then set them aside. They are the part of the cost you can actually see, and they rarely dominate.
The costs your team pays instead
Between the resignation and the new person being useful, the work does not pause. It gets redistributed, and the redistribution is where the real money goes.
Coverage. Someone absorbs the leaver's work on top of their own. They are not doing it as well, they are not doing it as fast, and something of their own is slipping while they do it. If you want a single number to sanity-check the whole exercise, this is the one to estimate: how many hours a week, across how many people, for how many weeks.
Dropped and delayed work. Some of the leaver's responsibilities simply stop. Often that is fine, and a departure is a reasonable moment to discover which work nobody actually needed. Often it is not, and the cost lands later as a missed deadline or a client noticing.
Your own hours. Recruiting, handover planning, reassurance conversations, and onboarding are all your time, taken from managing everyone else. This is the cost most managers underestimate most badly, because it does not feel like a cost — it feels like the job.
Knowledge that leaves. The context that lives in one person's head is the component that never appears in any model: why a decision was made, which client dislikes what, where the process breaks. Some of it can be captured before the notice period ends, which is what a proper handover is for, and some of it simply goes.
Team stability. One resignation makes the next one easier to imagine. Watching a colleague leave, and watching how the manager handles it, changes what everyone else thinks about their own options. Protecting the people who stay is the highest-leverage thing you do in that period, and the reason the first week after a resignation is worth spending on the team rather than on the job ad.
How long until the replacement is actually producing?
This is the largest cost in most departures and the one nobody budgets for, because a new hire looks fully staffed from the outside on day one.
Ramp-up is the period between someone starting and someone contributing what the previous person contributed. It ends at different times for different roles: a well-defined, procedural role where the work arrives in a queue is short; a role that depends on relationships, institutional context, or judgement built up over time is long. In the meantime you are paying a full salary for partial output while also spending experienced people's hours on training — a double cost, running simultaneously.
Two things shorten it, and both are inside your control. A structured onboarding plan puts the new person on real work sooner and reduces how much of the team's time gets consumed answering the same questions — the case for a 30-60-90 day plan. And documentation written before anyone resigns changes ramp-up from an oral tradition into a reading task.
What makes the same departure cost twice as much
The variance between two similar-looking resignations comes down to a handful of drivers. These are the levers worth knowing, because most of them are set long before anyone hands in notice.
- How concentrated the knowledge was. A single point of failure is the most expensive person on any team to lose. Cross-training is cheap insurance bought in advance.
- How much was written down. Undocumented work has to be rediscovered, and rediscovery is slower than reading.
- Seniority and scarcity. Roles that take longer to fill cost more in coverage regardless of salary, because the gap itself is the cost.
- Whether the handover happened. A notice period spent well transfers real work; a notice period spent politely transfers nothing.
- When it lands. A departure during your busiest period costs multiples of the same departure in a quiet month, because there is no slack to absorb it.
- Whether it was one or the first of several. Related resignations compound: each one removes some of the cover the previous one relied on.
How to estimate it for your own team
You can do this in an afternoon, and the point is not precision. It is having a number that came from your team rather than from an article.
- Write down the visible costs for one real, recent departure — fees, cover, interview hours, setup.
- Estimate coverage hours. Who absorbed the work, how many hours a week, for how many weeks, until the replacement was carrying it themselves.
- Estimate your own hours across recruiting, handover, and onboarding. Be honest; this will be larger than you expect.
- Estimate the ramp period — from start date to the point the new person needed no more help than anyone else.
- Convert hours to money using your organisation's own loaded cost figure, whatever finance uses. Do not invent one. If you cannot get it, present the total in hours, which is often more persuasive anyway.
- List what was dropped or delayed, without pricing it. A named list of consequences carries more weight with most audiences than a speculative figure.
What is worth spending to prevent it
Not every departure is preventable, and not every departure should be prevented. Someone in the wrong role leaving is usually cheaper than the same person staying, and a team that never changes has its own costs. The goal is not zero turnover; it is not paying the maximum price for the turnover you get.
The cheapest preventive work is unglamorous and has to happen before anyone resigns: cross-train so no role has exactly one person in it, keep documentation current enough to be useful, and use one-on-ones to hear about dissatisfaction while it is still a conversation rather than a resignation. Compared with the coverage-plus-ramp bill above, all of that is close to free — and unlike a retention bonus, it keeps paying whether the person stays or not.
FAQ
Is a counteroffer cheaper than replacing someone?
On the day, almost always. Over the following year, often not — the reasons someone started looking usually survive the raise, and a counteroffer sets a precedent your team will notice. Judge it on whether the underlying reason is fixable, not on the arithmetic alone.
Does a longer notice period actually save money?
Only if you use it. A notice period spent on a real handover transfers knowledge that would otherwise cost weeks to rebuild. A notice period where the leaver quietly winds down transfers nothing and costs you their salary anyway.
Is it cheaper to hire a contractor to cover the gap?
It moves the cost rather than removing it. Contract cover protects your team from the coverage burden, which is genuinely valuable, but a contractor also needs onboarding and will not absorb the institutional knowledge. It works best for defined, self-contained work and worst for relationship-heavy roles.
How do I make the case for retention spending without a statistic?
Cost out one real departure using the steps above and present it as what it is: an estimate from your own team, with the assumptions stated. A specific, checkable local figure beats a borrowed national one in almost every conversation with a budget holder.
Is some turnover healthy?
Yes. People leaving creates promotion room, brings in different experience, and surfaces work that was only being done out of habit. The costs described here are the reason to manage turnover deliberately, not the reason to fear it.
The bill for a resignation is mostly hours, mostly invisible, and mostly set months before the conversation ever happens — by how concentrated the knowledge was and how much of it was written down. Estimate one real departure on your own team, and you will have both a number worth quoting and a short list of things worth fixing while nobody is leaving. For more practical guidance on hiring, handovers, and holding a team together, visit YouManageIt.
