DCFR Insight 01 / Site Screening
7 Things to Check Before Calling a Data Center Site Viable
A rigorous pre-acquisition screen that separates marketable acreage from land that can physically, operationally, and jurisdictionally support a data center.
A viable site is a coordinated system, not a large parcel
Gross acreage, a nearby transmission line, and industrial zoning can make a parcel look compelling while concealing the constraints that ultimately determine capacity. A data center site must support the building, utility interface, electrical and generator yards, cooling or heat rejection, secure circulation, loading, fire access, stormwater, grading, buffers, and future phases as one coordinated system. The screening question is therefore not “Is there enough land?” It is “Can the entire operating and approval model fit inside the usable envelope without depending on unverified assumptions?”
1. Convert gross acreage into a usable development envelope
Begin by subtracting what cannot be relied upon: setbacks, easements, floodplain, wetlands, steep slopes, utility corridors, drainage paths, environmental buffers, road dedication, and sensitive-edge mitigation. Then test whether the remaining area is contiguous and proportioned for repeatable data hall modules and support infrastructure. A fragmented 40-acre parcel can be weaker than a clean 25-acre parcel if the usable land is divided into narrow or disconnected zones.
2. Separate visible power from deliverable power
A substation or line near the site is evidence of infrastructure, not evidence of available capacity. Early diligence should identify the serving utility, plausible point of interconnection, voltage level, route length, third-party crossings, substation or feeder upgrades, study status, queue exposure, deposits, phased energization options, and the difference between initial and full-build capacity. The land value should reflect what is confirmed, what is plausible, and what remains speculative.
3. Translate the target MW into physical geometry
Convert target IT load into rack count, data hall modules, approximate building footprint, support-yard demand, and circulation. Then test both primary orientations against the buildable envelope. The exercise should expose whether the parcel can support a compact building, a linear bar, phased pods, or a multi-building campus—and whether the claimed capacity depends on unrealistic rack density, under-sized yards, or the elimination of required access.
4. Prove access, logistics, and emergency circulation
A site that fits the building but cannot support secure entry, staff parking, contractor overflow, loading, fuel deliveries, equipment replacement, crane access, and fire apparatus circulation is not a viable site-fit. Test the largest vehicle and the most difficult replacement event, not only normal daily traffic. Identify off-site road improvements, sight-distance issues, bridge or turning constraints, and any route that crosses public-facing or sensitive edges.
5. Treat zoning, code, and AHJ exposure as schedule variables
Industrial zoning does not automatically mean a data center is by right. Confirm use classification, special or conditional-use triggers, height and setback limits, design review, noise standards, generator testing rules, fuel and battery provisions, fire access, water supply, and local political exposure. A technically buildable parcel can still be commercially weak if approval depends on a long discretionary process or unresolved interpretation.
6. Match cooling and water strategy to the site
Air-cooled, water-cooled, hybrid, and liquid-ready programs create different land, utility, acoustic, discharge, plume, and maintenance requirements. Screen water availability, sewer or blowdown pathways, heat-rejection yard size, prevailing winds, recirculation risk, sensitive receptors, and expansion. Do not assume a future tenant or MEP team can solve a cooling constraint that the site cannot physically accommodate.
7. Reserve stormwater, grading, buffers, and construction logistics before declaring fit
Impervious area drives detention, water-quality treatment, conveyance, and grading. Sensitive edges may require landscape, berm, acoustic wall, lighting control, or equipment setbacks. Construction requires laydown, temporary access, cranes, delivery staging, and utility sequencing. These demands should be reserved before the plan is called feasible; otherwise the “available” expansion area is often already consumed.
Use a disciplined advance / hold / reject decision
The screening output should not be a vague list of concerns. It should state whether the site should advance, advance with conditions, remain on hold pending a specific confirmation, or be rejected. Each condition should have an owner, evidence requirement, commercial consequence, and deadline tied to the acquisition process.
Seven viability tests before acquisition
| Test | Evidence required | Common failure mode | Decision consequence |
|---|---|---|---|
| Usable envelope | Survey/title constraints, setbacks, visible environmental and grading limits | Gross acreage is used as developable acreage | Reduce capacity or reprice land |
| Power deliverability | Utility contact, POI concept, route, capacity and schedule status | Nearby line is treated as committed power | Hold or condition acquisition |
| Physical site-fit | MW-to-module geometry and support-yard allowances | Building fits only by deleting roads, yards, or stormwater | Reduce MW or reject layout |
| Access and operations | Truck, fuel, replacement, security and fire-route logic | Daily car access works but heavy logistics fail | Require road/site redesign |
| Entitlement and AHJ | Use path, local standards, review process, political exposure | Industrial zoning is assumed to be sufficient | Extend diligence or reprice schedule risk |
| Cooling/water/noise | Scenario-based cooling, utility and receptor review | One unconfirmed cooling concept supports the entire deal | Carry alternate scenario or hold |
| Civil and construction | Stormwater, grading, laydown, phasing and buffers | Leftover land is expected to absorb everything | Reduce fit ratio and preserve reserve |
Early screening checklist
What to verify before advancing this site.
- Gross acreage reconciled with a contiguous usable envelope
- Target MW translated into racks, modules, building and support-yard demand
- Utility capacity, route, schedule and phasing separated into confirmed and unconfirmed items
- Secure access, truck courts, fuel delivery, equipment replacement and fire access tested
- Zoning, code, fire, environmental and community review pathways identified
- Cooling, water, sewer, noise and sensitive-edge scenarios screened
- Stormwater, grading, buffers, laydown and future expansion reserved
- Advance / hold / reject recommendation tied to a confirmation register
What DCFR would flag
Risks surfaced at the screening stage.
DCFR would flag capacity claims that rely on gross acreage, nearby-but-unconfirmed power, fragmented geometry, missing operational access, discretionary entitlement, unresolved cooling or water assumptions, and site plans that consume stormwater or expansion reserves.
Professional confirmation required
Items requiring licensed validation.
Final utility capacity, title, survey, environmental constraints, zoning and entitlement, code and fire requirements, civil grading and drainage, geotechnical conditions, acoustics, MEP systems, costs, schedule, and approvals require confirmation by the applicable professionals, utilities, authorities, and counsel.
Final takeaway
A site is viable only when its full infrastructure, operational, environmental, and approval model can be explained with visible assumptions and a credible confirmation path.
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.