Key takeaways
- The transaction documents define scope and duration; the operating plan should allocate that agreed time to the cases with the most disappearing evidence.
- Front-load relationships, exceptions and owner-only decisions. Software tours and ordinary steps are easier to recover after the overlap.
- Reverse shadowing turns private coaching into visible gaps. Record each intervention and retest after the procedure changes.
- End against process-level exit evidence, not a calendar alone: successor-run work, transferred authority, reconciled effects and owned exceptions.
The agreement sets the boundary; the operating plan spends it
Transition duration, duties, compensation, access and availability are transaction matters. This guide does not prescribe them. BizBuySell notes that buyer training varies with the business and buyer; the operating response is to allocate whatever has been agreed according to disappearing evidence, not copy a universal schedule.
Write a transition backlog with one row per recurring process or decision. Mark the next live case, current owner, successor, evidence source, authority gap and exit test.
| Work | Why now | Later evidence |
|---|---|---|
| Live relationship introduction | Context and trust require both people present | Successor owns contact and commitment record |
| Rare consequential exception | Decision rationale may exist only with seller | Case record, authority and escalation route |
| Normal software path | Usually recoverable from records and current staff | Procedure, recording and test account |
| Open commitment | History can disappear or be reinterpreted | Named owner, source, due state and expiry |
Run the transition as a shrinking-support sequence
- 01Observe seller-controlled workHuman approvalCapture real normal and imperfect cases. Record sources and corrections, not private speculation.
- 02Draft the operating packetAI judgmentWrite triggers, inputs, decisions, exceptions, authority, verification and recovery. Mark unknowns.
- 03Reverse-shadow the successorHuman approvalThe successor runs the case. Seller interventions are logged instead of silently fixing the result.
- 04Reduce seller accessTriggerUse the agreed contact path and response window. Route questions through the packet owner so repeated gaps are visible.
- 05Run seller-unavailable testsCodeTest normal work, one known exception and recovery. Reconcile the actual business state before declaring transfer.
Replace broad interviews with case questions
- What evidence caused you to choose this path?
- Which similar case would take another route?
- What are you authorized to decide, and where must this stop?
- Which customer, vendor or employee commitment changes the normal rule?
- How do you know the final state is correct?
- What would make a retry unsafe?
The seller handover checklist gives these answers a stable destination without asking for credentials or transaction terms.
An intervention becomes a failed test, not a favor
A successor prepares a weekly branch pack. The seller quietly replaces one service figure because a local team uses a different completion definition. Under ordinary shadowing, the report would leave correctly and the gap would stay hidden.
In reverse shadowing, the intervention is logged. The team records both definitions, reconciles source fields and reruns the pack. During the next agreed seller-unavailable window, the successor identifies the mismatch without private help and routes the unresolved definition to the controller.
Use a process exit card for every material handover
| Test | Pass evidence | If it fails |
|---|---|---|
| Normal case | Successor reaches verified finish | Repair missing instruction or access |
| Known exception | Correct owner and clock receive it | Add evidence, authority or route |
| Relationship case | Successor acts with visible context | Schedule consented introduction or retain owner |
| Recovery | Partial effect is reconciled before retry | Add stop, checkpoint and recovery owner |
| Maintenance | Successor can revise and withdraw old version | Transfer procedure ownership |
Limitations and when not to use this
- This guide assumes transition terms already exist. It is not legal, tax, valuation, employment, accounting, financial or transaction advice.
- Do not infer an appropriate duration, consulting arrangement or duty from this page. Use the agreement and qualified advisers.
- Some leadership and relationship knowledge will not transfer through documents or tests; retain explicit human ownership.
- The example is simulated. No customer result, connector or universal transition outcome is claimed.
Sources
- Buyer Training After a Business Sale — BizBuySell Accessed 9 August 2026
- NASA Knowledge Capture and Transfer: Supervisor's Guide — NASA APPEL Knowledge Services Accessed 9 August 2026
- Contingency Planning Guide for Federal Information Systems — NIST Accessed 9 August 2026
Open the seller handover checklist
Turn agreed transition scope into process-level evidence and tests.
Open the seller handover checklistUli 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.