Data Centre Customer Contract Models
Executive Summary
Key Takeaways
- ✓ Data centre customer contracts carry SLA-linked service credit provisions, renewal options, fixed escalators, and early termination rights, each of which should be modelled as an explicit provision rather than absorbed into a simplified revenue growth curve.
- ✓ SLA service credits should be modelled as a contingent revenue deduction tied to an uptime or performance assumption, not ignored on the assumption that the facility will always meet its committed service level.
- ✓ Renewal options, particularly tenant-favourable options exercisable at a pre-agreed rate, should be modelled as reducing the operator's re-pricing flexibility at the original contract's expiry.
- ✓ Early termination rights, where present, should be modelled as a specific downside scenario input, since they represent a revenue risk a standard churn assumption does not capture.
Objective¶
This guide sets out how to model data centre customer contract structure within Data Centre Financial Modelling, and how specific contractual provisions affect revenue durability.
Why Contract-Level Detail Matters¶
Data centre contracts, particularly wholesale colocation and hyperscale agreements, are typically large, long-dated, and individually negotiated. Unlike a high-volume, low-average-contract-value subscription business where individual contract terms average out across a large customer base, a single data centre contract's specific provisions can materially affect the facility's revenue durability, and should be modelled explicitly rather than absorbed into a simplified aggregate growth curve.
SLA Service Credit Provisions¶
Most data centre contracts include service level agreement (SLA) provisions specifying committed uptime or performance levels, with defined service credits owed to the tenant if the facility fails to meet them. These should be modelled as a contingent revenue deduction tied to an explicit uptime or performance assumption, informed by the facility's historical or benchmarked service level performance, rather than ignored on the assumption the facility will always meet its committed service level.
Renewal Options¶
Some contracts grant the tenant a renewal option exercisable at a pre-agreed rate, rather than the prevailing market rate, at the original term's expiry. This reduces the operator's re-pricing flexibility, and the model should apply the pre-agreed renewal rate for contracts carrying this provision, rather than assuming a market-rate reset consistent with Data Centre Pricing Models.
Escalation Clauses¶
Fixed annual escalators applied to the existing contracted base should be modelled against the specific escalator rate in each contract, consistent with the practice described in Colocation Financial Models, rather than a single blended portfolio-wide escalation assumption that can misstate the run-rate revenue base if escalator rates vary materially across the contract book.
Early Termination Rights¶
Where a contract includes an early termination right, the model should treat exercise of that right as a specific, distinct downside scenario input, modelling both the revenue loss and any termination fee, rather than folding this risk into a generic portfolio churn assumption, since early termination is a contract-specific, often binary risk rather than a statistically diversified churn pattern. See Take-or-Pay Contract for how this risk interacts with take-or-pay revenue protection.
Common Construction Pitfalls¶
SLA service credits ignored. Overstates revenue by assuming perfect service level performance with no contingent deduction.
Uniform escalator assumption across a contract book with varying escalator rates. Misstates the run-rate revenue base.
Renewal assumed at market rate despite a tenant-favourable pre-agreed renewal option. Overstates achievable re-pricing at contract expiry.
Early termination risk folded into a generic churn assumption. Understates the concentrated, contract-specific nature of this risk, particularly for large individual contracts.
Recommended Practices¶
- Model SLA service credits as a contingent deduction tied to an explicit performance assumption.
- Apply each contract's actual escalator rate rather than a blended portfolio assumption.
- Reflect pre-agreed renewal rates where a tenant-favourable renewal option exists.
- Model early termination risk as a specific downside scenario, not a generic churn assumption.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
Related Glossary¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
Why does contract-level detail matter more in data centre modelling than in a generic subscription model?
Because data centre contracts are typically larger, longer-dated, and individually negotiated, with provisions, SLA service credits, renewal rights, and termination rights, that can materially affect revenue durability at the level of a single contract, unlike a large-volume, low-average-contract-value subscription business where individual contract terms average out.
How should SLA service credit provisions be modelled?
As a contingent revenue deduction tied to an explicit uptime or performance assumption, reflecting the probability and magnitude of service credits the operator would owe tenants under its historical or benchmarked service level performance, not ignored on the assumption the facility will always meet its committed service level.
How do renewal options affect the model?
A tenant-favourable renewal option, exercisable at a pre-agreed rate rather than the prevailing market rate, reduces the operator's re-pricing flexibility at the original contract's expiry, and the model should reflect the pre-agreed renewal rate rather than assuming a market-rate reset for contracts carrying this provision.
How should early termination rights be modelled?
As a specific downside scenario input, modelling the revenue and any termination fee impact if the right is exercised, since early termination represents a distinct, contract-specific revenue risk that a standard portfolio-level churn assumption does not capture.
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 Pricing Models
Data centre pricing modelling sets the strategic assumptions behind the per-unit rates applied in a rack revenue model, list price versus negotiated discount, contract term length and its associated discount, and competitive benchmarking against comparable facilities. This guide sets out how to model pricing strategy as a distinct layer from billing mechanics, and why blending the two conceals whether a revenue change is coming from volume, mix, or genuine pricing movement.
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.
Take-or-Pay Contract
A take-or-pay contract is a common structure in hyperscale and larger colocation agreements under which the tenant is obligated to pay for its contracted capacity, whether measured in power, space, or both, regardless of whether it fully utilises that capacity during the contract term. This structure gives the operator a revenue floor independent of the tenant's actual utilisation pattern, which is particularly important during phased migrations or ramp-up periods when contracted capacity can materially exceed currently utilised capacity.