Understand the result before acting on it.
These definitions help readers interpret the site. Each analysis must still state its own units, assumptions, boundaries, and rule version.
The project's modeled cost meets or falls below the stated comparison price. This alone does not establish that the project can operate or obtain financing.
The price or cost used for comparison. It must use a comparable product, delivery point, currency year, and cost basis.
The share of the stated production capacity actually used over the stated period. Check the equipment scope and how the analysis defines it.
Actual output over a period divided by the output possible at continuous rated operation. It is not automatically the same as renewable availability or integrated-plant utilization.
The selling price needed for the model to meet its stated financial return requirement.
How easily a cost advantage disappears when the stated assumptions change.
An input value or boundary at which the cost advantage ends under the other named assumptions.
Failure even under the favorable combinations of other inputs allowed by the analysis. A single base-case sensitivity test does not prove this.
The support the project can actually receive after eligibility, timing, and other restrictions are considered.
The fraction of selected test cases that fail a stated condition. It is not a forecast probability unless the scenario weights and probability model justify that interpretation.
Whether the assessment supplies the evidence and follows the procedures required by its named framework version. It does not mean that the project is economically attractive.
The v1.2 rule specification uses the four signals below. They describe the assessment result, not a guarantee of project performance.
The assessment passes the stated rule profile. Continue with the next review step; financing, permits, and other requirements still need attention.
The case passes the relevant cost and stress gates but has the additional exposure identified by the profile. Address that exposure before relying on the result.
Revise the design, assumptions, controls, or evidence and rerun the assessment before proceeding.
Do not proceed on the basis of this assessment. State whether the reason is economic failure, an operating constraint, or incomplete evidence.
Some earlier notes use Go and Conditional Go. Read their local decision tables for the conditions attached to those labels. Conditional Go is not automatically identical to Caution in the v1.2 profile.