DCFR Insight 81 / Land Development · Infrastructure Strategy
How Do You Determine the Infrastructure Required to Make a Data Center Site Buildable?
A viable parcel can still require major off-site and on-site infrastructure. The development strategy must define what is required, who designs it, who funds it, who owns it, and when each system must be ready.
Start from the campus operating requirements
The starting point is not whether the parcel looks attractive. Define the business outcome the land must support and the evidence required to prove it. For this topic, the controlling inputs include power and substation work, public roads and intersections, and water and fire-flow systems. State assumptions explicitly so an early concept cannot quietly become a committed basis without validation.
Separate existing capacity from required improvements
Build the evidence on one controlled site and schedule basis. Reconcile power and substation work, public roads and intersections, water and fire-flow systems, wastewater and pump stations, fiber and communications routes, and stormwater, drainage and off-site outfalls rather than allowing each discipline to work from a different boundary, phasing assumption, utility date, or campus concept. When evidence is preliminary, label its confidence level and identify the party responsible for confirmation.
Map off-site and on-site scope together
A practical workflow is to inventory existing systems; then define demand by phase; then identify upgrade scope and permitting; then assign designer, funder, owner and maintainer; then build interface schedule; then capture cost and obligations in agreements. The sequence is intentionally decision-led: each activity should either confirm feasibility, expose a dependency, quantify an impact, create a mitigation, or support a commercial or investment gate.
Development Control Matrix
| Control question | Evidence required | If unresolved | Decision effect |
|---|---|---|---|
| What must be true? | power and substation work + public roads and intersections | Assign owner and confirmation date | Do not treat as confirmed |
| What controls timing? | build interface schedule + capture cost and obligations in agreements | Build downside scenario | Adjust capacity date or commercial milestone |
| What can defeat the site? | assuming public infrastructure will be available + unfunded off-site improvements | Mitigate, redesign, reprice, or exit | Escalate to investment gate |
| What can be traded? | public versus private delivery + temporary versus permanent infrastructure | Compare alternatives on one basis | Choose risk-adjusted outcome |
Planning-grade framework. Applicable law, utility rules, entitlement procedures, engineering criteria, transaction terms, and licensed-professional requirements vary by jurisdiction and project.
Assign delivery ownership for every asset
The highest-consequence failure modes include assuming public infrastructure will be available, unfunded off-site improvements, scope gaps at public-private interfaces, utility work not aligned with site schedule, and ownership or maintenance unresolved at turnover. Separate these from ordinary design development. A red flag belongs in the executive risk register when it can materially change deliverable capacity, approval probability, schedule, capital exposure, operations, or the ability to exit the transaction.
Tie infrastructure milestones to development phases
Real sites rarely optimize every variable at once. Typical trade-offs include public versus private delivery, temporary versus permanent infrastructure, oversizing for future phases versus near-term capital, and shared facilities versus control. Compare alternatives against the same capacity, date, cost, and risk basis. A mitigation that solves one discipline but creates a larger entitlement, utility, construction, or operating problem is not a complete solution.
Make infrastructure obligations visible in the investment case
Every required infrastructure element should have a defined technical basis, delivery party, funding mechanism, land right, approval path, completion date, and handoff standard. Record the decision, assumptions, unresolved confirmations, owner, target date, and trigger for reconsideration. That record becomes the bridge between diligence, transaction documents, entitlement, design, infrastructure delivery, construction, and future portfolio learning.
Early screening checklist
What to verify before advancing this site.
- The decision objective for Series Part 13 is explicit
- Power and substation work is supported by current evidence
- Public roads and intersections is supported by current evidence
- Water and fire-flow systems is supported by current evidence
- Wastewater and pump stations is supported by current evidence
- Cross-discipline assumptions use one controlled plan and phasing basis
- Material red flags have an owner, mitigation, cost and schedule effect
- Commercial milestones do not outrun technical and entitlement evidence
- The recommendation states what would cause the decision to change
What DCFR would flag
Risks surfaced at the screening stage.
DCFR would flag any site decision where assuming public infrastructure will be available, unfunded off-site improvements, scope gaps at public-private interfaces are still being treated as background assumptions rather than controlled development risks with evidence, ownership, and a decision path.
Professional confirmation required
Items requiring licensed validation.
Confirm project-specific land rights, zoning and entitlement requirements, utility capacity and agreements, environmental jurisdiction, civil and geotechnical criteria, life-safety requirements, infrastructure obligations, costs, schedules, and transaction terms with the applicable authorities, utilities, qualified counsel, and appropriately licensed design and technical professionals.
Final takeaway
Every required infrastructure element should have a defined technical basis, delivery party, funding mechanism, land right, approval path, completion date, and handoff standard.
Screen up to 20 candidate sites before selecting one for the full DCFR report.
Each DCFR Report Package includes a preliminary 20-site comparison PDF / export package plus one selected planning-grade feasibility report.