Understand Value for Money in PPPs: PSC, lifecycle costs, risk allocation, CAPEX, OPEX, performance, affordability, bankability, and decision governance.

Check it out!

Value for Money (VfM) in PPPs assesses whether procurement through a public-private partnership provides a better combination of costs, benefits, quality, risks, and lifecycle performance than other delivery alternatives available to the public authority. It does not simply mean choosing the lowest-cost option, nor proving that every PPP is superior to traditional procurement. The analysis should test whether the proposed structure creates additional public value on a justifiable basis, considering risk, schedule, service quality, flexibility, management capacity, and long-term costs.

What is Value for Money in PPPs?

VfM compares delivery alternatives and seeks to identify which one is likely to produce the best overall outcome for the public authority and users. The analysis combines qualitative and quantitative dimensions and must be consistent with the project’s maturity stage.

The starting point is not to ask how to justify a PPP, but which arrangement delivers the intended service with the best relationship among outcomes, costs, and risks. This distinction prevents the methodology from being used merely to confirm a preselected solution.

Why can’t VfM be reduced to the lowest cost?

Nominal implementation cost is only one part of the decision. A solution may have lower initial CAPEX and still generate higher OPEX, earlier reinvestments, greater exposure to delays, or poorer operational performance. Therefore, the comparison needs to use lifecycle costs and comparable service criteria.

It is also necessary to separate economic efficiency from budget constraints. An alternative may generate good economic value and still be incompatible with fiscal capacity, the disbursement schedule, or the management limits of the granting authority.

How does engineering influence Value for Money?

When the project does not yet have sufficiently characterized technical alternatives, demand, costs, and risks, VfM may merely turn uncertainty into apparently precise numbers. The decision needs to begin with a technically verifiable feasibility basis.

Technical and Economic Feasibility Study

The quality of engineering assumptions directly affects CAPEX, OPEX, schedule, availability, service life, maintenance, reinvestments, and risks. When these assumptions are weak, the economic comparator also becomes weak.

Engineering needs to ensure that the alternatives being compared start from equivalent functional scope. If one option considers redundancy, maintenance, contingency, and asset replacement while the other does not, the cost difference stops representing efficiency and instead reflects asymmetric assumptions.

Technical chain supporting Value for Money analysis

Scope and requirements

CAPEX and OPEX

Risks and schedule

Performance and lifecycle

Comparison of alternatives

VfM decision

Technical chain supporting Value for Money analysis

Public Sector Comparator and comparison of alternatives

The Public Sector Comparator is a hypothetical lifecycle-cost reference for traditional public delivery, adjusted according to the methodology adopted. It can support quantitative VfM, but it does not replace qualitative analysis and should not be treated as a universally mandatory methodology in every jurisdiction.

The comparison needs to make explicit the horizon, scope, schedule, costs, retained risks, transferred risks, service quality, and residual value. Sensitivity tests should show how the conclusion changes when material assumptions change.

Risks, transfer, and retention

Risk transfer only creates value when the risk is allocated to the party best able to manage it. Excessive transfer can increase price, reduce competition, or make the project unfinanceable. Poorly defined risks may later reappear as claims, rebalancing events, delays, or reduced performance.

The risk matrix needs to be connected to engineering, financial modeling, and the payment mechanism. Simply listing a risk in a table does not demonstrate that it has been properly priced or that there is real mitigation capability.

Qualitative VfM and quantitative VfM

The qualitative assessment examines whether the nature of the project favors a long-term contract, integration between investment and operations, performance-based specification, effective risk transfer, and competition. The quantitative assessment compares measurable costs and impacts using consistent assumptions.

The two dimensions are complementary. A favorable numerical result does not correct a lack of competition, unstable requirements, inability to measure performance, or risks that cannot reasonably be transferred.

Performance, availability, and service quality

In PPPs, public value does not derive only from delivery of the asset, but from the service provided throughout the contract. Indicators, service levels, availability, response times, and acceptance criteria need to be verifiable and compatible with the designed infrastructure.

Poorly formulated targets distort VfM because they disconnect payment, risk, and outcome. Overly strict targets can increase price without proportional benefit; loose targets can reduce apparent cost while degrading service.

CAPEX, OPEX, and reinvestments need to use the same basis

Comparing alternatives requires CAPEX, OPEX, reinvestments, and contingencies to be built on the same scope basis. Without consistent cost engineering, price differences may merely reflect incompatible assumptions.

Cost Engineering for Engineering Works and Services

CAPEX should reflect quantities, design assumptions, constraints, interfaces, mobilization, and contingencies compatible with project maturity. OPEX should reflect the operating model, maintenance, personnel, energy, insurance, licenses, technology, replacements, and other recurring costs.

Reinvestments deserve explicit treatment because long-term contracts span cycles of wear, obsolescence, and replacement. Ignoring these events can artificially favor the alternative that postpones costs to later years.

Residual value, handback, and closeout

The condition of the asset at the end of the contract also affects the comparison. Handback criteria, residual life, accumulated maintenance, and required replacements influence the value effectively received by the granting authority.

The VfM of an alternative that returns deteriorated assets at the end cannot be directly compared with another scenario that preserves condition and capacity without adjusting for that difference.

Sensitivity and switching values

A good analysis identifies assumptions capable of reversing the decision. Demand, CAPEX, inflation, schedule, financing cost, operational efficiency, construction delay, and risk value can change the result.

Switching values help show the point at which the preferred alternative ceases to be superior. This turns the analysis into a decision and monitoring instrument instead of producing only a point estimate.

Governance of assumptions and traceability

Each material assumption should have a source, date, owner, calculation method, and link to the discipline that originated it. Changes need to be controlled because a revision in demand or technical solution may alter costs, risks, and economic results.

The calculation record should allow independent reproduction. If the conclusion depends on undocumented manual adjustments, VfM loses auditability.

When should VfM be updated?

VfM should not be treated as a frozen document if the project structure changes materially. Relevant changes in scope, CAPEX, schedule, risks, financing, payment mechanism, or performance requirements may require reassessment.

Updating is especially relevant between initial studies, public consultation, finalization of procurement documents, and received bids because the project may gain information that changes the original comparison.

How to procure studies supporting VfM

The scope should provide for traceable assumptions, comparable alternatives, a risk matrix, lifecycle costs, performance criteria, scenarios, and records of the sources used. The public authority needs to be able to review the logic of the decision, not merely receive the final result.

Deliverables should clearly separate input data, assumptions, calculations, results, sensitivities, and limitations. The team needs to integrate engineering, costs, risks, operations, and financial-economic assessment without confusing technical responsibilities.

How to structure an alternatives comparison matrix

A Value for Money analysis needs to make explicit what is being compared. The PPP alternative, conventional public procurement, and any intermediate arrangements should share the same service objective, the same time horizon, and equivalent performance requirements. If one alternative considers higher service levels, greater redundancy, or more complete reinvestments, the comparison no longer isolates the effect of the delivery model.

DimensionComparison questionExpected technical evidence
ScopeDo the alternatives deliver the same functional outcome?Equivalent requirements, capacities, and boundaries
CAPEXDo costs use the same quantities and maturity basis?Calculation record, assumptions, and contingencies
OPEXDo operations and maintenance represent the same service level?Operating model and lifecycle costs
RisksWhich risks remain public and which are transferred?Risk matrix, quantification, and treatment
ScheduleIs there a real difference in implementation speed?Schedule, critical path, and interfaces
PerformanceHow will quality and availability be measured?Indicators, service levels, and acceptance criteria
CloseoutWhat condition will the asset be in at the end?Residual life, reinvestments, and handback

This discipline also prevents VfM from being confused with a comparison between public and private prices. The real objective is to compare ways of delivering the same service over time.

How to treat risks quantitatively in VfM

Risks alter the expected cost of each alternative. The analysis should identify events, estimate probability and impact where there is sufficient basis, and distinguish retained, shared, and transferred risk. A risk matrix that is well structured does more than support the contract: it helps explain why a given delivery model may create or destroy value.

Quantification should not create false precision. When historical data are weak, it is preferable to work with ranges, scenarios, and sensitivity rather than assign an apparently exact probability. The uncertainty of the estimate itself needs to remain visible in the result.

Risks transferred to the private party normally reappear in the bid price. VfM exists precisely to assess whether the cost of that transfer is lower than the benefit of reducing public exposure and improving performance incentives. Transferring a risk the private party cannot control tends to increase price without producing corresponding efficiency.

Competitive neutrality and costs that cannot be forgotten

Comparisons between traditional procurement and PPPs can be distorted when only one alternative includes administration, insurance, taxes, financing, oversight, or contract-management costs. The methodology needs to treat structural differences transparently to prevent the decision from resulting from accounting asymmetry.

The same applies to public costs for preparation, procurement, monitoring, verification, and management of a long-term contract. A PPP does not eliminate the need for public-sector capacity; in many cases, it requires a more qualified public governance function for decades.

Delivery time can also create value

Schedule differences may affect social benefits, operating costs of the existing system, revenue, and exposure to inflation. If the private structure allows earlier service availability, that benefit needs to be analyzed using consistent criteria. If the accelerated schedule is merely an assumption unsupported by permitting, land availability, or engineering, the benefit disappears.

Therefore, schedule and maturity should be assessed together. The content on Project Readiness is useful for distinguishing a physically executable schedule from a merely desired one.

Competition and market quality are part of Value for Money

A theoretically efficient structure can lose value if there are few bidders capable of competing, unnecessary barriers to entry, or risks that drive the market away. The analysis should consider the capacity of suppliers, lenders, and operators, as well as the degree of standardization or technological specificity of the project.

Technical requirements need to preserve competition without reducing performance. An overly prescriptive specification may limit innovation; a vague specification may transfer uncertainty into incomparable bids. The balance among functional requirements, performance criteria, and freedom of solution is part of project structuring.

How VfM relates to cost-benefit analysis

The cost-benefit analysis asks whether the project, viewed from an economic and social perspective, produces benefits greater than the relevant costs. VfM answers a different question: among viable ways of delivering the project, which structure is likely to produce better value?

The two analyses may use common information, but they should not be confused. A socially desirable project may not show VfM as a PPP; in that case, the correct conclusion may be to maintain the investment and change the procurement strategy.

How VfM relates to TCO and lifecycle cost

Long-term contracts require looking beyond the initial investment. TCO and lifecycle cost help structure operations, maintenance, consumption, replacements, support, and residual value. These components may explain why an alternative that appears more expensive in CAPEX offers a lower total cost or better performance.

The benefit is legitimate only when durability and maintenance assumptions can be technically demonstrated. Catalog theoretical service life does not replace a maintenance strategy, environmental conditions, criticality, and spare-parts availability.

Audit of assumptions before the decision

Before approving the conclusion, it is advisable to verify whether the main assumptions can be traced to technical sources, design documents, cost databases, and formal decisions. CAPEX, OPEX, schedule, demand, availability, and risks deserve cross-review because small inconsistencies can produce large cumulative effects in long-term contracts.

The review should test consistency, not only arithmetic. A calculation may be mathematically correct and still start from an incorrect quantity, impossible schedule, or maintenance strategy incompatible with the service level. This is where independent technical review adds value.

Ex ante VfM and ex post learning

The VfM used to structure procurement is necessarily prospective. After implementation, actual data on cost, schedule, quality, availability, claims, and performance can be compared with the original assumptions. This analysis does not retroactively change the decision, but it improves future studies.

An organization that preserves baselines, changes, and indicators turns completed contracts into an empirical basis for new estimates. Without this learning cycle, each new project again depends excessively on generic assumptions.

When a PPP may not generate Value for Money

A PPP may be unsuitable when the project is too small to support structuring costs, the scope changes frequently, performance cannot be measured objectively, demand is extremely uncertain, or the risk transfer needed to justify the model is not practicable.

Caution is also warranted for a project with low technical maturity that attempts to use a long-term contract to resolve uncertainties that have not yet been studied. In this situation, deepening pre-feasibility, feasibility studies, design, or operational data may create more value than bringing contract modeling forward.

How to review and accept a VfM study

Acceptance should verify whether the alternatives are comparable, sources and assumptions are documented, risks have been treated consistently, calculations are reproducible, and sensitivity tests address the main uncertainty drivers. The conclusion needs to follow from the evidence presented.

  • identifiable technical and economic baseline;
  • available calculation records and sources;
  • risk matrix consistent with the contracts;
  • documented scenarios and sensitivities;
  • explicit limitations and assumptions;
  • a conclusion that compares alternatives without confirmation bias.

Affordability, Value for Money, and bankability answer different questions

Three analyses often appear together and should not be treated as synonyms. Affordability checks whether the public authority can support the project’s financial obligations within its fiscal and budget capacity. Value for Money compares delivery methods and seeks to identify which one produces better overall value. Bankability examines whether the structure is acceptable to lenders and can support debt under reasonable conditions.

A project may show positive VfM and fail affordability; it may also be economically desirable and fail to achieve bankability. Governance should keep these questions separate to prevent a favorable conclusion in one dimension from being used as automatic proof of the others.

Steps in a technically defensible VfM analysis

The sequence begins with defining the public service and the genuinely available alternatives. Common assumptions for scope, demand, performance, schedule, and lifecycle are then consolidated. Only then does it make sense to estimate costs, identify risks, adjust differences among models, and run sensitivity tests.

  1. define the service outcome to be compared;
  2. select plausible delivery alternatives;
  3. normalize scope, requirements, and time horizon;
  4. estimate CAPEX, OPEX, reinvestments, and residual value;
  5. identify and treat the risks of each alternative;
  6. assess differences in schedule, performance, and flexibility;
  7. run scenarios and switching values;
  8. document limitations, conclusions, and conditions for future review.

The order matters. Starting from the financial result and adjusting assumptions until one alternative appears superior creates confirmation bias. The study should preserve the real possibility of concluding that the PPP is not the best arrangement.

Model quality and version control

Models used for public decision-making need to be reproducible. Inputs, formulas, assumptions, base dates, and scenarios should remain identifiable; material changes need to record reason, author, and effect on the result. A design revision that increases CAPEX, for example, should flow through to the economic model without loss of traceability.

Version control also prevents reports, presentations, and spreadsheets from using different baselines. The conclusion submitted for decision should point to a frozen set of assumptions and documents, preserving the audit trail.

Transaction costs and institutional capacity are part of the comparison

Structuring, procuring, financing, and managing a PPP have their own costs: studies, advisory services, competitive processes, verification, oversight, contract management, and potential renegotiation. These costs may be small relative to large projects, but become materially relevant when the project is small or not very complex.

There is also a cost associated with institutional capacity. Long-term contracts require a team capable of monitoring indicators, changes, risks, assets, and obligations. If that capacity does not exist and is not planned for, part of the value expected during structuring may be lost during execution.

How to deal with incomplete data without fabricating precision

Early-stage projects rarely have all the necessary information. The correct response is not to fill gaps with a single arbitrary value, but to classify information quality, record ranges, and test decision sensitivity. Critical assumptions with low reliability should trigger engineering action before the next gate.

When an uncertainty could change the preferred delivery model, it deserves priority investigation. Existing-condition surveys, demand studies, site investigations, asset diagnostics, or cost reviews may be economically small compared with the value of avoiding a structuring decision based on weak data.

Final considerations

Value for Money is a structuring decision supported by engineering, economics, risk, and governance. Its value lies in disciplined comparison among alternatives, not in confirming a PPP choice in advance. The better the quality of technical assumptions and traceability, the more defensible the public decision.

At the conclusion of VfM, technical risks need to be identified, quantified, and associated with owners and responses. Contractual allocation does not correct a risk that was never properly characterized.

Engineering Risk Management

Technical references

[1] WORLD BANK. Assessing Value for Money of the PPP. Available at: https://ppp.worldbank.org/assessing-value-money-ppp

[2] WORLD BANK. Appraising Potential PPP Projects. Available at: https://ppp.worldbank.org/appraising-potential-ppp-projects

[3] GOIÁS. PPP and Concessions Manual. Available at: https://goias.gov.br/goiasparcerias/wp-content/uploads/sites/37/2024/03/ManualdePPPseConcessoes.pdf

Frequently asked questions
Does Value for Money mean lowest cost?

No. VfM considers costs, benefits, quality, risks, and performance throughout the lifecycle and compares delivery alternatives.

Is the Public Sector Comparator mandatory for every PPP?

There is no single universal rule. The applicable methodology depends on the institutional framework and the structuring process adopted.

What is the role of engineering in VfM?

Engineering provides assumptions for scope, CAPEX, OPEX, schedule, performance, service life, reinvestments, and risks that support the comparison.

When does VfM need to be reviewed?

When material changes in scope, costs, risks, schedule, financing, or performance requirements alter the assumptions that supported the decision.

Additional technical resources

Related services

Core content on the topic

Related technical content