INSIGHTS / CAPACITY & PHASING
A tenant commitment consumes capacity at a particular location, under particular operating conditions, on a particular date. Decide what the next phase can promise by reconciling those conditions across power, cooling, water and the shared assets that serve them.
The master plan describes ultimate capacity. A lease or equipment release commits a specific slice of it. The gap becomes expensive when two phases depend on the same unbuilt substation, cooling reserve or utility connection. Both buildings can fit on the site while only one can operate under the promised conditions.
Expansion also consumes access and outage opportunities. A tie-in that is straightforward before occupancy can become unacceptable beside an operating tenant. The capacity decision therefore includes how the new load reaches service without spending the reserve or access needed by the existing load.
Commercial teams may track contracted IT load while engineers track connected equipment and providers evaluate a different demand basis. Those numbers cannot be added or compared until their boundaries agree. A future upgrade can appear in several phase plans even though its cost and delivery conditions remain unresolved.
Tenant changes compound the mismatch. A different ramp, cooling requirement or redundancy basis can alter shared-system demand without changing leased area. If allocations are updated only when a building opens, the next commitment is made against an outdated campus position.
Build a phase allocation ledger by system and service boundary. For each phase, identify usable capacity supported by evidence, existing obligations, protected operating reserve and the remainder available for new commitments. Keep future capacity in a separate conditional column with the asset and acceptance evidence needed to release it.
Test the next tenant at initial occupancy, full ramp and during the planned expansion tie-in. Use the limiting system at each point to set the offer. If electrical capacity is available but cooling or an acceptable outage window is not, the phase remains conditional. Ask the technical teams to establish the operating envelope rather than applying a campus-wide average.
Rephasing preserves existing infrastructure but changes the commercial promise. Accelerating a shared upgrade can preserve the requested ramp, but exposes capital before all beneficiaries arrive. A dedicated increment may separate tenant dependencies while consuming land, increasing maintenance and complicating later integration.
Compare all three against the same tenant ramp and operating reserve. Include the cost of temporary connections and the next expansion, so the apparently least expensive first phase does not win by leaving its enabling work in another budget.
Swipe or scroll to compare all columns.
| Route | When it fits | Tradeoff | Evidence before commitment |
|---|---|---|---|
| Rephase within available capacity | The tenant can accept a smaller opening load or later ramp. | Less early infrastructure spending; occupancy and revenue move. | A revised tenant ramp reconciled to usable capacity and reserve. |
| Advance the shared upgrade | Several supported phases depend on the same capacity increment. | Earlier capital exposure and dependence on shared-asset delivery. | A funded upgrade, provider conditions and an acceptable tie-in sequence. |
| Add a dedicated increment | The phase can be served separately without blocking later systems. | Potential separation of dependencies; more equipment, land and operating interfaces. | A technical and service basis that protects permanent corridors and reserve. |
Sitebraid would compare tenant commitments with provider evidence and the technical capacity record, locating every shared increment counted more than once. The output is a phase ledger showing the specific promise that cannot yet be supported.
We would connect each feasible ramp to the shared or dedicated works it requires, including tie-ins, stranded capacity and future-phase effects. The comparison identifies which tenant term or capital release must change.
We would translate the selected route into a defined capacity allocation and conditional releases for future increments. Acceptance evidence from the responsible technical and operating teams updates the ledger before another allocation is sold.
Keep operational reserve outside commercially available capacity. Require a new allocation check when tenant load, redundancy, cooling or ramp assumptions change. A provisional provider response should remain visibly provisional in the commercial decision.
Protect expansion corridors and tie-in access in the phase layout. If a shared upgrade slips, identify the load that must be deferred before committing the next increment, rather than assuming every tenant can retain its original ramp.
Require a phase-by-phase capacity position that reconciles to physical systems and accepted service conditions. It should identify available capacity, conditional capacity and the exact upgrade or operating restriction that separates them. A larger ultimate-buildout number is not evidence that the next tenant fits.
Before issuing the next capacity offer, take the proposed tenant ramp and the current shared-system ledger to the technical and commercial decision makers. Select the supported opening load, identify any conditional increment and change the offer or authorize its enabling works before making the commitment.
If your next tenant commitment is closer than the capacity to serve it, our Campus readiness work lines up the phase, the capacity and the date you have promised.
Illustrative assignments that connect a potential owner problem to evidence, alternatives and acceptance criteria. They are not claimed client results. Dated public context and sources appear in each article.
Build to plan or phase-gate is a false choice. What the retrofit premium, the forfeited queue slot and the cost of preserved optionality actually come to on a 240 MW growth increment, and which works belong in which column.
ERCOT attaches one Batch Zero allocation to one entity behind one point of interconnection, and never says how a campus divides it among tenants. What that means for apportionment, milestone risk and lease drafting.
Separate security drawdowns, CIAC and advance procurement before the same phase creates two liquidity demands ahead of tenant revenue.
The next tenant can expose a conflict that has been present since the master plan: available capacity, reserved capacity and capacity promised by a date are not the same thing.
A campus can have land and funding for expansion but no acceptable way to build it around its first tenant. Protect the next phase before the first one opens.