Knowledge transfer when someone changes roles

A useful handover leaves another person able to continue the work, recognize its limits and find help. Copying files is part of that job, but it does not establish that the recipient can make sense of the decisions, exceptions and relationships behind them. Plan knowledge transfer around the work that must continue, then check it through use.

Imagine a project coordinator moving to a different department in four weeks. They maintain a supplier schedule, coordinate approvals and know how to spot a delivery promise that needs checking. Their successor has access to the shared folder but has not handled a late change. This is a hypothetical example, not a report of a real transition.

The obvious request is “please write everything down.” A more useful question is: what must the successor be able to do, and what could prevent them from doing it after the move?

Start with the work at risk

Make a short inventory of responsibilities, current commitments and recurring decisions. Begin with real work: this month’s delivery review, the next approval deadline and the cases waiting for a response. A list of software tools or folder names will not tell you why the work matters.

APQC’s account of structured knowledge transfer recommends locating critical knowledge, prioritizing transfer opportunities and choosing methods that suit the situation. Its guidance also recognizes that recipients need time and an active role. Treat this as practitioner guidance, not a guarantee that a particular process prevents knowledge loss.

In the coordinator example, three questions help prioritize the inventory. What would have a serious consequence if missed? What does only this person currently understand? What cannot easily be reconstructed from an authoritative record? These are original discussion prompts, not a validated risk score.

The supplier schedule may already have a clear procedure. Recognizing when a date is provisional may depend on experience and a relationship with the supplier. The approval deadline may be documented but stored where the successor cannot access it. All three matter, but they do not call for the same transfer activity.

Agree who is responsible for the transition

The departing colleague should not have to carry the handover alone while completing an unchanged workload. A manager needs to settle priorities, protect time and identify who owns unfinished work. The recipient needs space to practise and ask questions. A facilitator can help surface assumptions, especially when the two colleagues have different levels of experience.

NASA’s guide for supervisors treats continuity as an ongoing management responsibility. It covers planning, role documentation, mentoring, shadowing and materials for successors. The useful lesson for a normal workplace is the combination of preparation and interaction—not an assumption that one aerospace organization’s procedures fit every team.

For our example, agree a bounded outcome: the successor will prepare a delivery review, explain which dates still need confirmation and route an approval exception to the correct role. The manager retains authority for any commercial commitment. Naming that boundary prevents the handover from quietly becoming a delegation of powers the successor does not have.

If responsibilities are divided among several people, write down those divisions. Use stakeholder mapping to identify important interfaces, but confirm arrangements directly. “Everyone knows who to ask” is precisely the sort of assumption a role transition can expose.

Choose a transfer method for each kind of gap

Use a document for information that needs to be retrieved accurately: recurring dates, system locations, definitions, named roles and the current approved procedure. Include enough context to explain when it applies and who maintains it. Link to the authoritative source rather than creating an uncontrolled copy of every policy.

Use a worked case for judgment. In the hypothetical handover, the coordinator could select an appropriately redacted delivery change and explain what first caught their attention, what information was missing and which alternatives they considered. The successor should be able to question the reasoning, not merely copy the final action.

Use a direct introduction for a relationship or coordination boundary. A contact list records a name; an introduction can clarify what that person handles, when to involve them and what information they need. Keep it role-based where possible so that the next departure does not immediately invalidate the handover.

Use supervised practice when the recipient must perform a task. Watching someone prepare the review is a useful start. Preparing the next review with appropriate oversight reveals different questions. Neither activity should bypass access controls, approval requirements or the safeguards applicable to the work.

The distinction is practical rather than absolute. A case discussion may improve a checklist; a practice session may reveal a missing contact. Let the handover material change as the recipient uses it.

Have a conversation about decisions, not just duties

Set aside one session to examine a specific difficult case. In our example, the facilitator might ask the coordinator to reconstruct a delivery change from the first notification to the final decision. The successor listens for points they would not yet know how to handle.

Useful original prompts include:

• What made this case different from the normal procedure?
• Which signal did you notice first, and what other explanation was possible?
• Which information did you check before acting?
• Where did your own authority end?
• What would you want someone taking over this case to verify rather than assume?

Avoid asking for a complete catalogue of intuition. Keep returning to the case, its context and the evidence available at the time. A recollection can be mistaken, and an experienced colleague’s workaround may no longer be appropriate. Check important points against current records and the responsible process owner.

The resulting note might explain that a supplier’s date was a planning estimate rather than a confirmed commitment. The lesson is not “never trust that supplier.” It is to distinguish the status of a date and seek the appropriate confirmation before making a downstream promise. That distinction can be built into a future review without turning a personal judgment into a permanent rule about another organization.

Let the recipient do the work

For the coordinator’s handover, start with a low-risk rehearsal using a closed or invented case. Ask the successor to find the relevant material, prepare a review entry and explain what remains uncertain. Then, where appropriate, move to supervised real work with the normal approvals intact.

Observe the process as well as the answer. Can they locate the current schedule? Can they distinguish an estimate from a commitment? Can they explain when they would stop and ask for help? A correct answer supplied by the predecessor is not the same as the successor independently finding a defensible route.

Record gaps as actions with owners. If a shared link is inaccessible, someone must fix access. If a term is ambiguous, update the explanation. If the successor cannot yet judge an exception, provide further supported practice or retain an escalation boundary. Do not convert every difficulty into a training request.

This connects with ADKAR’s distinction between knowledge and ability: knowing a procedure and being able to use it are different questions. A handover rehearsal is an original practical check, not a formal ADKAR assessment or a general certification of competence.

A workable four-week example

The following is a proposed schedule for our hypothetical role move, not a standard duration for knowledge transfer.

In week one, the manager, coordinator and successor identify the most consequential work, confirm responsibilities and resolve obvious access problems. They agree which activities will be postponed to make room for the handover.

In week two, the coordinator walks through an ordinary delivery review and one exception. The successor builds a short reference note in their own words, with links to the actual working records. Relevant colleagues check the contact and approval arrangements.

In week three, the successor leads a supported review. The coordinator observes and intervenes when the agreed boundaries require it. They revise the handover notes around the difficulties encountered, rather than producing a second, separate set of instructions.

In week four, the manager checks unresolved gaps, assigns ongoing support and confirms who owns the reference material after the move. Any post-transfer help from the former coordinator is explicitly agreed; the team does not assume permanent availability because the person still works in the organization.

Different work may need months of development or specialist qualification. A calendar deadline does not make an incomplete transfer safe. Use a change-readiness review when the proposed new allocation of work depends on conditions that are not yet in place.

When there is no overlap

Sometimes the person has already left, or a successor has not been appointed. Be explicit that this is a reconstruction effort, not a completed person-to-person transfer. Identify current commitments, available records and other people who participated in the work. Separate verified information from recollection and unresolved assumptions.

NASA’s transitions guide addresses rapid departures, redistributed responsibilities and support for people taking on unfamiliar work. In our example, the manager might temporarily separate schedule maintenance from exception approval, bring another experienced colleague into reviews and defer less important work while gaps are resolved.

Do not turn the missing colleague into the only recovery plan. External assistance, additional training, changed service expectations or a reduced scope may be needed. The manager should make those choices visible rather than leaving the successor to improvise silently.

Keep the knowledge useful after the handover

Return to the reference material after its first real uses. Check what was hard to find, which explanation became outdated and whether the right support was available. Name an owner and a review trigger, such as a process change or a newly discovered exception.

NASA’s lessons-learned lifecycle distinguishes collecting, recording, disseminating and applying lessons. That is a helpful reminder that storing an account is not the endpoint. For this handover, application might mean changing a review question or clarifying an escalation route—not merely uploading a recording.

Treat the four-week example as a starting point, not a guarantee. The test is local and concrete: can the people now responsible carry out the agreed work, recognize uncertainty and obtain appropriate help? That is the handover worth planning for.