Skip to content
Request Demo

Availability Payment vs. Demand Risk Models

Comparison • Intermediate • 2 min read

Audience
Government Agencies • Asset Owners • Lenders • Model Developers
Last Reviewed
July 2026
Updated
Version 1.0

Executive Summary

Availability payment and demand risk are the two primary revenue structures for concession-based infrastructure assets, differing fundamentally in which party bears usage risk. This comparison sets out the modelling differences between the two from an ongoing operations perspective: revenue driver, sensitivity testing focus, and the specific mechanics each requires in an operations-phase financial model.

Key Takeaways

  • Availability payment revenue depends on the asset meeting a defined performance standard regardless of usage; demand risk revenue depends directly on actual usage volume, and this fundamental difference drives distinct modelling and sensitivity testing priorities for each structure.
  • An availability payment model's central modelling risk is the deduction mechanism's correct implementation; a demand risk model's central modelling risk is the usage or throughput forecast and its downside scenario testing.
  • Availability payment revenue is generally lower-volatility from the operator's perspective, since it does not depend on unpredictable usage, while demand risk revenue carries genuine volume risk the operator must actively forecast and manage against.
  • Some infrastructure contracts blend the two structures, for example a minimum availability payment with an upside usage-linked bonus, and a model representing such a hybrid should build both mechanisms explicitly rather than approximating one as a proxy for the other.

Overview

Availability payment and demand risk are the two primary revenue structures used in concession-based infrastructure financing and operation. This comparison sets out the modelling differences between them from an ongoing operations perspective, extending the concession-level definitions in Availability Payment Model and Demand Risk Model.

Side-by-Side Comparison

Dimension Availability Payment Demand Risk
Revenue driver Meeting a defined availability/performance standard Actual usage or throughput volume
Usage risk borne by Public authority or contracting party Operator
Central modelling risk Deduction mechanism correctness Usage/throughput forecast accuracy
Revenue volatility (operator perspective) Generally lower Generally higher
Key sensitivity test Performance failure scenarios Downside usage/traffic scenarios
Typical sectors Social infrastructure (schools, hospitals), some rail/road PPPs Toll roads, some rail, ports

Modelling Focus for Each Structure

An availability payment operations model, covered in Availability Payment Modelling, centres on correctly implementing the deduction mechanism at the granularity the underlying agreement specifies, since this formula, not a usage forecast, is what actually determines realised revenue.

A demand risk operations model instead centres on the usage or throughput forecast, requiring explicit downside scenario capability across a realistic range of usage outcomes, since the operator's actual revenue depends directly on volumes it does not fully control.

Hybrid Structures

Some contracts combine elements of both — a minimum availability payment providing a revenue floor, combined with an upside usage-linked bonus above a threshold. A model representing this kind of hybrid structure should build both the deduction mechanism and the usage forecast explicitly, rather than approximating one structure as a rough proxy for the other, since each component responds to a genuinely different underlying risk.

Continue Reading

How OXXON tests thisRun a free structural check with FMAE

Frequently Asked Questions

What is the fundamental difference between availability payment and demand risk models?

Availability payment revenue depends on the asset meeting a defined performance standard regardless of usage; demand risk revenue depends directly on actual usage volume. The public authority or contracting party bears usage risk under an availability payment structure, while the operator bears it under a demand risk structure.

What is the central modelling risk for each structure?

For an availability payment model, it is the deduction mechanism's correct implementation against the underlying performance standard. For a demand risk model, it is the usage or throughput forecast and its downside scenario testing, since the operator's actual revenue depends directly on that forecast's accuracy.

Which structure carries more revenue volatility for the operator?

Demand risk revenue generally carries more volatility from the operator's perspective, since it depends on unpredictable usage volumes, while availability payment revenue is more stable provided the asset meets its performance standard, independent of how many people or how much volume actually uses it.

Can a single infrastructure contract combine both structures?

Yes. Some contracts blend the two, for example a minimum availability payment providing a revenue floor combined with an upside usage-linked bonus. A model representing such a hybrid should build both mechanisms explicitly, rather than approximating one structure as a rough proxy for the other.

Related Articles

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.

Performance-Based Contracts

A performance-based contract 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. This guide covers how to model the payment structure of a performance-based contract: the performance indicator framework, how bonus and deduction mechanics should be built as live formulas rather than static assumptions, and how this contract type differs from cost-based and fixed-fee arrangements.

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.

Demand Risk Model

A demand risk model is a financial model for a project finance concession in which the concessionaire's revenue is derived from user charges (tolls, fares, or fees) paid by users of the asset. The concessionaire's revenue therefore depends directly on actual demand for the asset's services, rather than on contractual availability payments from the public authority. Demand risk models are used for toll roads, airports, ports, urban transit systems, and other infrastructure assets where users pay directly for the service. The key risk in a demand risk model is that actual usage may be materially lower than projected, reducing revenue below debt service requirements.

Request Demo