How to review completion support commitments for Project Finance Transactions

Review completion support by separating each sponsor funding promise, tracing its triggers through the financing documents, and testing when cash could be required despite delayed debt availability. Verify caps, security requirements, funding mechanics, and release conditions against the operative language. The resulting deliverable is a sponsor-side completion support checklist identifying exposure where evidence permits, unresolved liquidity risks, proposed drafting changes, and evidence needed to confirm discharge. Keep base equity, contingent equity, completion funding, reserves, and guarantees separate unless express provisions connect them.

When to use this workflow

Use this workflow when sponsor counsel or an in-house financing team receives a completion undertaking, negotiates construction financing, reviews a material project change, or assesses whether completion support can be released. It addresses the sponsor’s obligation to fund or secure completion—not the entire financing diligence exercise.

The orientation is US transactional practice, including phased projects. Rights depend on the documents, governing law, facts, and deal structure. The filed agreements below illustrate negotiated provisions, not legal requirements or market standards. Entity authority, enforceability, and security-law questions require separate matter-specific analysis. The review recommendations are practical controls, not mandatory procedures.

What you need

Obtain the complete financing package, not just the document titled “completion guarantee.” Request:

• Credit and reimbursement agreements, equity contribution agreements, sponsor undertakings, guarantees, incorporated definitions, and certificate forms.
• Amendments, waivers, side letters, intercreditor provisions, and unredacted schedules establishing commitment amounts and timing.
• Construction budgets, sources and uses, contingency assumptions, remaining-cost forecasts, and the sponsor’s funding model.
• EPC and supply contracts, completion tests, engineer requirements, and relevant interconnection and revenue commencement milestones.
• Letters of credit, cash-security arrangements, reserve requirements, and proposed release certificates.

Assign stable document IDs and identify the sponsor entity, project company, site, and phase covered by each instrument. Record execution status and version. Ask finance personnel to distinguish committed funding from conditional sources; a model entry alone does not establish availability. Obtain evidence of contributions already made so remaining commitments can be reconciled.

Use the template

The Project Finance Transactions — Completion support checklist is a working review record. You can copy this table into your working document or spreadsheet. Use one row per distinct undertaking, adding rows where blocks, triggers, or release routes change the result.

In Source / evidence, cite the document ID, version, clause, and schedule or model cell. Distinguish contractual wording from forecasts. Amount / cap records the calculation basis, aggregation rule, contributions already credited, and uncertainty—not merely a headline amount.

Security / release captures the instrument’s requirements and the undertaking’s discharge conditions separately. Gap / decision distinguishes missing evidence from a negotiation position and records priority. Owner / closure identifies responsibility, status, and evidence required to close the item. Use statuses such as verified, awaiting evidence, decision required, and closed; a delivered certificate is not necessarily an accepted certificate.

Step by step

1. Inventory each promise and the entity that makes it

Read across the package for obligations to contribute, reimburse, guarantee, replenish, procure funding, or provide security. Separate base equity, contingent equity, completion-cost funding, reserves, and other guarantees. Identify the beneficiary and covered blocks. Check whether an obligation rests on the sponsor directly or requires it to cause another entity to perform.

Do not combine similarly named undertakings without checking cross-references. Section 12.02 of the Rivian agreement separates contingent-equity funding, security, and termination mechanics by block. This is a drafting example, not a prescribed structure. (sec.gov)

Record: Separate rows identifying obligor, beneficiary, block, source, and execution status. Flag inconsistent entity names or missing signatures.

2. Reconstruct the trigger and funding deadline

Trace defined terms and incorporated provisions until the trigger can be stated operationally: who identifies the shortfall, which forecast governs, whether notice is required, and when funds must arrive. Distinguish scheduled equity from event-driven contributions. Check whether demand is necessary or the obligation arises without it.

Section 12.03 of the Rivian agreement addresses specified completion-cost shortfalls, including advance conditions not satisfied in time. Funding lead times are partly redacted. (sec.gov)

Record: Trigger, calculation, notice, recipient, and funding sequence. Request missing operative terms rather than inferring deadlines from construction dates. Identify the consequence of late funding under the linked default provisions.

3. Quantify exposure without transferring caps between promises

Have finance calculate exposure separately for each undertaking. Determine whether a cap limits contributions, outstanding security, aggregate liability, or a particular block. Check whether prior funding reduces the commitment and whether reserve contributions, security draws, or guarantee payments receive credit. Investigate whether amendments or increased project costs change the calculation base.

Section 12.02 of the Rivian agreement contains a contingent-equity cap with redacted percentages. Do not import that cap into the separate Section 12.03 commitment without supporting language. (sec.gov)

Record: Verified amounts, model references, aggregation rules, credits, and any proposed protection against duplicate funding. Use “not yet quantifiable” where essential evidence is missing; absence of an express cap alone does not establish a numerical exposure.

4. Test the undertaking against debt-draw conditions

Compare project payment dates with debt availability and sponsor funding deadlines. Test a delayed draw, cost overrun, and missed completion longstop. Determine whether the sponsor must bridge payments because a certificate, consent, or test is outstanding. Distinguish a temporary liquidity requirement from an increase in total project cost.

Sections 3.3(b)–(c) of the Idaho Wind agreement illustrate borrower certification, payment evidence, and engineer review, subject to exceptions. The certification addresses permitted use and sufficient completion funding. (sec.gov)

Record: Scenario cash requirement, model cells, unavailable source, and assumption owner. Verify whether subsequent debt can reimburse the bridge or whether the contribution remains invested. Do not assume reimbursement merely because debt later becomes available.

5. Review security as a separate cash constraint

Check whether support requires cash, a letter of credit, or another permitted instrument. Review amount, beneficiary, issuer qualifications, expiry, replacement timing, drawing conditions, and return mechanics. Ask treasury to assess collateral and facility usage separately from ultimate payment exposure.

Section 12.02 of the Rivian agreement permits specified acceptable letters of credit instead of cash security. Substitution and issuer eligibility remain document-specific. (sec.gov)

Record: Security requirements and underlying obligation, distinguishing their duration. Flag expiry before anticipated release, nonrenewal consequences, and uncertainty about whether a security draw satisfies or merely secures the contribution obligation.

6. Verify completion and release independently

Map financing completion to construction acceptance, performance tests, engineer certificates, remaining costs, and required contributions or prepayments. EPC acceptance, revenue commencement, or another block’s completion is insufficient unless the financing language makes it sufficient.

Section 12.03 of the Rivian agreement uses block-specific completion, longstop, contribution, transfer, and prepayment mechanics to define release dates. (sec.gov)

Record: Each release route, evidence provider, recipient, required action, and surviving obligation. Distinguish termination of funding duties from cancellation or return of security. Check whether longstop consequences require a final payment or reconciliation rather than assuming that passing the date ends exposure.

7. Convert findings into sponsor instructions

For each material issue, state the preferred position, fallback, commercial consequence, and affected provisions. Options include an aggregate cap, payment credits, narrower shortfall definitions, or clearer block-specific releases. These are negotiation choices, not presumed entitlements. Separate requests for evidence from requested amendments or waivers.

Section 3.3 of the Idaho Wind agreement requires written waiver by the Administrative Agent with Majority Lender consent, or all-lender consent for the initial construction loan. Other documents may differ. (sec.gov)

Record: Sponsor approver, decision, proposed revision, approval authority, and closure evidence. Recheck definitions and related provisions after revisions; changing a cap in one undertaking does not resolve conflicting language elsewhere.

Worked example

Fictional scenario: Cedar Vale Sponsor LLC is financing two battery-storage blocks through Cedar Vale Project LLC. All parties, documents, amounts, and provisions are invented. Counsel receives proposed credit agreement CA-01, sponsor undertaking SU-01, letter-of-credit form LC-01, and model FM-01, all version 2.

SU-01 §2 requires $12 million of base equity before initial funding. Section 3 imposes a $7 million Block A contingent-equity cap and permits an acceptable LC. Section 4 separately funds defined completion shortfalls, without an express cap or incorporation of §3’s cap. Section 6 requires Block A completion evidence and payment reconciliation for release. LC-01 specifies expiry before the certificate delivery projected in FM-01 F22; issuer acceptance remains unconfirmed.

FM-01 D18 assumes a $4 million debt draw before equipment payments in D19. CA-01 §5.2 requires an engineer certificate that is absent from the supplied package. Counsel cannot conclude the draw will fail, but cannot verify timely availability. The following three entries are representative; base equity and Block B require separate rows in the full checklist.

The review changes the instruction from “approve support within $7 million” to “resolve separate completion exposure and bridge liquidity before approval.” The $4 million is a scenario, not a verified obligation or overall ceiling. Certificate timing may eliminate the bridge need; it does not resolve cap scope. The LC mismatch is supported by the proposed form and forecast, but final replacement requirements still require document review.

Common mistakes

• Applying one cap across the package. Identify its exact subject and negotiate express aggregation or credits where needed.
• Counting undrawn debt as immediately available. Match modeled draws to conditions and payment dates; identify unverified assumptions.
• Equating contractor and financing completion. Compare tests, remaining-cost treatment, and block-specific evidence requirements.
• Treating security expiry as discharge. Review instrument expiry, replacement duties, and underlying release independently.
• Clearing incomplete evidence. Keep redactions, missing schedules, and absent certificates open until verified or assigned for decision.

Final quality check

• Each undertaking identifies obligor, beneficiary, block, and operative version.
• Caps, credits, and aggregation conclusions have precise clause support.
• Triggers include calculation, notice, timing, and default dependencies.
• Scenarios reconcile to model cells and documented funding assumptions.
• Security amount, expiry, replacement, and release are checked separately.
• Completion and discharge conclusions address incorporated definitions and evidence.
• Sponsor instructions and revisions are consistent across linked documents.
• Source references are verified; open issues have owners and closure requirements.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review workflow in Word supports selecting the represented party and providing deal-specific instructions. Findings quote and locate clauses, rank severity, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name, or dismiss findings with reasons. Tabular review supports work across documents; counsel retains responsibility for cap interpretation, calculations, and release conclusions. Book a demo to discuss reviewing a completion-support package.

Frequently asked questions

Is completion support always a capped guarantee?

No assumption should replace document review. Identify contribution obligations, shortfall funding, security, and guarantees separately. Determine structure and cap scope from the provisions; refer enforceability questions for applicable-law analysis.

What if the sponsor can fund the base case but not a delayed draw?

Record the liquidity gap separately from total cost. Test payment dates and draw conditions, then obtain instructions on bridge capacity or revised funding mechanics. Verify whether later reimbursement is permitted.

Can support end when one project block is complete?

Check block-specific termination language, shared conditions, payment reconciliation, and surviving obligations. Record the evidence and actions for that block, including any separate security cancellation request.

How should redacted public agreements be used?

Use them to identify drafting questions, not to quantify your transaction or establish market terms. Missing percentages and lead times remain unknown; obtain the operative unredacted documents before clearing exposure or timing.

Sources

• Rivian — Loan Arrangement and Reimbursement and Sponsor Support Agreement, §§12.02–12.03: separate commitments, security, and release mechanics.
• Idaho Wind Partners 1, LLC — Credit Agreement, §3.3: construction-draw conditions and waiver authority.

Source scope as of October 13, 2026: these historical filed texts do not establish that the facilities remain outstanding or unamended.

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.