How to compare material contracts in a diligence table for Corporate Carve-Out Transactions

Compare material contracts by connecting each agreement to the acquired business, its current contracting entity, and the buyer’s proposed route to continued performance. Review complete contract sets, distinguish assignment from change-of-control provisions, and identify shared-contract, consent, economic, and transition-service dependencies. Record clause-level evidence alongside uncertainties and buyer actions in a comparison table. The deliverable is a source-backed decision record showing which arrangements can support standalone operations, which require separation or replacement, and which unresolved issues need commercial or drafting decisions.

When to use this workflow

Use this workflow when buyer’s counsel and in-house teams receive contracts for a business being separated from a larger group. Concrete triggers include parent-held software licenses, group purchasing commitments, and customer agreements covering both retained and acquired operations.

The scope is contract comparison, not a complete diligence report or closing checklist. Include target-entity contracts and outside arrangements the acquired business uses. Prioritize operational dependencies as well as value: a modest payroll contract may be essential to continuity.

This is a US-focused professional workflow guide. Transfer conclusions depend on contract language, governing law, transaction structure, and facts; cross-border arrangements require local review. SEC-filed agreements below illustrate negotiated solutions, not generally applicable rules or market standards.

What you need

Collect the proposed transaction structure and a perimeter matrix identifying the entities, assets, employees, IP, data, facilities, and services the buyer expects to receive. Establish who currently contracts for and uses each dependency, and who is expected to hold the arrangement after closing.

Obtain:

• Executed agreements, amendments, schedules, order forms, statements of work, side letters, and relevant notices.
• Shared and parent-level procurement, software, payroll, logistics, insurance, treasury, guarantee, and intercompany arrangements.
• Contract lists identifying counterparties, business users, spend or revenue attribution, and renewal information.
• Purchase-agreement drafts and schedules, proposed transition services agreement (TSA) services, and separation or replacement plans.
• Consent correspondence, counterparty proposals, and evidence supporting operational assumptions.

Give each contract family a stable ID. Distinguish unavailable documents, redactions, and incomplete execution copies. Ask business owners to identify essential arrangements absent from the seller’s material-contract list.

Use the template

Use Corporate Carve-Out Transactions — Material contracts comparison as the working record. You can copy this table into your working document or spreadsheet.

Use one row per decision-bearing arrangement. Split a shared master agreement into linked rows when services require different separation routes, retaining the common document ID.

“Entity / coverage” identifies the contracting entity and acquired-versus-retained use. “Evidence / status” records the version, clause or page citation, and completeness. Keep detailed calculations in a linked schedule, retaining decision-relevant amounts and triggers here.

Separate verified wording, interpretation, and missing evidence within cells. “Buyer decision / gap” states the response and what could change it. “Owner / priority” names an accountable function, explains urgency, and records the next review date. Reference cells by stable row and column, such as MC-014—Transfer / consent, rather than spreadsheet coordinates that change after sorting.

Step by step

1. Reconcile the contract population to the acquired business

Compare the seller’s list with the perimeter matrix and operational interviews. Ask how the business buys inputs, serves customers, processes data, pays employees, and accesses premises. Identify parent or affiliate arrangements that are not transferring with the business.

Data-room location does not establish acquisition scope. Conversely, a target-signed agreement may also support retained operations. Confirm coverage through schedules, orders, and business-owner evidence rather than the agreement title.

Record: row and document IDs, contracting entities, business coverage, and the reason the arrangement is material. Flag unconfirmed coverage and assign the missing operational evidence.

2. Establish the evidence set before comparing terms

Group masters with amendments, schedules, orders, and notices. Check execution status, effective dates, priority provisions, and whether later documents alter the terms under review. Preserve the data-room reference and reviewed version.

For each field, distinguish verified wording, not found in reviewed documents, redacted content, missing documents, and pending interpretation. “No restriction” cannot replace a missing schedule. Where documents conflict, identify the conflict before deciding which provision controls.

Record: citations and completeness in Evidence / status. Connect each document request to the field it prevents the team from resolving; do not mark an entire contract cleared because one provision was checked.

3. Compare transfer routes against the proposed structure

Read assignment, change-of-control, affiliate-transfer, partial-transfer, and subcontracting language separately. Test the asset transfer or equity acquisition, including any pre-closing reorganization, against the actual wording. Separate express language from governing-law interpretation.

For shared contracts, compare assignment, a standalone agreement, a new order, and temporary seller-supported access. Identify consent procedures, discretion, documented charges, and route-specific restrictions. Treat a proposed TSA as a bridge to investigate, not evidence that the underlying counterparty has authorized buyer access.

Record: the provision, proposed route, consent question, supporting evidence, and unresolved interpretation. State which entity would contract after closing and which business obligations would remain with the seller.

4. Compare the economics of standalone operation

Extract pricing dependencies, volume tiers, minimum purchases, exclusivity, renewal mechanisms, termination rights, and notice provisions. Determine whether retained-group volumes support pricing and whether commitments can be divided. Record a notice date only after checking its trigger and contractual counting convention.

Separate binding terms from replacement proposals and business estimates. A seller’s allocation of group spend does not establish the buyer’s contractual obligation. Compare termination or replacement costs with the proposed assumption of obligations and pre-closing breach treatment.

Section 2.04—not Section 2.02—of the Emergent–BTG agreement addresses assumed and retained liabilities, including pre-closing contract breaches and delayed-transfer contracts. Use it as a drafting example, not a conclusion about buyer exposure to third parties.

Record: economic triggers, evidence quality, liability-allocation questions, and requested pricing or drafting responses.

5. Map separation and transition dependencies

For each shared arrangement, identify the applications, people, data, facilities, vendors, and upstream services needed for performance. Compare contract availability with TSA duration and replacement readiness. Check the start event for each duration; similarly numbered service periods may not begin together.

The Seres–Nestlé TSA service schedule provides a concrete example: HR administration identifies IT.03 as a dependency, while logistics identifies vendor-contract conveyance and supporting services. Redactions limit conclusions about commercial details.

Record: service identifiers, enabling contracts, timing mismatches, and evidence supporting the bridge. Assign an operational owner to confirm scope and readiness; distinguish a planned replacement from a tested one.

6. Distinguish operational importance from negotiated deal protection

Compare each issue with purchase-agreement covenants, conditions, schedules, and remedies. Keep “needed to operate” separate from “express contractual closing condition.” Escalate critical operational gaps even when corresponding closing protection has not been negotiated.

Section 5.5(b) of the Matthews–Duravant agreement makes specified standalone shared-contract efforts dependent on a written buyer election, subject to timing and exclusions. Section 5.5(e) generally excludes missing consents or separation arrangements from determining condition satisfaction, except to the extent of a breach of Section 3.4 or 5.5. Read those provisions with the referenced conditions; an efforts covenant is not completed counterparty agreement.

Record: the buyer response—replacement, allocation language, price discussion, or requested closing protection—and its drafting reference. Label proposed protection unagreed and assign any time-sensitive election.

7. Resolve comparisons into owned decisions

Review the table with transaction counsel, procurement, finance, IT, and affected business owners. Test whether recommendations follow from cited evidence and whether operational plans match the legal route. Compare similar arrangements consistently without flattening differences in entities, services, or transaction triggers.

Tie priority to consequences: inability to operate, material unpriced obligations, time-sensitive elections, or manageable follow-up. Preserve rejected alternatives where they explain the choice.

Record: the decision, rationale, accountable owner, evidence request, and review date. Mark a row resolved only when uncertainty is resolved or expressly accepted by the authorized buyer decision-maker. Assigned follow-up remains visible even if the buyer accepts the risk.

Worked example

Fictional scenario: Alder Quay Holdings proposes an asset acquisition of Bellweather Components’ industrial-sensors division. The division uses parent-held procurement and warehouse software agreements and an affiliate logistics arrangement. All parties, documents, amounts, and provisions below are fictional.

The seller calls all three arrangements transferable. The acquisition draft assumes scheduled contracts, but schedules are incomplete and consent evidence is absent. Draft TSA service periods run from closing. Procurement has only a preliminary replacement estimate.

The comparison replaces a generic “obtain three consents” response with distinct decisions. MC-01 needs a commercial allocation as well as transfer analysis. MC-02 remains an access gap because missing permitted-user wording and vendor approval cannot be inferred. MC-03 presents a dependency mismatch even if the logistics bridge is signed. Its $24,000 proposal is not a committed operating cost. None is classified as a contractual closing condition without acquisition-agreement support.

Common mistakes

• Reviewing only target-signed contracts. Reconcile parent and affiliate arrangements to business use so essential services remain visible.
• Combining assignment and change of control. Extract both provisions and test the acquisition and related reorganizations separately.
• Treating group economics as buyer economics. Distinguish contractual commitments, management allocations, and unaccepted standalone offers.
• Using a TSA reference as proof of continuity. Verify scope, permissions, upstream dependencies, and replacement readiness.
• Calling a consent issue a closing blocker without support. Separate operational severity from negotiated conditions and identify requested protection.

Final quality check

• Every material dependency has a row or an identified evidence gap.
• Each row identifies the contracting entity and acquired-versus-retained coverage.
• Citations match reviewed versions, amendments, and relevant schedules.
• Missing, redacted, and unreviewed evidence is distinct from verified wording.
• Transfer conclusions reflect the structure; interpretation questions are assigned to counsel.
• Economics distinguish binding terms, allocations, estimates, and proposals.
• TSA periods and dependencies are checked against their actual start events.
• Every open issue has an owner and decision path; accepted uncertainty identifies the authorized decision-maker.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its transactional capabilities include tabular review across documents, while due diligence classification can organize the population and prioritize human review. For focused contract review in Word, lawyers can select the represented party or neither and provide deal-specific instructions; findings quote clauses, locate text, rank severity, and identify missing language as not present. Keep source validation, legal interpretation, and buyer decisions with the legal team. Book a demo to discuss this comparison workflow.

Frequently asked questions

Should every contract receive the same depth of review?

No. Prioritize loss of access, replacement cost, restrictive terms, and shared use. Record the scope of each review so a limited comparison is not mistaken for clearance of the entire agreement.

How should a shared master agreement appear in the table?

Retain a common contract-family ID. Create linked rows when orders, services, or business lines need different actions, and identify obligations that remain shared rather than implying each row is independent.

Can the buyer rely on the seller’s transferability summary?

Use it as a statement to verify. Request operative provisions and consent evidence. Preserve any disagreement between the summary and reviewed documents as an issue requiring explanation, not an assumption to overwrite.

When is a row ready to close?

When sources are checked, the response is agreed, and uncertainty is resolved or expressly accepted by the authorized decision-maker. A sent request or draft consent does not evidence completed counterparty action; retain assigned follow-up separately.

Sources

• Emergent–BTG Stock and Asset Purchase Agreement, Section 2.04: negotiated assumed and retained liability provisions.
• Matthews–Duravant Equity Purchase Agreement, Section 5.5: shared-contract elections, efforts, and condition qualifications.
• Seres–Nestlé Transition Services Agreement, Schedule of Services: documented service dependencies.

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.