How to compare material contracts in a diligence table for Project Finance Transactions

Compare material project contracts by testing how their obligations work together, not by summarizing each agreement separately. For the project sponsor, the table should connect construction delivery, revenue commencement, operating capability and sponsor support to the financing documents. Assign stable document IDs, extract clause-level evidence, identify mismatches and record the sponsor’s proposed response. The resulting deliverable is a source-linked comparison table separating verified terms, missing evidence and decisions requiring commercial or legal approval before the relevant financing milestone.

When to use this workflow

Use this workflow when sponsor counsel and the in-house finance team assess a project-contract package before financing negotiations, initial funding, a later draw or a material contract replacement. It is particularly useful when separate teams negotiated engineering, procurement and construction (EPC), equipment supply, offtake, interconnection and operations and maintenance (O&M) agreements.

The scope is contractual alignment: whether those agreements collectively support delivery, revenue and financing assumptions. Technical diligence, financial model validation and opinions on security, permits or enforceability remain separate workstreams.

This is a general US transactional workflow, not advice for a particular financing. Rights depend on operative wording, governing law, facts and deal context. The historical agreements cited below illustrate negotiated provisions, not legal requirements or market standards.

What you need

Collect executed project contracts with amendments, schedules, side letters, waivers and consents. Include site control, EPC, equipment supply, offtake, interconnection, O&M, contractual insurance requirements and sponsor support. Organize the package by project entity, site and phase.

Also obtain:

• The current financing draft or executed agreement, including definitions, conditions, covenants and incorporated forms.
• Direct agreements, assignment consents and documents identifying the secured parties.
• The approved construction schedule, revenue assumptions and technical descriptions of completion and performance tests.
• The sponsor’s negotiation checklist, risk tolerances, approval authority and commercial fallbacks.
• An index recording execution status, effective date, version and data-room location.

Ask technical and commercial teams which assumptions remain provisional. A model date is a comparison input, not proof that a counterparty owes performance by that date. Permits and technical reports provide context; they should not be treated as contracts merely to fit the table.

Use the template

Use Project Finance Transactions — Material contracts comparison. You can copy this table into your working document or spreadsheet. Create one row per comparison issue, rather than one overloaded row per contract.

Keep document IDs stable and cite sections, schedules or pages. “Verified terms” contains source-supported statements; “Dependency / mismatch” records analysis. This separation prevents an inference from becoming an apparent contract term.

In “Finance link,” identify the condition, covenant, default provision, collateral requirement or sponsor commitment—not merely “lender concern.” Record missing evidence separately. The action field should identify the preferred response, fallback where needed and accountable sponsor representative. The final field should distinguish open, risk accepted, amendment pending and closed, with approval or closure evidence.

For complex issues, link related row IDs. A revenue-delay row may depend on testing and sponsor-funding rows without repeating their analysis. Record priority and the required decision date within the action field.

Step by step

1. Define the comparison boundary

Identify the project entity, phase and financing milestone. Select topics that can change the sponsor’s decision: scope interfaces, price escalation, delivery, testing, damages, liability limits, termination, force majeure, assignment and lender cure rights.

Different milestones require different evidence. Idaho Wind section 3.2(c), for example, addresses effectiveness of specified documents and permits within its letter-of-credit conditions; it does not establish general permit timing (Idaho Wind credit agreement, §3.2). (sec.gov)

Table output: topic rows identifying the phase and financing dependency. Document why excluded contracts do not affect the selected questions; do not equate absence from a financing definition with commercial immateriality.

2. Establish the operative document set

Reconcile the index against supplied documents. Link amendments, change orders and consents to their underlying agreements. Check the named project company, counterparty, project description and execution status before extracting terms.

Where a clean compilation differs from signed documents, retain the discrepancy until counsel determines which text governs. A missing schedule is not evidence of absent obligations. Flag redactions preventing analysis, particularly pricing, liability caps and support amounts.

Table output: document IDs and citations, with missing attachments, disputed versions and unsigned documents in the evidence-gap field. Identify which conclusions depend on resolving each gap.

3. Normalize obligations without erasing differences

Compare obligations using their actual triggers. Mechanical completion, substantial completion, commercial operation and financing completion may describe different events. Capture tests, responsible parties, certificates and dependencies before comparing dates.

Apply the same discipline to money. Separate fixed price from escalation, delay damages from general damages, and aggregate caps from exclusions or separate sublimits. Determine whether equipment acceptance precedes the EPC contractor’s obligation to demonstrate integrated performance.

Table output: verified terms and an explanation of alignment or difference. If equivalence depends on engineering judgment, assign that question rather than declaring the milestones equivalent.

4. Test delivery against revenue and operations

Read construction, equipment, interconnection, offtake and O&M provisions together. Trace equipment delivery, energization, testing, revenue commencement and operating handover. Identify responsibility for each interface and the consequence of delay.

Compare extension mechanisms as carefully as baseline dates. Check whether EPC relief has corresponding relief under the revenue agreement, and whether O&M fees start before revenue. Compare termination longstops, notice periods and replacement rights against the same sequence.

Table output: each timing or scope discrepancy, supporting clauses and affected operating assumption. Assign financial quantification to the model owner; do not infer that delay damages cover the exposure merely because damages are available.

5. Connect discrepancies to financing and sponsor exposure

Map each material issue to document-effectiveness requirements, draw conditions, continuing covenants, defaults or collateral deliverables. Check whether the proposed fix itself needs consent, including an amendment, replacement contract or change order.

Classification matters. Li-Cycle section 7.05(d) differentiates additional project documents when addressing direct agreements and assignment or security-interest consents. Section 7.09 separately addresses continuing performance and enforcement obligations, subject to exceptions (Li-Cycle financing agreement, §§7.05, 7.09). Indexing a contract alone therefore does not establish compliance. (sec.gov)

Keep sponsor commitments separate. Rivian sections 12.02 and 12.03 address distinct contingent-equity and completion-funding arrangements. Do not import the former’s cap into the latter; public redactions also limit quantification (Rivian financing agreement, §§12.02–12.03). (sec.gov)

Table output: exact financing dependencies, separate support categories and unresolved exposure questions, including applicable caps, aggregation and release conditions.

6. Turn each material mismatch into a sponsor decision

State the preferred position, fallback and decision-maker. Options include aligning milestones, narrowing termination rights, obtaining a direct agreement or accepting an assessed exposure. Identify affected provisions rather than instructing colleagues to “fix bankability.”

Separate informational observations from negotiation instructions. Prioritize by consequence and proximity to the financing milestone. A missing assignment consent may need immediate attention even where commercial terms align. Record whether a proposed concession affects another comparison row.

Table output: specific action, accountable owner, priority, decision date and approval status. Link commercial cost analysis where available; otherwise assign it as an open question.

7. Verify resolution against evidence

Recheck findings against complete clauses, definitions, exceptions and amendments. Close a row only when the required evidence exists. An email promising an amendment does not establish execution or delivery.

For financing waivers, verify approval mechanics. Idaho Wind section 3.3 requires written waiver by the Administrative Agent with Majority Lender consent, but all Lenders’ consent for the initial construction loan (Idaho Wind credit agreement, §3.3). Do not assume those thresholds apply elsewhere. (sec.gov)

Table output: closure document and citation, or an expressly assigned open issue. Distinguish sponsor risk acceptance from satisfaction or waiver of a financing requirement. Transfer surviving actions to the responsible worklist without calling that transfer resolution.

Worked example

Fictional scenario: All parties, documents and provisions below are invented. Juniper Basin Sponsor LLC is financing a battery-storage project through Juniper Basin Project LLC. The signed EPC agreement requires completion by September 30, 2027; the signed tolling agreement requires availability from September 1, 2027. The financing draft separately requires schedule acceptance, an executed EPC direct agreement and complete support documents before initial funding.

Counsel has an unsigned direct agreement and a signed sponsor deed supplied without its referenced Schedule A. The project team suggests earlier testing solves the timing issue, but provides no contractual evidence that testing satisfies tolling availability. The dates show an obligation gap, not proof that actual completion will be late.

The comparison changes “documents substantially complete” into three decisions. R1 requires technical and commercial evaluation before date alignment or risk acceptance. R2 concerns execution and acceptance, without concluding the proposed wording is adequate. R3 prevents an unsupported exposure figure reaching the approval committee. No missing provision is reconstructed from expectations.

Common mistakes

• Comparing headings instead of triggers. Extract the event, required evidence and responsible party before comparing completion dates.
• Treating delay damages as full revenue protection. Compare triggers, exclusions and caps with the exposure; obtain a separate financial assessment.
• Ignoring extension asymmetry. Test relief and termination longstops across construction, revenue and financing provisions.
• Recording consent as yes/no. Identify the entity, contract version, scope and execution evidence. Distinguish assignment consent from lender cure arrangements.
• Applying one support cap everywhere. Analyze each commitment, cross-reference, aggregation rule and release condition separately.

Final quality check

Before circulating the comparison, confirm that:

• Each finding cites the operative version and exact provision.
• Amendments, schedules, side letters and direct agreements are linked or expressly missing.
• Completion and revenue milestones are compared by trigger, not label.
• Price, damages and support limits retain exceptions and aggregation rules.
• Financing consequences identify the provision, project phase and any consent dependency.
• Verified facts, analysis and missing evidence remain distinguishable.
• Open issues have owners and decision dates; closed issues have evidence and required approvals.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its transactional capabilities support tabular review across documents; due diligence classification can organize the package and prioritize human review. For revisions, contract review supports deal-specific instructions in Word and lawyer-controlled insertion or editing of suggestions as ordinary tracked changes. Counsel remains responsible for source verification, interpretation and decisions. Book a demo to discuss the comparison workflow. (decover.ai)

Frequently asked questions

Should every project contract receive the same review depth?

No. Prioritize delivery, revenue, site access, operations, collateral and sponsor exposure. Record why review is limited so an excluded topic is not mistaken for a cleared risk.

How should the table handle different completion definitions?

Retain each definition, test, certificate and dependency. Ask the technical adviser whether the underlying events coincide. Do not replace distinct milestones with one normalized date without evidence.

Can commercial risk be accepted without an amendment?

Record acceptance by the authorized sponsor decision-maker separately from contractual resolution. Check affected financing provisions and required approvals. Internal acceptance does not itself amend a contract or satisfy a lender requirement.

What happens when a key schedule is missing?

Identify the precise conclusion the schedule prevents, request it from the responsible owner and keep that conclusion open. A signed main agreement does not resolve missing pricing, performance or support evidence.

Sources

These historical SEC-filed agreements are drafting examples within the October 13, 2026 research scope, not confirmation of current facility status or subsequent amendments.

• Idaho Wind Partners 1, LLC — Credit Agreement, §§3.2–3.3.
• Li-Cycle — Loan Arrangement and Reimbursement Agreement, §§7.05 and 7.09.
• 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.