KnowledgeCapital

KnowledgeCapital › Guides

Knowledge transfer before retirement: a method that does not rely on memory

How to organise know-how transfer before an employee retires: spot what leaves, measure the risk, train a successor, prove it is done.

In short

A retirement can be seen years ahead; the knowledge leaves in a day. Transfer succeeds when, before the date, you know which knowledge depends on that one person, how much it matters, and who can take it over. KnowledgeCapital measures those three things and follows the transfer until a successor has been assessed at the required level.

Why the classic handover fails

The handover lasts two weeks and goes to open files, passwords and paperwork. What really mattered — the ear that knows when a pump runs badly, the way to restart a line after an emergency stop — is never written down, because nobody asked and the person does not know it is rare.

So the question is not "how do we make the expert write before leaving". It is: what do we depend on without knowing it?

The four steps that work

1. Spot what leaves with the person

Attach each piece of knowledge to the tasks it serves, then record who masters it, from 0 to 5. Knowledge held by a single person then shows up by itself: the key-person risk.

2. Measure the risk, do not guess it

Risk combines vulnerability (how many people know, how hard it is to pass on) and relevance (how often it is needed, what it cost to acquire). The method is published: it can be debated in a meeting.

3. Train a successor, with a dated plan

The action plan names a pair, sessions and a deadline before the departure. The internal academy turns sessions into a path where each level is validated by a test.

4. Prove it is done

Risk only drops when the successor has been assessed at the required level. It is never declared "closed" by hand: that is what stops people from feeling safe too early.

What it looks like on an industrial site

On a 1,900-person mining group (demonstration data), the five-year retirement wave hits 161 people and 33 pieces of knowledge have a single holder. The decision board ranks them by urgency and proposes, for each, the closest successor in skills and structure.

What KnowledgeCapital is not

Neither a document management system nor a wiki: both assume the knowledge has already been written. Here the first job is to find out where it lives and how exposed you are.

Documents that already exist stay where they are: connectors read SharePoint, your document management system, Notion or the intranet, and link them to knowledge — which immediately shows which critical knowledge has no document before the departure. To start from a blank space, follow the set-up order.

Frequently asked questions

How long before the departure should we start?

Twelve to eighteen months for knowledge that is hard to pass on. The initial map takes a few weeks; it is the successor's ramp-up that takes time.

Does the expert have to write documents?

No. Transfer happens through sessions, real questions and validated lessons learned. What gets written is written because a question was asked, not out of obligation.

How do we know the transfer succeeded?

When the successor is assessed at the required level on the knowledge concerned. The risk score then drops by itself.

No card. A space pre-filled with five years of demonstration data.

Try it free for 14 days   Watch the guided tour

Going further

Updated on

The other guides

Knowledge transfer before retirement: the method

How to organise know-how transfer before an employee retires: spot what leaves, measure the risk, train a successor, prove it is done.

Knowledge management software: how to choose

Knowledge base, wiki, document management or knowledge mapping: which knowledge management software answers which need, and the five questions that decide.

Knowledge management system: a 12-point evaluation grid

Twelve criteria to compare knowledge management software without solving the wrong problem: tacit knowledge, criticality, connectors, sovereignty, cost.

Skills mapping: method and software

How to map an organisation's skills: reference list, mastery levels, criticality. What separates an Excel matrix from a living map.

How to build a knowledge management system from scratch

The exact order for building knowledge management on a blank space: org chart, people, knowledge catalogue, processes, holders, criticality, assessments.

Key-person risk: knowledge held by one person

Spot knowledge that depends on one person, measure the exposure and organise a successor before the incident: the single point of failure of knowledge.

Lessons learned software with validation

Capture lessons learned from the field: contribution, validation by a committee, links to knowledge, search across four languages.

Industrial knowledge management for maintenance

Knowledge management for industry, mining and energy: maintenance know-how, rare skills, departures, and a method that holds up on site.

Sovereign knowledge management with local AI

Self-hosted knowledge management software: no outbound connection, local AI, built-in video conferencing, isolated data, full reversibility.

A knowledge ERP: what your ERP does not manage

An ERP manages stock, orders and payroll. It does not know who is the only person able to restart the line. KnowledgeCapital is the ERP of that resource.

Internal expert network: find who knows

Locate expertise in the organisation: an expert network based on measured mastery, questions routed to who knows, answers captured.

Succession planning for critical knowledge

A succession plan that starts from critical knowledge: who leaves, what leaves with them, who can take over, and proof that the successor is ready.

SharePoint knowledge base connector: setup and limits

The SharePoint connector reads your site pages and document libraries via Microsoft Graph, read-only, and links each file to the knowledge it describes.

DMS and knowledge management: Alfresco, Nuxeo, CMIS, WebDAV

Your DMS keeps documents; it does not say who knows. The connector reads Alfresco, Nuxeo or Nextcloud through CMIS or WebDAV, read-only.

Notion as a company knowledge base: a practical guide

Notion is great for writing together. How to structure a Notion knowledge base, and connect it to learn who actually masters what it describes.

Intranet knowledge management: map knowledge, no migration

Your intranet publishes procedures; it does not say who can apply them. The connector reads its pages, even without a sitemap, and feeds the knowledge map.