Stop tracking the power sale apart from the project that delivers it.
From contracted MW to delivered MW.
Navorda Offtake is the commercial layer of energy project development: the agreement that sells a project's power, recorded against the project that has to produce it. Physical and virtual PPAs, private wire, behind-the-meter, tolling and route-to-market — with commercial, delivery, credit and legal terms captured as structured fields. Govern what the project has committed to deliver — without replacing the systems that trade, settle or dispatch the energy.
Same project reality. More specialist depth: keep commercial commitments connected to the projects that must deliver them.
Last updated
Sound familiar?
The agreement is a PDF
Signed offtake agreements live on a shared drive. The contracted capacity, the delivery start date and the longstop are all in there somewhere — but none of them are data you can filter, sort or report on without opening the file and reading it.
The contract and the project live apart
The agreement is tracked in one system and the project that has to supply it in another. The link between them is a person's memory, and it holds right until the week that person is away and a permit date moves.
No portfolio answer when a project moves
When a project's schedule shifts, the question that follows is immediate: what have we already promised, to whom, and from when? Answering it means reopening contracts one at a time, which is why it usually gets answered late.
Contracted MW is not delivered MW.
A signed agreement is a promise with a date on it. When the promise lives in a contract folder and the project that has to keep it lives in a development system, the two are reconciled only when someone remembers to — usually in the weeks before a delivery date, by which point the options that existed a year earlier have closed. That distance between what has been sold and what is being built is not a reporting problem. It is where the commercial consequence of a development delay accumulates, unmeasured.
Everything you need
See what each project has already been promised
Every agreement is recorded against the project that generates the power, and each project page carries an Agreements tab listing what that specific asset supplies. Commercial commitments sit next to the permits, land and risks they depend on.
The stage is the one the dates support
Stage is calculated from the milestone dates actually recorded — negotiation started, term sheet, heads of terms, signed, effective, delivery start, delivery end, terminated. It is never typed by a user, so there is no stale status field nobody updated.
Nine agreement types, and you can add your own
Physical PPA, corporate PPA, virtual PPA/CfD, private wire, behind-the-meter, tolling, route-to-market and green-attributes sale ship as defaults. The list is configurable data, so a new structure does not wait for a software release.
Commercial terms as data, not prose in a notes box
Contracted capacity, annual volume, strike and floor price, tenor, pricing structure, indexation, escalation rate and currency are structured fields — filterable, sortable, exportable, and usable in the calculated metrics you define yourself.
Per-project exposure you read rather than recalculate
An agreement supplied by several projects is entered once per project, each piece holding its own contracted capacity. What a given asset owes is a value on the record, not a calculation someone redoes for every report.
Delivery, credit and legal terms captured before they matter
Delivery point, green-attribute treatment and balancing responsibility, alongside credit support, conditions precedent, longstop date, change-in-law protection and termination rights. The clauses that decide who carries what are recorded rather than assumed.
What teams can now answer
- Which agreements does each project supply, and what capacity has that project been committed to?
- What are the delivery start and longstop dates across every agreement in the portfolio?
- Which offtakers hold agreements with more than one of your projects?
- Which agreements are still pre-signature, and which are already effective?
- Could you export a register of contracted capacity, tenor and pricing structure for a lender tomorrow?
How it works
Record the agreement against its project
Create the offtake agreement on the project that generates the power. Where several projects supply one agreement, duplicate it per project so each piece carries its own contracted capacity.
Capture the terms that matter to you
Fill the commercial, delivery, credit and legal fields — or add, remove and regroup them, and rename the entity itself to PPA or whatever your team calls it, so the add-on matches your process instead of imposing one.
Read it wherever the question comes up
From the project's Agreements tab, from the list with the columns and filters your role needs, or from a CSV, Excel or PDF export.
Works seamlessly with the rest of Navorda
Navorda Offtake complements your ETRM, trading and settlement systems. It governs the agreement against the project that has to deliver it — contracted capacity, delivery dates, credit and legal terms — without touching settlement, meter data, imbalance, dispatch optimisation or forward curves, which stay where they already work.
Built on the same operating model
A signed agreement is a promise with a date on it. Navorda Offtake keeps that promise on the same record as the permits, land and milestones that decide whether the project can keep it.
Platform governs whether the project can deliver. Navorda Offtake governs what it has committed to deliver.
Navorda Platform governs: Project, then Permits, then COD, then Delivery obligation. Navorda Offtake manages: PPA, then Contracted MW, then Delivery start, then Longstop. COD slips → the delivery-start and longstop dates on the PPA that project supplies are read against the new COD, and the gap is visible at portfolio level.
Ready to see contracted capacity next to the projects that deliver it?
Put the power sale agreement in the same operating model as the land, permits and milestones it depends on.