Data Centre Model Governance Framework
Executive Summary
Key Takeaways
- ✓ A data centre model governance framework should assign clear ownership for capacity, pricing, and contract assumptions, with a named owner responsible for keeping each category current and defensible.
- ✓ Update triggers should be tied to specific events, capacity delivery milestone completion, contract renewal dates, and material power cost changes, rather than an arbitrary fixed review calendar disconnected from the events that actually make an assumption stale.
- ✓ Board or investment committee reporting should surface capacity headroom, contracted versus uncontracted revenue mix, and tenant concentration risk as standing metrics, not only aggregate revenue and EBITDA figures.
- ✓ A governance framework should survive personnel turnover, since model ownership, assumption sourcing, and update triggers documented only in an individual's institutional knowledge are lost when that person leaves.
Objective¶
This guide sets out a governance framework for data centre financial models within Data Centre Financial Modelling, building on the general Financial Model Governance discipline.
Assigning Model Ownership¶
The governance framework should assign clear ownership for capacity, pricing, and contract assumptions, with a named owner responsible for keeping each category current and defensible, consistent with the documentation standards in Data Centre Model Documentation Standards. Diffuse or undocumented ownership leaves no one specifically accountable when an assumption becomes stale.
Event-Driven Update Triggers¶
Update triggers should be tied to specific events, completion of a capacity delivery milestone, an approaching contract renewal date, or a material power cost change, rather than an arbitrary fixed review calendar disconnected from the events that actually make an assumption stale. A fixed calendar can miss a material change occurring between scheduled reviews.
Board and Investment Committee Reporting¶
Reporting should surface capacity headroom, the contracted versus uncontracted revenue mix, and tenant concentration risk as standing metrics, not only aggregate revenue and EBITDA figures, consistent with the KPI set described in Data Centre Financial KPIs. These sector-specific risk indicators are not visible in aggregate revenue and EBITDA figures alone.
Surviving Personnel Turnover¶
A governance framework should survive personnel turnover: model ownership, assumption sourcing, and update triggers documented only in an individual's institutional knowledge are lost when that person leaves, which is why the ownership, trigger, and reporting structures above should be formally documented rather than maintained informally.
Common Governance Failures¶
Undocumented or diffuse assumption ownership. No one specifically accountable for keeping capacity, pricing, or contract assumptions current.
Fixed-calendar review disconnected from actual update triggers. Misses material changes occurring between scheduled reviews.
Board reporting limited to aggregate revenue and EBITDA. Omits capacity headroom, revenue mix, and concentration risk indicators material to assessing the facility's actual risk profile.
Governance dependent on institutional knowledge. Collapses when a key individual leaves without formal documentation in place.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
Why does a data centre model need a specific governance framework rather than a generic one?
Because capacity, pricing, and contract assumptions in this sector are specific, technical, and tied to particular events, capacity delivery milestones, contract renewal dates, power cost changes, that a generic model governance framework not designed around this sector's mechanics would not adequately trigger review of.
How should model ownership be assigned?
With a named owner responsible for keeping each assumption category, capacity, pricing, contract terms, current and defensible, rather than diffuse or undocumented ownership that leaves no one specifically accountable when an assumption becomes stale.
What should trigger a model update, rather than a fixed review calendar?
Specific events, completion of a capacity delivery milestone, an approaching contract renewal date, or a material power cost change, since these are the events that actually make an assumption stale, and an arbitrary fixed review calendar disconnected from them can miss a material change between scheduled reviews.
What should board or investment committee reporting include beyond aggregate revenue and EBITDA?
Capacity headroom, the contracted versus uncontracted revenue mix, and tenant concentration risk as standing metrics, since these are the sector-specific risk indicators that aggregate revenue and EBITDA figures alone do not reveal, consistent with the KPI reporting discipline in Data Centre Financial KPIs.
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 Model Documentation Standards
A data centre financial model should maintain a documentation standard that traces capacity assumptions to their engineering or survey source, contract terms to the underlying agreements, and power cost pass-through methodology to the specific contractual mechanism it implements. This guide sets out the documentation practice that keeps a data centre model auditable and defensible as it is updated and handed over across successive reporting periods and personnel.
Data Centre Financial KPIs
A data centre financial model should track a defined set of KPIs spanning scale, utilisation, retention, pricing, efficiency, and profitability, since no single metric captures operating performance on its own. This guide sets out the core KPI set, MW under management, utilisation rate, churn, revenue per kW, power usage effectiveness, and EBITDA per MW, and how to interpret each correctly alongside the others rather than in isolation.
What Is Financial Model Governance?
Financial model governance is the set of policies, roles, and controls an organisation puts in place to manage the risk that comes from relying on financial models for material decisions. It is the organisational layer that sits above any individual financial model audit: governance determines when a model gets audited, who owns that decision, how versions are tracked, and what happens to findings once they exist. Most published governance content online is written for large, tier one banks operating under formal regulatory regimes. A private equity firm, a family office, or a mid market corporate finance team rarely has that scale of infrastructure, and does not need it, but still carries real exposure if no governance exists at all. This page defines governance at the level that actually applies to most organisations relying on Excel models, not just the largest ones.