How to compare material contracts in a diligence table for Corporate Restructuring Transactions

Compare material contracts against the company’s proposed restructuring steps, not simply against one another. Establish the contracting entities and controlling document families, extract consistent commercial and transfer-related terms, and assess each agreement against the planned merger, asset transfer, or separation. Record clause-level evidence separately from legal conclusions and missing information. The resulting diligence table should identify which contracts support the proposed operating structure, which require consent or another arrangement, and who must resolve each uncertainty before the company relies on the assessment.

When to use this workflow

Use this workflow when company counsel or an in-house legal team must compare material contracts across an out-of-court restructuring. Triggers include transferring a business into a subsidiary, merging operating companies, separating a division, or dividing shared purchasing and customer arrangements.

The comparison answers a defined question: can the proposed entities operate the relevant business under existing contractual arrangements after each step, and what exposure remains with the company? It supports decisions about consent requests, replacement arrangements, and sequencing; it does not replace corporate authorization analysis or a closing checklist.

This guide uses a US orientation, Delaware merger illustrations, and a limited federal procurement overlay. Contract conclusions depend on wording, governing law, entity form, facts, and structure. Bankruptcy, foreign-law, tax, securities, and antitrust analysis remain outside scope. Check applicable law and effective-date provisions for the transaction date rather than treating a live consolidated source as a historical snapshot.

What you need

Obtain the numbered restructuring plan and before-and-after entity charts. Identify merger survivors, asset destinations, and entities expected to perform customer and supplier obligations. “Internal reorganization” is not a sufficiently precise transaction description.

Build the source package around:

• Executed agreements, amendments, schedules, statements of work, incorporated terms, side letters, and existing consents.
• Material-contract selection criteria and business-critical exceptions, including low-spend contracts essential to continued operations.
• Contracting-party legal names, covered sites and businesses, business custodians, and source locations.
• Guarantees, security arrangements, intercompany support, and shared-use arrangements connected to the contracts.
• Proposed transitional services, replacement supply, licensing arrangements, and any federal contract transfers.

Assign stable document IDs. Record execution status and document-family relationships in the source index. An unaccepted amendment must not be treated as controlling merely because it is newer than the signed agreement.

Use the template

Use the Corporate Restructuring Transactions — Material contracts comparison template below. You can copy this table into your working document or spreadsheet.

Create one row per contract-topic-step combination when an agreement raises distinct decisions. A shared supply agreement may need separate assignment, pricing, and guarantee rows. Keep the contract ID constant and give each row a unique suffix.

Use consistent review topics: term, renewal, termination, assignment, change of control, guarantees, exclusivity, pricing, and governing law. Add agreement-specific topics, such as permitted software users or customer subcontracting restrictions. Record “not present in reviewed documents” where appropriate; do not silently omit an examined topic.

“Source / clause” identifies the document ID and clause or page. “Assessment / uncertainty” separates verified wording, missing evidence, and counsel’s interpretation. “Action / owner” includes the requested outcome, accountable person, and relevant milestone. “Status / evidence” identifies proof of resolution and the verifying reviewer. Use row IDs, not spreadsheet positions that change when sorted, for cross-references.

Step by step

1. Fix the transaction assumptions and comparison population

Record the step-plan version and assign step IDs. Establish each contract’s current legal party, business served, intended post-step user, and whether the contracting party changes. Have the business custodian validate operational coverage rather than infer it from the title.

Select contracts by both financial significance and operational dependence. Include a modest-value software license if the separated business cannot function without it. Record exclusions and their approver in the source index. Financing restrictions affecting the step should be linked to the comparison without turning it into a complete financing review.

Template output: parties, operations, affected steps, destinations, and unresolved mapping questions.

2. Assemble the controlling document family

Read amendments and incorporated documents with the master agreement. Reconcile changes to parties, scope, term, transfer restrictions, and pricing. An amendment relaxing assignment restrictions may leave a related guarantee untouched.

Distinguish “not supplied” from “confirmed nonexistent.” If a consent letter is mentioned but unavailable, retain the reference and request it. A custodian’s recollection can guide retrieval, but should not close the evidence gap. Record conflicting versions rather than choosing one without verification.

Template output: controlling source IDs and pinpoint references, plus an owner for missing schedules, incorporated terms, or execution evidence.

3. Extract comparable terms without flattening distinctions

Apply the same topic sequence across agreements. Capture expiration and renewal mechanics, termination triggers, transfer wording, guarantees, exclusivity, pricing dependencies, and governing law. Identify any contractual notice period and its triggering event rather than supplying a generic deadline.

Assignment of rights, delegation of performance, merger language, and ownership-change restrictions should not collapse into “transfer permitted.” A notice obligation differs from consent, and consent does not establish release unless the relevant documents support that conclusion.

For commercial terms, record the affected scope. Enterprise-wide volume pricing may not describe the pricing available to a separated business. Preserve conditions and exceptions in the summary; use a precise citation instead of reproducing whole clauses.

Template output: normalized terms, qualifying conditions, and separate rows for materially different triggers.

4. Test each restriction against the actual step

Apply the wording to the transaction mechanism. A stock ownership change, statutory merger, and asset assignment require distinct questions even if their business effects look similar. Assess successive steps separately: permission for an affiliate asset transfer does not answer a later merger question.

For Delaware mergers, § 259(a) vests constituent corporations’ property and rights in the survivor and attaches their debts, liabilities, and duties to it, while preserving creditor rights and liens. That statutory consequence does not alone resolve a contract-specific consent or notice analysis. See DGCL § 259(a).

For federal contracts, FAR 42.1204(a) permits government recognition of a successor following specified asset transfers when in the government’s interest. Paragraph (b) makes novation unnecessary for a stock purchase only where the contracting party remains legally unchanged, controls the assets, and performs the contract; other ownership-change issues may still warrant a formal agreement. See FAR 42.1204(a)–(b).

Template output: trigger analysis, assumptions, governing-law questions, and counsel assigned to unresolved interpretation.

5. Compare operating continuity and retained exposure

Check whether the intended entity receives the necessary service, supply, or licensed-use scope. For shared contracts, identify each business’s requirements, whether partial allocation is possible, and whether the proposed interim performance arrangement is permitted. Compare pricing, minimum purchases, exclusivity, termination exposure, and guarantees separately.

As negotiated wording—not a general legal rule—the 3M–Solventum separation agreement addresses shared contracts through partial assignment or amendment subject to limitations, and reasonable permissible alternatives where those routes are unavailable. It does not establish that another counterparty must accept similar arrangements. See § 2.8 of the executed agreement.

Record internal cost allocation separately from counterparty-facing obligations. The company’s preferred allocation is not evidence that the counterparty has accepted it.

Template output: operating consequence, proposed arrangement, retained exposure, and dependencies on linked rows.

6. Prioritize and assign a specific resolution

Rank issues by their effect on the proposed step and operating continuity, not clause length. An unresolved termination right under an essential supply agreement may outrank a routine notice under a replaceable service contract.

Specify the requested result: consent to a named transfer, confirmed coverage, amended pricing, replacement agreement, or guarantee release. Identify the decision-maker and fallback. Distinguish a business target date from a contractual deadline. Refer proposed sequencing changes to restructuring counsel instead of incorporating an unapproved assumption into the table.

Template output: priority, accountable owner, requested action, fallback, and milestone or sourced contractual timing.

7. Verify conclusions and freeze the comparison version

Have counsel verify high-impact assessments against the complete document family and current step plan. Reconcile inconsistent treatment of similar clauses. Differences may follow from governing law, party identity, or operational scope, but the reason should be recorded.

For applicable federal novation workstreams, FAR 42.1204(e)–(g) specifies submissions including affected-contract information, performance-capability evidence, transfer instruments, corporate approvals, and counsel opinions, as applicable, with specified flexibility for the contracting officer. Link that workstream rather than importing its requirements into every commercial-contract row. See FAR 42.1204(e)–(g).

Template output: verified status, evidence, reviewer, and expressly assigned open issues. Preserve the comparison version and step-plan assumptions; revisit affected rows when the plan changes.

Worked example

Fictional scenario: Alder Basin Holdings plans to transfer its pump division from Alder Basin Operations into a new subsidiary, Cove Pump Systems. Step S2 is the asset transfer; S3 merges Operations into Holdings. The retained business will operate through Holdings after S3. The business initially assumes an internal-reorganization exception covers every contract. All parties, documents, and provisions in this example are fictional.

The packet contains executed supply documents D101–D102, software license D201, and parent guarantee D301. The fictional supplier is Flint Channel Supply; the software provider is Northglass Software. Procurement confirms both businesses use the supplier. D101 requires written assignment consent; D102 bases pricing on combined purchasing. D201 permits affiliate use only for entities listed in missing Schedule B. D301 requires a separate written supplier agreement for release.

The comparison changes the recommendation from “send transfer notices” to distinct negotiations and evidence requests. Supply coverage must address both steps, not just Cove’s initial transfer. Software coverage remains unverified, not prohibited by assumption. The guarantee requires an independent release or exposure decision. These three entries are representative, not a complete review: additional rows must test S3’s effect on the remaining contract obligations before the comparison is finalized.

Common mistakes

• Using “consent required” as the entire assessment. Separate the trigger, operational coverage, pricing, and release questions, with distinct resolution tests.
• Treating the corporate step as dispositive. Test contract wording against each step, including subsequent mergers and changes in recipient identity.
• Allocating shared contracts solely by spend. Confirm sites, users, service scope, exclusivity, and pricing dependencies before proposing a split.
• Reviewing an amendment in isolation. Reconcile the master agreement, incorporated terms, and related guarantees before assigning status.
• Treating counterparty contact as completion. Verify the executed instrument, covered entities, conditions, and effectiveness; a request or draft is not resolution evidence.

Final quality check

• Each contract maps to a legal party, business, and current step ID.
• Materiality exclusions have a recorded decision-maker.
• Substantive findings have verified document and clause or page citations.
• Amendments, schedules, and incorporated terms are reconciled or expressly missing.
• Assignment, change of control, notice, novation, and release are distinguished.
• Shared-use, pricing, and retained-guarantee consequences are addressed.
• Open issues have accountable owners and defined evidence or decision requirements.
• Resolved rows contain evidence covering the current plan, including successive steps.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities include bulk document classification to organize diligence and prioritize human review. Tabular review supports comparison across multiple documents using the company’s review questions. Lawyers remain responsible for source completeness, transaction assumptions, and legal conclusions. Where findings require amendments, contract review supports review and redlining; lawyers can edit or insert suggestions as ordinary tracked changes in Word. Book a demo to discuss reviewing your restructuring contract population.

Frequently asked questions

Should every contract have the same number of rows?

No. Apply consistent review topics, but add rows when different steps, obligations, or owners require separate decisions. Link related rows through the contract ID and explain genuine differences between otherwise comparable agreements.

Can an affiliate-transfer exception close the issue?

Not alone. Verify the affiliate definition, conditions, intended recipient, and transaction mechanism. Then check operational scope, pricing, notice, retained liability, and any later restructuring step separately.

How should the table handle missing incorporated terms?

Cite the incorporating provision, identify the missing document, and assign retrieval. Mark affected conclusions unverified. Do not substitute current website terms without establishing that the applicable agreement incorporates that version.

Does consent resolve a shared-contract problem?

Only insofar as its wording addresses the problem. Confirm recipients of performance, permitted users, charges, conditions, and continuing liability. Keep unresolved commercial allocation or guarantee questions open even if transfer consent is obtained.

Sources

• Delaware Code, Title 8, § 259(a) — statutory consequences of a Delaware merger.
• FAR 42.1204 — federal successor recognition and applicable novation submissions.
• 3M–Solventum Separation and Distribution Agreement, § 2.8 — negotiated shared-contract mechanics, cited only as a wording example.

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.