A resignation starts two clocks. One counts down the formalities: reference letter, deregistrations, laptop, access rights. The other counts something that appears on no form, namely the days on which the person’s knowledge is still in the building. Almost every organisation has the first clock under control. The second usually runs out unnoticed.
This page covers both: a process from resignation to the last day, a checklist by area, and a plan for the knowledge handover that fits into the weeks that remain.
A note up front: this checklist is not legal advice. The legal references below follow German employment law, and notice periods and obligations can differ by contract, collective agreement, works agreement or country.
What does offboarding include?
Offboarding is the orderly exit of a person from the organisation. It has four areas:
- HR and payroll: confirm the resignation, clarify notice and remaining leave, reference letter, employment documents, deregistrations.
- IT and equipment: return devices, keys and badges, revoke access, settle mailbox and files.
- Team and customers: who takes over what, who is told when, how the team says goodbye.
- Knowledge handover: what knowledge depends on this person, and how does it stay with the organisation?
The first three areas are routine. They can be ticked off, and if something is missing, it shows quickly: the laptop is not back, the reference letter gets chased. In the fourth area, a gap only shows when a case comes up that nobody can solve any more. Often months later.
The process: from resignation to the last day
In Germany, the basic statutory notice period is four weeks to the 15th or the end of a month (section 622 BGB). With remaining leave and overtime, often only two weeks are left in which the person is actually at work. The timeline below assumes this tight case. With longer notice periods, the phases stretch accordingly.
Days 1 to 3 after notice
- Confirm the resignation in writing and record the last working day.
- Clarify remaining leave and overtime: will they be taken or paid out?
- Manager and HR agree who coordinates the offboarding.
- The manager notes the matters on which the person is regularly asked. This list is the starting point of the knowledge handover.
Week 1
- Talk to the leaver about the handover: what they consider critical themselves, and how much time they have for it.
- Compare and prioritise the list of matters: rare, costly cases first.
- Hold the first knowledge conversations.
- Tell the team and, where needed, customers who the contact person will be.
Week 2 to the last day
- Hold the remaining knowledge conversations and have the results reviewed and approved by a named person.
- Hand over ongoing work and set up cover.
- Prepare the reference letter and hold the exit interview.
- On the last day: equipment back, access revoked, farewell.
After the exit
- Hand over or send the employment documents.
- After a few weeks, check: which questions have come up since that the captured knowledge does not answer?
The checklist by area
HR and payroll
- Resignation confirmed in writing, last working day recorded
- Remaining leave and overtime clarified (taken or paid out)
- Reference letter prepared; in Germany employees are entitled to a written reference under section 109 GewO
- Certificate of leave for the current year issued (section 6(2) BUrlG)
- Deregistration from social insurance initiated
- Final payslip and annual tax statement prepared
- Company pension, company car, loans or advances settled
- Exit interview held
IT and equipment
- Laptop, smartphone and other accessories returned
- Keys, badge and access cards returned
- Access to systems, cloud services and customer portals revoked as of the last day
- Out-of-office message and mailbox forwarding set up
- Files moved from personal drives to shared storage
- Licences and subscriptions in the person’s name reviewed and reassigned
Team and customers
- Cover and successor for ongoing work defined
- Team informed about the departure and new responsibilities
- Customers, suppliers and partners informed, new contacts named
- The person’s open commitments and appointments handed over
- Farewell planned
Knowledge handover
- List of matters on which the person is regularly asked, including outside their formal responsibilities
- Rare, costly cases marked (less than once a quarter, but expensive when they go wrong)
- A conversation planned and held for each marked case
- Results reviewed and approved by a named person
- Captured knowledge stored where the successor will find it, with a date for the next review
- Contacts only this person knows made known to the team
Planning the knowledge handover: who, what, when
Many offboarding checklists have exactly one line about knowledge: “Handover completed”. A tick that says nothing about what was handed over or whether anyone can find it again. Three questions turn it into a plan.
What needs to be secured? Not everything. What happens every week, a successor learns on the job, slowly but reliably. The risky matters are the ones that happen rarely and then get expensive: the exception for the key account, restarting the line after a stoppage, the audit that only comes round once a year. A good question for the team: on which matters is this person asked even though they are not formally responsible?
Who is involved? The leaver provides the knowledge. The manager decides which matters come first. And a named person reviews and approves the result. Without that review, you end up with an archive in which nobody can later tell what still applies.
When does it happen? In the first week after notice, not the last. In the last week there is no time for follow-up questions, and the decisive cases do not come to mind on demand.
The format decides whether the handover actually happens. Ask someone to write a manual in their last weeks and usually no manual gets written. A conversation in which someone asks about concrete cases and follows up wherever the answer stays vague costs the person far less time. An AI-assisted interview takes around 30 minutes; three to five of them fit even into two remaining weeks. How such an interview works is described in the post on AI expert interviews.
Why the successor does not need to be in place for this, and which objections almost always come up in these weeks, is covered in more depth in the post on knowledge transfer in offboarding.
Common offboarding mistakes
- The knowledge handover starts too late. Wait until the last week and you get file locations and responsibilities, but not the exceptions.
- Handover means handing over to one person. If there is no successor yet, everyone waits until it is too late. Better: store the knowledge in verified form so that any future successor finds it.
- The handover document stays empty. An empty template titled “Handover” is a chore without instructions. Targeted questions about concrete cases achieve more.
- Nobody reviews the result. After a year, unreviewed knowledge can no longer be told apart from outdated knowledge.
- Access stays open. Accounts that remain active after the exit are a security risk. Revoking access as of the last day belongs on every list.
- The farewell gets skipped. How an organisation treats leavers is seen by the whole team. A proper farewell is also a message to those who stay.
When a key person leaves
For most departures, the checklist is enough. For some it is not: when the person handles matters nobody else can. How to recognise such single points of knowledge, and why a handover often only moves them elsewhere, is described in the post on single points of knowledge.
How knowledge capture works when a departure is already set and only weeks remain is shown on the page on acute knowledge retention. How organisations capture expertise without a specific trigger is described on the page capture knowledge.
