Knowledge lost when employees leave: a transfer plan and a handover template

Tracebrain is company memory built from every app and messenger your team uses, starting with Telegram and WhatsApp: it reads the conversations your team already has, with clients and with each other, and keeps what was decided, promised and paid, by client and by project, so the history stays with the company when people leave.

This guide is for the weeks after someone hands in their notice. It covers which knowledge actually leaves, a two-week knowledge transfer plan, a handover sheet you can download and fill in, and what to change so the next handover is shorter.

Which knowledge leaves with a person

Most teams prepare for the wrong loss. The code is in the repository, the contracts are in the drive and the tickets are in the tracker. Those stay. What leaves is the layer between them:

• What was agreed, and when. The discount offered on a call, the deadline moved in a chat, the extra page agreed for a fixed price. The contract says one thing; the last three weeks of messages say what the client now expects.
• What is still open. Promises the person made and has not kept, and promises the client made and has not kept. Both are invisible until a date passes.
• Who to ask. The bookkeeper who actually pays the invoices, the developer on the client's side who answers at night. Names that never reached a CRM.
• Why. Why a client gets weekly reports instead of monthly ones. Why a feature was dropped. Without the reason, the new owner repeats an argument that was settled.

All four have the same home: the person's direct chats. In many teams, and in most agencies, a client talks to one account lead in a Telegram or WhatsApp chat that only those two people can read. When the account lead leaves, their account leaves with them, and so does every agreement made in it.

A knowledge transfer plan for the notice period

Start in the first week of the notice, not the last. The person leaving still remembers the context, and clients can be introduced while they can still be asked.

Week one: list and assign

1. List every client and project the person owns. Go through their chats, their calendar and their open tickets, not only the CRM. A client who only ever messages them is easy to miss.
2. Name a new owner for each one. One person per row. "The team" is not an owner.
3. Fill in one row of the handover sheet per client (below). The person leaving writes it; the new owner reads it the same day and asks what is unclear.
4. Mark what is open on both sides. What we promised and what they promised, each with a date. These are the rows that cause trouble in the first month.

Week two: hand over and check

1. Hold one short handover meeting per client, with the sheet row on the screen. Fifteen minutes is enough when the row was written properly.
2. Introduce the new owner in the chat the client already uses. A message from the person leaving ("from Monday Sofia leads your project; she has the full picture") keeps the client from writing to an account nobody reads.
3. Move access, not passwords. Change who owns the logins in the team's password manager, and ask clients to add the new owner to accounts they own.
4. Check with the client. Ask them what they think is open. If their answer differs from the sheet, the sheet was wrong, and now is the cheap time to find out.
5. Keep the sheet. It is the first page the next owner reads, too.

The handover template

We made a handover sheet you can copy: download the knowledge transfer template (a CSV file that opens in Google Sheets, Excel or Numbers). It has one row per client or project, filled with two invented examples you can delete. Its columns are:

• Client or project, Leaving owner and New owner.
• What was agreed (with the date). The terms that are true now, with the day they were settled, so nobody has to scroll back to find them.
• We promised and They promised, the two directions an open promise goes in, and Due.
• Where it was said: the Telegram chat, the WhatsApp group, the email thread. The new owner needs to know where to look and where to reply.
• People to introduce, with what each one does.
• Access to hand over. Where the access lives and who can grant it. Never the password itself.
• Status and Checked with the client, so a row is closed only after the client has confirmed it.

The sheet works because it forces the question that chat history never answers on its own: of everything that was said, what is true now.

Why the sheet is still hard to fill in

The template makes the handover structured. It does not make it accurate. Every cell depends on the person leaving remembering what they agreed, with whom and when, across weeks of conversations in two or three messengers. A promise made in passing at nine in the evening is exactly the one that is forgotten, and it is exactly the one the client remembers.

The fix is not a longer template. It is having that record before anyone resigns.

What company memory keeps

Take the first row of the template. An invented account lead, Taras, ran a website project for a bakery chain. In one week the owner, Iryna, asked him in a direct Telegram chat for a wholesale order page, agreed to €600, and promised a price list by Friday. Taras promised the page for the Monday after.

With Tracebrain connected, that week did not stay in the chat. Each night the day's conversations became a note of what was decided, promised and paid. Iryna's page holds the price and the date she agreed it. The price list she owes and the page Taras owes are tasks with the day they were promised. The bakery project has a note of its own with its people and its decisions. When Taras hands in his notice, his handover row is already written; he checks it rather than reconstructs it.

That is the difference between a handover and a recovery. The sheet asks the person leaving to remember. A memory built from the conversations asks them only to confirm.

What Tracebrain does today, and what it does not

Each person connects their own Telegram, the way the desktop app signs in, and their WhatsApp as a linked device. Both are read-only. Their one-to-one chats become a profile per person, a nightly review and a task list, and projects get notes of their own. Claude, ChatGPT or any MCP client can ask that memory what was promised to a client through the MCP server, and everything downloads at any time as Markdown files.

Said plainly, three limits matter for a handover:

• Today each person's memory is their own. A team workspace, where every member's connected accounts write into one shared memory that stays when someone leaves, is in early access. Until then, the person leaving uses their memory to write the handover sheet.
• Group chats are not read yet. Agreements made in a large group still need the group's own search, and the Telegram knowledge base guide says how to use it.
• It reads Telegram and WhatsApp. Email, Slack and calls are on the roadmap, not live, so a handover that lives there still needs the sheet.

Why most company brains miss these chats in the first place is argued in a company brain for teams that never moved to Slack, and the company memory page compares the company brains by the apps they read. Tracebrain has a free trial; the pricing page has the details.