DATA CENTER SITE SELECTION
How to Evaluate Data Center Power Capacity Before Site Selection
Confirm the megawatts, delivery dates, service conditions, and expansion path that your operating plan needs before the location decision becomes a construction commitment.
By Hunter Drinkall · Published September 9, 2026
Updated October 20, 2026
Conceptual campus illustration. Not an actual client project or an electrical design.
Start with the load, then establish what the utility can deliver
Data center power capacity is a site-specific question. A regional supply outlook, a nearby transmission line, or a substation nameplate does not establish the power available to a particular parcel at a particular date.
Evaluate the proposed service against the facility’s load profile, commissioning plan, reliability objectives, financial assumptions, and future phases. Keep each answer tied to a dated source, its conditions, and the party responsible for confirming it.
Capacity at the delivery point
Identify the cumulative MW available for each phase, the voltage, the proposed service location, and the conditions attached to that answer.
A credible delivery schedule
Connect utility studies, approvals, equipment, site access, construction, testing, and energization to the facility’s required milestones.
Terms the project can support
Review service restrictions, customer obligations, reliability, upgrade costs, and the process for securing later capacity.
For the broader location strategy, see why power availability drives data center site selection.
Define the power request before asking whether a site works
Give the utility a consistent project package: parcel address or coordinates, preliminary site plan, requested service voltage, total facility demand by phase, commissioning requirements, load ramp, and the operating characteristics developed by the engineering team.
IT load and facility demand
For a visual explanation of MW, MWh and PUE, see our guide to how much power a data center needs.
IT load covers computing equipment. The utility service request must also account for cooling, electrical losses, and other facility systems within the agreed metering boundary.
Demand and operating behavior
Describe expected and maximum demand, commissioning overlap, load changes, power factor, power quality needs, and the proposed interaction with on-site generation or storage.
Dates and growth
Separate construction power, commissioning power, initial operations, and cumulative campus demand. State the required dates and the assumptions behind each step.
Keep the units clear. MW describes power; MWh describes energy used over time. An annual energy estimate or an average demand figure does not establish the maximum service capacity needed for the project.
The Department of Energy describes PUE as total annual facility energy divided by IT equipment energy. Use that energy-efficiency definition consistently; an annual PUE assumption alone does not establish peak utility demand. Have the design team develop the capacity request from the actual operating and commissioning cases.
Read the conditions behind every capacity statement
Ask the serving utility to identify the proposed delivery point and the engineering work supporting its response. Check whether capacity is available now, dependent on upgrades, subject to other requests, or only part of a long-range plan.
Preliminary indication
Useful for screening potential locations. Record the stated MW, timing, assumptions, validity period, and the studies still needed.
Engineering review
Request the applicable load, system, or facilities studies. Confirm that they address the same parcel, load profile, service configuration, and development phases.
Service arrangements
Review the applicable agreements, approvals, deposits, milestones, and remaining conditions with the utility and project advisers.
Document names and study processes vary by utility. Assess what the document actually supports, whether it remains current, and which conditions must be satisfied before the project can rely on its assumptions.
Dominion Energy’s Virginia data center request guidance illustrates the information a utility may require, including a site plan, load letter, and load-ramp schedule. It also describes staged service and site-specific power planning. Use the serving utility’s own current process for each candidate.
Use one utility-question matrix for every finalist
Send the same load basis to each utility and retain the responses in a comparison record. A headline MW figure is useful only when the timing, delivery location, restrictions, obligations, and evidence are also understood.
| Review area | Question to resolve | Evidence to retain |
|---|---|---|
| Deliverable MW and voltage | How much load can be served at the proposed delivery point for each phase? | A dated response matched to the project load request and service configuration. |
| Capacity status | What is preliminary, conditional, reserved, or committed, and what changes that status? | Written conditions, validity dates, competing-request considerations, and required customer actions. |
| Upgrade scope | Which transmission, substation, transformer, feeder, protection, and customer works are needed? | A defined scope with responsibility, approvals, access requirements, and cost assumptions. |
| Energization milestones | When can commissioning and each operating phase receive the required service? | A milestone plan showing dependencies, planning ranges, and remaining uncertainty. |
| Operating restrictions | What limits may apply during peak conditions, maintenance, emergencies, or an interruptible service arrangement? | Applicable service terms and an engineering review of their operating consequences. |
| Reliability configuration | Which upstream assets and routes are shared, and what can remain available during an outage? | Utility configuration information and a coordinated resilience review. |
| Costs and commitments | Which charges, deposits, minimum bills, or ramp obligations apply? | The applicable tariff or proposal, an itemized scope, and a project-specific financial model. |
| Expansion | What must happen to serve later cumulative demand? | A documented path covering studies, infrastructure, space, timing, and any capacity-hold conditions. |
Keep unanswered questions open, with an owner and a due date. Where a condition is essential to feasibility, use it as a decision gate before allowing attractive land pricing or other benefits to outweigh the gap.
Match each power phase to a separate operating milestone
Fictional planning example. The figures below are invented total facility demand requests at the utility delivery point. They are cumulative requirements for separate stages, not additional amounts to add together. Dates are measured from an assumed project start; they are not utility delivery estimates.
Commissioning · month 18
6 MW requested
Confirm the testing window, duration, overlap with other loads, and any temporary-service conditions.
Initial operations · month 24
18 MW requested
Establish the service configuration and upgrade milestones needed to reach the operating requirement.
Campus expansion · month 36
36 MW requested
Confirm the work, timing, customer actions, and evidence needed to serve the later cumulative requirement.
Suppose a preliminary response identifies 12 MW now and 18 MW after an upgrade, with no confirmed expansion plan. That response does not yet establish 18 MW by month 24 or 36 MW by month 36. The open questions concern both deliverable capacity and the required dates.
Review whether any interim service fits the commissioning and operating plan. Record its limits, duration, costs, and transition requirements alongside the permanent-service assumptions.
Build the schedule around the work that enables energization
Request milestones and dependencies for the actual service plan. Activities may overlap, and the utility’s study terminology or approval path may differ. The project schedule should show who owns each step and what could change its completion date.
Study and define
Resolve the load request, network review, facilities scope, delivery point, customer design, and the basis for any preliminary dates.
Enable and procure
Track land access, rights of way, permits, applicable approvals, equipment procurement, and the readiness needed to start construction.
Build, test, energize
Align utility and customer works, protection coordination, inspections, testing, commissioning windows, and the handoff to operations.
Connect the utility schedule with project management and collaboration. Keep a delayed-upgrade scenario visible so leadership can assess whether a later opening or a different site is more practical.
Review the complete service path and the on-site resilience plan
Look for shared failure points
Ask which feeds, substations, routes, transformers, and protection arrangements are shared. Two incoming feeds alone do not establish independence or a particular uptime outcome.
Coordinate facility resilience
Have the utility, electrical designers, and operations team review the relationship between incoming service, UPS, standby generation, storage, fuel arrangements, maintenance, and load management.
Request relevant outage and restoration information, planned maintenance practices, and the operating limits that may apply during abnormal grid conditions. Assess exposure to flood, wildfire, storms, heat, or other local hazards through the proposed configuration.
Use facility location risk analysis to retain the findings, mitigation actions, owners, and unresolved assumptions. Record what the evidence supports instead of treating a general utility reputation as a site-specific reliability assessment.
Compare the full power obligation across the load ramp
Model the applicable utility terms against the same demand and energy assumptions for every site. Separate one-time contributions from recurring charges and show the effect of commissioning, partial occupancy, delayed growth, and later phases.
Upfront obligations
Identify studies, deposits, customer-funded utility works, site electrical infrastructure, access, and other project-specific contributions.
Recurring charges
Review energy and demand charges, applicable riders, taxes, power-factor provisions, minimum bills, and charges tied to the proposed service.
Commitment terms
Review ramp assumptions, contract duration, capacity-hold conditions, collateral, reduced-load outcomes, and other obligations in the actual proposal.
Compare the base case with delayed upgrades and slower occupancy. Review any incentives assumptions through the same financial case, including their conditions and timing.
Land price is one input in the larger project model. See how cheap land can become an expensive data center project.
Establish how later power fits the campus plan
Ask whether future phases require another study, a different delivery configuration, additional transmission or substation works, or further customer commitments. Record how the utility manages future capacity requests and what is required to maintain any stated reservation.
Coordinate the electrical expansion path with the physical site: substation space, equipment access, utility corridors, easements, cooling, fiber routes, construction circulation, and separation from operating facilities.
Keep the next phase visible in the first decision
An expansion pad and an ultimate-load target address different parts of the plan. The decision record should show both the usable land strategy and the documented path to serving the later load.
Our guide to planning data center sites for future campus expansion connects these infrastructure questions with long-term site layout.
Turn utility responses into a decision record
Keep the same fields for every finalist. Cite the document or discussion date behind each conclusion and distinguish confirmed findings from planning assumptions. Retain changes when the load request, service offer, scope, or schedule is revised.
| Record | What to retain | Who should confirm it |
|---|---|---|
| Load basis | Versioned total-facility demand, commissioning cases, energy assumptions, voltage, and cumulative phases. | Project engineering and operations team. |
| Capacity evidence | Parcel-specific utility response, applicable studies, conditions, and validity dates. | Utility contact and project lead. |
| Delivery schedule | Required dates, utility milestones, dependencies, customer works, and delayed-service scenario. | Utility and project schedule owners. |
| Reliability | Proposed service paths, shared assets, outage information, and coordinated resilience assumptions. | Utility, electrical designers, and operations. |
| Economics | Tariff or proposal, upgrade contributions, recurring charges, commitments, and occupancy scenarios. | Finance with utility and project advisers. |
| Expansion | Later-phase capacity path, land and corridor requirements, future studies, and customer actions. | Utility and campus planning team. |
| Open conditions | Unresolved issues, evidence needed, action owners, due dates, and decision consequences. | Named owner for each condition. |
Advance when the evidence supports the project requirements and the remaining actions are defined. Keep a site conditional when a material question remains open. Reassess when a required capacity, timing, or operating condition cannot be supported.
The leadership recommendation should identify the feasible options, decisive evidence, open conditions, cost exposure, and the next commitments that depend on those answers.
Data center power capacity: FAQs
How do you evaluate data center power capacity before site selection?
Define total facility demand, commissioning needs, and the cumulative load ramp. Ask the serving utility for a site-specific review of capacity, voltage, upgrade scope, energization milestones, operating restrictions, reliability, costs, and later phases. Track the evidence and conditions behind each answer.
Does a nearby substation mean power is available?
Proximity is a starting point for discussion. The utility must assess the proposed delivery point, network constraints, existing commitments, required works, service configuration, and timing against the actual load request.
Is IT capacity the same as the utility service requirement?
IT capacity concerns the computing equipment. The facility service request also needs to reflect cooling, electrical losses, and other systems within the defined boundary, together with maximum demand and commissioning cases developed by the engineering team.
Can PUE establish the peak power request?
An annual PUE value relates facility energy use to IT energy use. It does not by itself establish peak utility demand. The design team should develop the service-capacity requirement using the project’s actual load cases and operating assumptions.
What should a utility capacity response include?
It should identify the parcel and delivery point, MW and voltage by phase, the status and conditions of the response, required studies or upgrades, timing assumptions, and customer actions. Review the actual scope and remaining conditions rather than relying on the document’s title.
Are two utility feeds enough to establish redundancy?
Two feeds may share upstream assets or routes. Review common failure points, maintenance and outage conditions, and the on-site resilience design with the utility, electrical designers, and operations team.
How should commissioning and expansion power be compared?
List each stage with its required date and cumulative total facility demand. Identify overlapping loads, temporary-service limits, permanent-service dependencies, and the actions needed for later phases. Match the utility response to every required stage.
Which power costs belong in the site comparison?
Include project-specific upfront contributions and recurring charges under the applicable tariff or proposal. Review deposits, upgrade obligations, demand and energy charges, minimum bills, ramp commitments, and the financial effects of delayed or slower occupancy.
Build the location decision around a workable power plan
WorldPoint Site Selection helps data center, industrial, and advanced manufacturing teams coordinate site evaluation, utility discussions, infrastructure planning, incentives, economic development relationships, and the broader requirements of a U.S. expansion.
Explore our site selection services or discuss the load profile, required dates, and future phases behind your location search.
WorldPoint provides advisory support. Brokerage activities are handled separately through CBREG True Team.