The decisions behind your portfolio, on the record.
Who decided what, on whose behalf, and what follows.
Every energy project is shaped by decisions taken away from it — in investment committees, boards, steering committees, lender meetings. Navorda Decisions records each one on the project it concerns: the forum, the date, the reference in the minutes, who it was taken on behalf of, the rationale and alternatives, the approved amount and capacity, the conditions attached. Then it keeps the follow-through honest: commitments become owned, dated tasks and evidence is attached to the record.
Reality travels upstream. Decisions and accountability travel downstream. Navorda governs both.
Last updated
Sound familiar?
Decisions live in minutes nobody reopens
The committee approved the EPC award with two conditions. Six months later the conditions are a line in a PDF on a shared drive, and nobody owns checking them. The decision happened; its governance did not.
Reality and decisions travel in opposite directions
Project status flows up to management through reports and decks. Decisions flow back down through email and hallway conversations. The two never meet in one record, so nobody can answer "what did we decide about this project, and did it happen?"
Accountability without a name on it
"The board decided", "the fund approved", "management agreed". Decisions taken on behalf of a committee, an SPV or a lender have no owner in the system — and the commitments that follow have no deadline.
Reality travels upstream. Decisions and accountability travel downstream.
Navorda governs project reality — milestones, land, contracts, risks, finance — and reports it upstream to management. Decisions closes the loop downstream: what management decided on that reality, on whose behalf, under which conditions, and which commitments and evidence follow. Status, closure and authorship are stamped automatically, in the same governed, versioned workspace as your milestones, land, contracts and risks. Navorda governs both directions.
What a decision record holds
Delivered as a default catalog every organization can edit. Grouped exactly as the product shows it.
Plus, on every record: the project it belongs to, the counterpart it was taken on behalf of, its commitments (Activities) and its evidence (Documents).
Default forums: Investment Committee, Board of Directors, Executive Committee, Steering Committee, Project Committee, Shareholders' Meeting, Lender / Bank Committee, Management (delegated authority). All editable.
A decision record holds five cards. Status: Status, Closed at, Closed by; the last two are stamped automatically. Identification: Decision type, Forum, Decision date, Reference (minute / resolution number). Rationale and impact: Rationale, Alternatives considered, Impact if not implemented. Economics: Currency, Approved amount, Approved capacity (MW). Conditions and follow-up: Conditions, Conditions status, Conditions due date, Review date, Comment. Every record also carries the project it belongs to, the counterpart it was taken on behalf of, its commitments (activities), its evidence (documents).
The default catalog: 19 fields in five cards. Rename, add, reorder and relist per organization.
Every decision, on the record. Every commitment, followed through.
A decision record: "Approve EPC contract award" — Investment Committee, Approved with conditions, on behalf of the Investment Committee — with the Economics and Conditions cards, two commitments with owners and due dates, and the signed resolution attached.
Illustrative records. Fields and lists are configurable per organization.
- Approve EPC contract award · Investment Committee · Approved with conditions · on behalf of the Investment Committee
- Hold project pending grid capacity confirmation · Steering Committee · Deferred · review date set
- Approve land option budget · Management (delegated authority) · Implemented · closed automatically
- Change module technology to bifacial · Project Committee · Approved · 2 commitments open
- Decline co-development partnership · Board of Directors · Rejected · rationale and alternatives on record
Illustrative decision record for the fictional project SOL-ES-017, Solar Alpha. The decision "Approve EPC contract award" was taken by the Investment Committee on 12 September 2026, reference IC-2026-09/04, on behalf of the Investment Committee, and its status is Approved with conditions. The Economics card shows an approved amount of 48 million euros and an approved capacity of 100 MW. The Conditions card records one condition, grid connection permit secured before NtP, with status Pending, a due date of 30 November 2026 and a review date of 15 December 2026. Two commitments follow as Activities: deliver the grid connection permit, owned by M. R., due 30 November 2026, in progress; and sign the EPC contract, owned by A. T., due 31 October 2026, open. One document is attached as evidence: the signed resolution IC-2026-09.pdf.
Illustrative example. Fictional project, round figures, generic committee names.
Record the decision. Follow it through.
One record per decision, on the project
Each decision belongs to a project and carries its own identity: name, type (investment, divestment, budget approval, contract award, financing, land strategy, grid and permitting strategy, hold or stop…), forum, date and the reference in the minutes or resolution. A project's Decisions tab is its governance history.
Taken "on behalf of" a named counterpart
Record who the decision was taken on behalf of — the COO, the Investment Committee, a shareholder, an SPV, a lender — from the same counterpart register your land and contract teams already use. Accountability gets a name, and you can filter and report by it.
Commitments tracked, not remembered
A decision's follow-ups are created as Activities on the record: an owner, a supervisor, a due date and a status on the company-wide board. "Deliver the grid permit by November" stops being a sentence in a minute and becomes a task someone is accountable for.
Evidence attached to the record
Attach the committee memo, the signed resolution, the approval email. The decision and its proof stay together, on the project, under the same access control as everything else.
Conditions, lifecycle and closure
Approved with conditions? Record the conditions, their status (pending, partially met, met, waived) and their due date, plus a review date. Move the status through Proposed, Under review, Approved, Approved with conditions, Deferred, Implemented, Rejected, Superseded or Withdrawn — and the moment a decision is closed, the record stamps when and by whom.
Your fields, your vocabulary
The record's fields are configurable per organization: rename them, add your own, reorder the cards, change the lists of forums and decision types, and even call the module "Resolutions" if that is your word. Approved amounts are formatted in the decision's own currency, and approved capacity is tracked in MW.
Governed like the rest of your portfolio
A decision register is only worth having if it can be trusted. Decisions inherits every control the platform already applies to your data.
Role-based access
Who may read, create, edit, delete or export decisions is a permission, assigned per role. Viewers see the register; editors maintain it; exports are a separate right.
Version snapshots
Decision records are part of your versioned data. Lock a baseline and the decisions as they stood at that date stay readable next to the milestones and figures of the same snapshot.
Authorship on every change
Who created and last edited a record is always visible, and closing a decision stamps the date and the user automatically.
Nothing lost by accident
Deleted decisions go to the Recycle Bin and can be restored by an administrator.
Duplicate across projects
A decision that covers several projects is recorded once per project — duplicate it to the next project with its fields and "on behalf of" carried over. Commitments stay with the original.
Readable by your AI, never writable
The Navorda MCP Connector exposes decisions to Claude, ChatGPT and other MCP clients through two read-only tools — "which decisions were approved with conditions this quarter?" — with counterpart contact data structurally excluded.
What teams can now answer
- What did the Investment Committee decide about this project — and did it happen?
- Which decisions were approved with conditions this quarter, and which conditions are still pending?
- Who owns the commitments that followed the last contract award, and by when?
- Which decisions were taken on behalf of a lender or an SPV, and where is the evidence?
How it works
Record the decision on the project
From the project's Decisions tab or the Decisions register: name it, pick the forum, the date and the status, enter the rationale and the approved amount, and choose who it was taken on behalf of.
Turn it into commitments
Add the follow-up tasks as Activities on the record, each with an owner and a due date. Attach the memo or the signed resolution as evidence.
Follow it through
Track the conditions until they are met, review on the review date, and move the status to Implemented. The closure is stamped. Report across the register with the pivot report or export it to Excel, CSV or PDF.
Included in Navorda Platform, connected to the rest
Decisions are taken where they are taken today — committees, boards, lender meetings. Navorda Decisions is the register of record for those decisions and the follow-through: it does not route approvals, collect votes or sign documents. Commitments and evidence are first-class Activities and Documents, shared with the rest of the workspace; a dedicated pivot report and Excel, CSV and PDF exports read the register.
A register of record. Not a workflow engine.
A decision register is only worth having if it is honest about what it does. Navorda Decisions records and follows through; it does not take the decision, run the meeting or rewrite the project.
Navorda Decisions governs
- One record per decision, on the project it concerns: forum, date, reference, rationale, alternatives, approved amount and capacity
- Who the decision was taken on behalf of, from the counterpart register
- Conditions, their status and due date, and the review date
- Commitments as owned, dated Activities, and the evidence attached to the record
- Status, closure and authorship, stamped automatically and kept in every version snapshot
- Who may read, create, edit, delete or export, per role
Your committees and tools keep governing
- Taking the decision: committees, boards and lender meetings decide; Navorda records
- Agendas, meetings and minutes: the Reference field points at minutes kept where they are
- Approval routing, votes and e-signature
- Changing milestones, budgets or finance entries: a recorded decision does not rewrite the project by itself
Who decided, on whose behalf, under which conditions — and whether it happened.
Frequently asked questions
Put your decisions on the record
Who decided, on whose behalf, under which conditions — and whether it happened. In the same governed workspace as the rest of your portfolio.