All insights

DCFR Insight 10 / Feasibility Reports

Planning-Grade Data Center Feasibility Reports: Scope, Evidence, and Decisions

A useful feasibility report converts assumptions into measurable site-fit outputs, evidence-ranked risks, decision gates, and a disciplined handoff to utilities, authorities, consultants, and acquisition teams.

Planning-Grade Data Center Feasibility Reports: Scope, Evidence, and Decisions

The report must help someone decide

A feasibility report is not valuable because it contains many pages. It is valuable because it allows a buyer, developer, broker, investor, or utility-facing team to understand what is plausible, what is constrained, what is unknown, and what action should occur next. Every section should connect evidence to a decision.

Separate five classes of information

The report should distinguish client inputs, externally observed facts, rule-based planning assumptions, calculated outputs, and confirmation-required items. Mixing these categories creates false confidence. A value entered by the client is not the same as a utility commitment; a map observation is not a survey; and a calculated building block is not final engineering.

Show the buildable envelope and the full land budget

The report should reconcile gross parcel area with setbacks, easements, environmental constraints, grading risk, buffers, and other no-build zones. It should then allocate the building, electrical and generator yards, cooling, fuel, water, access, parking, loading, fire routes, stormwater, construction, and expansion. The output should be dimensioned and traceable to quantity drivers.

Illustrative planning-grade site plan for a hypothetical 40-acre data center campus, with a dimensioned building, infrastructure yards, connected access, stormwater and expansion reserves.Open full-size plan ↗
Sample 01 — Site-fit and land allocation. This hypothetical 40-acre site shows an initial 40-megawatt (MW) information technology (IT) program, a 192,000-square-foot building, separate infrastructure yards, access, parking, stormwater and future development reserves. The 60-foot inset and all dimensions are illustrative assumptions; setbacks, easements, grading, drainage and access require site-specific confirmation. Open the plan at full size to read the dimensions.

Translate capacity into a repeatable geometry basis

Document IT load, rack density, estimated rack count, module size, module count, gross-up basis, selected building archetype, and approximate footprint. This prevents a site plan from becoming a decorative diagram and allows reviewers to challenge assumptions constructively.

Enlarged planning diagram of the same initial building: four 10 MW data halls, 1,000 assumed racks, 104,000 square feet of hall area and 88,000 square feet remaining for support and circulation.Open full-size plan ↗
Sample 02 — Building and infrastructure basis. The same 600-by-320-foot building is broken into four assumed 10 MW halls. At 40 kilowatts per rack, the planning program is 1,000 racks. Data halls occupy 104,000 square feet, leaving 88,000 square feet within the gross footprint for support and circulation. This is a program allocation, not a validated rack layout or coordinated floor plan. IT load is not total utility demand.

Treat utility, entitlement, and civil risk as parallel workstreams

Power, zoning, code, fire, water, sewer, environmental, access, grading, stormwater, acoustics, and community exposure should each have a current evidence level, key unknowns, responsible confirmer, schedule consequence, and next action. A generic red-yellow-green score is insufficient unless the reason and closure path are visible.

Include alternatives, not only one preferred scenario

A strong report compares at least a base case with one or more meaningful alternatives: lower or higher density, different cooling strategy, alternate yard orientation, phased building plan, mitigation-heavy sensitive-edge plan, or different utility route. Alternatives reveal whether the site is resilient or viable only under one fragile assumption.

Phased development plan for the same hypothetical campus, identifying the initial 40 MW building, a 6.43-acre future reserve, provisional construction access and the conditions required before expansion.Open full-size plan ↗
Sample 03 — Phasing and expansion. The same site retains a 6.43-acre future development reserve and a provisional construction access route while protecting the initial operating area and stormwater reserve. Future MW capacity is intentionally uncommitted: the next phase requires its own complete land budget, confirmed utility delivery, access and utility crossing review, and updated civil and permitting checks. All three samples are educational illustrations, not outputs from an analyzed customer site.

State the decision and the conditions attached to it

The executive conclusion should say advance, advance with conditions, hold, or reject. Conditions should be specific: obtain a utility study result; confirm a zoning interpretation; secure an easement; complete acoustic modeling; verify stormwater outfall; or reduce the program. The report should also state the commercial consequence if the condition is not met.

Provide a consultant handoff that reduces rework

The report should end with a confirmation register, source list, assumptions register, quantity schedule, open questions, and discipline-specific handoff. This allows civil, MEP, structural, fire, environmental, acoustic, legal, survey, geotechnical, and cost teams to start from a controlled basis rather than recreating the screening history.

Be explicit about what the report is not

Planning-grade feasibility is not final engineering, stamped design, legal zoning opinion, environmental clearance, utility guarantee, permit approval, contractor price, or investment advice. Clear exclusions protect credibility because they tell the buyer exactly where professional reliance must shift to the appropriate authority or consultant.

Minimum decision-ready report structure

Report elementRequired outputDecision valueHandoff
Basis and assumptionsInput/source/assumption classificationPrevents false certaintyAssumption register
Site constraintsBuildable envelope and no-build layersShows usable landSurvey/title/environmental questions
Capacity geometryRacks, modules, building and support systemsTests physical fitProgram and quantity basis
Infrastructure feasibilityPower, cooling, water, roads and fire accessExposes external dependenciesUtility/MEP/civil/AHJ actions
Risk and alternativesEvidence-ranked risks and scenariosTests resilienceRisk owners and closure evidence
RecommendationAdvance/hold/reject with conditionsGuides acquisition actionMilestones and decision gates
Confirmation packageOpen items, sources, quantities and contactsReduces consultant restartDiscipline-specific handoff

Early screening checklist

What to verify before advancing this site.

  • Client input, observed fact, assumption, calculation and confirmation item separated
  • Buildable envelope reconciled with all visible constraints
  • Capacity translated into racks, modules, building and support infrastructure
  • Utility, zoning, code, fire, civil, environmental and acoustic risks evidence-ranked
  • At least one meaningful alternative or sensitivity scenario evaluated
  • Advance / conditional advance / hold / reject recommendation stated
  • Conditions tied to owner, evidence, deadline and commercial consequence
  • Assumption, source, risk and consultant-handoff registers included

What DCFR would flag

Risks surfaced at the screening stage.

DCFR would flag reports that provide attractive diagrams without traceable assumptions, quantity drivers, alternatives, decision conditions, evidence levels, or a usable consultant handoff.

Professional confirmation required

Items requiring licensed validation.

All final engineering, code, zoning, legal, environmental, utility, survey, geotechnical, civil, acoustic, cost, schedule, permitting, financing, and construction conclusions require confirmation by the applicable licensed professionals, authorities, utilities, contractors, counsel, and owner.

Final takeaway

A planning-grade report earns trust by making the decision logic transparent, the uncertainty visible, and the next professional actions executable.

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.