Client Knowledge Handoff (Handoff)

Client Knowledge Handoff (Handoff)

1. 01

   Freeze the outgoing account's working documents 48 hours before the transition meeting

   Lock editing on the live wiki space so the departing lead cannot keep patching pages mid-handoff. Snapshot the current state so the incoming team reads one version, not three.

2. 02

   Separate durable knowledge from campaign ephemera before anything migrates

   Client brand rules, approval chains, and recurring deliverable specs belong in the permanent knowledge base. Draft copy, one-off briefs, and expired campaign assets get archived or deleted.

3. 03

   Map every recurring deliverable to its source document and named owner

   For each retainer line item, record where the template lives, who last updated it, and what triggers a refresh. A wiki platform with unified search such as Slab or Nuclino makes this mapping searchable rather than tribal.

4. 04

   Run a live retrieval test with the incoming team, not a read-through

   Ask the new owner to answer five real client questions using only the knowledge base. Every question they cannot answer in under two minutes marks a gap to close before the handoff is signed off.

5. 05

   Record a 10-minute walkthrough for each non-obvious process

   Written steps miss the judgment calls. A short screen recording attached to the relevant page captures why a deliverable is structured a certain way, which matters when the client asks six months later.

6. 06

   Assign a single knowledge owner per client space and name a backup

   Shared ownership means no ownership. One person is accountable for accuracy, with a named deputy so vacation or turnover does not stall updates.

7. 07

   Schedule a 30-day post-handoff review to catch drift

   Tools that monitor connected sources, such as Slite or GitBook, can flag pages that stopped matching reality. Use that signal to route corrections to the named owner instead of letting stale pages accumulate.