A resignation has come in, and alongside filling the position, the question soon arises how this person's knowledge stays in the company: how to invoice the special customer who has had custom terms since 2019, why the machine in Building 2 gets a different startup procedure on Mondays, where the login credentials for the supplier portal are kept and whom to call at customs when a shipment gets stuck.
During the notice period, a large part of this can be secured if you plan the weeks well. This guide shows what is realistically achievable in the remaining time, how a knowledge transfer plan for the notice period looks week by week, and gives you a handover checklist and interview questions to copy. How to spread knowledge across several people before the next resignation is covered in the guide on implementing knowledge management.
The notice period: how much time the handover has
Depending on the country, tenure and contract, you typically have somewhere between four weeks and a few months before the person leaves. In Germany, for example, the statutory baseline when an employee resigns is four weeks to the 15th or to the end of a calendar month (Section 622 (1) BGB), and many employment contracts and collective agreements set longer periods.
Only part of that time is available for the handover. Remaining vacation days get used, day-to-day business keeps running, and sometimes sick days or garden leave come on top. Out of an eight-week notice period, depending on remaining leave, you often get only two to three weeks in which knowledge can actually be handed over.
It also helps to plan for the fact that someone who has mentally moved on to a new employer puts less energy into detailed manuals. That is entirely human, and a well-prepared, shared plan makes it easier for both sides.
Knowledge loss after a resignation: what is achievable during the notice period
A clear view of what is achievable helps you use the weeks well.
What works
- Documenting the most important processes, namely the ones nobody else in the company masters
- Handing over access and tools: portals, licenses, admin rights, shared credentials (IT resets personal passwords instead of passing them on)
- Passing on contacts: who is the right person to talk to at customer X, at supplier Y?
- Handing over work in progress: open projects, half-finished quotes, verbal agreements with customers
- Training a successor, if one is already on board, ideally side by side and along an onboarding plan
What needs more time
A large part of tacit knowledge can hardly be passed on completely in a few weeks. Fifteen years of experience, such as which customer gets nervous without a reply within a day, which part is worth double-checking and which Excel sheet is the current one, does not end up in a handover document. Often the person does not even know that they know it, because it has long become second nature to them.
A handover document answers the questions the writer considers important, and three months later the successor often has quite different ones. So focus on what matters most and set clear priorities.
The knowledge transfer plan, week by week
Let us assume you have four effective weeks. Here is one way to divide them:
Week 1: Start with a map
Sit down with the person, an hour is enough to start, and make a list together: Which tasks do they handle regularly? Which ones rarely but with high importance, such as year-end closing prep, maintenance intervals or audits? Which tasks would quickly stall without them?
Sort that list by a single criterion: Can anyone else in the company do this? Everything a colleague also masters drops out. What remains is the risk list, as a rough guide five to ten items. For those items, pick the matching handover format from the knowledge transfer methods.
In parallel, sort out access: which systems, passwords and admin rights are tied to this person? This is quickly done and saves a lot of effort after the last working day.
Week 2: Capturing the critical processes in conversation
Work through the risk list item by item. Ideally the person demonstrates the process once, a colleague or the successor watches and asks questions, and someone captures the result, with screenshots of the key screens and notes on the exceptions ("if the customer is from Austria, then...").
Demonstrating brings out the steps that run on autopilot in someone's head. Sentences like "Oh right, first you have to quickly check the other list" almost always come up while showing and rarely while writing.
Week 3: Work in progress and relationships
Now for the open items: Which projects are running? What has been promised to customers verbally? Where are there agreements that are not written down anywhere, such as the discount the boss promised on the phone or the later payment terms tolerated for a long-standing customer?
For key customers and suppliers, a joint handover email or a short three-way phone call is worth it. It takes about twenty minutes per contact and gives the successor a good start in the relationship.
Week 4: Test run and closing the gaps
A very helpful exercise is a test day: the departing employee is "unavailable" for one day, and the successor or the team works with what has been documented. Every question that comes up points to a gap, and you use the final days to close exactly those gaps together.
It takes a little courage, and it shows reliably whether the handover holds up.
Handover checklist for departing employees
The following checklist sums up the weekly plan. Copy it into your ticketing or document system and tick it off together with the departing employee. The order follows the four weeks.
Handover checklist for departing employees
Employee: ______ Last working day: ______
Successor / deputy: ______ Responsible for the handover: ______
ACCESS AND TOOLS (week 1)
[ ] All systems, portals and licenses the person has access to listed
[ ] Admin rights, certificates and powers of attorney transferred (bank, authorities, suppliers)
[ ] Shared inboxes, forwarding rules and out-of-office message sorted out
[ ] Storage locations clarified: files, templates, personal spreadsheets
TASKS AND PROCESSES (weeks 1 and 2)
[ ] Task list created: regular / rare but critical
[ ] Risk list: what can nobody else in the company do? (rough guide: 5 to 10 items)
[ ] Each item on the risk list demonstrated once, written up, screenshots taken
[ ] Special cases and exceptions noted (customers, suppliers, systems)
[ ] Deadlines and recurring dates for the next 12 months recorded
WORK IN PROGRESS AND CONTACTS (week 3)
[ ] Open projects, quotes, complaints with status and next step
[ ] Verbal commitments and agreements with customers and suppliers written down
[ ] Key contacts per customer, supplier, service provider
[ ] Handover email or three-way call for key contacts
TEST AND WRAP-UP (week 4)
[ ] Test day: successor works without the person, every question noted as a gap
[ ] Gaps closed, documents filed in one fixed place
[ ] Onboarding plan for the successor in place
For the successor, the onboarding plan is also available as an Excel template to download.
Why structured interviews save more than "just write everything down"
Many companies ask the departing person to write everything down before they go. The result is usually a tidy document that describes the obvious steps well, while the finer exceptions are missing.
This has to do with how knowledge is stored in the head. What you do every day, you consider self-evident, so hardly anyone writes down that "of course you only release the order after quickly checking with Hanne". For the successor, that very sentence is valuable.
Good questions bring such details to light:
- "Walk me through a perfectly normal Tuesday."
- "What was the last thing that went wrong, and how did you notice it was going wrong?"
- "If you were on vacation for three weeks: what would pile up? Who would call you, and about what?"
- "At which step do you deviate from the official procedure, and why?"
A conversation built on questions like these often brings out more in one hour than days of documenting alone at a desk. The person being interviewed does not need to know in advance what is important, because the questions lead them there.
Software solutions now build on this principle as well. At wissa.ai, an AI conducts these structured interviews via chat, in conversations of around 15 to 20 minutes, and turns them into searchable process documentation that also shows where two people describe the same process differently. If someone mentions "Max actually handles that part," wissa.ai suggests inviting Max to the next interview, and you approve the invitation. In an acute resignation this works quickly, and it helps even more when you start earlier. Try one interview for free
The better answer: secure knowledge before anyone resigns
Everything in this article helps when time is short. Things become more relaxed when knowledge has already been shared beforehand, because what has grown over fifteen years is hard to fit into four weeks.
Breaking up a knowledge silo while everyone is still around is much easier than any handover under time pressure. That includes moving knowledge from shouts across the hallway into a documented process and keeping the documentation current when workflows change.
The way there is unspectacular: collect knowledge regularly while everyone is still around, in short conversations that fit into the working day. If you know which processes depend on which person (keyword: bus factor), you can meet the next resignation calmly. Then the notice period becomes what it should be: an orderly handover at a relaxed pace. For key roles with a long lead time, such as an upcoming retirement, succession planning spreads the transfer over many months.
If you would like to approach this systematically, wissa.ai is happy to help. The AI interviews your employees in short conversations and later checks back with them on whether workflows are still accurate. That keeps your process documentation current, every statement with a source and every change traceable. You can sign up right away, a free trial package to start with (10 credits, once per company, terms) usually covers a first interview, and interviewees don't need an account of their own. Try one interview for free
Conclusion
When an employee resigns, knowledge loss can be limited well: secure access, build a risk list of the five to ten items nobody else masters, have those items demonstrated, hand over work in progress and contacts, and finish with a test day without the person. The handover checklist above covers this in four weeks. You achieve even more by collecting knowledge regularly while everyone is still around, because then the next resignation becomes an orderly handover.
FAQ
Can I require an employee to document their knowledge before leaving?
In Germany, a proper handover is generally part of an employee's work duties (Section 611a BGB) up to the last working day, and the employer can assign handover and documentation tasks under its right to give instructions (Section 106 GewO). Check the details of an individual case with employment law advice. In everyday practice, the working relationship matters most: someone who leaves on good terms and experiences the handover period as appreciative passes on far more than the bare minimum.
What about knowledge when the employee is put on garden leave?
Under an irrevocable release from work, as with a German unwiderrufliche Freistellung, the duty to work ends when the leave begins, so any handover after that point is voluntary. Other garden leave arrangements may still let you ask for specific tasks, so check what yours says. Either way, schedule the most important handover sessions before the leave starts where possible, or set them out in the garden leave agreement. Many employees are still glad to help if the separation is fair. Priority then goes to access credentials, work in progress and a structured handover conversation covering the most critical processes.
Is two weeks of overlap between successor and predecessor enough?
Two weeks side by side are very valuable, above all for the situations that actually come up during that time. The month-end close, the escalation with the major account or the special case in shipping may not fall into those two weeks, though. So supplement the overlap with structured conversations about the rare, critical cases.
How do I identify which knowledge is truly critical?
Ask one simple question per task: could someone else in the company take this over tomorrow without calling the person? If not, the task goes on the risk list. As a rough guide, five to ten critical items remain per person, and that is where you focus the available time.
What if the notice period is already half over?
Then shorten the weekly plan: secure access (one day), create the risk list (one hour), and for each critical process hold one session in which the person demonstrates the workflow while someone takes notes and screenshots. That way you close the most important gaps even in a short time.
Sources
- Section 622 BGB (German Civil Code, notice periods for employment relationships): statutory baseline of four weeks to the 15th or to the end of a calendar month, with longer periods for dismissals by the employer depending on length of service.
- Section 611a BGB (employment contract): the obligation to perform work under instruction - the basis for the handover as part of an employee's duties.
- Section 106 GewO (German Trade Regulation Act, right to give instructions): the employer specifies the content, place and time of work, as far as the contract, collective agreement or works agreement do not fix them.
- Section 7(4) of the German Federal Leave Act (BUrlG): leave is only paid out if it can no longer be granted because the employment relationship ends.