thinkhard.SI

Prompt repository Managers & leads

Capture what a departing colleague knows before their last day

Someone with years of know-how is leaving, and you want an interview plan and a handover document that keep what only they know.

Registry no.
MGT-058
Collection
Managers & leads
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
7

Managers & leadsAny chat

The prompt

Score 10 of 10, Excellent

Use it when Someone with years of know-how is leaving, and you want an interview plan and a handover document that keep what only they know.

  • {{colleague_role}}
  • {{last_day}}
  • {{successor}}
  • {{responsibilities}}
  • {{existing_docs}}
  • {{time_available}}
  • {{context}}
Full prompt and why it works
Prompt
Help me capture what {{colleague_role}} knows before their last day on {{last_day}}, so that {{successor}} can run their work without calling them after they leave. Written handovers usually cover the documented work and miss what lives in someone's head: the exceptions, the workarounds, the people to call and the reasons behind odd-looking steps. I want to get those out in a few focused sessions while they are still here.

What they own (processes, systems, clients or suppliers, recurring tasks, reports):
"""
{{responsibilities}}
"""

What is already documented, and where: {{existing_docs}}
How much of their time I can book before they go: {{time_available}}
What I know about the departure (resignation, retirement, internal move, end of contract) and the mood around it: {{context}}

Produce, with a heading for each part:
1. A session plan: how many sessions and how long each is, which areas each covers, ordered by risk so the work most likely to break goes first.
2. Interview questions for each area, eight at most per area, aimed at what is not written down. For example: "What does this process look like when it goes wrong, and what do you do then?" or "Who do you call when the system does this, and why them?" Include requests to show rather than tell, such as walking through a task live while {{successor}} watches.
3. A handover document template for each responsibility, with the headings Purpose, How often, Steps, Exceptions and fixes, People and contacts (by role), Where things live, Warning signs.
4. A list of access and accounts to move to {{successor}} or a shared owner before the last day, by system name only. Never ask them to write passwords into the document.

Keep the tone respectful: this is about valuing what they know, not about checking up on them. Do not assume they will be reachable after they leave or that they owe more time than I can book. If my list of responsibilities looks incomplete, for example a task appears in the existing documents but not in my list, ask me about it before building the plan.

Variables

{{colleague_role}}
The person leaving, by role, for example "our office manager of 12 years".
{{last_day}}
Their last day, for example "Friday, August 29".
{{successor}}
Who takes over, by role, for example "the new operations coordinator".
{{responsibilities}}
Everything they own: processes, systems, clients or suppliers, recurring tasks and reports.
{{existing_docs}}
What is already written down and where, for example "a shared drive folder with old procedures".
{{time_available}}
How much of their time you can book, for example "six hours over the next two weeks".
{{context}}
Why they are leaving and the mood around it, for example "retiring, happy to help".

Why it works

  • What to make. The output is a session plan, questions per area and a handover template, which turns a vague handover into a few booked conversations.
  • An example. Sample questions aim at what goes wrong and who to call, the knowledge that written procedures usually miss.
  • If unsure. A responsibility that shows up in the documents but not in your list is raised with you before the plan is built.

How to use it

  1. Press Fill in blanks and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.
  4. When the answer comes back, check it before you use it. The Fact Check List lists every figure, quote and source in the answer worth checking, riskiest first.
Use it from code

Get this prompt as JSON from the free REST API, with your own text in the blanks, or let an AI assistant fetch it through the MCP server. No key.

curl -s https://thinkhard.si/api/v1/prompts/departing-colleague-knowledge-capture

With the MCP server added to Claude, ChatGPT, Cursor or VS Code, call get_prompt with {"prompt": "departing-colleague-knowledge-capture"}, or just ask for it by name.