How to build a due diligence findings and risk tracker for Project Finance Transactions

Build a sponsor-side project finance diligence tracker by linking each material finding to its source, financing consequence, responsible owner and closure evidence. Start with the project’s entities, contracts and funding stages—not a generic corporate checklist. Separate verified facts from missing evidence and unresolved legal questions, then prioritize issues that could delay funding, interrupt revenue or increase sponsor support. The deliverable is an evidence-backed decision record that lets the sponsor resolve, negotiate or expressly accept risks without treating document delivery as substantive clearance.

When to use this workflow

Use this workflow when sponsor counsel, the finance team and project personnel need a common view of diligence before financing commitments, signing or a construction draw. Refresh it after a material change order, replacement offtake agreement or revised completion forecast.

The scope is identifying and resolving diligence findings, not administering the entire financing. Work backward from the next financing decision while retaining findings relevant to later draws or conversion.

This guide uses a US transactional orientation. Contract rights depend on operative language, governing law, facts and deal context. The filed agreements below illustrate negotiated provisions, not general legal requirements or market standards. Permit validity, security perfection and sponsor liability require separate analysis under applicable law and the operative documents.

What you need

Collect the financing documents alongside the project evidence they test:

• An ownership chart identifying the borrower, sponsor, project companies, sites and development phases.
• Executed site-control, engineering, procurement and construction (EPC), equipment-supply, offtake, interconnection and operations agreements, including amendments, schedules, side letters and consents.
• Permits and approvals, insurance evidence and available technical-adviser reports.
• The construction schedule, cost-to-complete forecast, sources-and-uses model and draw assumptions, each with a version date.
• Draft or executed credit, security, direct-agreement and sponsor-support documents, including incorporated certificate forms.
• Existing issues lists, material counterparty correspondence and evidence of lender decisions or acceptance.

For each request, identify the financing question it should answer. A missing EPC schedule matters differently if it contains performance tests rather than administrative contacts. Request unredacted operative documents where caps, triggers or deadlines are obscured; record restricted access rather than guessing missing terms.

Use the template

The companion template is Project Finance Transactions — Diligence findings tracker. You can copy this table into your working document or spreadsheet. Use one row per actionable finding, not one row per document.

Assign stable finding IDs. Cite document IDs, versions and clauses or pages; for financial evidence, identify the workbook version, worksheet and cell. Link to a document index containing parties, execution status and data-room location.

In Evidence / gap, distinguish verified wording, missing evidence and interpretation awaiting advice. State confidence where material. Financing impact explains the consequence: draw availability, revenue timing, collateral coverage or sponsor exposure.

Priority combines consequence and proximity to the affected milestone. Owner / decision identifies both the person responsible for resolution and the person or body authorized to approve the response. Action / target distinguishes contractual deadlines from internal targets. The final field records disposition and supporting evidence, not merely a color. Retain dated updates and identify the reviewer in closure notes.

Step by step

1. Fix the review perimeter and funding decision

Identify the entities, sites, phases and financing stage under review. Distinguish signing, effectiveness, initial funding, subsequent draws and conversion. Confirm which document versions govern each stage; draft requirements remain provisional.

Ask the sponsor which decisions are imminent and which exposures require escalation regardless of timing. An unresolved land right may affect project viability, while an incomplete draw certificate may affect a particular funding request. Define the intended review cutoff so later uploads are not silently treated as reviewed.

Record: project, stage and immediate financing consequence on each row. Retain later-stage findings rather than dropping them from the review perimeter.

2. Establish the evidence chain

Assign stable document IDs and connect amendments, schedules and consents to the underlying agreements. Check the project entity and site. Identify the operative version while preserving superseded versions relevant to the issue.

Read incorporated attachments before summarizing rights. If an attachment is absent, record what cannot be determined—not that the obligation is absent. Verify material statements against documents rather than filenames or management summaries. Conflicting evidence should remain visible until reconciled.

Record: precise citations and bounded evidence gaps. Include execution status where relevant, and assign a request owner and internal response target for missing material.

3. Map project evidence to financing provisions

For each material project contract, identify relevant representations, conditions, covenants, defaults and collateral provisions. Check defined classifications: commercial importance alone does not establish treatment under the financing documents.

For example, Li-Cycle’s Section 7.05(d) distinguishes additional project documents by classification, with associated direct-agreement or assignment/security-interest consent requirements and qualifications. It supports checking the applicable category, not assuming every contract needs the same instrument (filed agreement, Section 7.05(d)).

Check whether the financing provisions address amendments, replacements or change orders, and whether existing consents cover the relevant version.

Record: project-contract and financing-document citations, classification and unresolved consent questions. Assign perfection questions for separate legal analysis rather than treating document collection as proof of perfection.

4. Test interfaces and sponsor exposure

Compare obligations across contracts. Align EPC completion and testing with revenue commencement, interconnection availability and financing milestones. Examine escalation, delay remedies, liability caps, termination, force majeure and lender cure rights where they affect that alignment. Ask whether a remedy covers the modeled loss, not simply whether a damages clause exists.

Analyze base equity, contingent equity, completion funding, reserves and guarantees separately. Rivian’s filed agreement separates contingent equity in Section 12.02 from completion funding in Section 12.03; redacted terms prevent complete public quantification. Do not import one commitment’s cap into another (filed agreement, Sections 12.02–12.03).

Record: the mismatch, model references and exposure question. Assign quantification to finance and interpretation of support obligations to counsel, including aggregation and release questions.

5. Prioritize and turn findings into decisions

Define an internal scale. “Critical” might require resolution or an authorized decision before the identified funding event; “high” might capture material exposure requiring prompt escalation. These are transaction-specific working definitions, not industry standards.

Separate priority from confidence. An unverified completion-support cap can warrant urgent review because exposure is unknown. Group related findings without merging distinct decisions or losing their evidence trails.

Identify the sponsor’s preferred response, fallback, commercial cost and decision-maker. Responses may include obtaining evidence, amending a project contract, revising financing language or requesting a properly authorized waiver.

Record: priority rationale, proposed action, approval authority and target. Keep informational observations separate from negotiation instructions.

6. Verify satisfaction, acceptance and waiver separately

Do not close a finding because a document was uploaded. Check content, signatures, required form and any acceptance requirement.

Idaho Wind’s Section 3.3 requires specified construction-loan conditions unless waived in writing by the Administrative Agent with Majority Lender consent; waiver for the initial construction loan requires all Lenders’ consent. Sections 3.3(b)–(c) address certifications, supporting evidence and independent-engineer review, with exceptions (filed agreement, Section 3.3). Those mechanics are transaction-specific.

Record: delivered, accepted, waived and deferred as distinct dispositions. Identify evidence of satisfaction and any required acceptance. Preserve written waiver scope, conditions and approval authority; do not treat an informal assurance as a documented waiver.

7. Close the finding or assign continuing treatment

Recheck remediation against the original issue. An amendment may fix revenue timing while introducing a termination right. Review both effects before closing the row.

Separate completed remediation from surviving obligations. Li-Cycle’s Section 7.09 illustrates continuing performance and enforcement obligations, subject to exceptions; possession of the contract does not demonstrate ongoing compliance (filed agreement, Section 7.09).

Record: reviewer, closure date, rationale and evidence reference. For continuing actions, identify the receiving owner and calendar or checklist entry. Distinguish contractual triggers from internal reminders. Keep the handoff open until accepted, and do not label substantive compliance complete merely because responsibility was transferred.

Worked example

Fictional scenario: Alder Basin Energy sponsors a US battery-storage project finalizing financing for a proposed $24 million first construction draw. All parties, documents, amounts and provisions below are fictional. Counsel reviews executed project contracts, draft financing documents and Model v7 before sponsor approval.

The EPC permits completion on September 30, 2027, while the revenue contract begins availability obligations on September 1, 2027. Incorporated Schedule C could affect those obligations, but no copy has been provided. A supplier consent identifies the original contract rather than its amended version. The sponsor-support draft states a $6 million contingent-equity cap and separately addresses completion funding without clearly applying that cap.

F01 requires the missing schedule and a timing analysis before counsel recommends amendment: the available evidence does not establish whether availability obligations are qualified. F02 requires examination of the consent’s operative scope; its citation alone does not establish exclusion of amendments. If coverage is inadequate and the funding condition survives, replacement consent or another authorized response is needed.

F03 prevents approval based on an assumed aggregate cap. Finance must model separate obligations using counsel’s interpretation. None of the rows establishes default or enforceability; missing evidence and draft requirements remain explicit dependencies.

Common mistakes

• Tracking documents instead of findings. “EPC received” hides milestone conflicts. Create separate rows for distinct risks linked to the same document.
• Treating modeled assumptions as rights. A spreadsheet cap does not establish a support limit. Reconcile the model to the operative obligations.
• Combining funding stages. Initial funding and later draws may have different conditions. Identify the applicable stage and incorporated forms.
• Closing on execution alone. A consent may concern the wrong entity or scope. Verify coverage and required acceptance.
• Treating waiver as a general cure. Identify the provision, event, approval authority and continuing conditions; preserve the written decision.

Final quality check

Before circulating the decision version, confirm:

• Each material row identifies the correct entity, site or phase.
• Citations resolve to reviewed documents, attachments or model cells.
• Executed terms, draft assumptions, missing evidence and legal judgments are distinguishable.
• Construction, revenue and funding dates are reconciled or flagged.
• Sponsor-support obligations are separately analyzed, with cap uncertainties visible.
• Dispositions have substantive evidence, including required acceptance or waiver approval.
• Unresolved issues have owners, decision-makers and targets; continuing actions have accepted recipients.

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 documents. In Word contract review, select the sponsor as represented party where appropriate and provide project-specific instructions. Findings quote and locate clauses, rank severity and identify missing language as not present. Lawyers retain responsibility for interpretation, risk acceptance and closure. Book a demo to discuss this workflow.

Frequently asked questions

Should every missing document become a finding?

No. Keep routine collection requests in the index. Create a finding when the gap prevents a material financing conclusion, blocks verification or requires an accountable decision. State the consequence.

How should the tracker handle unsigned financing drafts?

Cite the version and label requirements provisional. Track consequences if the terms remain, then recheck agreed documents. Do not present proposed lender conditions as existing borrower obligations.

Can sponsor risk acceptance close a row?

Record authorized acceptance separately, with rationale and residual exposure. It does not itself satisfy lender conditions or obtain counterparty consent. Keep those dependencies open unless independently resolved.

How much financial analysis belongs in the tracker?

Include consequences, tested assumptions and model references—not a duplicate model. For overruns or delayed draws, identify potentially responsive sponsor commitments and outstanding legal or finance validation.

Sources

These historical SEC-filed agreements are drafting examples within the October 13, 2026 research cutoff, not confirmation that facilities remain outstanding or unamended.

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