01 · Schedule
Obligation schedule
Every obligation across every contract, grouped by cadence — what's due this week, this quarter, this year — with each entry one click from its verbatim clause.
Which answer is your team working from?
That's a real finding. A top-tier US renewable energy developer is running Kaskad across an operating renewable-energy project — a dozen-plus agreements: site leases and their amendment chains, the PPA, interconnection, the financing stack, and the land documents wrapped around them. Every deadline, renewal window, and notice requirement — cross-referenced across the whole set and resolved to the calendar.
The findings below are drawn from that engagement. Identifying details have been changed; the substance hasn’t.
They're the notice that didn't go out, the window that closed unnoticed, the answer taken from one document when the truth lived across two.
Every deadline, renewal window, and notice requirement in the project, visible before it lands. Nothing sits dormant in a contract nobody has opened since closing.
An outage, a casualty, a late report from your operator. You see what you're contractually required to do, who has to be notified, and by when — in minutes, not after a scramble through the PDFs.
The miss that turns an operational hiccup into a lender conversation is the one nobody saw coming. That's what stops happening.
From the operating project described above, clause citations intact.
In this project, the PPA grants expansion rights, subject to the offtaker's right of first offer. The financing agreement says this:
"The Borrower shall not (nor shall it allow Holdco or the Project Company to) expand the Project pursuant to Section 20.2 of the Power Purchase Agreement."
Whoever answers from the PPA alone answers wrong. The correct answer only exists across both documents.
In this project: one repair milestone and ninety days. The PPA sets a repair completion milestone. If repair isn't complete within 90 days of that date, the offtaker gains the right to terminate the PPA on written notice. Their asset manager isn't re-reading clauses to count days — every date in the chain sits on the calendar, from the milestone through the grace period to the end of the notice window.
PPA termination means the loss of a Material Project Document — an Event of Default under the financing agreement with a 60-day cure. One missed operational date cascades from the offtaker to the lenders.
This project's PPA requires the LC renewed at least 30 days before it expires, with proof delivered 15 days out. Miss the window and the offtaker may immediately draw the entire amount. The LC itself is issued under the financing agreement and auto-extends each year — unless the issuing bank opts out, which it may do up to that same 30-day mark. The bank's opt-out notice can arrive the exact day your replacement was due. One instrument, two documents, zero slack. A once-a-year task with no natural owner.
The contract set yielded ~2,500 obligations and ~1,500 defined terms. Volume is the easy part. What makes it dependable:
Not a summary you have to take on faith: the actual contract language, with the section number, one click from every entry. Check any of it against your executed documents.
When the current rent schedule lives in the fourth amendment, you see the current answer — and the old language is marked superseded, with dates. Defined terms resolve across every agreement.
"Within ninety (90) Days following the Repair Completion Milestone Date" becomes an actual date. Monthly reports, annual forecasts, renewal windows: recurring obligations carry their schedules.
Obligations arrive grouped by concern and filterable by document, party, and type — not as a 2,500-row spreadsheet. Anything your team doesn't track can be dismissed. The extraction is the starting point. Your team's judgment is the product.
Every obligation across every contract, grouped by cadence — what's due this week, this quarter, this year — with each entry one click from its verbatim clause.
Set what your team tracks once — payment deadlines, notice windows, reporting duties — and Kaskad respects it across every contract in the portfolio.
Milestone dates, capacity figures, counterparty details — the external facts your obligations depend on, kept alongside the clauses that consume them.
Pre-built cascade narratives: when an outage, casualty, or counterparty default hits, the chain of triggered obligations is already traced — across every agreement at once.
PPAs, interconnection agreements, financing stacks, ground leases and their amendments.
Leases and amendment chains, lender consents, estoppels, operating agreements.
Concession agreements, O&M stacks, and the financing documents wrapped around them.
Owner-side obligation tracking across the whole contract family.
The common thread: small teams responsible for tens to hundreds of negotiated agreements where a single missed window has seven-figure consequences.
Executed PDFs: leases, PPA, interconnection, financing, amendments. No integration, no data migration.
The full contract set, extracted and cross-referenced in the application: every deadline, deliverable, right, and consequence — organized by concern and resolved to the calendar.
Your GC and asset managers check the output against the source documents. Any entry, any agreement, down to the clause.
Pick the project whose contract set worries you most — the one with the amendments nobody has re-read since closing. Send us the documents and see what your contracts are already telling you.