How to map entity changes and required approvals for Corporate Restructuring Transactions

Map a corporate restructuring by pairing before-and-after entity charts with a numbered transaction step plan, then tracing each step to corporate authorizations, contractual permissions, filings, and evidence of effectiveness. The resulting entity restructuring matrix identifies which legal person changes, where assets and liabilities move, what authorizes that movement, and what remains unresolved. For company counsel, the essential distinction is between the intended organizational outcome and a supported execution sequence: an updated chart alone does not establish that transfers or approvals are complete.

When to use this workflow

Use this workflow when a proposed merger, internal asset transfer, or business separation changes ownership, contracting parties, asset destinations, or responsibility for liabilities. It serves in-house counsel coordinating corporate records, business teams, and specialist advisers before approving the restructuring sequence.

The scope is out-of-court US restructuring, with Delaware corporate-law illustrations and a federal procurement overlay. Other entity forms and jurisdictions require separate analysis. Assign tax, securities, antitrust, employment, and permit questions to appropriate specialists. The deliverable is an evidence-backed approval map, not a complete closing checklist or legal opinion.

What you need

Collect the current chart, proposed chart, and numbered step plan together. Obtain legal names, formation jurisdictions, entity types, ownership records, governing documents, and existing approvals. Identify the legal owner of each material asset and the actual party to each affected contract; business-unit names are insufficient.

Organize supporting requests by entity and step:

• Merger or transfer drafts, asset schedules, liability allocations, and intercompany arrangements.
• Contracts and amendments, financing documents, guarantees, liens, permits, and relevant intellectual-property and employment records.
• Existing consents, notices, government-contract records, and proposed transition arrangements.
• Execution versions, corporate records, filing evidence, and conditions controlling when each step may proceed.

Assign stable document IDs. Index execution status, date, amendments, source location, access restrictions, and reviewer. Identify a custodian for missing material. Distinguish “not supplied” from “confirmed not to exist”; neither establishes that approval is unnecessary.

Use the template

The companion template is Corporate Restructuring Transactions — Entity restructuring matrix. You can copy this table into your working document or spreadsheet. Use one row for each approval requirement or unresolved question attached to a step.

“Entity change” identifies legal parties and the survivor, recipient, or continuing entity. “Assets / duties” records what moves or remains, including retained guarantees. “Evidence” contains document IDs and clause, schedule, or page citations—not merely folder links.

“Approval / basis” distinguishes corporate authorization, consent, notice, novation, release, and filing. Separate counsel’s analysis from documented facts. “Dependency” identifies prerequisites or effectiveness conditions. The last columns identify the accountable owner, next action, unresolved question, and acceptable completion evidence. Use stable row IDs, such as S02-C03, across charts and issue lists.

Step by step

1. Reconcile the legal entities before assessing approvals

Compare the current chart with ownership records and governing documents. Confirm names, forms, jurisdictions, ownership percentages, and relevant share classes. Replace chart shorthand with legal names and stable entity identifiers.

Compare the proposed chart with the step plan. Every disappearing entity, survivor, or recipient should correspond to an implementing transaction. Confirm that the supporting draft names the same parties.

Record discrepancies in matrix rows identifying conflicting sources and the corporate-records custodian. Do not assess a subsidiary exception using an unverified ownership assumption. The output is a reconciled entity baseline with expressly assigned gaps.

2. Separate each legal movement into a numbered step

Break “move the services business” into identifiable transactions. A separation might require an asset contribution, contract amendments, an intercompany settlement, and a later merger, each with different parties and dependencies.

For every step, identify the transferor, recipient, assets, allocated liabilities, intended effective point, and implementing instrument. Distinguish legal ownership from operational use. Identify liabilities intended to remain with the transferor and any guarantees expected to continue.

Enter each movement and its predecessor in the matrix. If sequencing changes, reassess affected approval rows rather than merely renumbering the chart. The output is a transaction sequence against which permissions can be tested.

3. Identify the applicable corporate approval route

Analyze entity form, jurisdiction, governing documents, and mechanism together. Under the ordinary Delaware domestic merger route, DGCL § 251(b) addresses constituent-board approval and advisability; § 251(c) addresses stockholder adoption and filing. Test statutory exceptions and alternative routes before assigning tasks. See DGCL § 251. (delcode.delaware.gov)

For asset movements, § 271(a) addresses board action and authorization by a majority of outstanding stock entitled to vote for sales, leases, or exchanges of all or substantially all assets. Section 271(c) generally removes the stockholder-resolution requirement for transfers to a subsidiary wholly owned and controlled, directly or indirectly, by the transferor, unless its certificate provides otherwise. Assess the threshold and relevant exceptions, including § 272. See DGCL §§ 271–272. (delcode.delaware.gov)

Record the route, factual predicates, reviewing counsel, and unresolved analysis. Separate authorizations, signatures, filings, and effectiveness where their evidence differs. Identify whose approval is needed and in what capacity; an officer’s signature is not evidence of every underlying authorization.

4. Test contracts against the actual transaction mechanism

Review assignment, merger, operation-of-law, change-of-control, guarantee, and termination provisions against the proposed step—not its business label. Read amendments and incorporated terms together. Establish whether the contracting party changes.

DGCL § 259(a) provides for merger vesting of property and rights and attachment of liabilities to the survivor, preserving creditor rights and liens. Do not treat that statutory consequence as a substitute for analyzing contract language and applicable permit requirements. See DGCL § 259(a). (delcode.delaware.gov)

Create distinct rows for consent, notice, and release questions. Do not mark a parent guarantee released merely because a contract assignment is permitted. Record the clause reference, counsel’s interpretation, and any missing contract-family documents. The output is a permission analysis tied to each actual movement.

5. Isolate government contracts and shared arrangements

For federal contracts, distinguish asset transfers from stock purchases leaving the contracting party unchanged. FAR 42.1204(a) permits government recognition of a successor in specified asset-transfer circumstances when in the government’s interest. Paragraph (b) says novation is unnecessary for a stock purchase where the contracting party remains legally unchanged, controls the assets, and performs; other ownership-change matters may require a formal agreement. See FAR 42.1204(a)–(b). (acquisition.gov)

Assign applicable novation submissions separately. Paragraphs (e)–(g) address supporting documents and contracting-officer flexibility; they are not a universal restructuring checklist. Record the procurement owner, required evidence, and unresolved government-recognition question. (acquisition.gov)

For shared commercial contracts, identify continuing users, proposed allocation, and remaining exposure. As negotiated examples only, 3M–Solventum §§ 2.8 and 2.12 address shared-contract arrangements and execution of applicable ancillary agreements. They do not establish permission for another transaction. (sec.gov)

6. Convert findings into execution dependencies

Classify unresolved items: do they prevent the planned step, require resequencing, or permit a specifically supported delayed arrangement? Preserve each condition’s clause reference and identify satisfaction or waiver authority. Keep conditions separate from covenants and deliverables.

For a proposed delayed transfer, record the interim legal holder, permitted performance arrangement, economic allocation, retained exposure, and event permitting eventual transfer. Negotiated delayed-transfer provisions appear in 3M–Solventum §§ 2.10–2.11; transition-support termination does not itself establish that required approvals have been obtained. (sec.gov)

Enter the dependency, decision-maker, and escalation point in each affected row. Resolve circular sequences before approving the plan. Business acceptance of risk should not be recorded as evidence of counterparty consent.

7. Validate the map against completion evidence

Walk through the sequence with corporate, commercial, finance, and specialist owners. Specify evidence for every row: executed resolutions, signed consents, notice-delivery records, filing records, or other applicable effectiveness evidence. Record signatory capacity and recipient where relevant.

Keep “drafted,” “approved,” “executed,” and “effective” distinct. Compare the evidence received with the completion criterion recorded earlier, rather than changing the criterion to fit available documents.

Issue a dated matrix linked to matching chart and step-plan versions. Assign open issues an owner and decision point, then recheck the analysis whenever the structure changes. The output is a controlled approval map showing both completion and remaining execution constraints.

Worked example

Fictional scenario: Alder Quay Holdings, Inc. owns all shares of Alder Quay Operations, Inc. and Alder Quay Services, Inc.; all three are Delaware corporations. Step S01 transfers Operations’ service assets to Services. Step S02 merges Operations into Holdings, with Holdings surviving.

Counsel has charters, a ledger confirming sister-company ownership, a draft transfer agreement, and a signed customer agreement. A fictional equipment schedule shows $4 million in value but supplies no business-wide financial context. The fictional customer clause requires prior written consent to assignment. A draft list suggests an affected federal contract, but the contract itself is missing. No approvals or consents have been supplied.

The first row prevents reliance on the subsidiary exception based solely on common ownership; the amount alone does not resolve the asset-significance question. The second requires a consent workstream rather than reliance on the transfer instrument. The third preserves uncertainty instead of inventing a novation conclusion.

Together, these findings require counsel to reconsider whether S02 can proceed as planned while S01 remains incomplete. The matrix must also address obligations remaining with Operations immediately before the merger and their intended treatment afterward. Separate merger-authorization and filing rows remain necessary; these three entries are representative, not a completed approval map.

Common mistakes

• Mapping businesses instead of legal persons. Identify the documented owner or contracting party before assigning a destination.
• Assuming internal transfers need no approvals. Test the actual ownership relationship, governing documents, mechanism, and contract language.
• Treating merger vesting as blanket permission. Keep statutory consequences and contractual-trigger analysis separate.
• Combining consent, novation, and release. Record separate bases and completion evidence, especially for continuing guarantees.
• Using “handled” to conceal gaps. Substitute a source citation, unresolved question, accountable owner, and sequencing consequence.

Final quality check

• Every chart change corresponds to a numbered legal step.
• Names, jurisdictions, ownership, survivors, and recipients reconcile to records.
• Approval routes reflect actual relationships and governing documents.
• Contract conclusions use complete agreements and relevant amendments.
• Legal sources support the propositions; applicable effective-date provisions are checked for the transaction date.
• Approvals, signatures, filings, and effectiveness have appropriate completion evidence.
• Every open issue is resolved or assigned with its execution consequence recorded.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its due diligence capabilities to organize materials through bulk classification and prioritize human review; tabular review supports work across documents. Contract review can focus on deal-specific instructions, with findings quoting clauses, locating text, ranking severity, and identifying missing language as not present. Counsel retains responsibility for entity relationships and approval conclusions. To assess fit for this document-to-matrix workflow, book a demo.

Frequently asked questions

Should each entity have only one matrix row?

No. Repeat entity identifiers across distinct questions. One entity may require rows for transfer authorization, customer consent, guarantee release, and a later merger filing.

Does the proposed chart establish the transfer destination?

It records intent. Reconcile it with the implementing instrument, schedules, conditions, and effectiveness evidence before marking the movement complete. Track interim and final destinations separately where necessary.

How should an unavailable contract be recorded?

Identify the missing document, request owner, custodian, affected step, and unresolved trigger analysis. A contract list can identify possible exposure but cannot establish assignment wording.

Can an unresolved consent remain open after restructuring?

Only after assessing whether the actual documents and applicable law support the proposed arrangement. Record the interim holder, permitted performance, retained exposure, authority, and eventual completion evidence. Do not assume internal allocation resolves third-party rights.

Sources

• Delaware Code, Title 8, §§ 251 and 259.
• Delaware Code, Title 8, §§ 271–272.
• Federal Acquisition Regulation 42.1204.
• 3M–Solventum Separation and Distribution Agreement, March 31, 2024.

Scope: General professional workflow guidance; transaction-specific conclusions depend on actual language, governing law, facts, and applicable effective-date provisions.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.