Dry Utilities for Data Centers: What Developers Need to Prepare Before Construction Starts
Power and fiber are the two constraints that end data center deals before they begin -- and the site preparation work that unlocks them has to start earlier than most developers expect.
Site selection for data centers is dominated by power availability. But the work that actually delivers power, fiber, and telecom to a parcel -- the dry utility coordination layer -- is where schedules slip and budgets expand. Developers who treat dry utilities as a construction detail rather than a pre-construction dependency discover the problem too late to solve it cheaply.
This is a practitioner guide to what dry utility preparation for a data center actually involves, what to coordinate with whom, and where the common oversights are.
What Dry Utilities Cover
In the context of data center development, dry utilities refers to the electrical, telecommunications, and fiber infrastructure that must be physically routed onto the site, coordinated with utility providers and carriers, and prepared for connection before the building becomes operational. The term distinguishes these services from wet utilities (water, sewer, stormwater), which involve different regulatory and contracting processes.
For a data center, dry utilities include:
High-voltage electrical service from the utility, including substation feed, transformer placement, and distribution switchgear
Telecom and fiber laterals from multiple carriers, with diverse physical entry points
Conduit pathways for routing cables across the parcel and into the building
Utility easements and rights-of-way for running services from the public right-of-way to the building
Handholes, pull boxes, and duct banks sized for current capacity and future growth
Each of these requires coordination with a different party -- the electrical utility, individual fiber carriers, the municipality or county, and the design team. None of them move fast, and they do not move in parallel by default.
Electrical Service Coordination
The electrical utility coordination track is typically the longest and most consequential. It begins with confirming that the available grid capacity at or near the site can actually serve the proposed load.
Proximity to a substation does not guarantee available capacity. A site adjacent to a 138 kV substation may still require a new distribution transformer, substation upgrades, or a new dedicated feed -- each of which involves utility engineering studies, procurement of long-lead equipment, and utility construction timelines that routinely run 18-36 months.
The steps that need to happen before the utility can commit to a service schedule:
Preliminary capacity confirmation. The developer or their electrical engineer contacts the serving utility with the project's proposed load (in MW) and requests a preliminary service availability assessment. This establishes whether the substation can serve the load and what upgrades might be required.
Formal load study submission. A load study (or system impact study) request is the formal entry point to the utility's interconnection queue. The study determines what grid upgrades are triggered, who pays for them, and what the timeline is. Load studies for large data center loads can take 6-12 months and cost $50,000-$250,000 depending on utility.
Utility service agreement. Once the load study is complete, the developer negotiates a utility service agreement covering load, voltage, delivery schedule, metering configuration, and applicable tariff. For loads above certain thresholds -- which vary by utility and state -- this involves the new large load tariff frameworks now in place in over 20 states.
Physical infrastructure design. After the service agreement is in place, the utility designs the actual service delivery infrastructure: transformer placement, conduit runs, metering equipment, and any distribution upgrades. The developer typically needs to provide a transformer pad and vault, conduit stub-outs from the right-of-way to the pad, and coordinated access during utility construction.
Developer oversight matters throughout this process. Load studies contain assumptions about facility ramp-up, redundancy configuration, and peak demand that can be modeled incorrectly. Utilities set study timelines that benefit from developer follow-up. Service agreement terms -- particularly around large load tariffs, curtailment obligations, and cost-of-upgrade assignments -- require legal and financial review before execution.
Fiber and Telecom Coordination
Data centers require carrier-diverse, physically redundant fiber connectivity. A single carrier entering the building through a single conduit is a single point of failure. Most institutional tenants require at least two carriers entering via diverse routes, physically separated from each other and from the electrical service entry.
The coordination sequence with fiber carriers involves:
Carrier availability research. Before site control, the developer should identify which carriers have existing lit fiber within reach of the parcel. This means checking carrier colocation maps, reviewing prior utility permitting records, and in some cases engaging a telecom consultant who can pull route information from state conduit databases or direct carrier inquiries.
Meet-point identification. Each carrier has a designated meet-point -- typically a handhole or junction in the public right-of-way -- from which the developer extends a conduit lateral onto the parcel. Identifying meet-point locations, confirming the carrier can extend service, and understanding lead times (12-24 months for new fiber laterals from carriers not yet in the area) are pre-design steps.
Conduit design and sizing. The developer designs and installs the conduit pathway from the meet-point to the building. Conduit is sized for current carrier requirements plus expansion capacity. Multiple carrier paths should be physically separated -- different routes, different handholes, different building entry points -- to achieve true redundancy.
Right-of-way permits and easements. Running conduit from the public right-of-way onto private property, or across adjacent parcels to reach a meet-point, requires municipal permits and in some cases private easements. These are not fast. Right-of-way permits in active jurisdictions can take 3-6 months. Easement negotiations with adjacent landowners have no fixed timeline.
A common failure mode: developers identify fiber availability during due diligence and confirm that carriers serve the general area, but do not confirm which carriers will run a new lateral to the specific parcel, on what timeline, and at what cost. The distinction between "fiber nearby" and "fiber to this building, redundantly, in the project schedule" is significant.
Duct Banks, Handholes, and Site Infrastructure
The physical infrastructure that routes dry utilities across the parcel and into the building is part of the site's civil scope but is coordinated with utility and carrier requirements.
Duct banks are groups of conduits encased in concrete or installed in PVC that route electrical and telecom services underground. Data center duct bank design involves:
Separate banks for electrical (high voltage) and telecom, typically 6 feet of horizontal separation minimum
Bank sizing based on current utility requirements plus 30-50% expansion capacity
Routing that avoids conflicts with water, sewer, stormwater infrastructure, and building foundations
Pull box and handhole placement at intervals that allow cable installation without exceeding manufacturer bend radius and pull force limits
Handholes and pull boxes are access points in the duct bank system where cables are pulled through. Location, sizing, and load rating (for traffic-bearing installations) are specified by the serving utilities and carriers, not just the developer. Misaligned specifications are a common source of rework.
Utility easements on the parcel define where utilities have the right to run their infrastructure, access it for maintenance, and restrict development within the easement corridor. Easements should be confirmed before finalizing building placement, parking, and landscaping, since their locations constrain site layout.
Common Developer Oversights
Starting utility coordination after design begins. Utility service timelines run 18-36 months for large loads. Design takes 12-18 months. These do not fit sequentially. Load study submission needs to happen at or before design kickoff, not after design development is complete.
Confirming fiber availability, not fiber deliverability. Carrier maps show where existing routes run. They do not confirm new lateral availability, timeline to construction, or cost for a specific parcel. Direct carrier inquiry is required.
Single building entry point for fiber. Two carriers entering the building through the same conduit sleeve in the same wall are not redundant. Physical path separation -- different entry points, different routing -- is a tenant requirement and should be confirmed in the telecom design before construction.
Undersizing conduit for future growth. Data center load and connectivity requirements grow over the facility's life. Duct banks and handholes are embedded in concrete. Over-engineering conduit capacity during construction is significantly cheaper than digging up and replacing infrastructure during operations.
Missing utility easement review in site planning. Easement corridors that bisect a parcel can prevent the developer from locating buildings or mechanical yards where the site plan calls for them. This is a pre-design site constraint, not a permitting step.
Underestimating municipal right-of-way permitting timelines. In active development markets, municipal engineering departments reviewing ROW permits are backlogged. A 3-month estimate for permit approval that actually takes 9 months delays conduit installation, which delays carrier connectivity, which delays tenant move-in.
The Developer's Dry Utility Checklist
Before site control:
Confirmed electrical service capacity at serving substation for project load
Identified two or more fiber carriers with deliverable laterals to the parcel
Confirmed physical separation routes for diverse carrier entry exist or can be constructed
Reviewed title for existing utility easements and their impact on site layout
Before design kickoff:
Load study submitted to serving electrical utility
Preliminary service agreement terms in negotiation
Carrier meet-point locations confirmed and conduit design initiated
Right-of-way permit applications submitted or timeline confirmed
Before construction permit:
Utility service agreement executed
Telecom carrier agreements and construction timelines confirmed
Duct bank and handhole design complete and reviewed by serving utilities
Easements for cross-parcel or adjacent routing recorded
Dry utility coordination does not get easier after construction begins. The parties -- utilities, carriers, municipalities, adjacent landowners -- each operate on their own schedules and respond to their own priorities. The developer's leverage is highest at the earliest stage, and the cost of late discovery is highest at the latest stage.
Treating dry utilities as a pre-construction workflow rather than a construction deliverable is one of the simpler discipline improvements available to data center development teams.