Knowledge transfer when someone leaves

When someone leaves, their knowledge goes with them—unless you capture it. Handover gives you a checklist per role, space to record a Loom or notes per responsibility, and one place for the next person. So “how did they do that?” has an answer.

Start a handover

The problem

Tribal knowledge — passwords, processes, and “how we actually do X” live in one person’s head. When they go, it goes.
Ad hoc handovers — a few docs, a call, and hope. The new person spends weeks reconstructing what the last person knew.
Offboard tells you to revoke access — Handover tells you what to pass on. Both matter; they’re different problems.

Checklist by role

Responsibilities, logins, key contacts. Clone for this person. Check off as you record.

Record per item

Loom, doc, or written notes. “How to run the report,” “who to call for X.” One link per topic.

One link for the successor

Share one handover pack. They see everything you captured. Onboard faster, fewer repeats.

Don’t let knowledge walk out the door

Join teams that turned “where’s that again?” into “it’s in the handover.”

Start a handover