Manage a multijurisdiction corporate separation

---
name: manage-a-multijurisdiction-corporate-separation
category: start
description: Manage a multijurisdiction corporate separation with legal and human protection, perimeter control, asset and obligation reconstruction, Day 1 authority transfer, disentanglement, and independent assurance. Use when a global business must separate without losing operational accountability.
---
# manage-a-multijurisdiction-corporate-separation
## When to use
- Use for a global divestiture, demerger, spinout, joint-venture exit, court-ordered separation, or cross-border restructuring.
- Use when employees, works councils, pensions, licenses, regulated services, customers, data, tax, banks, sanctions, systems, and shared operations cross the perimeter.
- Do not transfer people, data, assets, liabilities, or control solely from a high-level deal perimeter.
## Preconditions
- Establish clean teams, conflict rules, legal-privilege boundaries, human-impact oversight, works-council engagement, and jurisdiction-specific authority.
- Freeze an evidence-backed baseline with entity, perimeter, contract, asset, liability, people, data, system, control, license, and dependency IDs.
- Define signing, antitrust, foreign-investment, regulatory, employee, privacy, tax, sanctions, creditor, and closing conditions.
## Procedure
Run four linked workstreams: legal and human perimeter; asset, obligation, data, and control reconstruction; Day 1 authority transfer; disentanglement and assurance.
1. Open a corporate separation command register recording decisions, authority, conditions, assumptions, evidence, owners, dates, and supersession.
2. Protect employees, customers, vulnerable users, whistleblowers, pensions, wages, safeguarded assets, confidential bidders, and continuity-critical services.
3. Decompose the commercial perimeter into legal entities, branches, people, roles, contracts, permits, assets, liabilities, IP, data, records, systems, controls, accounts, and dependencies.
4. Classify each item as transfer, retain, duplicate, license, novate, migrate, replace, terminate, settle, share temporarily, or unresolved with legal basis.
5. Reconcile entity, people, contract, asset, liability, data, system, control, license, and dependency reconciliation across schedules, source records, operational owners, and counterparties. For every material item, maintain separate effective timestamps, evidence, owner, epoch, and accepted instruction source for legal ownership, employer responsibility, economic benefit, operational control, data-controller role, system administration, bank authority, and service delivery.
6. Map employee consultation, transfer, immigration, payroll, benefits, equity, pensions, union, safety, retention, and sensitive-case handling by location.
7. Map customer and supplier consent, regulated-service continuity, guarantees, debt, insurance, tax, customs, sanctions, banking, permits, and minority rights.
8. Design data and system separation by purpose, residency, minimization, consent, retention, legal hold, identity, access, encryption, interface, and deletion proof.
9. Define Day 1 operating models, accountable executives, delegated authorities, bank mandates, approvals, controls, policies, incident paths, records, and service levels.
10. Contract transition services with scope, data, security, audit, change, price, capacity, dependencies, breach, exit, extension, and step-in rights.
11. Prepare opening balances, intercompany settlement, stranded costs, working capital, tax positions, assets, liabilities, and control certifications.
12. Rehearse close, employee and customer communication, identity and banking transfer, data moves, service failure, regulatory delay, partial close, and rollback.
13. Transfer authority only after each condition and evidence gate passes; use signed handovers, monotonic authority epochs, and stale-instruction rejection. Model a legally transferred item still operated under a transition service as split authority, and make rollback a new forward authority state rather than a rewind of effective legal transfer.
14. Reconcile Day 1 people, payments, access, contracts, balances, data, transactions, support, incidents, and customer outcomes before declaring stability.
15. Drive TSA exit, residual access removal, record handoff, data deletion, license novation, stranded-entity cleanup, claim resolution, and independent assurance.
## Failure plan
- Hold the affected jurisdiction, entity, service, or asset wave when authority, consultation, consent, continuity, opening balance, control, or rollback is unproven.
- Preserve the valid pre-close state for items that have not transferred and use reconciled corrective action for items already legally transferred.
- Escalate material human harm, unlawful data movement, regulatory breach, liquidity failure, or uncontrolled shared authority immediately.
## Worked example
A regulated group separates operations in twelve countries on one close date while works-council consultation, banking mandates, pension assets, shared customer contracts, cloud identities, data residency, licenses, and transition services mature at different times.
## Done
- A corporate separation command register records legal and human perimeter, conditions, decisions, authority, evidence, owners, and unresolved risk
- Entity, people, contract, asset, liability, data, system, control, license, and dependency reconciliation proves the disposition and authority of every material item
- A Day 1, disentanglement, and separation assurance report records signed handovers, opening balances, service continuity, residual access, TSA exit, deletion, obligations, independent findings, and acceptance