How to compare material contracts in a diligence table for Private Company Acquisitions

Compare material contracts by grouping each executed agreement with its amendments, extracting consistent commercial and legal fields, and assessing those terms against the buyer’s acquisition structure and operating plan. Preserve clause-level citations and distinguish confirmed wording from missing evidence and counsel’s interpretation. The resulting diligence table should identify relationships at risk, economics or restrictions affecting valuation and integration, and findings requiring evidence, consent analysis, acquisition-agreement treatment, or an express buyer risk decision. Each material finding should have an owner and a defined resolution test.

When to use this workflow

Use this workflow when buyer’s counsel or an in-house acquisition team receives a private target’s customer, supplier, distribution, licensing, outsourcing, financing, or other operational contracts. It is particularly useful when seller summaries obscure differences or the buyer needs to compare business-critical relationships.

Set the perimeter using the proposed acquisition agreement’s material-contract categories, buyer instructions, and operational significance. A low-spend license supporting the target’s core product may deserve closer review than a larger, replaceable supply arrangement. Do not let disclosure thresholds become the sole diligence threshold.

This guide assumes US transactional practice, not a single governing state law. Contract assessments require the actual wording, applicable law, entity structure, and transaction facts. Record whether the proposed deal is an equity purchase, merger, or asset acquisition, and distinguish closing from planned later integration steps. The table supports professional analysis; it does not establish enforceability or replace specialist review.

What you need

Assemble these inputs before comparison:

• Executed agreements, amendments, statements of work, schedules, orders, side letters, and relevant notices or waivers.
• The target entity chart, acquisition perimeter, proposed deal structure, and planned post-closing transfers.
• Seller contract schedules and a document index showing stable IDs, versions, execution status, and data-room paths.
• Revenue, spend, purchase volumes, dependency assessments, and replacement information, each with its source and reporting period.
• Buyer instructions covering integration, critical relationships, acceptable restrictions, and escalation priorities.
• The acquisition agreement draft, if available, including relevant representations, disclosure schedules, and consent provisions.

Keep operating data separate from contractual commitments. Record historical purchases as historical purchases, not minimum obligations; record forecasts separately from committed revenue. Request available notices and correspondence where current term, breach status, or a waiver depends on them.

Use the template

The companion template is Private Company Acquisitions — Material contracts comparison. Copy this table into your working document or spreadsheet. Start with one row per contract family; add linked issue rows when provisions require separate decisions.

Use these field conventions:

• ID / sources: Family ID, operative document IDs, and clause or page citations for each substantive extraction.
• Parties / role: Exact contracting entities, category, and whether the target buys, sells, licenses, or distributes; identify governing law here or in the linked analysis.
• Value / dependency: Sourced financial measures, reporting period, operational importance, and replacement uncertainty.
• Term / exit: Expiration, renewal, notice window, termination triggers, and transition obligations.
• Economics / limits: Labeled summaries of pricing, commitments, exclusivity, liability formulation, and material exceptions.
• Transfer / control: Separate assignment, control changes, notice, consent, and consequences.
• Assessment / gaps: Separate sourced facts, legal interpretation, exposure, priority, and missing evidence.
• Action / owner: Next step, responsible person, decision date or milestone, status, and resolution evidence.

Repeat the schema by category for larger portfolios. Link longer extracts and analyses by stable ID. Use “not supplied,” “uncertain,” and “not located in reviewed documents” precisely rather than treating blank cells as favorable answers.

Step by step

1. Define the comparison population and buyer questions

Translate the acquisition perimeter into a review population. Include contracts held by acquired entities and identify seller-group arrangements outside the perimeter on which the business depends. Ask what evidence establishes continued access after closing.

Choose category-specific questions. Customer review should address revenue continuity and service commitments; supplier review, minimum purchases and substitution; licensing review, permitted entities, users, and uses. Financing and regulated relationships may require specialist input rather than comparison solely with ordinary operating contracts.

Record: Family ID, contracting entity, category, inclusion reason, operational dependency, and structure assumption. Maintain an exclusion record so the team can distinguish deliberate scoping from an overlooked contract.

2. Establish the operative document family

Link the base agreement to supplied amendments, orders, schedules, waivers, and side letters. Check execution and effective dates. Identify referenced documents that were not supplied and distinguish a draft from an executed version.

Read hierarchy provisions. Section 13.11 of the Molina–Bright Health stock purchase agreement incorporates schedules and related agreements and gives the agreement body precedence over inconsistencies, except expressly identified disclosure exceptions. This is a drafting example, not a default hierarchy for target contracts.

Record: Operative document IDs, hierarchy citations, execution gaps, and targeted requests. Preserve superseded versions without presenting their wording as current.

3. Extract terms without flattening differences

Read complete provisions governing term, renewal, termination, pricing, commitments, exclusivity, and liability. Follow definitions and cross-references. Capture exceptions that could change the buyer’s assessment, including restrictions relevant to combining the target with the buyer’s existing operations.

For liability, retain the measurement period, fee base, aggregate or per-claim formulation, and exclusions. “Capped at fees” conceals differences between preceding-period fees and fees payable under a particular order. Distinguish the target’s exposure from the counterparty’s exposure.

For renewal, verify the triggering date, notice method, recipient, and available evidence of earlier notices before treating a calculated deadline as settled.

Record: Concise summaries with citations, actual thresholds, qualifications, and unresolved calculations. Keep contractual amounts separate from financial-report metrics.

4. Test transaction-sensitive wording against the structure

Separate assignment restrictions, direct or indirect control changes, notice, consent, termination options, and automatic consequences. Check whose ownership matters and whether affiliates or specified transfers receive different treatment. Assess closing and later procurement or entity consolidation separately.

If the structure remains unsettled, state conditional assessments. Refer uncertain application to counsel under the relevant governing law; absence of express control-change wording is not itself a final transfer conclusion.

Do not infer an underlying requirement from a closing checklist. Section 2.4(b)(ix) and (xii) of the Granite Southeast–Roberts Family equity purchase agreement separately requires specified contract consents in full force and an executed insurance change-of-control letter. These are negotiated deliverables, not requirements governing another contract.

Record: Trigger, transaction assumption, potential consequence, uncertainty, and evidence needed.

5. Compare exposure within meaningful groups

Compare like relationships first. Customer revenue exposure and software dependency are not interchangeable because both contracts restrict termination or transfer. Use business importance, proximity of the trigger, potential disruption, evidence gaps, and alternatives to explain priority.

Identify concentrations: several significant customers approaching renewal, multiple suppliers subject to minimum purchases, or several licenses limiting affiliate use. State the common assumption behind the comparison. Avoid unexplained numerical scores that hide incomplete evidence.

Record: Relative priority, comparison group, and a sentence explaining escalation. Separate counsel’s interpretation from the business recommendation and identify whose input is still needed.

6. Convert findings into bounded buyer actions

Assign a disposition: request evidence, obtain legal interpretation, seek business input, propose acquisition-agreement treatment, develop a consent approach, or document risk acceptance. Specify what closes the issue.

Replace “confirm consent” with a defined task: obtain the executed amendment, assess the trigger against the equity purchase, and identify the required response. Coordinate counterparty outreach through the deal team. Where contractual notice timing matters, assign verification of the deadline and delivery mechanics.

Link proposed acquisition-agreement treatment to the relevant draft section or schedule entry. Keep proposed protection distinct from agreed protection and confirmed resolution.

Record: Action, owner, decision milestone, status, negotiation link, and resolution evidence. Accepted risk should identify the authorized buyer decision-maker.

7. Reconcile and verify the comparison

Reconcile the table against seller schedules, the document index, and the review perimeter. Investigate unmatched documents, schedule entries without agreements, and competing operative versions.

Reopen source clauses for high-priority findings and verify amendment effects. Have the responsible lawyer review uncertain interpretations and the business team confirm dependency assumptions. Preserve a short change history when new evidence changes an assessment.

Record: Verification status, reviewer, evidence reference, and resolved disposition or assigned open question. The completed table should distinguish “review complete” from “issue resolved.”

Worked example

Fictional scenario: Alder Reach Holdings proposes to purchase all equity in Morrow Signal Systems, a private equipment-monitoring business. Morrow will remain the contracting entity initially; procurement consolidation is planned later. All parties, documents, amounts, and provisions below are invented.

The supplied executed families include customer agreement C01, software master L01, and supply agreement S01 with amendment A01. L01 references an order that is missing. Internal reports R01 and P01 show prior-year revenue and spend; operations memo O01 identifies a key sensor dependency. No buyer closing date has been fixed, so actions use decision milestones rather than invented calendar deadlines.

MC-01 leads the transaction-trigger review because express wording raises a continuity question tied to closing. MC-02 cannot be ranked as low risk merely because spend is lower: the missing order and unknown replacement difficulty require evidence. MC-03 prompts purchasing analysis and notice preparation rather than an unsupported consent demand.

The buyer should therefore pursue three different actions, not a blanket consent campaign. None of these rows proves the issue resolved. The missing order, absent consent evidence, and unverified purchases remain visible rather than becoming presumed favorable facts.

Common mistakes

• One row per uploaded file: Amendments become disconnected. Group the family and cite the operative provision.
• Calling every restriction “consent required”: Notice, assignment, and termination rights collapse into one label. Preserve each trigger and consequence.
• Equating value with importance: Low-spend infrastructure disappears. Record dependency and replacement evidence alongside financial measures.
• Reducing liability to a number: Fee bases and exceptions vanish. Preserve the formulation and direction of exposure.
• Closing findings on seller assurances: An explanation replaces evidence. Attribute the statement and identify corroboration still needed.

Final quality check

• Every included family has a stable ID, contracting entity, and inclusion basis.
• Operative versions, amendments, execution status, and missing components are reconciled or flagged.
• Material summaries have verified clause or page citations.
• Financial metrics identify sources and periods, separately from contractual commitments.
• Transfer assessments state the structure and distinguish closing from later integration.
• Priorities explain buyer exposure, uncertainty, and relevant business input.
• Every open issue has an owner and resolution test; accepted risks identify the decision-maker.
• Resolved issues cite evidence, and review completion is not confused with resolution.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its transactional capabilities include tabular review across multiple documents. Due diligence document classification can help organize the population and prioritize human review. Use these capabilities to support the comparison while retaining lawyer verification and buyer decisions. To discuss this material-contract workflow, book a demo.

Frequently asked questions

Should every target contract receive a full comparison row?

Use the agreed perimeter and operational significance to determine review depth. Preserve an exclusion record and expand review when a dependency or transaction-sensitive restriction emerges.

How should amendments appear in the table?

Link them to the family ID, summarize the operative position, and cite the changing amendment. Retain superseded wording for verification, not as the current answer.

What if the seller says no consent is needed?

Attribute the statement. Review the executed family against the structure and request supporting waivers or consents. Keep uncertainty assigned until counsel has assessed the evidence.

Can the table replace a buyer issues memorandum?

It can support the summary, but evidence comparison and buyer decisions differ. Elevate material interpretations, negotiation choices, and unresolved commercial questions, linking them back to the table.

Sources

• Molina–Bright Health stock purchase agreement, § 13.11: incorporation and document-precedence drafting example.
• Granite Southeast–Roberts Family equity purchase agreement, § 2.4(b)(ix), (xii): distinct consent and insurance change-of-control deliverables.

These filed agreements illustrate negotiated wording, not general law or market standards.

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.