Someone left. Half the knowledge walked out with them.
Your senior engineer gave two weeks’ notice. They’re the only person who understands three client environments inside out.
You have 10 working days to extract knowledge that took two years to accumulate. Most MSPs spend those days on access revocation and equipment returns. The knowledge transfer gets squeezed into one rushed afternoon.
The scenario:
You want to build an offboarding knowledge transfer process that captures critical information before an employee leaves.
The prompt:
You’re creating a knowledge transfer checklist for departing engineers.
Context: [paste the role and key responsibilities of the departing team member]
Build a process that covers:
Day 1–2: Identify all client environments where they’re the primary or sole contact
Day 3–5: Recorded knowledge transfer sessions (30 min each, structured Q&A)
Day 6–8: Shadow sessions where the replacement handles tickets with the departing engineer watching
Day 9–10: Documentation review and gap identification
Include: interview questions for each session, documentation template, handoff sign-off checklist.
Flag anything that’s only in their head and not written down.