How to compare material contracts in a diligence table for Business Merger Transactions

Compare material contracts by reviewing complete contract families against consistent fields, then separating contractual wording from its effect on the proposed merger. For the acquirer, the deliverable is a source-linked table showing which relationships may require consent or notice, permit termination, constrain integration, or create financial exposure. Each finding should identify the affected target entity, controlling provision, unresolved evidence, and accountable decision-maker. Use the table to prioritize legal and commercial decisions—not to turn incomplete documents into apparently settled conclusions.

When to use this workflow

Use this workflow when an acquirer’s legal team has received contracts but needs a disciplined basis for comparison, follow-up requests, and deal decisions. Typical triggers include an initial data-room population, a draft material-contracts disclosure schedule, or a revised merger structure that changes the analysis.

The scope is contract comparison, not a complete merger closing checklist. Cover customer, supplier, distribution, licensing, debt, lease, and other relationships selected for this transaction. Include contracts that constrain the combined business even when their revenue or spend is modest.

This guide uses a US baseline with Delaware corporate-merger context. Other formation jurisdictions, entity types, and contractual governing laws need separate analysis. Under Delaware Code §259(a), constituent corporations’ property and rights vest in the survivor, and their liabilities and duties attach to it. That succession rule is not a contract-specific consent determination: analyze the wording, transaction structure, and applicable law separately. (delcode.delaware.gov)

What you need

Collect these inputs before substantive comparison:

• Structure information: constituent entities, proposed survivor, ownership changes, and contemplated post-closing transfers or integration steps.
• Complete contract families: executed agreements, amendments, schedules, statements of work, order forms, incorporated terms, side letters, waivers, and existing consents.
• Scope criteria: the draft merger agreement’s Material Contract definition, disclosure schedules, and additional acquirer priorities.
• Business context: relationship owner, revenue or spend with its measurement period, operational dependence, replacement options, and known disputes.
• Review instructions: priority issues, escalation criteria, authorized reviewers, and restrictions on sensitive information or counterparty contact.
• Document index: stable IDs, filenames, data-room locations, versions, execution status, and amendment relationships.

Do not treat a negotiated Material Contract definition as a universal threshold. Section 3.18(a) of the SEC-filed Dayforce/Dawn merger agreement defines Material Contracts for that agreement and requires a corresponding disclosure-letter list. It illustrates deal-specific scope and disclosure architecture, not a general review threshold. (sec.gov)

Use the template

Use Business Merger Transactions — Material contracts comparison as your working table. You can copy this table into your working document or spreadsheet.

Use one row per contract family and comparison topic. Repeat the stable family ID across related rows so assignment analysis remains distinct from pricing or liability analysis without losing the relationship between findings.

Source / evidence identifies the document ID, clause, and page, with a short quotation or precise paraphrase. Cite the controlling amendment, not just the original provision. Link business inputs separately so revenue figures are not mistaken for contract terms. Compared terms contains factual extraction; Merger effect / uncertainty contains interpretation and dependencies.

Use consistent topics: term/renewal, termination, assignment, change of control, consent/notice, exclusivity, pricing, liability, and governing law. Add categories such as sublicensing or minimum purchases where needed. Do not force unlike contracts into false equivalence.

Use Priority / action for significance, scope basis, next action, and escalation timing. Use Owner / status for an accountable reviewer or role and the decision state: awaiting documents, legal analysis, business decision, action in progress, accepted risk, or resolved. Link lengthy reasoning or approval evidence through a stable issue ID rather than burying it in a cell.

Step by step

1. Define the comparison population

Start with the proposed Material Contract definition and disclosed list. Reconcile them against the data-room index and business-team relationship lists. Identify contracts outside the negotiated definition that matter to continuity or integration.

Separate disclosure scope from review scope. A low-spend exclusive supply arrangement may warrant detailed review because replacement is difficult. A high-value expired agreement may instead require confirmation of continuing orders and the terms governing them.

Record: family ID, parties, contract type, scope basis, and initial priority. Put the scope basis in the action cell or a linked note. Flag discrepancies for follow-up; do not silently remove undisclosed contracts.

2. Establish the controlling contract family

Group the executed agreement with amendments, orders, schedules, and incorporated terms. Check execution status, effective dates, affected entities, and order-of-precedence language. An amendment may change assignment rights while leaving termination provisions untouched.

Preserve superseded text as history, but identify the controlling document for each topic. If incorporated online terms are missing, request the applicable version rather than substituting today’s website language. Distinguish an unavailable schedule from confirmation that none exists.

Record: source IDs and controlling provisions. Where completeness is uncertain, state what is missing and which conclusion it prevents. Retain the reviewed-document list in the linked family index.

3. Extract terms into comparable fields

Review the same core topics across every family, separating genuine inapplicability from missing information. Capture duration, renewal, termination, assignment, change of control, consent and notice, exclusivity, pricing, liability, and governing law.

Preserve defined terms and qualifiers. For liability, identify the cap’s basis, measurement period, exclusions, and separate limits rather than entering one number. For pricing, distinguish fixed charges, minimum commitments, volume adjustments, and unilateral change rights. For renewal, capture the notice window, recipient, and delivery method.

Record: concise factual terms with clause/page citations. Use “not located in reviewed documents” only with an identified review set. It does not establish absence across an incomplete family.

4. Apply the actual merger structure

Compare assignment and change-of-control wording against the specific entities and transaction steps. Check references to merger, transfers by operation of law, direct or indirect control changes, affiliate transfers, and later movement to an integration entity.

Distinguish a potential trigger from its consequence. Record whether the text calls for notice, prior consent, a termination option, or another response. Do not treat these consequences as interchangeable or assume an exception covers every integration step.

Record: the relevant transaction fact, provisional interpretation, and remaining legal question. Identify whether the concern arises at signing, closing, legal effectiveness, or a later action. For notices, capture the contractual mechanics and any unresolved recipient information.

5. Compare commercial exposure across relationships

Group related rows by topic and business dependency. Compare customer termination exposure, supplier continuity, territorial exclusivity, license restrictions, and recurring commitments within meaningful groups—not one undifferentiated ranking.

Keep economic bases visible. Comparing a fee-based liability cap with a fixed-dollar cap requires the applicable period, exclusions, and relevant exposure. Ask finance to validate commercial figures. Avoid double-counting master-agreement and order-level spend when assessing concentration.

Record: exposure, supporting business input, and priority rationale. Escalate concentrated risks and repeated restrictions that could collectively constrain integration. Label unquantified exposure explicitly rather than inventing an aggregate amount.

6. Convert findings into bounded actions

Choose the next decision for each material finding: request evidence, obtain legal analysis, seek consent or waiver, propose an amendment, revise integration plans, or ask an authorized business owner to accept exposure.

Link the finding to the relevant merger-agreement representation, disclosure exception, covenant, or condition where applicable. Compare the actual drafting; do not automatically label every desired consent a closing condition. Identify proposed negotiating positions separately from existing obligations.

Record: action, owner, decision dependency, deal-document reference, and escalation point. Route counterparty outreach through the deal team. Keep detailed consent preparation and closing administration in their respective trackers, linked to the comparison row.

7. Verify and release the comparison

Have the responsible lawyer verify material findings against the sources, exceptions, and amendment history. Resolve conflicts between rows before circulating a summary. When new documents change an assessment, update the affected rows and preserve the reason.

Close an issue only with supporting evidence or an authorized decision appropriate to that issue. A requested consent is not an obtained consent. Acceptance of commercial exposure does not establish contractual compliance.

Record: reviewer, review date, resolution evidence, or the named owner of an open question in the status cell or linked note. Release a dated version whose summary priorities reconcile to the underlying rows.

Worked example

Fictional scenario: Harborline Analytics, Inc. proposes to acquire Cedar Vale Systems, Inc. through a merger of Harborline’s acquisition subsidiary into Cedar Vale, with Cedar Vale surviving as Harborline’s subsidiary. Harborline plans to move customer servicing to another affiliate after closing. All parties, documents, provisions, and amounts below are fictional.

The population includes a principal customer agreement, a component supply arrangement, and a software license. The business team initially groups all three as consent matters. Comparison distinguishes a potential merger-triggered consent, a continuity gap, and a later operating-model restriction.

Orion warrants focused consent analysis despite Cedar Vale’s survival. Its revenue supports priority but does not establish the legal consequence of failing to obtain consent. Birchstone needs evidence and an operational response, not an invented minimum-purchase figure. Juniper requires review of the missing user terms before concluding that the affiliate lacks permission.

These findings do not establish that all three matters must prevent closing. The deal team must determine the contractual implications, deal-document treatment, and authorized commercial response. The comparison preserves those distinctions rather than converting every high-priority row into a closing blocker.

Common mistakes

• Reviewing only the base agreement. Establish controlling amendments and incorporated terms before comparing conclusions.
• Treating survival as contractual clearance. Analyze merger, control, assignment, and later integration events separately.
• Using “none” for incomplete evidence. Identify the missing document and the conclusion it prevents.
• Ranking contracts only by value. Include operational dependence, replacement difficulty, exclusivity, and integration restrictions.
• Calling a requested consent resolved. Require evidence of the relevant consent or document an authorized risk decision without relabeling it contractual compliance.

Final quality check

• Each family identifies the actual contracting entity and counterparty.
• Executed versions, amendments, and incorporated materials are reconciled or explicitly missing.
• Material findings have verified document, clause, and page references.
• Extracted terms remain separate from interpretation and business assumptions.
• Merger triggers and later integration restrictions are distinguished.
• Priority rests on documented exposure and dependencies, without double-counting.
• Open issues have accountable owners; resolved or accepted-risk items have supporting records.
• The dated summary reconciles to the released comparison rows.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities include tabular review across multiple documents and bulk classification to organize review populations and prioritize human attention. Its contract review workflow accepts deal-specific instructions and presents source-linked findings. Lawyers retain responsibility for completeness checks, merger-structure analysis, and recommendations. To assess this workflow against your contract population, book a demo. (decover.ai)

Frequently asked questions

Should every contract receive the same review depth?

No. Apply consistent core screening, then increase depth for significant relationships, incomplete families, unusual restrictions, and integration dependencies. Record why a family received lighter review and which topics remain unchecked.

How should we handle several orders under one master agreement?

Keep a shared family ID. Add rows where orders change pricing, duration, termination, liability, or contracting entity. Check precedence and aggregate commitments without counting the same economic obligation twice.

Can the table say no consent is required?

Record that conclusion only after responsible counsel reviews the relevant wording, completeness, structure, and applicable law. Limit it to the analyzed event: clearance for the merger does not necessarily cover subsequent affiliate transfers or use.

What if the disclosure schedule and uploaded contracts disagree?

Preserve both sources and open a reconciliation item. Determine whether the discrepancy reflects an omitted contract, different scope criteria, superseded wording, or an incomplete upload. Do not silently rewrite the seller’s disclosure position.

Sources

• Delaware Code, Title 8, §259(a): statutory succession in Delaware mergers; not an individual contract-trigger determination.
• SEC-filed Dayforce/Dawn merger agreement, §3.18(a): historical example of negotiated Material Contract scope and disclosure architecture, not a market standard.

Scope: General professional workflow guidance using the October 13, 2026 research cutoff. Recommendations are not legal mandates; contract conclusions depend on actual language, governing law, facts, and deal context.

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.