Guide: capturing expert knowledge before retirement
Before experience retires.
What a skilled worker has learned in thirty years is rarely in the manual. It can be captured — if you start early.
This page answers the question every company with experienced people asks itself: how does their knowledge reach those who come after them? Without a farewell project and without an interview marathon — on the side, in everyday work.
The best way to capture experience knowledge before retirement is not the farewell conversation but early and on the side: the experienced person brings in knowledge where they work — by voice message, photo or text —, Explicio asks when something is missing, links it with existing documents and records who said it and when. The successor later asks in their own words and gets the answer with its source.
- EARLY, NOT IN THE LAST MONTH
- IN EVERYDAY WORK, NOT IN INTERVIEWS
- WITHOUT ASSESSING PEOPLE
Capturing expert knowledge: the essentials first.
- Expert knowledge is not in any manual: why a machine starts differently, which arrangement applies to which customer, whom to call when it is urgent.
- It comes up at work, not in a farewell meeting. Starting early collects over months what a single interview never captures.
- It takes the least effort when the experienced person explains through the channel they already use: voice message, photo, video or a short text.
- Follow-up questions close the gaps while the person is still around. Declining is part of it and is respected.
- Planning follows areas and assets, never people or leaving dates. Capturing knowledge does not mean assessing people.
How do you capture expert knowledge before someone retires?
Early, on the side and where the work happens. If you only schedule a handover meeting in the last month, you get what the experienced person thinks of in an hour — not what they have learned in thirty years. Most of it comes to mind while they work: at the machine, with the customer, looking at a drawing.
With Explicio they bring in exactly then what they would explain anyway — as a voice message, photo, video or short text via the messenger, mail or web chat the team already uses. Explicio asks when something is missing, links what was said with manuals, drawings and maintenance reports, and records who said it and when.
The successor later asks in their own words and gets the answer with its source down to person and time. If something contradicts the manual, the contradiction is shown instead of one version quietly winning.
What is expert knowledge — and what does knowledge transfer mean?
Expert knowledge comes from doing. Someone who has run the same machine for years can hear when a bearing is about to fail; someone who has looked after a customer for years knows what they need at quarter end. Hardly anyone writes this down, because day to day it goes without saying.
Knowledge research distinguishes explicit knowledge, which is in documents, from tacit knowledge, which sits in people. Expert knowledge often lies in between: it can be explained when someone asks at the right moment. Knowledge transfer means passing it on so that others can work with it — in writing and with its origin.
What is in the manual — and what only she knows.
The manual stays important. But it describes how things should be — not how they really run after thirty years at exactly this machine.
- setpoints, maintenance intervals and inspection plans
- work instructions in the official order
- parts lists, drawings and wiring diagrams
- the contact point at the manufacturer
- why the machine starts up differently after a tool change
- which fault is harmless — and which is not
- which customer has which special arrangement
- whom to call at the supplier when it is urgent
Explicio puts what the manual lacks next to it and links the two — nobody changes the manual itself.
Six ways to pass on expert knowledge.
No method is wrong. They differ in how much they capture, what they cost the experienced person and whether the result can be found later.
When to start? A timeline for handing over an area.
The more months between start and handover, the more situations in which something gets explained. The plan follows the area, not a list of people.
- TWO TO THREE YEARS BEFORE01Name the areasWhich machines, customer relationships and processes depend on knowledge that is written down nowhere? This is decided with the experienced people, not about them.
- FROM THEN ON02Bring it in at workExplained when it happens: during a fault, a customer visit, a maintenance job. A few minutes on the side instead of a project of its own.
- IN THE FINAL YEAR03Let the successor askWhoever takes over asks their own questions. What stays open shows the gaps — now a meeting is worth it, about the open points rather than everything.
- AFTER THE FAREWELL04The knowledge stays findableAnswers keep naming their source. What becomes outdated is superseded and remains visible as an earlier version.
Four steps that happen on the side.
No project of its own, no interview plan — the knowledge comes in during everyday work.
- STEP 1 · NAME THE AREAS01What it is about — not whomDecide which machines, processes and customer relationships matter first. Priorities are set by area and asset, never by person or year of leaving.
- STEP 2 · BRING IT IN AT WORK02Explain it when it happensThe experienced colleague sends a voice message from the shop floor, a photo of the nameplate, a short video of the move — through around 20 channels and in her own language.
- STEP 3 · EXPLICIO ASKS03Close the gaps while she is still thereIf something is missing — which variant, from which value, what happens otherwise —, Explicio asks. If she does not want to answer, Explicio remembers the refusal and does not ask again.
- STEP 4 · THE SUCCESSOR ASKS04In their own words, with the sourceWhoever takes over asks in the chat or by voice message and gets the answer with its source down to person and time — even years later.
A follow-up question nobody else asks.
A skilled worker brings in a knack, Explicio asks a follow-up question — and a year later the successor asks. An example: whether and how Explicio asks depends on the contribution.
On press 3, after a tool change, run two empty strokes first, otherwise the first part tears.
Does that apply to every tool on press 3 — or only to certain ones?
Only to the large deep-drawing tools. The small ones run straight away.
A year later, the successor: why do we run press 3 empty first after a change?
With the large deep-drawing tools, two empty strokes, otherwise the first part tears.
Source: voice message from the early shift, with person and dateWhen the owner hands over the business.
In a business succession, more leaves than one specialist's knowledge. Whoever built the business knows the history of every customer relationship, the arrangements with suppliers and the reasons behind prices, recipes and contracts — much of it never written down.
For buyers and successors, exactly this knowledge is part of the value: due diligence shows what is missing, and after the handover whatever was not passed on costs money. Tax and legal questions belong with the chamber of commerce, tax advisers and lawyers; this guide is only about the knowledge.
Checklist for handing over knowledge.
To tick off — whichever tool you work with.
- Named the areas, machines and customer relationships that depend on undocumented knowledge
- Asked the experienced colleagues whether and how they want to take part
- Involved the works council early
- Chosen a channel the team already uses
- Gathered existing manuals, drawings and reports
- Explanations come in during daily work, not only in meetings
- Open questions are asked while the person is still there
- The successor asks for themselves and reports what is missing
- Contradictions with the manual are resolved, not silently overwritten
- Agreed what happens to contributions after the person leaves
Capturing knowledge does not mean assessing people.
Capturing experience knowledge means working with people who will soon leave. That is why the limits are built in, not just promised.
- record what someone knows, and who it came from
- ask when something is missing — and accept a no
- link what was said with documents and maintenance reports
- assess anyone — neither a person's performance nor their knowledge
- keep lists by age or year of leaving
- set contributions against each other — no ranking, no competition
- take in anything nobody consciously brought in
What a works agreement should cover is on our page for works councils and data protection.
Situations where exactly this knowledge is at stake.
Three cases from manufacturing and energy supply — and a calculator that shows with your own numbers what it costs when this knowledge leaves.
What people often ask.
When should you start?
As early as possible, ideally years before the last working day. Knowledge comes up in everyday work, not at the push of a button — the more months in between, the more situations in which something gets explained.
What does the experienced person have to do?
Learn nothing new: they send what they would explain anyway as a voice message, photo, video or text through a channel they already use, and answer follow-up questions if they like. Explicio remembers a refusal.
Does the works council have to agree?
Explicio is a technical device within the meaning of § 87(1) no. 6 of the German Works Constitution Act — its introduction is subject to co-determination, even without any evaluation of people. The agreement stays short because much is already ruled out.
Is it evaluated who knows how much?
No. Explicio does not assess people and keeps no rankings — neither by knowledge nor by contributions. Priorities are set by area and asset, never by person or age.
Does it work without the cloud?
Yes. The Explicio Box sits in your network and is operated by us; language model, image understanding and search run locally there. Alternatively, Explicio runs in the EU cloud on hardware operated by Explicio in Germany.
What remains after she has left?
Everything she brought in — as a source in every answer. Her account can be closed, the knowledge stays with the company. If she asks for her contributions to be erased, Explicio removes them completely.
On method, duration and succession.
What is the difference between knowledge transfer and knowledge management?
Knowledge management is the framework: how a company collects, organises and keeps knowledge findable. Knowledge transfer is the part where knowledge passes from one person to others — before retirement, that is the part that matters most.
How long does knowledge transfer before retirement take?
As long as the area offers situations in which something gets explained — usually several months to years. Because bringing it in happens on the side, the long period costs little; a single meeting shortly before the farewell does not replace it.
Does this also help with business succession?
Yes. Arrangements, the reasons behind prices and contracts and the history of customer relationships can be brought in the same way and later queried with a source. Tax and legal questions belong with the chamber of commerce, tax advisers or lawyers.
Bring in knowledge first. Then decide.
After a short conversation we set up your trial space. Then bring in a voice message from your business — and see how Explicio asks follow-up questions. The 30 days only start after that.
- Term
- 30 days from the first knowledge
- Calculator
- knowledge risk with your numbers
- Works council
- what an agreement covers