What is a data center feasibility study?
A data center feasibility study tests whether a site can support a target amount of information technology, or IT, capacity within its power, cooling, land-use, infrastructure, delivery, and economic constraints. It should establish plausible capacity by phase, an approval path, and the unresolved dependencies that could change cost or the operating date.
Define the delivery model first. Powered land, a shell, a fitted facility, colocation space, and an owner-operated campus carry different commitments and economics.
Define the capacity and the operating milestone
| Input | Establish | Why it changes the decision |
|---|---|---|
| Capacity | Target IT megawatts (MW), workload, and expansion phases | Building area alone does not establish computing capacity |
| Date | Required accepted operation for each phase | Shell completion, energization, and commissioned operation are different milestones |
| Power position | What the utility has studied or committed to deliver | Infrastructure and contract conditions may still control service |
| Facility requirements | Density, cooling, reliability, and tenant specifications | These determine systems, equipment space, cost, and testing |
| Commercial model | What is delivered, funded, and operated by each party | The development plan and financial model must cover the same scope |
JLL's 2026 outlook identifies secured power as a central development constraint. Begin diligence with the documents behind the capacity and delivery date. JLL Global Data Center Outlook
Read the commitment behind the power number
A nearby substation shows where infrastructure is located. A utility study or agreement establishes a different set of facts: proposed service, required improvements, timing, cost responsibility, and conditions.
Dominion's January 2026 process description illustrates the distinction. Its engineering agreement leads to a study of infrastructure, estimated energization, and costs. Its later construction agreement is the stage at which capacity is reserved. Other utilities may use different stages and terminology. Dominion's submission to PJM
Record the service location, document date, capacity basis, milestones, and customer obligations. Distinguish requested capacity from studied, reserved, contracted, or energized service using the actual document terms.
Utility MW and IT MW need a consistent basis
Illustrative planning calculation using hypothetical assumptions.
Assume 48 MW of total facility power is available at the operating condition being modeled. If total facility power is assumed to be 1.20 times IT power at that same condition, the arithmetic supports 48 ÷ 1.20 = 40 MW of IT load.
Engineering, reliability requirements, and operating limits must support the result. Annual power usage effectiveness, or PUE, measures total facility energy relative to IT energy; it does not certify peak electrical capacity. Keep the planning ratio and a measured annual PUE distinct. The Green Grid's PUE guidance, hosted by Lawrence Berkeley National Laboratory
Data center site selection and permitting checklist
| Workstream | Resolve | Source material | Decision affected |
|---|---|---|---|
| Land and rights | Control of the land, access, and utility routes for all phases | Survey, title, parcel assembly, and easements | Acquisition and layout |
| Power | Capacity, service dates, improvements, and conditions | Utility correspondence, studies, agreements, and milestones | Phase size and operating date |
| Campus fit | Buildings and infrastructure within the actual site constraints | Layout showing substations, cooling, generators, drainage, access, setbacks, and expansion | Deliverable program and land needs |
| Zoning and entitlement | Approval path for all proposed uses | Adopted rules, project approvals, pending changes, and agency input | Land-use strategy and schedule |
| Cooling and water | Operation under local resource and climate conditions | Design basis, climate assumptions, and provider responses | Systems, limits, and cost |
| Generation and emissions | Approvals for the proposed equipment and operating mode | Fuel and equipment basis, air-agency requirements | Backup or bridge-power strategy |
| Noise | Applicable limits and effects at relevant receptors | Equipment data, layout, local rules, acoustic assessment | Placement, mitigation, and approval risk |
| Connectivity | Carrier service and route arrangements | Carrier confirmations, routes, easements, delivery dates | Suitability and operational resilience |
| Civil and environmental | Access, flood, drainage, geotechnical, ecological, and contamination constraints | Screening, surveys, relevant studies, and agency input | Usable area, mitigation, and infrastructure |
| Procurement and commissioning | Releases, equipment, installation, energization, testing, and acceptance | Procurement schedule and commissioning strategy | Achievable operation |
| Commercial case | Capacity, delivery scope, commitments, and downside cases | Agreements, cost plan, phase dates, financial model | Proceed, restructure, or hold |
Turn the applicable items into a project-specific approval matrix: agency, approval, trigger, submission, dependencies, status, and next action.
The permit path includes the supporting infrastructure
The substation, generation plant, fuel storage, cooling, water arrangements, and battery systems can introduce requirements beyond the building's land-use approval. Establish which apply to the selected design and operating mode.
Keep adopted rules, pending changes, and existing project approvals distinct. Loudoun County's March 2025 changes introduced special-exception requirements for uses previously allowed by right, with grandfathering provisions. Further standards remain under development as of this guide's September 2026 review. Apply that local example only where it governs. Loudoun County
Community and political research can inform the strategy. Project diligence still needs to resolve the actual layout, equipment, noise, and infrastructure requirements.
A phased campus needs a phased feasibility answer
Illustrative diligence scenario using hypothetical project documents.
A concept assumes two phases open in the same year. The utility documents support an earlier service milestone for phase one but make phase two dependent on another infrastructure improvement. The second building also occupies land reserved for future electrical infrastructure.
The useful output identifies two decisions: revise the layout and test the economics of staged delivery. The report should show the affected phase, supporting documents, revised capacity assumptions, and unresolved utility milestone.
For a leased facility, use the customer agreement's actual commercial terms. For an owner-operated campus, evaluate delivery cost and operating requirements. Each phase needs a consistent capacity, scope, cost, and date.
Comparing sites or phases? Bring the target IT load and operating date. We'll discuss the diligence questions that could change the development plan.
For contractors, test the path to accepted operation
Connect design releases and owner-furnished equipment to procurement, installation, energization, and testing. A completed shell can still be waiting for systems or acceptance work.
Check package boundaries around equipment supports, power connections, cooling distribution, controls integration, temporary arrangements, and commissioning. Reconcile vendor exclusions with the contract documents before declaring a responsibility gap.
On a phased campus, examine how later construction affects the operating phase: access, utility tie-ins, isolation, testing, and any permitted outages. Those dependencies belong in the delivery plan.
What should data center feasibility software show?
Follow a requirement into the concept. Where does an equipment setback come from? Where does the equipment sit? What changes in capacity, land needs, or phasing if it moves?
Different tools address different parts of that work. Spark advertises zoning, permitting, and stakeholder intelligence. Site-design tools, utility engineering, and document coordination address additional questions. Evaluate how the conclusions connect to your proposed campus.
Extending AutoSitu to data center feasibility
AutoSitu offers site feasibility, design QA/QC, compliance review, takeoff, and scope gap analysis for development and construction.
We are extending that approach to data center feasibility: connecting site constraints, approval requirements, and project documents to the campus and phases a team intends to deliver.
In a project discussion, we'll identify which existing AutoSitu capabilities apply and which data center-specific requirements need further development or specialist input.
Data center feasibility and permitting FAQ
What makes a site suitable for a data center?+
The site must support the required power, cooling, connectivity, infrastructure, approvals, and delivery schedule. Evaluate these against a defined IT load and operating model, including expansion requirements.
Does a nearby substation mean power is available?+
No. Available capacity, required improvements, obligations, and dates need utility-specific confirmation. Use the study or agreement's actual terms to describe the service position.
What permits does a data center need?+
Investigate land-use, civil, building, fire, and relevant environmental or infrastructure approvals. Generation, fuel storage, battery systems, and water arrangements may add requirements. The jurisdiction and project design determine the final list.
How much land is needed for a data center?+
Test the campus layout against the target capacity. Buildings, electrical and cooling infrastructure, drainage, access, setbacks, and expansion all consume land; a single acreage-per-megawatt assumption cannot establish site fit.
Can onsite generation bridge a utility delay?+
Potentially, if fuel, permits, emissions limits, equipment, electrical design, and commercial requirements support the intended operation. Emergency-backup equipment should not automatically be assumed suitable or permitted for continuous use.
What should we bring to a project discussion?+
Start with the parcel, target IT load, operating date, and delivery model. Add utility correspondence, concept plans, owner requirements, and studies as available. Identify the decision you need to make next.