100 Knowledge Transfer Questions to Ask Before Someone Leaves

Ask someone to document their job and you will get a list of tasks. Ask them the right questions and you will get the judgment behind those tasks. The difference is enormous, and it is the reason a structured question bank is the most underrated tool in knowledge transfer. Generic prompts like please write a handover doc produce generic answers. Specific, well-categorized questions produce the context a successor can actually use.

Questions work because they lower the activation energy of capture. A blank document is intimidating and open-ended; a pointed question is easy to answer in a sentence or two. String enough of those answers together, across the right categories, and you have captured more usable knowledge than any wiki page the person would have written on their own.

Why categories matter

Grouping questions into categories does two things. It makes sure you cover the whole surface of a role rather than only the parts that come to mind, and it lets you go deep in one area at a time instead of jumping around. We use eight categories that together capture the operational reality of almost any role.

• Role and responsibilities: what only this person handles
• Decisions and rationale: why things are the way they are
• Risks and warnings: what should never be done, and what broke before
• Systems and access: what is critical and who owns it
• People and relationships: who must be involved
• Processes and workarounds: how the work really gets done
• Customers and accounts: the context behind the relationships
• Projects and handoffs: the real status of what is in flight

The questions that draw out judgment

Within each category, the most valuable questions are the ones that ask about reasoning and exceptions rather than steps. What would you tell the next person on their first day? What looks broken but is intentional? Which decisions would you revisit, and what would have to change first? Who is the real expert when something goes wrong? These questions reach the tacit knowledge that documentation never captures because it never occurs to anyone to write it down.

A document lists steps. The right question reveals the judgment behind them.

How to run the session

Treat it as an interview, not a worksheet. Ask one question at a time, follow the interesting threads, and record the reasoning behind every answer. Start from the systems and decisions that would hurt most to lose, because you will rarely get to all hundred questions and you want the highest-value answers first. Capture verbatim where you can; the way an expert phrases a warning often carries more meaning than a tidy summary would.

Avoid the common traps

Two mistakes derail most question-driven handovers. The first is asking only factual questions and skipping the why, which leaves the successor with steps they cannot adapt. The second is capturing answers nowhere durable, so the session happens but the knowledge evaporates into a chat thread. Pair good questions with a place to store and review the answers, and the session pays off long after it ends.

Examples from each category

It helps to see the kinds of questions that draw out real judgment rather than surface facts. Under decisions and rationale, ask why the current approach was chosen over the alternatives, and what would have to change to revisit it. Under risks and warnings, ask what has broken before and what the next person should never do. Under people and relationships, ask who must be consulted before a major decision and who the real expert is when something goes wrong.

Under systems and access, ask which tools have non-obvious configuration and what integrations quietly depend on each other. Under processes and workarounds, ask which manual steps are easy to forget and which exceptions come up often enough to plan for. Each of these reaches past the documented surface into the operating reality that makes the difference between a successor who copes and one who thrives.

Adapt the bank to the role

A hundred questions is a starting bank, not a script to read verbatim. The right set depends on the role. An engineering handover leans heavily on systems, incidents, and technical debt. A customer success handover leans on accounts, history, and escalations. An operations handover leans on vendors, approvals, and exceptions. Pick the categories that carry the most weight for the role in front of you, go deep there, and treat the rest as a checklist to make sure nothing important is silently skipped.

The point of the structure is coverage and depth, not bureaucracy. Used well, the question bank turns an intimidating, open-ended handover into a focused conversation that produces answers a successor can actually use, in far less time than asking someone to write it all down from a blank page.

Make the answers easy to give

The best questions still fail if answering them feels like a chore. Lower the friction wherever you can: let people answer out loud rather than in writing, capture the response verbatim, and never ask the same question twice. A fifteen-minute conversation that yields a dozen specific, recorded answers beats a two-hour writing assignment that yields a tidy document nobody trusts. Respecting the expert's time is not just courtesy; it is the difference between a transfer that happens and one that is endlessly postponed.

Turn answers into trusted memory

Questions are only half the job. Once captured, answers should be reviewed, organized, and made searchable so the successor can find them later without re-interviewing anyone. That is where a structured system earns its place. WorkFera uses these eight categories as the backbone of a guided Fera interview, then routes the answers through review and locks them into a Knowledge Clone. You can find the full, categorized set of questions on our resources and use them today, with or without us, in a single focused session rather than a string of scattered meetings.