PlaybookPrompts

Design a knowledge transfer plan when someone is leaving

Productivity & Planning offboardingplanningteam-management

When a team member leaves, institutional knowledge walks out with them unless transfer is planned deliberately. This prompt builds a structured handoff before the last day arrives.

Prompt
You are my chief of staff helping me design a knowledge transfer plan for a departing team member. Here is the departing person's role: {{DEPARTING_ROLE}}. Here is the number of weeks until their last day: {{WEEKS_REMAINING}}. Here are the main areas of work they own: {{AREAS_OF_OWNERSHIP}}. Here is who will absorb their responsibilities (if known): {{SUCCESSORS_OR_INTERIM}}. Here are any known gaps or risks: {{KNOWN_GAPS}}.

1. Map every area of ownership into three categories: (a) must transfer completely before last day, (b) can be documented and self-serve after they leave, and (c) can be rebuilt from scratch if needed.
2. For the must-transfer category, create a week-by-week schedule that fits within {{WEEKS_REMAINING}} weeks. Each week should have a specific handoff goal, not just 'continue meetings'.
3. Identify the five documents or artifacts that most urgently need to be created or updated. For each, write a one-sentence brief the departing person can use to scope the work.
4. Flag any single points of failure — relationships, access credentials, tribal knowledge — that have no current backup and need immediate attention.
5. Draft a 15-minute weekly check-in agenda I can use with the departing person to track progress against the plan.

If {{WEEKS_REMAINING}} is fewer than two weeks, restructure the output as a triage plan rather than a full transfer — not everything will be possible.
Variables to fill in
  • {{DEPARTING_ROLE}}
  • {{WEEKS_REMAINING}}
  • {{AREAS_OF_OWNERSHIP}}
  • {{SUCCESSORS_OR_INTERIM}}
  • {{KNOWN_GAPS}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{DEPARTING_ROLE}}{{WEEKS_REMAINING}}{{AREAS_OF_OWNERSHIP}}{{SUCCESSORS_OR_INTERIM}}{{KNOWN_GAPS}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.