Skip to content
Request Demo

A Colocation Portfolio's Blended Occupancy Figure Masks a Power-Constrained Capacity Ceiling

Case Study • Advanced • 3 min read

Audience
Investment Committees • Lenders • CFOs
Last Reviewed
July 2026
Updated
Version 1.0

Executive Summary

This is an illustrative, composite scenario, not a specific real transaction. It follows a colocation portfolio whose reported occupancy was calculated against total floor space, masking that rising tenant rack density had already made power the actual binding constraint at several facilities, materially overstating remaining sellable capacity ahead of a planned acquisition. The core lesson: remaining capacity headroom should be calculated against a facility's actual binding constraint, power, space, or cooling, not against floor space or nameplate capacity alone.

Illustrative Scenario

This case study is a composite, educational scenario built from patterns commonly observed in data centre financial model reviews. It does not describe a specific, identifiable portfolio engagement, and any resemblance to a particular operator is coincidental.

Background

A multi-facility colocation operator maintained portfolio-wide occupancy reporting calculated as leased floor space divided by total available floor space, used both for internal capacity planning and to represent remaining growth capacity to prospective acquirers ahead of a planned sale process.

The Problem

The portfolio's reported occupancy percentage suggested meaningful remaining capacity available for new tenant growth at most facilities. However, average tenant rack density had been rising steadily across the portfolio as existing and new tenants adopted newer, higher-performance computing equipment with materially higher power draw per rack than the facilities had originally been designed around.

Findings

An independent capacity review, conducted as part of acquisition due diligence, tested the portfolio's reported occupancy and remaining capacity figures against each facility's actual power and cooling headroom, not floor space alone. The review found that at several facilities, available power, not floor space, had already become the binding constraint on remaining sellable capacity: floor space remained nominally available, but the facilities' power distribution and cooling capacity were substantially committed, leaving materially less genuinely sellable capacity than the floor-space-based occupancy figure implied.

Root Cause

The portfolio's occupancy and capacity reporting tracked only floor space utilisation, consistent with a commercial real estate convention, without a parallel power and cooling headroom calculation. As tenant rack density rose across the portfolio, this single-constraint reporting approach increasingly diverged from the facilities' actual sellable capacity, a divergence that went unnoticed in routine internal reporting because no metric was tracking the power and cooling constraint independently.

Risk

Had the acquisition proceeded on the basis of the original floor-space-based capacity reporting, the acquirer would have overpaid for growth capacity that was not, in fact, available without additional capital investment in power and cooling infrastructure at the affected facilities, a material difference to the achievable growth case underpinning the acquisition price.

Resolution

The due diligence findings were incorporated directly into the transaction structuring: the acquisition price was adjusted to reflect the actual, power-and-cooling-verified remaining capacity at each facility, and a separate capital plan was agreed for the infrastructure investment required to restore growth capacity at the power-constrained facilities, consistent with the verification discipline in Data Centre Acquisition Models.

Lessons Learned

  • Remaining capacity headroom should be calculated against a facility's actual binding constraint, power, space, or cooling, as set out in Data Centre Capacity Planning Models, not against floor space or nameplate capacity alone.
  • Rising average rack density across a portfolio can shift the binding constraint from floor space to power without any change in reported floor-space occupancy, a divergence that single-constraint reporting will not surface.
  • Acquisition due diligence should independently verify capacity headroom rather than accepting the target's own reported occupancy and remaining capacity figures, consistent with Data Centre Financial Due Diligence.
  • The Data Centre Financial Model Checklist item requiring capacity tracking against all three co-binding constraints exists specifically to surface this class of risk before it materially affects a transaction's economics.

Continue Reading

How OXXON tests thisRun a free structural check with FMAE

Frequently Asked Questions

Is this a real client engagement?

No. This is an illustrative, composite scenario built from patterns commonly observed in data centre financial model reviews. It does not describe a specific, identifiable portfolio or transaction.

What did the portfolio's original occupancy reporting show?

A stable, moderate reported occupancy percentage calculated as leased floor space divided by total available floor space, suggesting meaningful remaining capacity available for new tenant growth across the portfolio's facilities.

What was actually constraining capacity at several facilities?

Rising average tenant rack density, driven by newer, higher-performance computing equipment, had increased power draw per rack to the point that available power, not floor space, had become the binding constraint at several of the portfolio's facilities, even though floor space remained nominally available.

How was the power constraint identified?

An independent capacity review, conducted as part of acquisition due diligence, tested the portfolio's reported occupancy and remaining capacity figures against each facility's actual power and cooling headroom, not just its floor space, and found that several facilities had materially less genuinely sellable capacity than the floor-space-based occupancy figure implied.

What was the financial impact of the overstated capacity?

The acquirer's initial valuation had assumed a level of achievable near-term growth capacity that, once tested against actual power and cooling headroom, was not available at several facilities without additional capital investment in power and cooling infrastructure, materially affecting the achievable growth case underpinning the acquisition price.

What should the portfolio's original capacity reporting have done differently?

Tracked remaining sellable capacity against all three co-binding constraints, power, floor space, and cooling, identifying whichever was actually binding at each facility, rather than reporting occupancy and remaining capacity against floor space alone.

Related Articles

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.

Rack Density

Rack density measures how much power a tenant's rack draws, expressed in kW per rack, and by extension how much heat must be removed by the facility's cooling system to support it. Rising rack density, driven by higher-performance computing equipment, is the primary reason power and cooling capacity, rather than floor space, increasingly bind data centre capacity before floor space is exhausted, and density tier is a primary basis for colocation pricing.

Data Centre Occupancy & Utilisation Models

Data centre occupancy modelling requires distinguishing three related but distinct capacity states: billed (contracted) capacity, actually utilised capacity, and total available capacity. This guide sets out how to model each state and the ratios between them, and why conflating billed occupancy with actual utilisation misrepresents both revenue durability and the facility's true remaining capacity headroom.

Data Centre Acquisition Models

Acquiring an operating data centre requires verifying the quality and durability of its existing contracted revenue, confirming its actual remaining capacity headroom against the binding constraint, and assessing synergy potential specific to combining data centre operations, shared power procurement, network ecosystem consolidation, and overhead rationalisation. This guide sets out how to model a data centre acquisition, distinct from a greenfield development or an internal expansion decision.

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