Performance-Based Contracts
Executive Summary
Key Takeaways
- ✓ A performance-based contract pays according to measured output or outcome performance rather than input cost, aligning the provider's financial incentive directly with the owner's desired service result.
- ✓ The performance indicator framework underlying the payment mechanism should be modelled as a set of individually tracked metrics with their own threshold and payment consequence, not aggregated into a single blended performance score that obscures which specific metric is driving a payment outcome.
- ✓ Bonus and deduction mechanics should be built as live formulas that actually respond to modelled performance scenarios, since a mechanism only shown functioning in a passing base case has not genuinely been tested.
- ✓ Performance-based contracts shift a different risk than cost pass-through or fixed-fee arrangements, since the provider bears the risk of failing to meet a defined performance standard, while the owner bears the risk that the standard itself was set at an unrealistic or poorly calibrated level.
- ✓ This contract structure is closely related to, but broader than, availability payment and service level agreement mechanisms, which are specific applications of performance-based payment to particular infrastructure contexts.
Objective¶
This guide covers how to model the payment structure of a performance-based infrastructure contract, within Infrastructure Asset Management Financial Modelling, as the general framework specialised by Availability Payment Modelling and Service Level Agreement Models.
Payment Tied to Output, Not Input¶
A performance-based contract pays according to measured output or outcome performance — availability, response time, condition standard, or a similar defined metric — rather than reimbursing the provider's actual input cost. This aligns the provider's financial incentive directly with the asset owner's desired service outcome, in contrast to a cost pass-through arrangement, which reimburses cost regardless of the resulting service quality.
Modelling the Performance Indicator Framework¶
The performance indicators underlying the payment mechanism should each be modelled individually, with its own defined threshold and specific payment consequence, rather than aggregated into a single blended performance score. Aggregation obscures which specific metric — a response time failure, an availability shortfall, a condition standard breach — is actually driving a given bonus or deduction outcome, weakening both internal management of the contract and any external review of it.
Bonus and Deduction Mechanics as Live Formulas¶
Bonus and deduction formulas should be built to respond dynamically to modelled performance scenarios, and specifically tested against scenarios where performance actually falls below or exceeds a defined threshold. A mechanism that has only ever been shown to function correctly in a passing base case, where no deduction is triggered, has not been genuinely verified — the same discipline applied in the PPP Model Checklist to availability payment deduction mechanisms applies equally here.
Risk Allocation¶
A performance-based contract shifts the risk of failing to meet a defined performance standard onto the provider, in exchange for the possibility of a bonus payment for exceeding it. In turn, the asset owner bears the risk that the performance standard itself was calibrated unrealistically — set too easy, such that bonus payments accrue without genuine service improvement, or too difficult, such that the provider cannot realistically meet it regardless of genuine effort, undermining the contract's intended incentive alignment.
Relationship to Availability Payments and SLAs¶
Availability payment mechanisms and service level agreements are specific, widely used applications of the general performance-based payment structure described here: an availability payment ties revenue to a defined availability performance standard, while an SLA more broadly defines multiple service quality metrics with their own thresholds and consequences. Both should be modelled using the same core discipline set out in this guide, specialised to their specific metric set.
Common Construction Pitfalls¶
Blended performance score. Aggregating multiple distinct performance indicators into a single score obscures which specific metric is driving a payment outcome.
Untested deduction mechanism. Building a bonus or deduction formula that has only been verified in a passing base case, with no test of an actual performance shortfall scenario, leaves the mechanism functionally unverified.
Unrealistic performance standard. Setting a threshold without reference to genuine achievable performance data undermines the contract's intended incentive alignment in either direction.
Recommended Practices¶
- Model each performance indicator individually, with its own threshold and payment consequence.
- Build bonus and deduction formulas as live mechanics and test them against actual performance shortfall and outperformance scenarios.
- Calibrate performance thresholds against genuine achievable performance data for the specific asset or service type.
- Disclose the specific metric or metrics driving any bonus or deduction outcome in reporting.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
- Availability Payment Modelling
- Service Level Agreement Models
- Asset Performance KPIs
- O&M Financial Models
Related Glossary¶
Related Checklists¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
What is a performance-based contract?
A contract that pays an infrastructure operator or service provider according to measured output or outcome performance, rather than reimbursing input cost, aligning the provider's financial incentive directly with the asset owner's desired service outcome.
How should the performance indicator framework be modelled?
As a set of individually tracked metrics, each with its own threshold and payment consequence, not aggregated into a single blended performance score, since aggregation obscures which specific metric is actually driving a bonus or deduction outcome.
Why must bonus and deduction mechanics be tested as live formulas?
Because a mechanism only shown functioning correctly in a passing base-case scenario has not genuinely been tested — the formula must be verified to trigger correctly when a modelled performance scenario actually falls below or exceeds a defined threshold.
What risk does a performance-based contract shift, compared to cost pass-through or fixed-fee arrangements?
The provider bears the risk of failing to meet a defined performance standard, while the owner bears the risk that the standard itself was calibrated unrealistically, either too easy to consistently exceed or too difficult to reasonably achieve.
How do performance-based contracts relate to availability payments and SLAs?
Availability payment and service level agreement mechanisms are specific applications of the broader performance-based payment structure to particular infrastructure contexts — this guide covers the general framework both specialise.
Related Articles
Infrastructure Asset Management Financial Modelling
Infrastructure asset management financial modelling is the discipline of modelling an infrastructure asset's ongoing operation, maintenance, and renewal across its full economic life, from the perspective of the owner or operator responsible for that asset once it is in service, rather than the transaction-close or lender perspective covered elsewhere. This page is the hub for the Knowledge Centre's asset management and operations modelling content: how a lifecycle model is structured across planning, construction, operations, renewal, and disposal, how whole-life cost and lifecycle cost analysis compare competing options, and how maintenance, renewal, and capital replacement should be planned and funded. Sector-specific operations models, performance and reliability modelling, and institutional assurance practice for this domain are indexed here as it expands.
Availability Payment Modelling
Availability payment modelling builds the revenue mechanics of an availability-based infrastructure contract into an ongoing operations-phase financial model: the base payment, the deduction formula responding to unavailability or performance failure, indexation, and the lifecycle reserve funding the structure typically requires. This guide covers that operations-phase build, complementing the audit-perspective treatment of the same mechanism covered in the availability payment model glossary entry and the PPP model checklist.
Service Level Agreement Models
A service level agreement (SLA) financial model represents the multiple, individually defined service quality metrics an infrastructure operator commits to meet, the credit or penalty calculation triggered when a metric falls short, and the reporting cadence against which performance is measured. This guide covers how to build an SLA model: structuring each metric independently, avoiding a single composite score, and connecting SLA credits and penalties to the broader operations financial model.
Asset Performance KPIs
Asset performance KPIs are the defined metrics an asset owner tracks to measure whether an infrastructure asset or portfolio is delivering against its level-of-service commitment, spanning physical condition, availability, cost efficiency, and service delivery dimensions. This guide covers which KPIs an asset management financial model should track, how each connects back into the funding and renewal model rather than existing as a standalone reporting exercise, and how KPI selection should match the specific level-of-service targets the asset owner has committed to.
O&M Financial Models
An O&M financial model represents the operating cost, contract structure, and performance incentive mechanics of an outsourced or in-house operations and maintenance arrangement for an infrastructure asset, across sectors including transport, water, and social infrastructure. This guide covers how to build an O&M financial model at this general cross-sector level: the contract types an O&M arrangement typically takes, how cost pass-through and fixed-fee structures differ, and how performance incentives and deductions should be modelled as a distinct mechanic from base O&M cost.
Availability Payment Model
An availability payment model is a project finance structure in which the public authority (the contracting authority) pays the private concessionaire a periodic payment contingent on the asset being available for use according to defined performance and availability standards, regardless of actual usage levels. The payment is not linked to traffic volumes, passenger numbers, or other demand metrics. Revenue risk remains with the public sector; the private sector takes construction risk, availability risk, and performance risk. Availability payment models are common in hospitals, schools, prisons, roads, and rail infrastructure where the contracting authority wishes to retain demand risk while transferring construction and maintenance risk.