The cost of losing a senior employee: calculate your company’s exposure

You can fill the vacancy and still be missing the context

Hiring someone with comparable experience does not give them your company’s history. They may know the software but not why a client has different terms, which approach was already rejected or which incident requires a conversation before anyone changes a setting. That gap matters even when the replacement is excellent.

It becomes harder when context is scattered: the proposal in Drive, the scope change in a conversation, project data in another application and the explanation in the senior employee’s head. The knowledge lost when somebody leaves is therefore different from the inventory of files handed over.

Ask two separate questions: what will filling the role cost, and which work could not continue using the information currently available? The first informs recruitment spending. The second identifies knowledge worth recovering and the people who need access to it.

Separate spending, internal time and operational risk

The CIPD employee retention guide identifies recruitment, training and knowledge loss among the costs associated with turnover. Applying that to your company requires keeping the categories visible instead of combining them into one unexplained number.

• Direct spending: an external recruiter, advertising or temporary support that is actually purchased.
• Internal time: interviews, handover, mentoring and reconstructing processes. Payroll already covers it, but it displaces other work.
• Observed operational impact: rework, a delay with a verifiable cost or a specific incident.
• Unresolved risk: an account or process that could fail. Record the exposure without presenting it as a loss that has already happened.

This distinction gives management something more useful than an alarming estimate. It shows which category needs cash, which consumes capacity and which needs a preventive action. It also makes it easier to assign the right owner to each part of the calculation.

Collect the inputs before assigning a value

Operations can coordinate this work with the department lead and whoever understands employment costs. The director does not need to reconstruct every procedure personally. Management approves the scope and decides which dependencies deserve attention first.

Collect recruitment spending, planned handover hours, who will mentor the replacement and which tasks nobody else can currently handle. To value internal time, use a consistent employment cost and working hours basis. If one estimate uses gross salary and excludes other employment costs, label it. Do not compare it directly with a fully loaded cost.

Distinguish measured hours from estimates. Scheduled handover sessions provide evidence. A general impression that everyone is always blocked suggests something to investigate, but is not yet a reliable multiplier. Ask what other work can be done while waiting. Waiting for an answer and having no productive alternative are different situations.

A worked example: €3,000 in spending and 84 internal hours

This is a hypothetical example, not a Savia customer result. It assumes €3,000 for external recruitment and an internal cost of €35 per hour. Each group of hours belongs to a separate activity and is counted once.

The €5,940 combines external spending with a value assigned to internal time. It is not €5,940 of additional cash payments. It also does not measure the complete value of knowledge lost. The example excludes vacancy coverage, future errors and assumed lost revenue.

Next, check the 84 hours against the actual calendar. Where mentoring includes training that any new starter would need, identify it as normal onboarding. The calculation becomes useful when each assumption can be discussed and corrected, rather than defended as a precise universal total.

A replacement’s whole salary is not a loss

A person who is learning also produces useful work. Their salary over four months does not prove that four months of salary have been lost. Estimating a capacity gap requires evidence of expected output, actual output and other factors that could explain the difference.

With a hypothetical annual employment cost of €60,000 and a four-month learning period, the salary scenario would be:

€60,000 ÷ 12 months × 4 months = €20,000 of salary cost during the learning period.

Report this separately. Do not automatically add it to the €5,940 above or describe it as money a knowledge tool will recover. Some valued hours may already appear in other budgets, and the learning period contains productive activity.

Apply the same discipline to a delayed project. Do not record the full contract value as a loss when only its delivery date changed. Record a penalty, extra work or affected margin when there is evidence. If the impact is still unknown, leave it open and explain what information would let you evaluate it.

Dependency can cost money before anybody leaves

A departure makes the problem visible, but interruptions and waiting can exist long beforehand. An expert repeats an explanation, another colleague searches for the correct agreement and a team works out an exception that was solved before. These are signals to measure, not percentages to borrow from a different company.

The knowledge loss calculator uses team inputs to estimate annual interruption and waiting costs. It also presents a separate replacement salary scenario. It does not price lost knowledge or calculate every recruitment and training expense.

If you use the result to compare options, keep the report’s assumptions and do not add the replacement scenario to the annual total. An indicative figure helps choose where to investigate. To support an investment decision, follow it with a sample of actual questions, hours and blocked work in the selected department.

Which knowledge should you recover before a handover?

Start with knowledge that has three characteristics: only one person understands it, it affects important work and it would be difficult to reconstruct. The list might include client exceptions, recovery steps for an incident or technical decisions that the standard procedure does not explain.

For each case, record the question the replacement should be able to answer, available sources and the missing explanation. A recording of a real task allows follow-up questions about exceptions. Distinguish current practice from something done once under unusual circumstances.

Then ask somebody who was not present for the explanation to use it. Can they find its source? Recognise when the rule does not apply? Identify who should approve an exception? If they only understand the material with the senior employee sitting beside them, the transfer is still incomplete.

The knowledge transfer interview questions help structure that conversation. A dependency inventory should connect each critical process to an owner, a possible replacement, supporting sources and the part that still needs an explanation.

How a digital brain helps after the handover

A company digital brain brings connected sources and people’s contributions together so that context can be consulted. Savia incorporates documents and explanations, shows their sources and helps collect answers from relevant experts when information is missing. Contributions still need the applicable review controls.

The purpose is to keep recovered knowledge accessible to the next account owner, the operations team and future starters. It can also provide context to the company’s AI tools and agents, with access controls. A source makes an answer easier to check; it does not guarantee that the underlying information is current or correct.

Management does not need to become the documentation team. It selects the priority process and who can validate the result. Scope, source connections and expert participation are agreed during Savia’s supported implementation. The contribution expected from the department should be explicit before the project starts.

Turn the estimate into a specific decision

A useful cost report ends with a decision, not just a large number: protect an account handover, recover an operational exception or make one expert’s reasoning accessible. Assign an owner, an effort budget and a way to check whether another person can now use the information.

Compare the cost of acting with the problem actually observed, rather than a theoretical hundred per cent saving. Recovering knowledge cannot prevent every departure, remove all training or replace the new senior employee’s judgement. It does allow you to test how much context another person can already use.

Before approving a project, request a demonstration with questions from the chosen process, authorised sources and a question that should remain unanswered. Then measure whether the replacement finds the information, interprets it correctly and still needs assistance. That evidence supports a decision about expanding to another department.