Data Centre Scenario Analysis
Executive Summary
Key Takeaways
- ✓ Data centre scenario analysis should move related drivers together consistently, occupancy, pricing, and churn typically deteriorate together in a downside demand scenario, rather than flexing a single driver in isolation.
- ✓ Power cost shock scenarios should test the model's power cost pass-through mechanics explicitly, since who bears power cost volatility depends on the specific tenant or offtake agreement allocation, not a generic cost increase assumption.
- ✓ Tenant concentration scenarios are particularly important for hyperscale build-to-suit facilities, testing a single anchor tenant's counterparty deterioration or early termination, a risk pathway a diversified colocation demand scenario does not capture.
- ✓ Scenario outputs should be presented as a small number of clearly labelled, internally consistent cases (for example, base, downside, severe downside) rather than an unstructured range of individually flexed variables.
Objective¶
This guide sets out how to build correlated, structurally coherent scenario analysis for a data centre financial model within Data Centre Financial Modelling.
Correlated Driver Movement¶
Scenario analysis should move related drivers together consistently rather than flexing a single variable in isolation. In a genuine downside, a market demand slowdown typically depresses both occupancy and achievable pricing while increasing churn simultaneously; a scenario that flexes only occupancy while holding pricing and churn constant is not structurally coherent and understates the combined downside impact.
Power Cost Shock Scenarios¶
A power cost shock scenario should test the financial impact of a material power cost increase against the facility's actual pass-through mechanics: whether cost volatility is borne by the tenant, the operator, or shared under a defined formula in the underlying tenant or offtake agreement. The actual contractual allocation determines who bears the impact, not a generic assumption that operating costs simply rise across the board. See Data Centre Power Consumption Models.
Tenant Concentration Scenarios¶
Tenant concentration scenario testing is particularly important for hyperscale build-to-suit facilities, where revenue is typically concentrated in a single anchor tenant. A scenario testing that tenant's counterparty credit deterioration or exercise of an early termination right, as described in Data Centre Customer Contract Models, captures a risk pathway that a diversified colocation demand scenario, built around many smaller tenants, does not need to and cannot meaningfully represent.
Presenting Scenario Outputs¶
Scenario outputs should be presented as a small number of clearly labelled, internally consistent cases, typically base, downside, and severe downside, each defined by a coherent combination of driver assumptions, rather than an unstructured range of individually flexed variables that does not correspond to any single coherent future state a lender, investor, or board member can reason about directly.
Common Construction Pitfalls¶
Single-variable flexing presented as scenario analysis. Fails to capture the correlated driver movement that characterises a genuine downside.
Power cost shock modelled as a generic cost increase. Ignores the facility's actual pass-through allocation, which determines who actually bears the impact.
No distinct tenant concentration scenario for a hyperscale-anchored facility. Understates the concentrated counterparty risk specific to single-tenant revenue structures.
Recommended Practices¶
- Move related drivers together consistently within each named scenario.
- Test power cost shocks against the facility's actual pass-through mechanics, not a generic cost increase.
- Build a distinct tenant concentration scenario for hyperscale or other single-tenant-anchored facilities.
- Present outputs as a small number of clearly labelled, internally consistent cases.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
Why should scenario analysis move multiple drivers together rather than flex one at a time?
Because in a genuine downside, related drivers typically deteriorate together, for example a market demand slowdown depresses both occupancy and achievable pricing while increasing churn, and a scenario that flexes only one of these in isolation is not structurally coherent and can understate the combined downside impact.
What is a power cost shock scenario and how should it be modelled?
A scenario testing the financial impact of a material power cost increase, modelled against the facility's actual power cost pass-through mechanics, whether cost volatility is borne by the tenant, the operator, or shared under a defined formula, since the actual contractual allocation determines who bears the impact, not a generic assumption that costs simply rise.
Why does tenant concentration scenario testing matter particularly for hyperscale facilities?
Because hyperscale build-to-suit revenue is typically concentrated in a single anchor tenant, so a scenario testing that tenant's counterparty credit deterioration or early contract termination captures a risk pathway that a diversified colocation demand scenario, built around many smaller tenants, does not need to and cannot meaningfully represent.
How should scenario outputs be presented?
As a small number of clearly labelled, internally consistent cases, typically base, downside, and severe downside, each defined by a coherent combination of driver assumptions, rather than an unstructured range of individually flexed variables that does not correspond to any single coherent future state.
Related Articles
Data Centre Financial Modelling
Data centre financial modelling is the discipline of modelling a data centre operator's revenue, cost, and capital structure from its capacity-denominated drivers, power, space, and cooling capacity, rack density, and tenant contract structure, rather than the generic market-price and headcount-growth drivers used in most corporate models, or the pure occupancy-and-lease-term drivers of conventional commercial real estate. This page is the hub for the Knowledge Centre's data centre financial modelling content: how colocation, hyperscale, and enterprise business models each require a distinct model architecture, how rack revenue and occupancy are decomposed into their separable underlying drivers, and how capacity planning and financial KPIs tie the model together, as this domain expands to cover operations, revenue, investment, and governance practice across the sector.
Data Centre Sensitivity Analysis
Data centre sensitivity analysis flexes one driver at a time, holding all others constant, to rank which individual assumptions, occupancy, pricing, power cost, and PUE, most affect model outputs such as revenue, EBITDA, or debt service coverage. This guide sets out how to construct a driver-by-driver sensitivity table for a data centre model and how it complements, rather than substitutes for, correlated scenario analysis.
Hyperscale Data Centre Models
Hyperscale data centre models finance a facility developed and leased to a single large cloud or technology tenant under a long-dated contract, structured around phased, capacity-denominated capex drawdown rather than a single completion event. This guide sets out how to model phased delivery, contracted revenue recognition, and the concentrated counterparty and power availability risks distinctive to this business model.
Data Centre Customer Contract Models
Data centre customer contracts carry specific structural provisions, SLA-linked service credits, renewal options, fixed annual escalators, and early termination rights, that materially affect revenue durability and should be modelled explicitly rather than assumed away in a simplified revenue growth curve. This guide sets out how to model each provision's financial effect and why contract-level detail matters more in this sector than in a generic subscription revenue model.