Knowledge Transfer Interview Questions: The 42 to Ask

A knowledge transfer interview is a structured conversation with a departing employee about how their work actually gets done. It is not an exit interview. An exit interview asks why someone is leaving; a knowledge transfer interview asks what they know. Most companies run the first and skip the second, which is why the person replacing them starts from close to zero.

Below are 42 questions in six sections, built around the four kinds of knowledge that walk out of the door, and a short guide to running the session so people actually answer them.

Why the exit interview does not cover this

The two conversations have different purposes, different interviewers and different outputs, and collapsing them into one meeting produces neither.

An exit interview is a retention instrument. It exists to find patterns across many departures. A knowledge transfer interview is an operational instrument, and it exists to serve exactly one person: the successor. The questions have almost nothing in common.

The four kinds of knowledge that leave

Most handover documents capture the first category and miss the other three. That is the whole problem in one sentence.

Explicit knowledge is what is already written down somewhere. Process docs, logins, file locations. Easy to transfer and usually the only thing anyone bothers to transfer.

Procedural knowledge is how the work is actually sequenced, including the shortcuts and workarounds that never made it into the process doc because they contradict it.

Relational knowledge is who to call. Which colleague actually approves the thing that the org chart says someone else approves. Which supplier answers on WhatsApp and which needs a formal email.

Judgment is the expensive one. When to escalate, which rules bend, what the last three people who tried this got wrong. It is the hardest to elicit because the person holding it does not experience it as knowledge. They experience it as obvious.

The most-cited figure in this field puts it at 42% of institutional knowledge being unique to the individual who holds it, existing nowhere else in the organisation. That comes from a 2018 YouGov survey of 1,001 US knowledge workers commissioned by Panopto, a video platform vendor, so treat it as an order of magnitude rather than a precise number. Nobody has re-measured that share since, which is telling in itself. That share is what the questions below are trying to reach.

The 42 questions

Opening: mapping the role (5 questions)

Start wide. These calibrate everything after them and are easy to answer, which matters for getting the conversation moving.

1. If you had to explain your job to a competent stranger in three sentences, what would you say?

2. What does a normal week look like, hour by hour, in rough proportions?

3. Which parts of your job would surprise someone reading your job description?

4. What percentage of your week is planned work versus things that come to you?

5. If you disappeared tomorrow with no handover, what breaks first? What breaks in a month?

Procedural: how the work actually happens (10 questions)

6. Walk me through your most frequent task from trigger to completion.

7. Where in that process do you deviate from the documented procedure, and why?

8. What is the task that takes you twenty minutes and would take a new person a full day?

9. Which tools do you use that are not on the official stack?

10. What do you check before you consider something finished?

11. What is the recurring deadline that nobody else in the company has in their calendar?

12. Which task have you automated or scripted for yourself?

13. What breaks regularly, and what is your standard fix?

14. What is the workaround you have never told anyone about?

15. If you had to write down one process before you go, which would it be?

Relational: who to call (8 questions)

16. Who do you talk to most in an average week, and what about?

17. Who actually approves things, as opposed to who is supposed to?

18. Which relationship took you longest to build, and what made it work?

19. Who owes you a favour, and who do you owe one to?

20. Which supplier, client or partner has a preference you only learn by getting it wrong?

21. Who is the person outside your team you would call in a genuine emergency?

22. Which colleague should the next person meet in their first week, and why?

23. Are there relationships that need a personal introduction rather than an email?

Judgment: the expensive part (11 questions)

These need the most patience. Expect "it depends" and follow it up. "It depends" is the beginning of an answer, not the end of one.

24. What decision do you make regularly that has no written rule behind it?

25. When you say it depends, what does it actually depend on?

26. What is the most expensive mistake you have seen someone make in this role?

27. What did you get wrong in your first six months?

28. Which rule do you break, and when is breaking it the right call?

29. What is a warning sign you have learned to spot early?

30. When do you escalate, and to whom?

31. What advice would you give your replacement that contradicts the official guidance?

32. Which decision seemed unimportant at the time and turned out to matter a lot?

33. What do you know now that you wish someone had told you on day one?

34. If you could leave your successor one paragraph, what would it say?

Context and history (5 questions)

35. Why is this process the way it is? What was tried before?

36. Which decision are people still living with, and who made it?

37. What has been proposed repeatedly and rejected, and why?

38. What is the story behind the thing everybody complains about?

39. Which client or project has history the next person needs to know before they speak to them?

Closing: gaps and priorities (3 questions)

40. What have I not asked about that I should have?

41. What is the one thing that will definitely go wrong after you leave?

42. If your successor could only read three documents, which three?

Running one of these? Everything above is free and always will be. Rinto turns the same conversation into a role document automatically, so the write-up stops being the step that gets skipped. Join the waitlist.

How to run the session

Start at notice, not in the final week. The last week is consumed by goodbyes, handover admin and a person who has already mentally left. Knowledge transfer done in the final three days produces a file nobody opens.

Split it across sessions, and finish early. Three conversations of 45 minutes beat one exhausting two-hour block. Memory works associatively, and people remember things between sessions. Some of the best material arrives at the start of session two. Hold the last one at least a week before the leaving date, because the write-up takes a few hours and the leaver needs time to check it.

Put the successor in the room for some of it, not all of it. They ask better follow-ups than any manager or HR partner, because they are the only person who knows what they do not know. Have them join for the procedural and context sections. Keep them out of the relational and judgment sections, because nobody says "the director signs whatever Sandra approves" in front of the person who will work with Sandra next month. Where no successor has been hired yet, someone from the team who will absorb the work in the interim joins in their place.

Record it if you can, and transcribe it. Note-taking during a knowledge interview means you are writing instead of listening, and the follow-up question is worth more than the note. Ask before you record rather than announcing it, say who will hear it, and delete it once the document is written. In the EU this is personal data processing under the GDPR and needs a legal basis and a retention period. In the Netherlands, doing it as a standing practice is a matter for the works council. If you cannot record, bring a second person to take notes so the interviewer only listens.

Follow every "obviously" and "it depends." Both are markers for tacit knowledge. When someone says "obviously you'd check the batch number first," they have just told you something that is not obvious to anyone else, and they will not repeat it unprompted.

Ask for the mistakes. People will happily tell you what to do and rarely volunteer what not to do. The failure modes are usually more valuable than the procedure, because a competent successor can work out the procedure and cannot work out which shortcut cost someone three weeks in 2024.

What to do with the answers

An interview transcript is not a handover. The output needs to be a document organised the way the successor will need it, which is by situation, not by the order the conversation happened in.

Eight sections, in this order: what this role owns, the recurring calendar, the processes that matter, the people map, the judgment calls with their conditions, the known failure modes, the history and settled arguments, and the first week and first month. Anything you cannot get into that structure belongs in a linked appendix rather than the main document. The interviewer writes it within a week of the last session, and the leaver checks it before they go. If those are different people, say so when you book the sessions.

This is the part that reliably does not happen. The interview gets recorded, the transcript sits in a folder, and the successor never finds it. Running the conversation is the easy half. Turning forty answers into something someone can use on their second Tuesday is the half that gets skipped, which is the problem Rinto was built to solve: the interview runs itself, and the output arrives already structured.

Common questions

What is a knowledge transfer interview? A structured conversation with a departing employee about how their work actually gets done: the sequence, the judgment calls, the relationships and the failure modes that never made it into any document. It is run by the leaver's manager or whoever absorbs the work, not HR, and its output is documentation the next person can use.

How is it different from an exit interview? An exit interview asks why someone is leaving and exists to find patterns across many departures. A knowledge transfer interview asks how the job works and exists to serve one person: the successor. Different owner, different questions, different output.

When should you run one? From the moment notice is given, not in the final week. Three sessions of about forty-five minutes across the notice period works better than one long block, because people remember things between sessions. Hold the last one at least a week before they leave, so there is time to write it up and have them check it.

Who should be in the room? The departing employee and the interviewer, usually their manager. The successor joins for the sections about process and history, because they ask the best follow-up questions there. They stay out of the sections about people and judgment, where their presence changes the answers.

How many questions should you actually ask? Far fewer than 42. Pick the sections that match the risk: if the role is well documented and the successor overlaps, judgment and relationships are enough. If nobody else can do the work and there is no successor, you need all six sections.

What do you do with the answers? Turn them into a document organised by situation rather than by the order of the conversation. Eight sections: what the role owns, the recurring calendar, the processes that matter, the people map, the judgment calls with their conditions, the known failure modes, the history, and the first month. The interviewer writes it within a week, the leaver checks it before they go. This is the step that reliably gets skipped, because nobody is told it is theirs.