Build the Handover Before the Seller Leaves

Work through the handover with the seller and successor

Use one shared pass for a defined company or function. Check an item only when its evidence exists and the successor has participated where the item calls for a test. Possessing a document or account is not the same as controlling the recurring work.

Separate access, process and authority transfer

CISA recommends role-based access, least privilege, removal of unnecessary accounts and periodic account review. Use the company's approved identity and credential systems for that work. The checklist records only whether the controlled transfer was completed.

Shadowing explains the work; reverse shadowing tests the transfer

1. 01Seller performs, successor observesHuman approval
   Capture the evidence actually consulted, including side checks and changes of path. Ask why only after the concrete choice is visible.
2. 02Successor performs, seller observesHuman approval
   The successor uses the current procedure and named accounts. The seller stays silent unless a pre-agreed stop condition appears, then records the correction beside the case.
3. 03Successor handles an exceptionHuman approval
   Use a real exception where safe or a clearly labeled simulation. Test the owner, clock, evidence packet, authority and escalation route.
4. 04Seller becomes unavailable for an agreed windowTrigger
   Run a normal operating cycle with emergency stop conditions intact. Log interruptions rather than solving them invisibly.
5. 05Team verifies the effect and updates the recordCode
   Confirm the customer, system or report reached the intended state. Version the procedure if the test changed it.

Close the checklist with unresolved risks still visible

A completion percentage is navigation, not proof. Before sign-off, review every unchecked item and assign a named owner and due date. Keep permanent owner or executive responsibilities explicit; a handover is allowed to end with accountable human gates.

For a broader diagnosis, start with the owner-dependency assessment. For the post-close sequence around the handover, use the post-acquisition integration guide. Once one process passes reverse shadowing, map it with the workflow mapper.

Limitations and when not to use this

• This operational checklist is not legal, tax, financial, employment, cybersecurity, valuation or transaction advice, and it does not establish that a handover is legally complete.
• Do not enter passwords, recovery codes, personal data, customer names, deal terms or other secrets. Use approved identity, password-management and record systems.
• Local browser storage may be unavailable or cleared. Copy or print the checklist if the record matters, then store it in the organization's approved system.
• Checking every item does not remove leadership, relationship or rare-event risk. The accountable owner must review the evidence and unresolved risks.

Sources

1. Enhanced Visibility and Hardening Guidance for Communications Infrastructure — CISA Accessed 5 August 2026
2. Continuity Guidance Circular 1 — FEMA Accessed 5 August 2026
3. Post Merger Integration Checklist — DealRoom Accessed 5 August 2026

Related reading

• Post-Acquisition OpsSee where the handover ends and controlled recurring execution begins.
• Post-AcquisitionFit the seller transition into the wider stabilization and integration sequence.
• Owner DependencyDiagnose the authority, work, relationship and exception risks behind the checklist.
• Workflow MapperMap one handed-over process into explicit steps and exception destinations.