How to organize a legal due diligence document index for Project Finance Transactions

Organize a sponsor-side project finance diligence index around project entities, assets, document families and financing milestones—not upload order. Assign stable document identifiers, preserve execution and version evidence, and connect each agreement to its amendments, attachments, consents and financing purpose. Distinguish documents supplied from facts verified and conditions accepted. The resulting deliverable is a source-linked index that lets counsel locate the relevant records, identify missing evidence and assign targeted requests without treating a populated data room as proof that funding requirements are satisfied.

When to use this workflow

Use this workflow when sponsor counsel or an in-house team prepares a financing data room, receives lender diligence requests, or inherits records assembled by development and construction teams. It is especially useful where project companies, sites or phases share infrastructure, suppliers or sponsor support.

The scope is document identification, organization and verification—not substantive diligence clearance or management of every funding condition. This guide uses a US transactional perspective. The cited agreements illustrate negotiated obligations, not general law or market standards. Contract interpretation, permit sufficiency and security perfection require separate analysis under the operative documents and applicable law.

What you need

Collect these inputs before assessing completeness:

• Project map: sponsor and borrower entities, ownership, sites, project blocks, phases and shared facilities.
• Financing framework: current financing drafts, lender requests, milestone definitions, document schedules and incorporated forms.
• Project records: site-control instruments, permits, engineering, procurement and construction (EPC) agreements, equipment supply, offtake, interconnection, operations and insurance records.
• Support records: equity commitments, completion support, guarantees, security documents, direct agreements and assignment consents.
• Source inventory: room locations, execution copies, signing records, existing lists and responsible sponsor contacts.

Ask construction and commercial teams about off-room records, particularly change orders and technical attachments. An upload inventory alone cannot establish which documents should exist.

Use the template

Use the Project Finance Transactions — Diligence document index below. You can copy this table into your working document or spreadsheet. It is the team’s work product, separate from its findings and funding-conditions trackers.

Assign each separately reviewable file a stable ID. An identifiable missing document can receive a reserved ID, with “not supplied” in the source field. Do not reuse an existing ID for a replacement agreement.

Record original filenames and retrievable locations in the source field; add clause, page or exhibit references for particular observations. Family links connect base contracts, amendments, schedules, waivers and consents. Keep execution status distinct from effectiveness: signatures alone may not establish that effectiveness conditions occurred.

The financing link should identify a clause, milestone or defined document category. Verification records evidence, not clearance: “signatures present; Schedule B absent” is preferable to “reviewed.” Assign the next evidence-gathering action to an accountable person.

Step by step

1. Establish project boundaries and categories

Start with the entity and asset map. Identify who owns or leases each site, signs each material contract and receives revenue. For shared infrastructure, distinguish the contracting entity from the projects entitled to use it.

Create categories suited to the actual project: ownership, land, permits, construction, equipment, revenue, interconnection, operations, insurance, financing and sponsor support. Add phase or block references where funding or completion differs. For permits, identify the relevant site and activity without assuming that possession establishes sufficiency or transferability.

Record: entity, site, phase and financing purpose. Flag uncertain allocations for confirmation rather than assigning every document to the borrower.

2. Inventory files and assign stable identifiers

Inventory files before renaming or moving them. Preserve original filenames so existing correspondence and lender comments remain traceable. Use neutral IDs such as PF-001 rather than identifiers containing a changeable status.

Compare apparent duplicates by content, signatures and attachments. Identical names do not establish identical documents; different names may contain the same execution copy. Select a reference copy and identify duplicates without deleting potentially relevant evidence during inventory.

Record: Doc ID, title, parties, source location and provisional version status. Keep any access restriction visible so reviewers know how to obtain restricted evidence.

3. Reconstruct each document family

Read amendment recitals and internal references to identify underlying agreements and prior modifications. Check whether incorporated schedules, technical specifications and forms are supplied. Keep unsigned convenience consolidations distinguishable from executed instruments.

An EPC family may include performance tests, milestone schedules and change orders; an offtake family may include pricing schedules and commencement notices. A site-control family may include recorded instruments, amendments and related access rights. Index these relationships rather than assuming one PDF contains the complete arrangement.

Record: parent and related IDs, execution evidence, effectiveness information and missing components. If amendment numbering jumps, request clarification; do not infer the missing amendment’s existence or terms.

4. Map documents to financing questions and milestones

Use the identified financing version to distinguish signing, effectiveness, initial funding, later draws and conversion. Mark links to unagreed provisions as provisional. Cite relevant definitions and exhibits as well as the condition itself.

For example, Idaho Wind’s §3.3 addresses each construction loan. Sections 3.3(b)–(c) require specified draw certifications, supporting payment evidence and independent-engineer review, subject to exceptions. Standing project contracts therefore do not identify all evidence required for later draws under that agreement. See the Idaho Wind Credit Agreement, §3.3. (sec.gov)

Record: milestone, financing version, clause and related evidence IDs. Identify recurring certificates separately from the underlying contracts; leave satisfaction decisions to the conditions tracker.

5. Connect collateral, consent and support evidence

For material project contracts, locate the direct agreement, assignment consent or other instrument contemplated by the financing documents. Compare entity names, contract dates and amendment references. A consent naming an earlier agreement warrants a scope check, not an automatic conclusion that coverage is absent.

Li-Cycle’s §7.05(d), for example, differentiates requirements for additional project documents by classification, including direct agreements and assignment or security-interest consents or contractual rights. Those contractual provisions are not a complete statement of perfection law. See the Li-Cycle Loan Arrangement and Reimbursement Agreement, §7.05. (sec.gov)

Index base equity, contingent equity and completion support separately.

Record: supporting instrument IDs, classification questions and mismatches requiring collateral or sponsor counsel’s review.

6. Separate availability, completeness and verification

Use consistent factual descriptions: not supplied, incomplete, unsigned, executed copy supplied, or superseded. Separately identify what counsel verified. None means lender acceptance or waiver.

Assess whether redactions prevent the intended review. Rivian’s §12.02 contains redacted percentages concerning contingent equity; §12.03 addresses a separate completion-funding commitment. The public text cannot fully quantify sponsor exposure, and one commitment’s cap should not be assumed to govern another. See the Rivian Loan Arrangement and Reimbursement Agreement, §§12.02–12.03. (sec.gov)

Record: checks performed, material redactions, missing evidence and responsible owner. Route legal conclusions to a linked findings record rather than embedding unexplained clearance labels.

7. Reconcile requests and issue a controlled index

Compare the index with lender requests, financing definitions and the project team’s contract inventory. Investigate records mentioned in correspondence but absent from the room. Resolve inconsistent entity names before circulation.

Date the issued index and specify its source-room cutoff. Preserve prior versions so later uploads do not obscure what reviewers previously received. Assign responsibility for updates when amendments or replacement instruments arrive; maintain document history rather than overwriting it.

Record: outstanding actions and owners. Put the issue date and cutoff in the header, and cross-reference substantive findings or funding decisions in their separate trackers.

Worked example

Fictional scenario: Alder Basin Sponsor LLC is arranging construction financing for Alder Basin Solar LLC. All parties, documents, provisions and dates in this example are fictional. The room contains an executed EPC agreement, signed amendment 1, an executed power purchase agreement (PPA) and a draft EPC direct agreement. The financing draft identifies the amended EPC agreement as a major project document.

Amendment 1 moves mechanical completion from June 1 to August 1, 2027. The PPA retains a July 1, 2027 scheduled delivery commencement date. The construction manager says revised dates were commercially agreed, but supplies no PPA amendment. Amendment 1 also incorporates an absent replacement Schedule B.

These entries replace a generic upload request with three evidence requests. The missing schedule prevents verification of the revised construction sequence. The date mismatch warrants substantive review, not a finding of an existing default. The direct agreement needs a coverage check; omitting the amendment’s name does not alone determine its legal scope. The sponsor can prioritize these requests without misrepresenting the documents as cleared.

Common mistakes

• Filing everything under the sponsor. Confirm the actual contracting entity and affected site against the source.
• Treating the newest upload as operative. Distinguish a recent draft from an executed amendment before replacing the reference copy.
• Omitting technical attachments. Request incorporated tests, specifications and delivery schedules from the teams holding them.
• Equating delivery with acceptance. Record availability here; retain acceptance, waiver or deferral evidence in the conditions tracker.
• Combining sponsor support in one row. Separate commitments and security instruments so differing triggers, project scope and release provisions remain identifiable.

Final quality check

Before circulation, confirm:

• Every material file has a stable ID and retrievable source.
• Entity, site and phase allocations match documentary evidence.
• Agreements link to supplied amendments, attachments, waivers and consents.
• Execution, effectiveness and verification remain distinguishable.
• Financing links identify the correct version, clause and milestone.
• Missing records and material redactions are explicit.
• Every open issue is resolved with evidence or assigned to an owner.
• The issue date, source cutoff and prior versions are retained.

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 work across multiple documents, and contract review supports examining indexed agreements. Keep the index as the team’s work product, with lawyers verifying sources, document relationships and financing implications. To discuss this sponsor-side workflow, book a demo.

Frequently asked questions

Should the index follow lender request numbering?

Keep request numbers as cross-references, not primary IDs. One request may require several agreements and certificates; one contract may answer multiple requests. Stable IDs survive revisions to the lender list.

Should missing documents appear in the index?

Yes, when an identifiable document is expected or referenced. Mark it “not supplied,” cite the reference and assign an owner. Where existence is uncertain, record a confirmation request rather than inventing a title or date.

How should shared infrastructure records be indexed?

Identify actual parties and affected projects. Link access, allocation and operating arrangements. Counsel must assess whether those records establish the financed project’s required rights; folder placement cannot answer that question.

When is the index ready for lender review?

When scope is clear, sources are retrievable and gaps are candidly assigned. Not every request must necessarily be closed, but the sponsor should agree what remains outstanding and avoid describing an incomplete room as complete.

Sources

Historical filed agreements are used only as drafting examples; their current facility status is not assessed. The reference cutoff is October 13, 2026.

• Idaho Wind Partners 1, LLC — Credit Agreement, §3.3
• Li-Cycle — Loan Arrangement and Reimbursement Agreement, §7.05
• Rivian — Loan Arrangement and Reimbursement Agreement, §§12.02–12.03

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.