Planning Strategy
What a Planning-Grade Data Center Feasibility Report Should Include
The difference between vague site commentary and a structured feasibility package that supports real decisions.
Vague commentary is not enough
A useful feasibility report should not simply say that a site appears promising. It should identify the assumptions used, the calculated demand, the visible constraints, and the professional confirmations still required. The value is not certainty; the value is structured decision support before larger commitments are made.
Site capacity and buildable envelope
The report should start with the site: gross area, usable planning area, apparent constraints, buildable envelope, access edge, sensitive edges, and major no-build issues. Without this foundation, later capacity statements are weak.
Data center geometry basis
The building should be generated from target IT load, rack density, rack count, data hall module logic, gross-up assumptions, and geometry type. A report should show why the building has the approximate size it does, not present it as an arbitrary rectangle.
Infrastructure and support systems
Power, utility, cooling, water, generator, fuel, battery/UPS, parking, loading, fire/service access, stormwater, buffers, and expansion reserve should be treated as calculated planning objects. Each should have a driver, area, placement logic, and confirmation flag.
Risk, cost, schedule, and sustainability
A planning-grade report should identify schedule risk, utility risk, entitlement risk, environmental exposure, constructability issues, sustainability pathways, low-water or low-carbon options, and likely next-step consultant needs.
Assumption register and handoff
The report should separate user inputs, DCFR planning assumptions, calculated outputs, visible constraints, and confirmation-required items. That makes the document useful for internal review, broker discussion, investor screening, and consultant kickoff.
Early screening checklist
What to verify before advancing this site.
- Executive feasibility verdict
- Buildable envelope and site-fit model
- Data center geometry basis
- Power/cooling/water/access/fire/stormwater review
- Sustainability pathway
- Cost/schedule/risk summary
- Assumption register
- Confirmation-required checklist
What DCFR would flag
Risks surfaced at the screening stage.
DCFR would flag gaps between claimed feasibility and actual planning-grade support, including missing site-demand objects or unconfirmed assumptions.
Professional confirmation required
Items requiring licensed validation.
Final engineering, legal zoning opinions, utility capacity, environmental clearance, survey, geotechnical, acoustic, cost, schedule, permit, entitlement, and authority approvals require professional confirmation.
Final takeaway
A serious feasibility report turns uncertainty into a structured decision framework.
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.