1 Project Value and the Assessment Baseline

Understanding project value

Project value concerns the outcomes a project is expected to create for stakeholders compared with what would happen without it. Those outcomes may include financial returns and nonfinancial effects, including safety, service quality, compliance, resilience, or customer satisfaction.

A project can create value even if it exceeds its budget. Conversely, meeting cost and schedule targets does not ensure that the intended benefits will be produced. Delivery performance and the value of the resulting outcomes are related, but they are not the same assessment.

When impacts can be expressed in money, an appraisal may compare benefits and costs over time. However, no single ratio captures every relevant consideration: impacts may be difficult to monetize, distributed unevenly, or uncertain. Assess value against project objectives and stakeholder priorities, using financial measures alongside appropriate nonfinancial evidence.

Establishing a credible baseline

A baseline is the documented reference point for assessing a project's expected or actual effects. For a value assessment, it should describe the credible business-as-usual outcome: what is likely to happen if the project does not proceed, including existing activities, expected market developments, and their costs, benefits, and risks. “Without the project” does not necessarily mean that nothing changes.

Record the baseline at a stated date. Document its key assumptions, evidence, objectives, time horizon, and measures. Then compare the project option with that reference point, separating effects caused by the project from outcomes that would have occurred anyway.

If assumptions or circumstances change, preserve the original baseline and record any approved revision. Without this record, apparent improvement or deterioration may simply result from a moving point of comparison.

For example, when considering replacement of an aging system, the baseline should include expected maintenance, failure rates, and service performance if the system remains in use. It should not simply assume zero cost or zero benefit. Assess the replacement by comparing its expected outcomes with this realistic alternative.

Separating value, cost, risk, and feasibility

Value, cost, risk and uncertainty, and feasibility are connected, but each answers a different question:

• Value: What benefits and other outcomes are created, for whom, and relative to what alternative?

• Cost: What money and resources are required, including relevant ongoing and opportunity costs? A cost change affects the value calculation, but is not itself proof that value changed.

• Risk and uncertainty: How might outcomes differ from estimates, and how likely or consequential might those differences be? Risks can change expected value or confidence in it; they are not the same as a realized loss.

• Feasibility: Can the project be delivered and operated within its technical, legal, commercial, organizational, and resource constraints? A project may have attractive potential value but be infeasible, while a feasible project is not automatically worthwhile.

Reassessing when conditions change

Suppose new regulation requires a safety feature in a system replacement. The requirement may increase delivery cost, reduce the range of feasible designs, and lower the project's net value. These are distinct findings: the cost estimate changed, the feasible options changed, and the value comparison must be recalculated.

Changes in market demand, technology, regulation, or economic conditions should likewise be assessed for their effects on the baseline, project outcomes, costs, risks, and feasibility. Rather than describing such a change vaguely as a “value change,” identify which of these elements changed and update the comparison transparently.