Key takeaways
- Start with work that would pause or change without the owner, then schedule the next real case before scheduling another interview.
- Record the cue, evidence, decision, exception and result. A video of someone clicking through software rarely captures why they chose that path.
- Separate relationship context from authority. An introduction transfers contact; it does not automatically transfer permission or trust.
- Finish with successor-run normal and imperfect cases. A document is an input to transfer, not proof that transfer happened.
Inventory what disappears, not everything the owner knows
A career contains more knowledge than any transition can capture. The useful boundary is narrower: which recurring business result would wait, weaken or change if this person were unavailable next week? NASA's knowledge-transfer guidance recommends building capture into normal operations, documenting roles and using cross-training rather than waiting for the last moment.
Rank named processes, decisions and relationships. “Sales” is too broad. “Approve a nonstandard service renewal” has a trigger, evidence, authority and a finish that another person can test.
| Dependency | Evidence to capture | Proof of transfer |
|---|---|---|
| Recurring execution | Trigger, inputs, sequence, finish and known failure routes | Successor completes a live normal case |
| Decision judgment | Contrasting cases, rejected options, threshold and escalation | Successor routes two ambiguous cases consistently |
| Relationship context | Commitments, history, contact preference and successor | Successor handles a live interaction with consent |
| Exception recovery | Symptom, diagnosis, safe stop, repair and verification | Successor reconciles an imperfect case |
| Authority | Role, limit, expiry, refusal and fallback owner | Decision proceeds or stops without owner override |
Use a five-pass live-case loop
- 01Choose the next real caseTriggerPut the next scheduled report, customer exception or supplier decision on the calendar. Do not invent a perfect demonstration.
- 02Let the owner work normallyHuman approvalThe successor records the cue, sources checked, rejected paths and the moment the owner changes course. Interrupt only to clarify evidence.
- 03Write one case recordAI judgmentDraft the rule or bounded example from what happened. Link it to the source record; do not treat a transcript as the final procedure.
- 04Reverse-shadow the next caseHuman approvalThe successor performs the work. Every owner intervention becomes a visible gap rather than quiet coaching.
- 05Run an absence testCodeFor an agreed window, remove the private shortcut. Reconcile the actual finished state and repair the record before repeating the test.
The retirement packet needs decisions and tests, not a folder tour
| Record | Minimum content | Maintenance owner |
|---|---|---|
| Process card | Trigger, owner, inputs, output, finish | Successor process owner |
| Decision ledger | Criteria, examples, authority, refusal | Accountable decision owner |
| Exception ledger | Recent failure, clock, route, repair evidence | Operational exception owner |
| Relationship register | Context, commitments, consented introduction | Named relationship successor |
| Evidence map | Source of truth, access owner, retention location | System or data owner |
| Test log | Expected, actual, intervention, repair, retest | Transition lead |
Keep credentials, personal information and confidential transaction terms out of the packet. Record the approved access-transfer path instead. The seller handover checklist uses the same boundary.
A corrected dispatch decision is worth more than another recording
Northline's owner plans to step back. The team has recordings of the dispatch screen, but the owner still changes the schedule when a technician lacks the right certification, a customer has a same-day promise, or the job requires a part held at another branch.
The successor shadows three real exceptions, records the evidence and writes the authority boundary. During reverse shadowing, one promise exists only in the owner's inbox. The test fails. The repair is a shared commitment record with an owner and expiry, followed by another live run.
The result is not a claim that dispatch is automated. It is evidence that one hidden dependency became observable and testable.
Close the transfer by retiring the private shortcut
- The successor completes a normal case from the real trigger.
- A known exception reaches a named owner inside its clock.
- Authority is explicit; out-of-scope decisions stop safely.
- The final system or business state is reconciled.
- The successor can change the procedure and withdraw the old version.
- Remaining owner-only knowledge has a named containment plan rather than a false “complete” label.
Limitations and when not to use this
- This is operating guidance, not retirement, succession, transaction, valuation, legal, tax, accounting or employment advice.
- A finite overlap cannot capture a career. Some relationship, leadership, craft and novel judgment remains human and develops through practice.
- Do not prescribe transition duration or contractual duties from this guide. Use the actual agreement and qualified advisers.
- Northline is simulated. No customer result, connector or complete knowledge-transfer claim is made.
Sources
- NASA Knowledge Capture and Transfer: Supervisor's Guide — NASA APPEL Knowledge Services Accessed 9 August 2026
- Space Shuttle Tacit Knowledge Capture Oral Histories — NASA Accessed 9 August 2026
- Buyer Training After a Business Sale — BizBuySell Accessed 9 August 2026
Build the handover record
Turn the first process into named evidence, authority, exceptions and successor tests.
Build the handover recordUli Prantz
Builds and operates all-agents
Uli Prantz builds all-agents, the process-automation platform this site documents. He writes about the operational side of automating recurring business work: where deterministic code beats model judgment, where it does not, and where a human still has to approve.