A larger campus is not always a scaled-up version of the first phase. Growth can trigger a new transmission route, another water source, more treatment, different cooling, additional road access and a larger operating organization. Those thresholds need to be identified before the first phase consumes the land, rights or capital needed to solve them.
The campus problem
Illustrative scenario, not a claimed client result.
An owner controls enough land for a very large campus. Phase one is supportable, phase two needs a shared substation expansion and later phases assume another supply route and regional water project. Tenant A is committed, Tenant B is negotiating and the ultimate campus remains a market forecast. The owner must decide which enabling rights and assets to secure now and which capital should wait for verified service and tenant credit.
Capacity growth is discontinuous
A first connection may support one committed phase without supporting the ultimate campus. Adding another phase can require a shared upgrade whose lead time begins before the next tenant is certain. Rack density and cooling choices can change facility demand and water use differently from the IT-load headline.
Building shared assets early can preserve schedule and scale while exposing the sponsor to demand that may not arrive. Waiting can protect capital while losing a corridor, equipment slot or service window. The decision should compare the cost of preserving the option with the cost and probability of later reconstruction.
The Texas context
ERCOT describes exceptional large-load growth and now uses specific integration processes for qualifying projects. TWDB has stated that it is developing better information for data center, AI and related water demand. These records show why larger campus proposals require evidence and coordinated planning. They do not establish that every announced load will operate or that every campus must reach a particular size.
Use a threshold register to control expansion capital
For each scale stage, identify current capacity, the next constraint, lead time, required land or right, earliest commitment date and expected funder. Run the second tenant late and the next supply route unavailable. Separate requested, reserved and operating capacity.
Sitebraid would maintain that threshold record across tenant negotiations, provider work, design, procurement and operating handoffs. Each accepted phase updates remaining capacity and future constraints so capital follows current evidence.
Solutions and their tradeoffs
Build independently deliverable phases
Keep each release tied to a supportable tenant and service package.
Conditions to resolve: Some duplication may be justified by reduced common-mode and stranded-asset risk.
Advance selected shared infrastructure
Secure long-lead rights or assets where waiting would destroy a valuable expansion option.
Conditions to resolve: The sponsor must carry the unsupported portion and define recovery from later tenants.
Concentrate the buildout
Use scale where several tenants and providers can support a coordinated release.
Conditions to resolve: Test common-mode exposure, liquidity, construction congestion and the consequence of a late phase.
Expansion thresholds change the development model
Swipe or scroll to compare all columns.
| Stage | Decision focus | Typical discontinuity to test |
|---|---|---|
| Initial committed phase | Deliver independently supportable service | First connection, treatment and operating team |
| Shared campus buildout | Allocate common assets across contracted tenants | Substation, main, corridor or central plant expansion |
| Large multi-source campus | Coordinate several providers and operating modes | Additional supply route, fuel, water or market structure |
| Ultimate option | Preserve rights without underwriting a forecast as fact | Regional infrastructure, new approvals and stranded-asset exposure |
This is the development problem behind our capacity allocation challenge. Our Campus readiness capability explains the scope Sitebraid can take on.
Our approach: from the decision to delivery
Use consistent definitions for IT load, total facility demand, contracted service and equipment nameplate. Build threshold maps for power, fuel, water, treatment, drainage, fiber, roads, construction logistics, emergency response and staffing. For each threshold, identify the trigger, lead time, land reservation, approval, capital owner, operating consequence and fallback. Reconcile changing rack density and cooling designs with shared-system capacity instead of scaling the first-phase assumptions linearly.
Create the threshold register
Tie every material capacity step to evidence, lead time, authority and capital. Separate a physical reservation from funded and accepted service.
Stress tenant and supply timing together
Model Tenant B late, a second supply route unavailable and a cooling requirement that changes shared water and power demand. Identify which early choices preserve or consume the response.
Gate capital against option value
Fund a right, corridor or design package early when its preservation value is supportable. Defer full construction when the obligation depends mainly on uncommitted tenants.
Update the campus basis after every phase
Sitebraid coordinates the current tenant, infrastructure, provider and approval record. Each accepted phase changes the remaining capacity and operating environment. The next investment decision should use that current record, not the original marketing master plan.
How we protect the decision
Do not describe requested, modeled or announced megawatts as operating capacity. Do not assume linear growth in water, cooling, staffing or grid effects. Keep redundancy and emergency reserves outside saleable capacity unless the responsible engineers and operators establish otherwise. Preserve alternatives without financing an unsupported ultimate campus.
The result the owner should require
The owner has a phased infrastructure plan with named thresholds, protected rights, funded releases and conditions for later capital. The first phase can operate independently within its accepted basis. Expansion commitments are tied to provider evidence and tenant support, with the stranded-cost downside visible before approval.
How to measure progress
- Thresholds with unresolved land, provider or approval dependencies.
- Shared capital supported by contracted tenant payments.
- Time between tenant commitment and required infrastructure release.
- Capacity and corridors preserved after each accepted phase.
The decision to take forward
Plan the large campus as a sequence of infrastructure thresholds. Secure scarce rights early when their option value is clear, but release construction capital only when service evidence and tenant support justify the exposure.
Continue with One campus. Several tenants. Who owns the spare capacity? to examine the connected decision.