How to prepare a due diligence request list for Business Joint Venture Transactions

Prepare a participant-side joint venture diligence request list by mapping each party’s contributions, the venture’s operating dependencies, and your client’s funding and control exposure. Translate those dependencies into evidence requests directed to the correct entity. Give each request a priority, decision gate, responding owner, and completion test. The resulting deliverable is a controlled list linking documents and unanswered questions to investment, drafting, or operating decisions—not a generic demand for corporate records or a premature conclusion that the venture is ready to proceed.

When to use this workflow

Use this workflow when a term sheet, contribution outline, or commercial model identifies who will provide capital, equipment, technology, personnel, customers, and services. It serves participant counsel and in-house teams preparing an initial request list or refining requests after reviewing draft venture documents.

The task is evidence collection, not a complete diligence report or closing checklist. Separate formation, signing, funding, asset transfer, and operational launch: evidence needed for one decision may not satisfy another.

This guide uses a US commercial-transaction perspective. Delaware LLC rules apply only where that entity law governs; contractual ventures and other entity forms require different analysis. Regulatory, tax, competition, foreign-investment, and transfer-effectiveness questions need jurisdiction-specific specialist input. The China-focused filed agreements cited below illustrate negotiated document relationships, not US law or current foreign-law requirements.

What you need

Start with the current term sheet, draft venture agreement, ownership diagram, proposed capitalization, business plan, and contribution schedule. Obtain your client’s investment criteria, approval process, and limits on additional funding, guarantees, or operational support.

The contribution schedule should distinguish cash, transferred assets, licensed technology, leased premises, services, secondments, and retained assets. Identify each provider, recipient, valuation basis, and intended availability date. Do not group an affiliate-owned asset under the participant’s name without checking the proposed transfer or license arrangement.

Also assemble:

• Organizational documents, authority records, financing commitments, and available encumbrance information.
• Contributed contracts and proposed supply, distribution, IP, services, and affiliate agreements.
• The document-room index, confidentiality arrangements, and access restrictions.
• Known permit, workforce, customer-consent, and IP provenance dependencies.

Draft requests before every document arrives. Identify preliminary assumptions so they generate questions rather than unsupported findings.

Use the template

Use the Business Joint Venture Transactions — Diligence request list. You can copy this table into your working document or spreadsheet.

Assign requests stable IDs such as R-001 and documents separate IDs such as D-001. “Subject/entity” distinguishes your participant, counterparty, contributed business, venture, and relevant affiliates.

“Evidence requested” specifies documents, coverage, and explanations. “Decision/dependency” states why the response matters. “Priority/gate” identifies significance and the decision point, such as signing approval or funding.

“Owner/access” identifies the responder and permitted recipients. In “Source/status,” cite document IDs and clauses or pages; distinguish received, incomplete, unavailable, and verified. A received document is not necessarily a completed response.

Use “Next action/closure” for the remaining question, internal decision owner, and completion test. For example, closure may require reviewing an executed license and its schedules, not merely receiving a draft. Keep extensive findings in a linked issues record, using the request ID to preserve traceability.

Step by step

1. Define the participant’s exposure and diligence perimeter

Write a scope statement identifying your client’s proposed interest, contribution, commercial role, guarantees, and reliance on the other participant. A minority cash investor needs different evidence from a technology owner licensing its core platform.

Map essential functions to their providers. Determine whether equipment, customer contracts, personnel, or financing sit within the contribution perimeter or remain with a participant’s affiliate. Request historical operating information only where it helps test the contributed business or proposed operating assumptions.

Record: Entity-specific request categories, supported investment decisions, and specialist referrals. Assign responsibility for excluded subjects rather than silently omitting them.

2. Turn each contribution into an evidence package

For cash, request commitments, conditions, payment mechanics, and evidence supporting availability. For property, request ownership records, liens, valuation support, transfer documents, and relevant consent provisions. For technology and services, request rights provenance, scope, duration, delivery criteria, capacity, and replacement arrangements.

Delaware LLC contributions may include cash, property, services, and promises to contribute. Unless the LLC agreement provides otherwise, a member must perform its contribution promise; failure to contribute required property or services can give the company an option to require cash equal to the unperformed agreed value recorded by the LLC. Request the promise and recorded valuation rather than relying on a budget entry. See Delaware LLC Act §§ 18-501–18-502(a).

Record: Separate requests for the commitment, valuation, ownership or capacity, and proposed delivery evidence. Distinguish transferred ownership from permission to use an asset.

3. Identify conditions before setting request priorities

Separate signing, funding, transfer, and launch dependencies. Ask when each obligation becomes due, which conditions apply, who may waive them, and what evidence demonstrates satisfaction.

For Delaware LLCs, conditional contribution obligations cannot be enforced until their conditions are satisfied or waived as specified in § 18-502(b). Section 18-502(c) permits the LLC agreement to specify contribution-default consequences. Neither provision proves that a particular capital call or remedy applies to your deal. See § 18-502(b)–(c).

As a negotiated example, Weichai–Ballard Article 6.5 links contributions to specified documents, a business license, an account, and other conditions. Its contribution timing in Article 6.4 is redacted, so the filing cannot establish that timetable. See the filed agreement, Articles 6.4–6.5.

Record: Each request’s gate, condition reference, and missing evidence. Prioritize decision-blocking gaps without treating receipt as substantive satisfaction.

4. Request the full operating agreement family

Request contributed customer contracts separately from new venture contracts and participant-affiliate arrangements. Include schedules, amendments, side letters, and incorporated documents. Identify the actual obligor where an affiliate will supply personnel, equipment, or services.

Target assignment and change-of-control language, consent requirements, exclusivity, minimum purchases, pricing, IP scope, termination, and survival. Ask which arrangements are indispensable to launch and which can be replaced, at what cost.

Weichai–Ballard Article 13.2 makes specified procurement subject to a separate supply agreement; Article 27.7 provides a continuation period for certain ancillary agreements following a participant’s equity exit. These negotiated dependencies explain why reviewing the main agreement alone is insufficient. See Articles 13.2 and 27.7.

Record: Linked requests for each agreement family, missing attachments, responsible entities, and affected operating dependencies.

5. Test governance, funding, and exit together

Request voting arrangements, reserved matters, delegation instruments, signing authority, funding approvals, and deadlock procedures. Distinguish economic ownership from approval rights and authority to bind the entity.

Delaware LLC § 18-402 supplies management and authority defaults unless the agreement provides otherwise, including member management tied to profit interests and default binding authority for members and managers. A capitalization table alone therefore does not establish the negotiated control arrangement. See Delaware LLC Act § 18-402.

Test disagreement over additional funding or an essential operating contract. Request valuation procedures, buyout funding assumptions, transfer restrictions, guarantee releases, and continuing technology or supply rights. Danone–Weight Watchers § 8.10 assigns different valuation and election roles and preserves a license in a defined exit scenario; these are negotiated provisions, not default remedies. See § 8.10.

Record: Scenario-specific requests and the commercial owner who must assess the resulting exposure.

6. Make requests answerable and control access

Replace “provide all IP documents” with a bounded request identifying the proposed licensed technology, ownership chain, relevant licenses, restrictions, and unresolved provenance gaps. Specify whether you need an executed document, draft, factual explanation, or confirmation that no document exists.

Assign a responding entity and owner. Agree handling for sensitive pricing, customer, personnel, and technical information before circulation. Refer competitor-sensitive disclosures and uncertain confidentiality arrangements to counsel; ordinary document-room access should not be the assumed solution.

Record: Scope, responder, access limitation, and agreed response target. Keep administrative targets separate from contractual deadlines, and identify alternatives where disclosure is restricted.

7. Reconcile responses and issue the controlled list

Check each response against its completion test. A file marked “final” may be unsigned; an executed agreement may lack schedules. Maintain an index showing version, execution status, amendment chain, redactions, and restrictions. Preserve superseded drafts without confusing them with operative documents.

Split partial responses into focused follow-ups. If evidence remains unavailable, assign the decision whether to seek substitute evidence, negotiate protection, defer commitment, or accept uncertainty. Risk acceptance can resolve a decision without verifying the underlying fact; record that distinction.

Record: Source citations, residual gaps, decision owners, and closure evidence. Issue a dated list with stable IDs and retain response history.

Worked example

Fictional scenario: Cedar Arc Components proposes to invest $7 million for a 40% interest in a Delaware LLC venture with Lumen Quay Systems. Lumen would provide equipment, a technology license, and launch support. Cedar’s investment committee must decide whether to authorize signing before transfer preparations are complete.

All parties, amounts, documents, and provisions in this example are fictional. The team has draft venture agreement D-001, equipment schedule D-002, and draft license D-003. D-001 § 4.2 makes the equipment contribution subject to financing releases. Its governance provision refers to an absent reserved-matters schedule. D-002 lists machines but supplies no ownership evidence. D-003 § 9.3 links license termination to Lumen ceasing to hold equity. No release evidence or alternative license has been supplied.

R-001 does not prove defective title: it identifies missing evidence and a funding dependency. R-002 presents a textual continuity concern requiring negotiation or a credible replacement plan. R-003 establishes neither adequate nor inadequate minority protection because the relevant terms are absent.

Cedar can distinguish information needed before signing approval from evidence required before funding. Any decision to proceed should identify the remaining uncertainty and agreed protection; the request list itself does not authorize funding or establish satisfaction of conditions.

Common mistakes

• Sending a generic acquisition list. Organize requests around shared control, participant commitments, and dependence on retained businesses.
• Treating affiliates as interchangeable. Identify the asset owner, provider, and obligor; request supporting evidence from the correct entity.
• Closing requests on receipt. Verify execution, attachments, amendment chains, and substantive responsiveness.
• Giving every request equal priority. Tie priority to a decision gate and explain the missing evidence’s effect.
• Assuming equity exit ends operating dependence. Request continuing licenses, supply, transition support, and guarantee arrangements.

Final quality check

• Material contributions have commitment, ownership or capacity, valuation, and delivery requests.
• Participant, counterparty, affiliate, contributed-business, and venture records are distinguishable.
• Funding conditions are separate from signing and launch requirements.
• Requests identify responders, priorities, decision gates, and completion tests.
• Source references match the correct version and clause or page.
• Missing schedules, redactions, and unsigned documents remain visible.
• Open issues are resolved or assigned; accepted uncertainty is not marked verified.
• Access restrictions and permitted recipients are confirmed.

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. Contract review and tabular review can support examination across venture and ancillary agreements. Lawyers define requests, verify source evidence, and determine whether responses are sufficient. To discuss this participant-side workflow, book a demo.

Frequently asked questions

Should we request documents about our own participant?

Yes. Check your client’s contribution ownership, authority, funding commitments, and delivery capacity. Route internal requests to responsible business owners rather than assuming the negotiating team has verified those facts.

How do we handle an unformed venture?

Request proposed documents, responsible preparers, and expected completion evidence. Distinguish documents not yet created from existing documents missing or withheld. Assign future deliverables to the appropriate gate.

When should a request move to the issues list?

Create a linked issue when a response or unresolved gap requires a drafting, economic, consent, or risk-acceptance decision. Keep the request open if evidence remains outstanding; an issue entry does not replace follow-up.

Can public filings replace direct requests?

Use them to identify agreement architecture, not to establish your deal’s facts. Filings may omit schedules or redact terms. Obtain complete operative documents rather than filling gaps with another venture’s wording.

Sources

The legal scope follows the October 13, 2026 research brief. Filed agreements illustrate negotiated provisions, not market standards.

• Delaware LLC Act, Subchapter V: Finance, §§ 18-501–18-502
• Delaware LLC Act, Subchapter IV: Managers, § 18-402
• SEC-filed Weichai–Ballard Joint Venture Agreement
• SEC-filed Danone–Weight Watchers Joint Venture Agreement

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.