When Someone Leaves: Moving Knowledge from the Person to the Company

The staff departure process: portfolio handover, revoking access, transferring open work, customer communication and continuity.

What a company will lose when someone leaves is not decided on the day they go — it is decided months earlier. Only one thing determines it: was what that person knew held in the system, or in their head?

Not the leaving day, but the way of working

The most effective way to improve handover is not to intervene at the moment of departure. If the knowledge is already in the system, handover becomes a formality; if it is not, no handover meeting is enough. The daily habits that provide it:

  • Notes after conversations: what was discussed and what was promised. Knowledge left to memory leaves with the person.
  • Recorded next steps: every open record needs a task and a date.
  • Customer communication through the system: a relationship running through a personal phone cannot be handed over.
  • A written portfolio: “who looks after this customer” belongs on the record, not in team memory.

The departure checklist

  1. List the portfolio. Every assigned customer, open opportunity, ticket and task in one report.
  2. Transfer the critical items first. Recent quotes, open complaints, contracts approaching renewal — these must not wait for the last day.
  3. Ask for handover notes. A few sentences per key customer: the state of the relationship, sensitive topics, who decides. This is the most valuable output of a handover.
  4. Introduce the new owner to the customer. A short message from the departing person lands far better than a silent switch.
  5. Reassign open tasks. A task left without an owner disappears within weeks.
  6. Revoke access. On the last day, at a stated time. An account left open creates both a security and an accountability problem.

The forgotten parts of revoking access

Disabling the account is not enough. Commonly missed:

  • Mobile app sessions and stored tokens.
  • The extension and call forwarding — left in place, customers call into a void.
  • Access to shared mailboxes and WhatsApp lines.
  • Exported files: spreadsheets pulled in the final weeks may already have left the company, which is why exports need to be logged.
  • Automation rules: rules assigning work to the departing person must be updated, or records fall into a gap.

Deactivate rather than delete

Deleting a departing person’s account also breaks the signature on historical records: who did what and when becomes untraceable. The right action is deactivation — login closes, history remains. Showing them as “former staff” in reports keeps historical comparisons correct.

Measuring single-person dependency

The real risk is visible before anyone leaves. Two simple indicators are enough:

  • Portfolio concentration: how many of your largest customers depend on one person?
  • Areas with no backup: if only one person holds the records and knowledge for a topic, that area is single-person dependent.

Track those two regularly and the handover problem is solved months in advance rather than on the leaving day.

Frequently asked questions

Should we tell customers someone has left?

You need to introduce the new owner; you do not need to explain why. “X will be looking after you from now on” is enough and preserves continuity.

How much time should handover take?

It depends on portfolio size, but it must not be left to the last day. Graduated handover from the moment of notice beats a single handover meeting.

Are a departing person’s notes personal data?

Notes about customers are company records and stay. Records such as their own performance reviews have a different status; ask your legal adviser about retention periods.

Next step: to see portfolio handover and access management, request a demo.