Operating model and limits
TOOL 2.0 is a project-control workspace. It connects assumptions, monthly KPI reviews, evidence, actions and dated decision records around one saved project.
The public Beta is free for registered users until 20 November 2026 and requires no payment card. Beta accounts may hold two active projects and five saved versions per project. Intelligence membership remains separate.
Financial outputs remain management-level screening estimates—not engineering design, grid studies, supplier quotations, financing offers or investment-grade forecasts.
Recommended monthly workflow
Select the project
Create or load the project in Project overview before opening any workflow module.
Refresh the case
Update material load, tariff, outage, cost and schedule assumptions in Financial screening.
Complete the KPI review
Choose Developer, Consultant or Owner and assess only that role's monthly KPIs.
Close exceptions
Watch or Blocked KPIs automatically create owned actions with a due date and closure-evidence requirement.
Record the decision
Update evidence, complete actions and issue a dated decision report only after review.
The six modules
Project overview
Create, select and revisit the saved project that anchors all calculations and workflow records.
Financial screening
Test system strategies, costs, benefits and downside cases; save versions when assumptions materially change.
Monthly review
Review role-specific KPIs and record the period's management conclusion and material variance.
Evidence
Register the source, date, scope, limitation and decision supported by each material input.
Actions
Manage exceptions through responsibility, due date, required closure evidence and completion status.
Decision reports
Generate a dated record of reviewed assumptions, outputs and decision gates.
Role-based KPI templates
Choose the participant that owns the decision
Stage gates, schedule and COD, site rights, permits, interconnection, CAPEX and priority-risk closure.
Data completeness, assumptions, deliverables, client decisions, technical issues, evidence currency and next-period work.
Savings, peak demand, resilience, budget, operating impact, internal approvals and stakeholder readiness.
Debt-service coverage, funding, revenue certainty, downside risk, covenants, due diligence and security.
Connection, network constraints, protection, power quality, dispatch, metering and energisation.
Permits, policy eligibility, safety, environment, emissions, community, procurement and reporting.
Design, procurement, construction, quality, HSE, commissioning, availability and maintenance.
KPI status and decision rules
No conclusion has been recorded; this KPI is outside the completed review.
Evidence supports the approved plan and no exception action is required.
A variance needs active monitoring; the system creates an action automatically.
The issue prevents progress or approval; the system creates an action and the review remains on Watch.
Automatic exception actions
When Interconnection is marked Blocked, saving the monthly review creates an Action linked to that KPI. It inherits the review owner and due date. If either is blank, TOOL 2.0 assigns the selected role and a date 30 days ahead. The action states the closure evidence required. Complete it only after that evidence has been registered and checked.
Monthly close checklist
- Select the correct saved project and reporting month
- Review every KPI relevant to your role; do not treat Not reviewed as a pass
- Confirm every Watch or Blocked item has an owner, due date and required closure evidence
- Register current quotations, approvals, studies and datasets in Evidence
- Close actions only after checking the evidence, then issue the dated decision record