How to build a closing deliverables checklist for Project Finance Transactions

Build a sponsor-side closing deliverables checklist by separating signing, effectiveness, initial funding, later draws and conversion, then mapping each required document or action to its financing provision. Assign a preparer, signatory and recipient; identify dependencies; and track execution, delivery and satisfaction separately. The resulting checklist should show whether the project can reach the intended financing milestone, who owns each blocker, and what evidence supports satisfaction, waiver or permitted deferral. It should also preserve the distinction between contractual requirements and additional requests still being negotiated.

When to use this workflow

Use this workflow when sponsor counsel and the in-house project team are preparing a project financing for signing or funding, particularly where construction payments, permits, project contracts, equity contributions and lender approvals must align. Start when financing drafts identify meaningful conditions; do not wait for execution versions.

The checklist coordinates legal, treasury, engineering, insurance and project-development contributors. Its scope is closing readiness, not a replacement for technical diligence, the funds-flow memorandum or ongoing covenant administration.

This is a general US transactional workflow. Contract rights depend on actual language, governing law, facts and financing structure. Project-location requirements, security perfection and permit applicability need separate analysis. The historical SEC-filed agreements below illustrate negotiated provisions, not universal requirements or market standards.

What you need

Collect both the requirements and the evidence available to satisfy them:

• Financing package: current credit agreement, definitions, condition schedules, certificate forms, security documents, account arrangements and amendments or waivers.
• Project package: entity records, site-control documents, permits, engineering, procurement and construction (EPC) contracts, equipment supply, offtake, interconnection, operating arrangements and insurance evidence.
• Collateral package: required searches, filing instructions, title materials, consents and direct agreements, with local counsel’s instructions where applicable.
• Sponsor funding package: equity commitments, completion support, guarantees, support security and the current funding plan.
• Closing instructions: milestone dates, proposed funds flow, adviser requirements, circulation arrangements and signature-release instructions.
• Document index: stable IDs, versions, execution status and locations, including amendments, schedules and missing attachments.

Ask the finance lead which advance pays the next construction obligation. A checklist organized around signatures alone can conceal a gap between document execution and available proceeds.

Use the template

Use the Project Finance Transactions — Closing deliverables checklist below. You can copy this table into your working document or spreadsheet. Link supporting records rather than compressing away information needed to explain status.

Assign stable row IDs, such as CD-014, and document IDs, such as FIN-01. Include the project entity or block in the deliverable cell. In Source / form, identify the clause, relevant definitions, exhibit and document version. During negotiations, distinguish proposed conditions from agreed requirements.

Split conditions into linked rows where separate contributors supply different components. The responsibility field separates preparation, signing and receipt; identify an individual accountable for progress, not only a department.

Record contractual timing separately from the internal target in Due / dependencies. Track execution and delivery independently, including signatures held pending release. In Satisfaction / authority, distinguish pending, satisfied, waived and deferred. Where acceptance is required, preserve it; otherwise identify who verified satisfaction and the supporting basis. Do not invent a lender sign-off requirement.

Step by step

1. Define the financing milestone and checklist boundary

Create separate groups for signing, effectiveness, initial funding, subsequent advances and conversion where applicable. Read what makes each milestone operative rather than inferring the sequence from document titles.

Identify the borrower, site and project phase covered by each condition. Multiple project blocks may require separate readiness assessments even when one sponsor supports them. Include letter-of-credit issuance if it is part of the immediate closing sequence.

Record: milestone, entity or block, contractual timing and checklist owner. Retain later-stage items in a separate group without presenting them as immediate blockers.

2. Extract conditions from the complete financing package

Read conditions alongside definitions, schedules, certificate forms and cross-references. Include actions as well as documents: depositing equity or establishing an account requires evidence beyond a signed instrument.

Reconcile your extraction against lender counsel’s checklist. Flag requests without an identified contractual basis for clarification rather than silently treating them as agreed conditions. Check whether representations or no-default confirmations must be repeated at funding.

For example, Idaho Wind’s Section 3.2(c) requires specified documents and permits then required to be effective to remain effective within its letter-of-credit conditions. It does not establish statutory permit timing. See the Idaho Wind Credit Agreement, Section 3.2(c).

Record: source, form, qualifications and required satisfaction evidence. Assign unresolved interpretation questions to counsel.

3. Assign responsibility and confirm document form

Identify who prepares, signs and receives each item. Confirm the signing entity and authority, and identify technical-adviser review needed before certification. For opinions and specialist reports, confirm the required provider, addressees and agreed scope.

Separate an underlying project contract from its consent or direct agreement. Check parties, amendments and covered obligations. An executed EPC contract does not establish that a separately required contractor consent exists. For collateral items, obtain counsel’s required filing or delivery evidence rather than equating signatures with perfection.

Record: accountable owner, signing entity, recipient, form reference and any authority, coverage or attachment issue.

4. Map dependencies that could prevent funding

Work backward from the intended advance. Connect the draw certificate to cost support, engineer review and sponsor funding evidence. Ask whether the officer can truthfully certify using current information, including changes since the certificate was drafted.

Idaho Wind’s Sections 3.3(b)–(c) illustrate borrower certification, payment support and independent-engineer review, subject to exceptions. Certification addresses permitted costs and sufficient funding for specified completion milestones. Consult Section 3.3 and its referenced forms, not a generic draw-document list.

Assess sponsor support separately from loan availability. Rivian’s Sections 12.02–12.03 distinguish contingent equity from completion-shortfall funding, including circumstances where advance conditions are not satisfied in time. Section 12.02’s cap should not be imported into the separate Section 12.03 commitment. Material figures and lead times are redacted in the filed Rivian agreement.

Record: predecessor row IDs, reviewers, funding dependencies and unresolved shortfalls. Do not quantify exposure from redacted terms.

5. Test satisfaction against final evidence

Compare each final document with the agreed form and controlling condition. Verify attachments, entity names, signature capacity, version and delivery. Distinguish collected signatures from authorized release and effective delivery.

Where a condition requires continuing effectiveness, identify confirmation beyond execution. Where it requires receipt of funds, obtain evidence of receipt rather than relying on a transfer instruction. For filing conditions, preserve the evidence specified by the documents and counsel’s instructions.

Record: execution and delivery states, evidence reference, reviewer and remaining discrepancy. Remove superseded documents as support for current satisfaction, while retaining their history.

6. Resolve exceptions through the correct authority

Classify each proposed solution: correction, alternative satisfaction evidence, amendment, waiver or permitted deferral. Verify the approval mechanism before representing that an agent or lender counsel can resolve the issue alone.

Idaho Wind’s Section 3.3 provides for written waiver by the Administrative Agent with Majority Lender consent, but requires all Lenders’ consent for the initial construction loan. These are that provision’s negotiated thresholds, not general financing rules. See Section 3.3.

Record: proposed treatment, authorized approvers, written evidence, scope and resulting deadlines. A pending waiver request remains pending; an internal decision to accept risk does not itself satisfy a financing condition.

7. Freeze the closing snapshot and transfer surviving items

Reconcile the checklist with execution versions, release instructions and the funds-flow memorandum. Produce a dated snapshot identifying satisfied conditions, documented exceptions and unresolved blockers. Escalate discrepancies to the sponsor’s authorized decision-makers before the relevant milestone.

Keep subsequent edits distinguishable from the record used for the closing decision. Transfer properly deferred items and relevant recurring obligations to an owned follow-up calendar without expanding this checklist into full covenant administration.

Record: snapshot reference, disposition of every immediate condition and receiving owner for each surviving item. Preserve the deferral approval, trigger and deadline; do not erase unfinished work by marking it closed.

Worked example

Fictional scenario: Juniper Basin Sponsor LLC is financing a wind project through Juniper Basin Wind LLC. The team targets signing and an initial $18 million construction advance in the same week. All parties, amounts, documents and provisions in this example are fictional.

The agreed execution version of FIN-01 separates signing from initial funding. Section 4.2(b) requires a draw certificate, cost support and engineer review. Section 4.2(f) requires an EPC direct agreement covering the amended construction contract. Section 4.2(h) requires evidence that initial sponsor equity reached the designated project account.

The project team reports readiness because financing signatures are arranged. Counsel tests initial-funding readiness:

The decision changes from “ready to fund” to “three initial-funding conditions unresolved.” Signing may remain possible if its separate conditions are satisfied, but that does not establish funding readiness.

Counsel first pursues evidence and corrections. The budget cannot replace missing invoice support; naming the original EPC does not conclusively resolve amendment coverage; and a transfer instruction does not prove receipt. No waiver authority is supplied in this example, so counsel must check FIN-01 before proposing an exception.

Common mistakes

• Combining signing and funding. Report readiness separately; signatures may not release construction proceeds.
• Using one row for the project-contract package. Separate the EPC, amendments, consents and direct agreements where owners or evidence differ.
• Treating delivery as satisfaction. Identify missing attachments, review comments and effectiveness questions instead of relying on a green status cell.
• Treating sponsor support as one capped commitment. Map each obligation separately and resolve missing unredacted terms before assessing exposure.
• Closing exceptions on informal assurances. Verify authority and retain the written waiver or deferral, including surviving obligations.

Final quality check

• Every immediate item identifies its milestone and project entity or block.
• Clause references and forms match the controlling version, not a superseded draft.
• Each item has an accountable owner, appropriate signer where needed, recipient and dependency sequence.
• Execution, release, delivery and satisfaction are distinguishable and supported.
• Draw certifications have the required financial and technical support.
• Exceptions preserve approval authority, written terms and scope.
• Open issues are resolved or assigned, blockers remain visible, and deferred obligations have receiving owners.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Sponsor teams can use contract review with deal-specific instructions and tabular review across financing documents to help identify requirements. Due diligence capabilities include bulk document classification to organize the project package and prioritize human review. The checklist remains the team’s work product; lawyers determine satisfaction and approval authority. To assess the workflow against your documents, book a demo.

Frequently asked questions

Should sponsor counsel adopt lender counsel’s checklist unchanged?

Use it for reconciliation, not as the sole source. Verify contractual support, identify additional requests and add sponsor dependencies such as equity receipt, engineer review and signature-release authority.

Do later-draw conditions belong in this checklist?

Keep them in a separate milestone group or linked record. Identify which also apply to the initial advance without suggesting that all future draw evidence must exist at signing.

How should missing permits or project consents be recorded?

Identify the particular item, source requirement and applicable milestone. Distinguish missing evidence from a conclusion that authorization is absent. Assign legal or technical review where applicability or timing remains uncertain.

When can a deferred deliverable be marked closed?

Treat the original condition as addressed only where the documents and authorized approval support that result. Track the surviving obligation separately, with its owner, trigger and deadline. “Addressed for funding” must not imply performance is complete.

Sources

These historical filings provide drafting examples, not confirmation of current facility status or subsequent amendments.

• 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.