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

Compare material contracts by separating contributed contracts, new venture agreements, and participant-affiliate arrangements, then testing each against the venture’s operating model. Record clause-level evidence, transfer and consent requirements, economic commitments, operating rights, and exit consequences in one comparison table. For the represented participant, the deliverable is an evidence-backed decision record showing which contracts support the proposed contribution, which create conflicting obligations, and which require consent, amendment, replacement, or authorized risk acceptance before signing, funding, transfer, or operational launch.

When to use this workflow

Use this workflow when a participant’s legal team must evaluate the contracts supporting a proposed business joint venture: customer relationships, supply commitments, technology licenses, premises, services, and affiliate support. Typical triggers include agreeing the contribution perimeter, reviewing draft venture documents, or testing whether the venture can operate independently after launch.

The scope is contract comparison, not a complete diligence investigation. Prioritize contracts whose absence or restriction could impair revenue, essential inputs, technology access, funding, or continuity. A low-value but irreplaceable license may deserve more attention than a large purchase order with readily available alternatives.

This guide uses a U.S. commercial-transaction perspective. Entity law, contract governing law, asset location, and operating jurisdictions may differ. Contract conclusions depend on the actual wording, applicable law, facts, and deal structure. Regulatory approvals, tax, competition, foreign-investment restrictions, and transfer effectiveness require separate analysis where relevant.

What you need

Obtain the proposed ownership and operating structure, the represented participant’s objectives, and a description of what each participant will contribute or retain. Request:

• Executed material contracts, amendments, schedules, side letters, waivers, and consent evidence.
• Draft venture and contribution documents, IP licenses, supply agreements, transition services, guarantees, and affiliate commitments.
• A contract-to-business map identifying customers, suppliers, technology, facilities, and services needed for launch.
• Ownership, lien, performance, dispute, and renewal information, with business contacts responsible for confirming facts.
• Participant review instructions covering unacceptable restrictions, continuity needs, economic exposure, and escalation authority.

Build a supporting document index with stable IDs, parties, agreement family, execution status, amendment chain, and missing attachments. Preserve superseded versions without confusing them with operative documents. Request incorporated purchasing terms and order forms where they affect the comparison.

Use the template

Use Business Joint Venture Transactions — Material contracts comparison as the working table. You can copy this table into your working document or spreadsheet. Create one row per material issue within a contract family; do not force an entire agreement into one cell.

“Contract / role” distinguishes contributed contracts, new venture contracts, and retained participant or affiliate arrangements. Identify the actual contracting entities, not just their group names. “Evidence” contains the document ID, clause and page, execution status, and controlling amendment.

“Economics / rights” captures comparable terms, including relevant units, currencies, and timing formulas. “JV dependency / exit” connects those terms to another agreement or operating requirement. “Gap / impact” separates missing evidence from an adverse provision and states the participant’s exposure.

The final column records the response, accountable owner, decision authority, target milestone, status, and resolution evidence. Use stable row references, such as R-04, to link related issues. Where a cell becomes unwieldy, reference a supporting analysis rather than removing qualifications.

Step by step

1. Set the participant’s comparison questions

Start with the intended transaction mechanics. Is the participant transferring an existing business, licensing technology, contributing services, or committing to buy output? Determine which entity must hold each operating right and which participant remains responsible for performance.

Write a focused instruction: “Identify contracts that restrict transfer to the venture, require continuing participant guarantees, or terminate before replacement supply is available.” Identify the intended milestone for each dependency; a signing issue may differ from a launch issue.

Record: contract role, intended venture use, participant-specific question, and affected milestone. Mark uncertain transaction mechanics as assumptions requiring confirmation.

2. Establish the operative contract set

Group each base agreement with its amendments, orders, schedules, incorporated terms, and waivers. Reconcile party names against the proposed contribution perimeter. Do not treat an affiliate’s contract as the participant’s asset without establishing the relevant ownership and transfer arrangements.

Distinguish signed documents from negotiated drafts. If pricing resides in an absent schedule, record that absence rather than treating the agreement as economically complete. Where versions conflict, ask the document owner to establish which controls.

Record: document IDs, execution status, operative amendment references, and missing materials. Assign unresolved version questions before relying on the disputed wording.

3. Normalize terms without erasing differences

Compare like terms across each contract family: assignment, change of control, consent, exclusivity, minimum purchases, pricing, IP use, termination, and survival. Preserve trigger definitions, exceptions, timing formulas, and the obligated entity. Distinguish a committed minimum from a forecast and an automatic renewal from a discretionary extension.

Separate contribution commitments from affiliate operating undertakings. As a negotiated example, the Danone–Weight Watchers agreement addresses capital contributions and DAP’s responsibility for affiliate performance separately in § 6.1. This illustrates a comparison question, not a universal responsibility allocation (filed agreement, § 6.1).

Record: concise term summaries with pinpoint references. Explain noncomparable terms rather than giving them identical labels.

4. Test transfer and operating continuity separately

Compare the proposed mechanics with the assignment and change-of-control wording. An asset contribution and an equity investment pose different questions; test the actual structure rather than assuming the same clause governs both. Identify the consent giver, exceptions, conditions, and evidence needed for any proposed reliance.

Then ask whether the venture receives usable rights. A supply agreement may cover only specified facilities; a technology license may permit participant use while leaving venture access unresolved. Transfer consent alone may not cure those limits.

Record: transfer question, operating restriction, affected milestone, and proposed consent, amendment, replacement, or legal analysis. Distinguish consent requested, consent received, and consent verified as sufficient for the proposed transaction.

5. Reconcile economics and contribution dependencies

Compare minimum purchases, exclusivity, price adjustments, service charges, guarantees, and contribution promises against the operating plan. Identify obligations remaining with the participant although the venture receives the benefit. Ask finance to validate quantities, prices, and allocation assumptions; do not manufacture missing inputs.

For a Delaware LLC, § 18-501 permits property, services, and contribution promises as well as cash. Section 18-502 addresses performance obligations, conditional contributions, and agreement-specified default consequences. Apply these provisions only where Delaware LLC law governs; do not infer a remedy absent from the relevant agreement (Delaware LLC Act, §§ 18-501–18-502).

For comparison purposes, distinguish the promised contribution, agreed value, conditions, and separate contract needed to deliver it. Flag an unconditional contribution promise dependent on an unresolved supplier consent.

Record: economic exposure, source assumptions, linked contribution clauses, conditions, and the owner of each valuation or performance question.

6. Compare termination and exit across agreements

Read the venture agreement beside essential supply, license, services, and guarantee arrangements. Test withdrawal, equity transfer, deadlock buyout, breach, and ordinary expiry separately. Ask what continues, for how long, at whose cost, and under which document. Include notice, cure, transition assistance, and any necessary release.

The Weichai–Ballard agreement subjects specified exclusive procurement to a separate supply agreement. Article 27.7 provides a six-month continuation period for specified ancillary agreements after a participant ceases holding equity, followed by termination under their terms. These are negotiated dependencies, not general continuity rules (filed agreement, Articles 13.2 and 27.7).

Record: scenario, linked clauses, continuity gap, and proposed response. Do not infer unavailable ancillary terms.

7. Turn comparisons into assigned decisions

Rank issues using participant priorities and available evidence. A verified restriction and an unresolved question can both require escalation, but their remedies differ. State why the issue matters: inability to transfer revenue, uncertain launch cost, continuing liability, or loss of essential technology.

Translate each discrepancy into a request: obtain consent, amend wording, clarify affiliate responsibility, confirm pricing, arrange replacement supply, or seek authorized risk acceptance. Link the affected contribution provision, representation, covenant, indemnity, or governance decision where relevant.

Record: action, owner, decision authority, target milestone, and evidence needed to close the row. Preserve the original finding alongside the resolution so reviewers can follow the reasoning.

Worked example

Fictional scenario: Alder Process Systems proposes contributing a component business to a venture with Bracken Industrial Holdings. Counsel represents Alder. Alder will license process technology, and its affiliate will provide maintenance services. The operating plan assumes uninterrupted supply, technology access after an equity exit, and fixed launch-period maintenance charges.

The review set contains executed supplier agreement S-01, draft venture agreement J-01, draft technology license L-02, and draft affiliate services agreement A-03. Supplier consent has not been produced; the services pricing schedule is absent. All parties, documents, clauses, and commercial facts below are fictional.

R-01 prevents the team from equating a contract list with transfer readiness. R-02 requires Alder to decide whether and on what terms it will permit continued technology use; the operating plan alone does not establish that commitment. R-03 requires evidence before a price adjustment can be justified. None of the rows establishes consent refusal, an acceptable post-exit royalty, or an excessive maintenance charge.

Common mistakes

• Comparing titles instead of roles. Identify the obligor, beneficiary, facility, and venture use before grouping contracts.
• Treating silence as permission. Specify the documents reviewed and request missing incorporated terms before drawing a conclusion.
• Using equity percentages to infer contractual rights. Map contribution, consent, signing, and performance responsibilities separately.
• Reviewing exit only in the venture agreement. Test essential licenses, supply, services, and guarantees against each relevant scenario.
• Closing an issue on a promise. Keep “consent expected” open until the designated reviewer verifies consent or approves an alternative.

Final quality check

• Every material operating dependency has a row or an explicit missing-document entry.
• Entity names and contributed, retained, and new-contract roles match the proposed structure.
• Evidence references identify operative clauses, amendments, schedules, and execution status.
• Transfer analysis remains separate from operating-rights analysis.
• Economic and timing assumptions are distinguishable from verified terms.
• Exit conclusions identify the scenario and dependent agreements reviewed.
• Legal propositions are checked against applicable primary sources; filed examples are not treated as governing law.
• Open issues have owners, decision authority, and milestones; resolutions have evidence or documented risk acceptance.

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 materials and prioritize human review; tabular review supports comparison across multiple documents. In contract review in Word, lawyers can choose the represented party, provide deal-specific instructions, and assess findings that quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers verify findings and edit or insert suggestions as ordinary tracked changes. To discuss this participant-side workflow, book a demo.

Frequently asked questions

Should every contract receive the same review depth?

No. Prioritize operating dependency, economic exposure, transfer sensitivity, and replacement options. Record the review scope so a targeted check is not mistaken for comprehensive clearance.

How should affiliate contracts appear?

Identify the affiliate as the actual party and describe the venture’s dependency. Separately cite any participant undertaking concerning affiliate performance; do not merge distinct responsibilities.

Can a public filing establish acceptable terms?

It can illustrate wording, not suitability or market standards. The Weichai–Ballard filing includes redacted provisions. Obtain complete transaction documents rather than filling gaps from another venture’s arrangements.

When is the comparison ready for decision-makers?

When findings are traceable, uncertainties are explicit, and each requested decision has an owner and rationale. Material open issues may remain, but identify the milestone they affect and who must resolve or accept them.

Sources

• Delaware Limited Liability Company Act, §§ 18-501–18-502: contribution forms, conditional obligations, and default consequences.
• SEC-filed Weichai–Ballard Joint Venture Agreement: procurement and ancillary-agreement dependencies.
• SEC-filed Danone–Weight Watchers Joint Venture Agreement: contribution and affiliate-performance allocation.

The filed agreements concern China-focused ventures. They illustrate negotiated document relationships, not U.S. law or current foreign-law requirements.

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.