How to prepare a post-closing obligations tracker for Project Finance Transactions

Prepare a sponsor-side post-closing obligations tracker by transferring surviving undertakings from the executed financing package into a clause-linked register with accountable owners, verified triggers, contractual deadlines and closure evidence. Separate recurring covenants, event-driven notices, later funding conditions and sponsor support commitments because each requires different oversight and proof. The resulting deliverable is an owned calendar and evidence register showing which entity must act, what could interrupt funding, what establishes completion and which uncertainties still require a decision—not simply which documents were delivered at closing.

When to use this workflow

Use this workflow when sponsor counsel hands an executed project financing to legal, treasury, construction and asset-management teams. Refresh it after amendments, new project contracts, construction-to-operations transitions or changes to completion support.

Include deferred closing deliverables, continuing obligations and conditions for subsequent funding. Link the closing checklist, construction schedule and finance model rather than reproducing them. The tracker should identify required actions and evidence, not become a second project-management system.

This guide assumes US transactional practice. Contractual rights depend on the operative language, governing law, facts and deal context. The historical filed agreements below illustrate negotiated provisions, not generally applicable requirements or market standards. Separate applicable-law analysis remains necessary for permits, collateral perfection and sponsor liability.

What you need

Start with the executed credit agreement, amendments, incorporated certificate forms, security documents, sponsor support agreements, account arrangements, direct agreements and written waivers or deferrals. Reconcile the final closing checklist, especially items marked complete because delivery was postponed.

Collect current project documents governing construction and revenue: EPC and equipment contracts, offtake arrangements, interconnection documents, operations agreements, required approvals and insurance evidence. Include schedules, expiry provisions and amendments; a closing-date index alone is insufficient for this workflow.

Obtain the construction and funding schedule, completion-test requirements, project-entity chart, reporting calendar and operational owner list. Treasury should supply its support model separating base equity, contingent equity, completion funding and reserves. Reconcile that model to actual commitments rather than treating financial assumptions as contractual facts.

Use the template

Use the Project Finance Transactions — Post-closing obligations tracker. Copy this table into your working document or spreadsheet. Create one row per independently actionable obligation; split requirements when owners, triggers, recipients or completion evidence differ.

In ID / obligor, name the entity legally responsible, not merely its sponsor group. Use stable document IDs with clause, exhibit or page citations in Source. Include linked definitions and amendments where needed to understand the obligation.

In Trigger / dates, distinguish the contractual deadline from an internal preparation date. Preserve the trigger itself, including any knowledge threshold or notice requirement. Mark unresolved dates explicitly rather than entering assumptions.

Owner / recipient identifies the accountable sponsor-side role and required receiving party; operational ownership does not change the legal obligor. Dependencies / risk records prerequisites and potential financing consequences, distinguishing verified consequences from questions for counsel.

For recurring duties, retain a parent row and dated occurrence rows, such as PC-014-01. One successful delivery closes that occurrence, not the continuing obligation. Use linked evidence references rather than embedding every supporting document in the table.

Step by step

1. Establish the operative document set and handoff boundary

Reconcile the signed financing package against the closing index. Link amendments, schedules, side letters and waivers to their underlying documents. Identify the entity, site and project phase covered by each instrument.

Separate completed closing items from deferred undertakings, continuing covenants and later draw or conversion conditions. A deferred deliverable needs a post-closing row even when the financing itself has closed. Read the deferral instrument for its actual deadline, conditions and approval basis.

Record: document IDs, precise citations, obligors and missing-source flags. Assign responsibility for obtaining missing attachments; do not mark extraction complete while material incorporated terms remain unavailable.

2. Extract duties by trigger, not just by covenant heading

Review reports, notices, collateral, project contracts, approvals, insurance, accounts, completion and support provisions. Include restrictions requiring review before amendments, change orders or other project decisions. Read definitions and incorporated forms, then classify duties as fixed-date, recurring, event-driven, continuous or funding-dependent.

Continuous duties need an internal review mechanism, not an invented contractual deadline. Li-Cycle’s §7.09 addresses performance of financing and project-document obligations, action against termination and enforcement of material counterparty obligations, subject to express exceptions. See the filed agreement, §7.09. (sec.gov)

Record: required action, type, qualifications and source. For continuous duties, identify the operational evidence to review and label periodic checks as internal controls rather than contractual reporting requirements.

3. Translate triggers into verified dates and preparation windows

Preserve the contractual trigger before calculating a date. Check business-day definitions, notice mechanics, relevant calendars and adjustment provisions. Have a second reviewer verify significant calculations against the source.

Work backward to allow preparation, signatures, counterparty cooperation and delivery. These intermediate dates are sponsor planning choices unless prescribed by the documents. For event-driven notices, identify who will learn of the event and how that information reaches legal.

Li-Cycle’s §7.16(b) provides specified renewal, replacement-contract and/or DOE-acceptable replacement-plan alternatives not later than six months before defined offtake contracts expire. This is a negotiated look-ahead requirement, not a general renewal rule. See §7.16(b). (sec.gov)

Record: trigger evidence, contractual deadline, internal preparation date and unresolved calculation questions. Do not replace a notice period with an arbitrary recurring calendar entry.

4. Connect obligations to later draws and project changes

Keep draw conditions visible without treating them as ordinary calendar covenants. Idaho Wind’s §3.3(b)–(c) requires borrower certification, payment support and independent-engineer review, subject to exceptions. The certification addresses permitted cost use and sufficient funding for specified completion milestones. See §3.3. (sec.gov)

For each anticipated advance, connect the required package to the current budget and engineer’s timetable. Distinguish an unsatisfied funding condition from a covenant breach; review the operative provisions before assigning a default consequence.

Route newly acquired property and additional project documents through legal review. Li-Cycle’s §7.05(d) illustrates classification-dependent requirements for supplemental security documentation, direct agreements and assignment or security-interest consents or rights. It does not establish all applicable perfection requirements. See §7.05(d). (sec.gov)

Record: affected draw, evidence dependencies, classification questions and consent review. A signed project contract does not alone establish satisfaction of associated financing requirements.

5. Assign sponsor support obligations separately

Create distinct rows for base equity, contingent equity, completion-cost funding, reserves and guarantees. Identify the obligor, beneficiary, project block, trigger, funding timing, limits, security and release conditions. Reconcile each commitment with treasury’s model and cash availability assumptions.

Rivian’s filed agreement separates contingent equity under §12.02 from completion-cost funding under §12.03, including specified circumstances involving advance conditions not being satisfied in time. Do not import one commitment’s cap into another; redacted terms prevent full quantification from the public filing. See §§12.02–12.03. (sec.gov)

Record: separate references, verified limits, funding dependencies and release evidence. Assign unavailable terms for resolution rather than guessing exposure or assuming physical completion releases every commitment.

6. Define evidence and escalation before the first deadline

Agree with each owner what establishes preparation, delivery, acceptance and discharge. Use distinct statuses: “preparing,” “delivered,” “accepted where required,” “waived,” “deferred” and “closed.” Do not require acceptance where the contract requires only delivery, or treat delivery as sufficient where consent is required.

Verify waiver authority. Idaho Wind’s §3.3 requires written waiver by the Administrative Agent and Majority Lenders, but all Lenders’ consent for the initial construction loan. These are transaction-specific thresholds. See §3.3. (sec.gov)

Record: evidence requirements, escalation owner and written waiver or deferral terms. Flag threatened funding interruptions with the affected advance and missing prerequisite. Do not infer waiver from silence or a green status cell.

7. Publish an owned calendar and maintain the register

Have sponsor legal confirm obligation descriptions and business owners acknowledge responsibility. Transfer verified deadlines and internal preparation dates into the team’s existing calendar process, retaining the register as the source-linked record.

Set review intervals appropriate to construction activity and upcoming funding. Require owners to report new contracts, amendments, permit developments, approaching expiry and completion changes. After an amendment, reassess affected obligations, dates and evidence requirements rather than merely indexing the document.

Record: next internal review, open decisions and change history. Preserve superseded entries for traceability. Close individual occurrences separately and retire continuing duties only when their contractual endpoint is verified.

Worked example

Fictional scenario: Alder Basin Sponsor owns Alder Basin ProjectCo, which has closed construction financing for a battery-storage project. All parties, documents and terms below are fictional.

Credit agreement FIN-01 requires a draw package five business days before the requested advance. Its incorporated form requires engineer review. Side letter SIDE-02 requires delivery to the agent of an offtake replacement plan six calendar months before expiry; it expressly uses the corresponding date without business-day adjustment. Completion undertaking SUP-01 has separate funding and release provisions.

Treasury wants an advance but has not confirmed its requested date. Cost support is available, engineer review is outstanding and the executed support schedule is missing from the handoff set.

The entries change three decisions. Treasury cannot call the advance ready merely because invoices exist. The commercial team receives an internal preparation target distinct from the contractual deadline. Sponsor legal leaves support exposure unresolved rather than borrowing a cap from another commitment. Missing documents and evidence remain explicit, with assigned next actions.

Common mistakes

• Copying the closing checklist unchanged. Re-extract surviving and recurring duties; a closing delivery list will not capture later triggers.
• Assigning every row to legal. Give operational information owners responsibility for identifying events, with a legal escalation contact.
• Recording only contract expiry. Capture earlier renewal or replacement-plan deadlines separately from the expiry date.
• Treating later draws as routine administration. Track current certifications, budget support and required third-party review for each advance.
• Closing support rows at physical completion. Verify each commitment’s contractual release conditions and supporting evidence independently.

Final quality check

• Each material row names the correct obligor, project phase and operative clause.
• Definitions, schedules, amendments and written waivers have been checked against source documents.
• Contractual deadlines and internal reminders are distinguishable; significant calculations have a second review.
• Recurring duties remain active, and event-driven duties have information owners.
• Draw rows identify missing evidence without automatically labeling it a covenant breach.
• Sponsor commitments have separate triggers, limits and release tests.
• Closure evidence supports status; every open issue has an owner and next action.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review and tabular review capabilities can support examination of obligations across financing documents; due diligence classification can organize the package and prioritize human review. In Word, give sponsor-specific instructions and review findings quoting clauses, locating text and ranking severity. Lawyers retain interpretation and verification; the tracker and calendar remain team-maintained work products. Book a demo to discuss this review workflow.

Frequently asked questions

Should later funding conditions go in this tracker?

Yes, where they affect anticipated post-closing advances. Label them as funding conditions and connect each occurrence to its draw. Keep funding readiness separate from conclusions about breach or default.

How do we track event-driven notices without known dates?

Record the trigger, required response period and information owner. Calculate the deadline once the triggering facts are verified. If knowledge matters, preserve the relevant evidence rather than assuming when the clock began.

Can we close a row when a document is sent?

Only where sending satisfies the obligation. Check delivery mechanics, recipient and required content. If acceptance, consent or another action is necessary, retain separate evidence and statuses for those stages.

What changes when an obligation is waived or deferred?

Retain the written authorization, approval basis, scope and conditions. For a deferral, record the revised deadline without deleting its history. Reassess linked draw conditions and support assumptions; do not assume they changed too.

Sources

These historical filed agreements illustrate negotiated wording; they do not establish current facility status or market standards.

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