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
The campus service boundary must be established with the relevant providers and qualified teams. ERCOT's Large Load Integration materials address the electrical process. TCEQ's industrial wastewater guidance identifies a separate body of requirements for discharge. Neither establishes the project-specific headroom, lead times or expansion thresholds used in the hypothetical example below.
The second phase fails on water before it runs out of power
Consider a hypothetical campus opening at 40 MW of facility demand in month 12, with a second 40 MW phase proposed for month 30. The accepted first-stage electrical envelope is 90 MW after the technical allowances used in this example. The first phase therefore leaves 50 MW of electrical headroom, which appears to support the second phase. These are site assumptions, not regulatory thresholds or industry sizing ratios.
Assume each phase needs 0.35 MGD of peak makeup and the supported supply is 0.60 MGD. Together the two phases require 0.70 MGD, creating a 0.10 MGD gap despite adequate base-case electrical headroom. A water upgrade taking 20 months from funding to accepted service must be released by month 10 to support month-30 occupancy, before the first phase opens. That duration is hypothetical and excludes contingency; actual release timing must allow for the critical uncertainties.
Now introduce a tenant cooling change that adds 12 MW to the second phase. Total facility demand becomes 92 MW, exceeding the assumed electrical envelope by 2 MW. The water upgrade alone no longer makes the phase deliverable. A longer-lead electrical increment, a revised cooling configuration or a reduced tenant envelope is also needed. Leasing must track the change through both systems instead of using the unchanged building area as evidence that the phase still fits.
The live-campus interface creates a third threshold. Suppose expansion requires a preinstalled isolation point and the operator will not permit the alternative later outage. The interface must be ready before month-12 turnover even if the second building is speculative. Protecting that interface can be justified independently of ordering the second phase's full equipment. This separates scarce options worth preserving now from construction capital that should wait for stronger tenant evidence.
If the second tenant slips to month 42, the arithmetic water release date moves to month 22. That does not automatically allow the owner to defer: quote validity, approvals, corridor availability and provider reservations may expire first. The recommended decision is to preserve those rights and the first-turnover interface, while making major upgrade releases conditional on confirmed demand and provider evidence. Reconcile the threshold register at each tenant change, not just at annual master-plan reviews.
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.
A completed phase-threshold register
Illustrative schedule measured from month zero. Durations exclude contingency and are not utility commitments. MW is facility demand; MGD is peak makeup demand. No universal megawatt trigger is asserted.
Swipe or scroll to compare all columns.
| System | Two-phase test | Release or preservation point | Consequence |
|---|---|---|---|
| Electrical service, base case | 80 MW against 90 MW supported | Preserve future route rights; no extra base-case capacity claimed | 10 MW remaining, not permission for any tenant change. |
| Water supply | 0.70 MGD against 0.60 MGD supported | Month 30 minus 20 months = month 10 | Fund an accepted upgrade or reduce/rephase the second commitment. |
| Electrical service after cooling change | 92 MW against 90 MW supported | Assumed 24-month upgrade: month 6 for month-30 service | A late change can invalidate the original schedule even after water is funded. |
| Operating tie-in | Later outage route not accepted | Isolation interface before month-12 turnover | Preserve the option independently of the speculative building. |
| Second phase moves to month 42 | Water need moves, rights may not | Nominal water release month 22, subject to rights and provider validity | Do not confuse deferred construction with a preserved route. |
This is the development problem behind our capacity allocation challenge. Our Campus readiness capability explains the scope Sitebraid can take on.
Putting the analysis to work
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.
How Sitebraid would support this decision
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
Let the earliest cross-system constraint govern the next tenant offer. In the worked case, water controls the base expansion, a cooling change introduces an earlier electrical decision, and the operating interface must be protected at first turnover regardless. Preserve scarce options early; release larger construction commitments only against a reconciled phase case.
If your campus is heading toward a gigawatt, our Campus readiness work flags the phase where your operating model has to change.
Continue with The data center campus is becoming an industrial utility system. to examine the connected decision.