How to track conditions precedent with source references for Project Finance Transactions

Track project-finance conditions precedent by linking each funding requirement to its operative clause, incorporated definitions and forms, satisfaction evidence, and approval authority. Separate signing, effectiveness, initial funding, later draws, and conversion: evidence delivered for one event may not satisfy another. The sponsor’s deliverable is a conditions precedent tracker showing what remains open, who must act, and the record supporting closure. Distinguish delivery from satisfaction, identify acceptance requirements where applicable, and preserve the authority and terms for every waiver or deferral.

When to use this workflow

Use this workflow when sponsor counsel and the project team prepare for a financing closing, construction draw, letter-of-credit issuance, or conversion to term financing. It addresses coordinated evidence from the project company, contractor, independent engineer, insurers, counterparties, and financing parties—not the entire financing lifecycle.

The scope is sponsor-side closing coordination in US-oriented project finance. Permit validity, security perfection, and enforceability require separate applicable-law analysis. The historical filed agreements below illustrate negotiated provisions, not universal requirements or market standards. Actual rights depend on the operative documents, governing law, facts, and deal context.

What you need

Start with the operative financing agreement, amendments, schedules, certificate forms, and incorporated conditions. Confirm the version governing the funding event; an agreed draft is not execution evidence.

Assemble:

• The project-entity, site, phase, facility, proposed funding amount, and event-date list.
• Relevant engineering, procurement and construction (EPC), equipment-supply, offtake, interconnection, site-control, insurance, permit, and sponsor-support records.
• Required draw certificates, payment support, cost-to-complete information, and independent-engineer materials.
• Execution, delivery, acceptance, consent, and waiver correspondence.
• A document index with stable IDs, versions, execution status, and repository locations.

Name a sponsor owner for each evidence stream. Distinguish the preparer, authorized signatory, recipient, and person empowered to make any required acceptance decision.

Use the template

Use the Project Finance Transactions — Conditions precedent tracker below. You can copy this table into your working document or spreadsheet. Maintain one row per independently resolvable condition, with linked subrows for bundled requirements.

In Requirement / source, identify the agreement ID, version, section, applicable definition, and incorporated exhibit. Page numbers aid navigation but should not replace clause references. In Evidence / location, record the document ID, pinpoint, version, and stable repository link; for a workbook, include the sheet and cell range.

Use Owner / delivery for preparer, signatory, recipient, and target date. Dependencies captures preceding actions, such as engineer review of the schedule attached to the borrower certificate. Approval authority identifies the contractual decision-maker and consent threshold, where applicable—not simply the recipient.

Separate document progress—draft, executed, delivered—from condition disposition—open, satisfied, waived, or deferred. Record acceptance separately when required. Closure needs supporting evidence and any required approval record; a green cell is insufficient.

Step by step

1. Fix the event and governing document set

Identify the requested event: signing, effectiveness, initial construction advance, subsequent draw, letter-of-credit issuance, or conversion. Specify the borrower, project block, facility, amount, and target date.

Read the conditions with their definitions and cross-references. Initial closing does not necessarily resolve later draw tests. For example, Idaho Wind’s Section 3.3 subjects each construction loan, including the initial loan, to specified conditions.

Record: event-specific CP IDs and the controlling document version. Identify amendments affecting each requirement. Keep disputed applicability open for counsel’s decision rather than silently excluding it.

2. Break each condition into testable requirements

Ask what must exist, who must provide it, in what form, at what time, and subject to whose satisfaction. Preserve materiality qualifiers, exceptions, and defined terms. Separate document deliverables from factual tests, such as no default or accuracy of representations.

Split bundled conditions when different evidence or owners determine their components. A project-document condition might address execution, effectiveness, delivery, and consent; uploading a signed contract answers only one question. For factual certifications, identify the underlying review rather than treating the signature as proof of every statement.

Record: concise satisfaction tests and exact clause references in linked subrows. Retain a parent row so partial completion cannot appear as full satisfaction.

3. Assign evidence and its preparation sequence

Work backward from submission. Determine whether invoices feed a payment schedule, whether that schedule requires engineer review, and whether the borrower certificate must use the reviewed figures. Check prescribed forms and exceptions before requesting unnecessary material.

Idaho Wind’s Sections 3.3(b)–(c) illustrate borrower certification, payment support, and independent-engineer review, subject to exceptions. The certification addresses permitted project-cost use and sufficient funding for specified completion milestones. These are transaction-specific requirements.

Record: evidence IDs, preparer, signatory, recipient, target delivery, and dependencies. Label contractual timing separately from internal preparation dates. Assign an owner to missing attachments as well as the principal certificate.

4. Verify substance against the source

Check the correct entity, site, contract version, funding period, and amount. Confirm attachments and reconcile figures across the request, certificate, and supporting schedules. Record which version was actually reviewed; a filename saying “final” proves little.

For project documents and permits, distinguish possession from evidence addressing the contractual test. Within its letter-of-credit framework, Idaho Wind’s Section 3.2(c) addresses specified documents and permits remaining in full force and effect. It does not establish statutory permit timing.

Record: what each source establishes, its pinpoint, and missing factual or legal confirmation. Route permit-effectiveness questions to the appropriate reviewer. Do not infer effectiveness merely from delivery or infer ineffectiveness merely from a missing record.

5. Resolve blockers through the correct authority

For each gap, choose whether to complete evidence, correct a document, request a waiver, or negotiate a deferral. Check event-specific waiver and amendment provisions before proposing relief.

Idaho Wind’s Section 3.3 requires written waiver by the Administrative Agent with Majority Lender consent, but all Lenders’ consent for the initial construction loan. Do not import that threshold into another transaction or condition.

Record: decision-maker, threshold, requested relief, affected event, conditions attached, and written authorization reference. Distinguish proposed relief from granted relief. If authority or scope is unclear, keep the condition open and assign the clarification.

6. Test the sponsor consequence of delayed satisfaction

Escalate a blocked draw’s cash consequences without turning the tracker into a full sponsor-exposure model. Ask treasury when cash is needed, what other funding is available, and whether support documents address the shortfall.

Rivian’s Sections 12.02–12.03 distinguish contingent equity from completion support. Section 12.03 addresses specified completion-cost shortfalls, including circumstances involving untimely satisfaction of advance conditions. Public redactions limit quantification; do not assume one commitment’s cap limits another.

Record: blocked event, treasury owner, linked support provision, and required decision. Use unredacted operative documents for exposure analysis. An alternative cash source does not itself establish satisfaction of the lender’s condition.

7. Close the row and preserve the handoff

Confirm the evidence matches the final condition, including any required acceptance. Capture who determined disposition, when, and on what record. Reconcile with the closing team’s outstanding-items list before issuing the funding-readiness summary.

For authorized deferrals, transfer the obligation, owner, trigger, and due date into a linked post-closing work product. For recurring conditions, create a fresh event-specific test rather than carrying forward satisfied status automatically. Recheck time-sensitive certifications if funding moves.

Record: final evidence, required approvals, residual qualifications, and linked deferred or recurring tasks. Preserve a dated closing snapshot so later revisions do not erase the basis for the decision.

Worked example

Fictional scenario: Alder Basin Solar LLC, sponsored by Juniper Field Holdings, requests a $14 million initial construction advance. Its invented credit agreement, CA-01, requires a borrower certificate supported by an engineer-reviewed cost schedule, an effective interconnection agreement, and an executed contractor direct agreement. The agent assesses satisfaction; initial-advance waivers require written agent action with all-lender consent.

The certificate uses cost schedule version 6; the engineer reviewed version 5. The signed interconnection agreement references an effectiveness notice absent from the supplied records. The direct agreement remains unsigned. An agent email expresses comfort proceeding but supplies no lender-consent record. All parties, documents, amounts, and provisions are fictional.

The tracker replaces “substantially delivered” with three specific decisions. Finance must reconcile changed costs; counsel must establish effectiveness; and the financing team must complete the direct agreement or document authorized relief. The supplied evidence supports no unqualified satisfied status. If funding slips, sponsor treasury must separately assess cash needs rather than assuming lender funding will arrive.

Common mistakes

• Combining funding stages. Separate initial funding, later draws, letters of credit, and conversion so event-specific tests remain visible.
• Citing only the checklist. Cite operative provisions, definitions, and forms; the checklist is not the contractual source.
• Treating execution as effectiveness. Identify any additional evidence needed for the actual effectiveness test.
• Accepting mismatched cost packages. Reconcile certificate, invoice, schedule, and engineer-review versions before closure.
• Recording informal comfort as waiver. Verify authority, written scope, and residual obligations before changing disposition.

Final quality check

• Every row identifies its event, entity, and operative document version.
• Clause references, definitions, exceptions, and incorporated exhibits match the source text.
• Evidence links resolve to the exact version and relevant page or cells.
• Execution, delivery, effectiveness, and required acceptance are separately addressed.
• Waivers and deferrals identify authority, written terms, and event scope.
• Open issues are resolved or expressly assigned with a decision target.
• Deferred and recurring tasks have linked handoffs; the closing snapshot is preserved.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Sponsor teams can use contract review and tabular review across financing documents to support their analysis. Due diligence document classification can organize materials and prioritize human review. The tracker remains the team’s work product; lawyers verify source references, applicability, evidence, and approval authority. To assess this workflow for your closing documents, book a demo.

Frequently asked questions

Should one tracker cover several project companies?

Yes, if every row identifies the entity and event. Separate rows where evidence or authority differs. A shared project contract does not establish satisfaction for every borrower or site.

Can a delivered certificate close a condition?

Only if it meets the operative requirement. Check form, attachments, signature, substance, timing, and required review or acceptance. Record delivery separately while those checks remain unresolved.

How should missing schedules or redacted terms be handled?

Identify the gap and its effect on the satisfaction decision. Request the complete operative source from an authorized holder. Do not infer financial thresholds or certificate requirements from another transaction.

Is a waived condition the same as a deferred condition?

No. Read the written relief to determine whether performance is excused, postponed, event-limited, or replaced by another obligation. Preserve its actual terms in the disposition and handoff record.

Sources

Historical filed texts illustrate negotiated drafting, not current facility status or market standards.

• Idaho Wind Partners 1, LLC — Credit Agreement, Sections 3.2–3.3.
• 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.