Skip to content
Request Demo

Data Centre Model Audit

Technical Guide • Advanced • 2 min read

Audience
Lenders • Investment Committees • Advisory Firms • Model Developers
Last Reviewed
July 2026
Updated
Version 1.0

Executive Summary

A data centre model audit tests the structural integrity of the model's formulas and logic, distinct from validating the reasonableness of its input assumptions. This guide sets out the audit procedures specific to a data centre model: verifying capacity constraint calculations, revenue driver formulas, and power cost pass-through logic actually compute what they are represented to compute, free of circularity, hardcoding, or broken links.

Key Takeaways

  • A data centre model audit tests structural integrity, whether formulas correctly compute what they are represented to compute, distinct from model validation, which tests whether input assumptions are reasonable.
  • Capacity constraint formulas should be audited to confirm the model actually calculates the minimum of power, space, and cooling headroom, rather than silently defaulting to a single constraint.
  • Revenue driver formulas should be traced to confirm occupancy, price, and density tier mix are genuinely separable in the calculation, not combined in a way that only appears decomposed in the presentation layer.
  • Power cost pass-through logic should be audited against the actual tenant or offtake agreement terms to confirm the model implements the specific contractual allocation, not a simplified default.

Objective

This guide sets out how to audit the structural integrity of a data centre financial model within Data Centre Financial Modelling, applying the general Financial Model Auditing discipline to this sector's specific mechanics.

Audit Versus Validation

A model audit tests structural integrity, whether the model's formulas correctly compute what they are represented to compute, free of circularity, hardcoding, or broken links. This is distinct from model validation, which tests whether the model's input assumptions themselves are reasonable and well-sourced. Both are necessary and neither substitutes for the other.

Auditing Capacity Constraint Formulas

Capacity constraint formulas should be traced to confirm the model actually calculates remaining sellable capacity as the minimum of power, space, and cooling headroom, consistent with Data Centre Capacity Planning Models, rather than silently defaulting to a single constraint, typically floor space, which would overstate capacity if a different constraint actually binds.

Auditing Revenue Driver Formulas

Occupancy, price per unit of committed capacity, and density tier mix should be traced through the model's calculation to confirm they are genuinely separable inputs in the underlying formula, not combined into a single blended figure that only appears decomposed in the presentation layer while the underlying calculation actually uses one blended rate.

Auditing Power Cost Pass-Through Logic

Power cost pass-through logic should be traced against the actual terms of each material tenant or offtake agreement to confirm the model implements that specific contractual allocation, tenant, operator, or shared formula, rather than a simplified default that happens to produce a similar-looking output under current assumptions but would diverge under a power cost shock.

Common Audit Findings

Recurring findings in data centre model audits include: capacity constraint calculations that default to floor space without checking power or cooling headroom; revenue formulas presented as decomposed but calculated from a single blended rate internally; power cost pass-through hardcoded as a flat assumption rather than linked to the actual contractual allocation mechanism; and phased capex drawdown schedules disconnected from the capacity delivery tranches they are meant to fund.

Continue Reading

How OXXON tests thisRun a free structural check with FMAE

Frequently Asked Questions

What is the difference between a data centre model audit and model validation?

A model audit tests structural integrity, whether the model's formulas correctly compute what they are represented to compute, free of circularity, hardcoding, or broken links. Model validation tests whether the model's input assumptions are reasonable and well-sourced. The two are complementary but distinct.

How should capacity constraint formulas be audited?

By tracing the formula calculating remaining sellable capacity to confirm it actually takes the minimum of power, space, and cooling headroom, rather than silently defaulting to a single constraint, typically floor space, which would overstate capacity if a different constraint actually binds.

How should revenue driver formulas be audited for genuine separability?

By tracing occupancy, price per unit, and density tier mix through the calculation to confirm they are genuinely separable inputs in the underlying formula, not combined into a single blended figure that only appears decomposed in the presentation layer while the underlying calculation uses one blended rate.

Why does power cost pass-through logic require specific formula-level audit attention?

Because the model should implement the specific contractual power cost allocation defined in each material tenant or offtake agreement, and an audit should trace the formula to confirm it actually applies that specific allocation rather than a simplified default that happens to produce a similar-looking output.

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.

What Is a Financial Model Audit?

A financial model audit is an independent, structured examination of an Excel based financial model to confirm that its mechanics, logic, and outputs are reliable enough to support a decision. It is not a check of whether the assumptions are optimistic or conservative. It is a check of whether the model actually calculates what its author believes it calculates. Every year, lenders extend debt, investment committees approve capital, and boards sign off on transactions using numbers that came out of a spreadsheet nobody outside the immediate deal team has independently verified. A financial model audit exists to close that gap before it becomes expensive.

Data Centre Capacity Planning Models

Data centre capacity is jointly constrained by power, floor space, and cooling capability, and the binding constraint can shift as tenant rack density changes. This guide sets out how to model capacity planning across all three constraints simultaneously, how phased capacity delivery should be scheduled against demand, and why treating any single constraint as the sole capacity driver risks overstating achievable revenue.

Data Centre Financial Model Checklist

This checklist covers the structural checks specific to data centre financial models, on top of the general financial model audit baseline. It focuses on capacity constraint tracking (power, space, cooling), revenue driver decomposition (occupancy, pricing, density mix), power and cooling cost structure, and tenant contract and concentration risk. It is intended for lenders, investors, and advisors reviewing a colocation, hyperscale, or enterprise data centre model ahead of a financing or investment decision.

Request Demo