Key takeaways
- Negotiate legal terms with qualified advisers. This operating handover begins after scope and authority are agreed and focuses on how recurring work will continue.
- Schedule the seller around real cases, not a lecture calendar. A correction made during a live exception reveals more than another hour of general explanation.
- Transfer authority separately from instructions. A successor who knows the steps but cannot approve the exception still depends on the seller.
- Use an absence test before the overlap ends: the successor runs a normal case and an exception, verifies the effect and repairs the record without private seller help.
Separate the operating handover from the transaction
The purchase agreement may define training hours, consulting work, employment terms, access, representations and obligations. Those are legal and commercial matters for the parties and their advisers. This page does not prescribe them. It starts with the operating question left after those terms are set: what must another person be able to run?
BizBuySell describes seller training as transfer of the company's particular systems, processes, relationships and pending situations. It also notes that the amount and form depend on the business and buyer. That variability is exactly why a generic calendar is weak evidence. Thirty hours can be ample for a stable, documented shop or useless when the important exception never appears.
| Record | What belongs in it | Completion evidence |
|---|---|---|
| Transition terms | Agreed time, scope, availability and contractual boundaries | Reviewed agreement and named advisers |
| Access register | Systems, accounts, data owners and recovery paths | Successor access tested; secrets transferred through approved channels |
| Operating packet | Triggers, inputs, decisions, exceptions, relationships and finished states | Versioned record tied to real cases |
| Control test | Normal case, imperfect case, seller-unavailable run and recovery | Successor-controlled effect reconciled |
Spend the overlap window on evidence that will disappear
- 01Choose the first processesHuman approvalUse frequency, consequence, owner dependence, evidence readiness and repeatability. The acquisition process inventory keeps those dimensions visible and ranks attention without calling a process safe to automate.
- 02Book live cases before interviewsTriggerPut the next scheduled report, service recovery, supplier exception or approval on the transition calendar. Ask the seller to work as usual while the successor records inputs, decisions and corrections.
- 03Write the decision boundaryHuman approvalName what the successor may decide, the threshold, evidence required, expiry and escalation. If authority has not transferred, the packet must say so plainly.
- 04Turn corrections into rules or examplesAI judgmentA stable correction can become a rule. A variable judgment becomes a bounded example set. A consequential commitment remains with a named accountable person.
- 05Reverse-shadow the next runHuman approvalThe successor performs the work while the seller observes. Questions become documentation gaps; interventions become failed test evidence.
- 06Run the seller-unavailable testCodeRemove the private shortcut for an agreed window. Reconcile the final business state and record exceptions that could not be closed.
A readable transition packet has six linked parts
| Part | Minimum content | Test |
|---|---|---|
| Process card | Trigger, owner, frequency, inputs, output and finish condition | Can the successor tell when work starts and ends? |
| Decision table | Criteria, thresholds, authority, refusal and expiry | Can the same evidence produce the same route? |
| Exception ledger | Recent exception, response, owner, clock and closure evidence | Does every known failure have a safe destination? |
| Relationship map | Contact, context, commitments, successor and introduction status | Has the successor handled a live interaction? |
| Evidence map | Source record, retention location and access owner | Can another person reconstruct the result? |
| Test log | Case, expected state, actual state, intervention and repair | Did the successor control the run? |
Do not put passwords, tokens or personal secrets in this packet. Record the approved transfer channel and access owner instead. The seller handover checklist stores progress only in the browser and includes the same no-secrets boundary.
Northline uses the seller on the exception, not the happy path
Northline is a fictional service company. A completed-job review runs most afternoons. The new controller can follow the normal checklist, so another demonstration of the happy path has little value.
The seller's time is reserved for three imperfect jobs: a missing change order, a customer-specific billing instruction and a job whose photographs do not prove completion. The successor records the evidence rule, the authority boundary and the destination for each unresolved case.
During reverse shadowing, the seller intervenes once because the customer instruction lives in an old email. The run fails the control test. The repair is a shared commitment record with an owner and review date, followed by another live run. No connector or customer result is implied.
Use exit tests instead of a handover-complete checkbox
- Normal execution: the successor starts from the real trigger and reaches the verified finish without coaching.
- Exception control: a known imperfect case reaches a named owner within its response clock.
- Authority: decisions are made by an authorized role or stop at the correct approval gate.
- Relationship continuity: the successor handles a live interaction with the relevant context and commitments visible.
- Recovery: a failed or partial run is reconciled before it is retried or closed.
- Maintenance: the successor can update the procedure, withdraw the old version and explain what changed.
A failed test is useful. It points to the next packet repair while the seller is still available. A ceremonial sign-off with no live test hides the same gap until the overlap has ended.
Limitations and when not to use this
- This is general operating guidance after an acquisition decision. It is not legal, tax, accounting, employment, cybersecurity, valuation or transaction advice.
- Training scope, consulting arrangements, access and authority must follow the actual agreement and qualified advice. This page does not recommend a duration or contract term.
- Some leadership, relationship and novel judgment cannot be reduced to a procedure. Keep an accountable human owner and an explicit escalation route.
- Northline is simulated. No customer outcome, connector, system support or complete knowledge-transfer claim is made.
Sources
- Buyer Training After a Business Sale — BizBuySell Accessed 6 August 2026
- The Great Ownership Transfer: A new era of business stewardship — McKinsey Institute for Economic Mobility Accessed 6 August 2026
- Contingency Planning Guide for Federal Information Systems — NIST Accessed 6 August 2026
Build the seller handover
Turn the overlap window into named evidence, authority and successor-control tests.
Build the seller handoverUli 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.