Offboarding knowledge transfer: the template and the AI alternative
The template is below and it is the one worth running in a notice period. Read the middle column closely and it doubles as a list of everything that should already have been written down.
Someone has resigned and there are about ten working days. The instinct is to ask for a document covering everything they know, which produces forty pages nobody reads. The better use of the time is narrow and dated: collect the things that will break on a specific day if they are not collected, and let the rest go.
The offboarding knowledge transfer template
Eight rows, in priority order. The third column is the part that gets skipped and the part that decides whether any of this is usable in month three: each item needs a shape, not a paragraph.
| What to collect | Where it actually lives now | The form to collect it in |
|---|---|---|
| Recurring obligations with dates | Executed agreements, clause by clause | Obligation, the event that starts the clock, notice window, next date due |
| Commitments made to people outside the company | Sent mail, and the memory of calls | One line each: to whom, what was promised, by when, current status |
| Commitments owed back to you | Received mail, meeting notes that may not exist | One line each: who owes it, promised date, when it was last chased |
| Decisions of the last twelve months and their reasons | Threads, calls, and one person's head | Decision, date, the option not taken, and why it was not taken |
| Live external relationships | Nowhere at all | Per counterparty: who actually replies, the history, last contact, current temperature |
| In-flight documents and their true version | A drive holding several plausible versions | Which file is current, and what inside it is still contested |
| Numbers in dispute | Finance mail and invoice threads | The number, the source it came from, and what exactly is contested |
| The next ninety days of dates | A calendar plus recall | A dated list, each line saying what breaks downstream if it slips |
Two omissions are deliberate. Process documentation is not on the list, because it is the part that is usually already written and rarely the part that hurts. Account and system access is not on it either, because that is a revocation task for whoever runs your IT rather than knowledge, and mixing the two is how the knowledge half ends up as the row nobody finished.
How to run it in the days you have
- Days one and two: the dated rows. Obligations, then the ninety day list. These are the items with a clock, and a clock does not care that somebody left.
- Days three to five: both commitment rows. Work from sent mail rather than from memory. Memory produces the impressive promises and omits the small ones, which are the ones that break.
- The second week: relationships and reasons. Best done as a conversation with the successor rather than a form, one counterparty at a time, and captured in writing the same day.
- Do not attempt completeness. A finished list of the eight rows above beats an unfinished attempt at everything, and everything was never available in ten days anyway.
Why the template is triage
Look down the middle column again. Almost every row already exists in written form somewhere: in mail, in the executed agreement, in an invoice thread. The exceptions are the relationship row and the reasons row, which is exactly why those two are the hardest and the most valuable. What the template really asks is for one person, in their last week, to act as an indexing service for two years of their own correspondence, from memory, while also finishing their handover and looking for their next job.
That is why the output quality of an exit checklist is not a discipline problem to be solved with a better form. It is a timing problem. The material was collectable every week for two years, cheaply, in small pieces, and the entire cost was moved to the worst possible fortnight. The full version of that argument, and what a departure actually costs, is preserving institutional knowledge when people leave.
The alternative, and where it stops
The alternative is not a better checklist. It is that six of those eight rows are a query rather than an exercise, because a record was being written from the correspondence all along: obligations with their trigger events, commitments in both directions with dates, decisions with the reason attached, the current version of the document and what is contested in it. That record is produced by institutional knowledge capture running as an ordinary part of the week, and what it accumulates into is AI institutional memory. The offboarding conversation then covers the two rows that were always human, which is close to the ideal outcome and nothing like the fortnight described above.
Where it stops is worth being blunt about. It is installed for a single person, so it covers the correspondence that reached that one account and nothing beyond it. It does nothing about access revocation, badges, equipment or sample custody, which stay with IT and the lab. It is not a validated system, so controlled documents and anything under change control remain in the systems qualified to hold them. And it cannot produce what never existed in writing anywhere: the exact boundary between what a machine can and cannot carry out of a departing person's work is AI for knowledge transfer.
One drug development specific note, because it changes the priority order above. In a biotech most of the dated rows are owed to organizations outside the building: a contract research organization's report deadline, a notice period in a collaboration agreement, a manufacturing slot with a booking window, a regulatory clock. Those are the rows where the cost of a gap is measured in program months rather than in awkwardness, which is why they sit at the top of the template and why the ninety day list is the one thing not to leave until the final Friday. The concept level version of what is moving in all of this is institutional knowledge transfer.
Six of those eight rows, already standing
A working app keeps them current out of ordinary correspondence: obligations with the event that starts the clock, promises in both directions with their dates, decisions with the option not taken written beside them. Have a look at the demo, then decide whether the notice period was ever the right fortnight for this work.
See the demo