DCFR Insight 42 / Entitlement Site Planning + Basis of Design
Adapting the Data Center Basis of Design for Entitlement Site Planning
A repeatable data center product cannot be dropped onto a parcel unchanged. The entitlement plan must preserve capacity and standardization while proving jurisdiction-specific land use, infrastructure, life-safety, environmental, and community performance.
The entitlement plan is a controlled translation
The reference master plan and Basis of Design define the intended product; the entitlement plan translates that product into the parcel and approval system. It should preserve the capacity, reliability, security, constructability, maintainability, and expansion logic that create business value while resolving local setbacks, height, coverage, access, fire response, buffers, noise, water, stormwater, environmental resources, transportation, architecture, and public infrastructure. Treat neither the standard plan nor the local concept sketch as automatically controlling.
Issue one jurisdictional design basis
Create a written basis that identifies the proposed use and approval path, target IT and utility capacity by phase, reliability assumptions, building and yard modules, substation and generation strategy, cooling and water basis, parcel and title geometry, grading datum, fire and emergency criteria, security zones, access and heavy-haul routes, environmental constraints, off-site interfaces, local design standards, and known deviations. Record the source, owner, maturity, date, and confirmation action for each assumption.
Plan the ultimate campus before optimizing Phase 1
Show the full build-out envelope and the sequence that reaches it. Reserve corridors and operating clearances for additional buildings, substations, transmission, roads, stormwater, water and wastewater, cooling assets, fuel, fiber, construction access, replacement routes, and environmental mitigation. Test whether Phase 1 grading, utilities, landscape, or approval conditions block later phases. A plan that wins an initial permit by consuming the expansion path may destroy the site's portfolio value.
Convert gross acreage into usable capacity geometry
Overlay surveyed boundaries, title exceptions, easements, setbacks, buffers, flood and drainage constraints, wetlands and habitat, slopes, geotechnical zones, utility corridors, road reservations, security standoff, fire access, stormwater, construction areas, and off-site tie-ins. Fit real modules with dimensions and service zones rather than diagrammatic blocks. Report the capacity range and the constraint that sets it. If a planning condition moves a buffer or route, the capacity calculation and investment basis should change with it.
Design the public and operational edges together
Data-center approvals increasingly focus on the campus edge: adjacent uses, building scale, façades, rooftops, equipment screening, substations, transmission lines, lighting, noise, landscape, berms, roads, and drainage. Develop sections and receptor-based views that show both compliance and long-term operations. Landscape and architectural commitments must allow security visibility, equipment access, utility clearances, fire operations, replacement, snow or debris management, and maintainable planting over the asset life.
Entitlement-Ready Site-Plan Test
| Plan layer | Must show | Acceptance question | Common hidden failure |
|---|---|---|---|
| Capacity and phasing | Real modules, yards, clearances, sequence and ultimate build-out | Can each phase operate while the next is built? | Phase 1 consumes expansion or replacement space |
| Land and constraints | Survey, title, easements, buffers, hazards, grading and usable envelope | Does controlled land support every required element? | Gross acreage masks unusable or unowned corridors |
| Access and safety | Normal, emergency, construction, heavy-haul and replacement routes | Do geometry, rights and operations work by phase? | Public approval plan omits delivery or emergency movement |
| Utilities | Source, route, facility, right, capacity, redundancy, phase and interface | Is each connection executable and maintainable? | An arrow substitutes for route and delivery evidence |
| Community edge | Sections, receptors, noise, lighting, views, buffers and maintenance | Can the mitigation perform for the asset life? | Screening conflicts with security, utilities or access |
Integrate access, life safety, and construction logistics
Test normal staff and service access, emergency apparatus, hazardous-material response, construction traffic, heavy haul, crane setup, laydown, commissioning, maintenance, and full equipment replacement by phase. Confirm road geometry, grades, turning, loads, gates, queuing, clear heights, staging, secondary access, and conflicts with security or public roads. An entitlement drawing can look complete while omitting the temporary and replacement movements required to deliver and operate the campus safely.
Show utilities as phased systems, not arrows
For power, transmission, substations, water, wastewater, stormwater, fiber, fuel, and communications, show source, route, corridor width, major facilities, land rights, crossing constraints, phase, capacity, redundancy, provider interface, construction access, maintenance, and expansion. Distinguish existing, proposed, third-party, and unconfirmed elements. A nearby line or conceptual arrow does not prove an acceptable route, timely connection, or right to construct and maintain it.
Create a deviation register between standard and local design
Every departure from the reference product should state the reason, requirement or stakeholder issue, options tested, capacity and reliability effect, cost, schedule, operations impact, affected studies and approvals, decision owner, acceptance, and whether the change should update future master-plan principles or the Basis of Design. Likewise, every requested local modification or waiver should identify the standard, justification, equivalent performance, decision path, and fallback if denied.
Freeze the plan by decision gate, not by drawing date
Define controlled releases for pre-application, application, public notice, staff report, hearing, final decision, detailed design, early works, and construction. At each gate, identify permitted changes and required revalidation. Changes to capacity, building envelope, equipment location, access, grading, drainage, utility routes, environmental impacts, or commitments may require amended studies, notice, hearings, conditions, easements, or commercial terms. The drawing revision process should expose those consequences before design advances.
Standard-to-Local Deviation Register
| Deviation | Evidence required | Decision effects | Feedback action |
|---|---|---|---|
| Jurisdictional requirement | Code, interpretation, condition or agency criteria | Capacity, design, cost, schedule and operations | Update regional rule set if repeatable |
| Site constraint | Surveyed, investigated and spatially coordinated condition | Module fit, route, grading, phasing or mitigation | Refine screening and diligence scope |
| Stakeholder response | Defined impact, alternative analysis and approved commitment | Edge design, operating limit or public obligation | Add accepted response to option library |
| Product improvement | Performance, constructability or lifecycle evidence | Reference plan or Basis of Design change | Assign product owner and version date |
| Requested waiver | Standard, authority, justification, equivalent result and fallback | Approval uncertainty and redesign exposure | Record outcome and future use limits |
The governing application requirements and legal effect of plan changes vary. Confirm submittal, conformance, modification, amendment, notice, and hearing requirements with the authority and qualified local counsel.
Feed entitlement learning back into the product
After each decision, record which plan features triggered redesign, study, condition, delay, cost, opposition, or operational concern and which responses were accepted. Separate local one-offs from repeatable regional patterns. Update siting criteria, consultant scopes, master-plan modules, Basis of Design requirements, evidence standards, schedule allowances, and negotiation playbooks. Continuous improvement occurs when the next site begins with a better product and a better question set, not merely a copy of the last approved plan.
Early screening checklist
What to verify before advancing this site.
- One jurisdictional design basis controls capacity, product assumptions, parcel facts, approvals, and local criteria
- The ultimate campus and every phase preserve infrastructure, construction, maintenance, and replacement paths
- Usable capacity is calculated from coordinated constraints rather than gross acreage
- Public-facing edge design remains compatible with security, utilities, fire access, operations, and maintenance
- Access analysis includes emergency, construction, heavy-haul, commissioning, and full replacement movements
- Utilities show source, route, facility, capacity, rights, ownership, maintenance, and phasing
- Standard-to-local deviations quantify capacity, reliability, cost, schedule, approval, and operational effects
- Each plan release defines permitted changes and required revalidation
- Local modifications and waivers have authority, evidence, fallback, and decision paths
- Lessons update future screening, consultant scopes, master plans, Basis of Design, and playbooks
What DCFR would flag
Risks surfaced at the screening stage.
DCFR would flag an entitlement concept that looks complete but cannot trace its capacity, access, utilities, constraints, mitigation, phasing, and deviations to one controlled jurisdictional design basis.
Professional confirmation required
Items requiring licensed validation.
Confirm land-use and application requirements, plan conformance, modifications, hearings, conditions, and legal effect with the authority and qualified local counsel. Confirm survey, civil, utility, environmental, fire, security, architecture, engineering, cost, construction, and operational assumptions with the responsible licensed professionals and providers.
Final takeaway
The best entitlement plan protects the repeatable data-center product by adapting it deliberately—not by ignoring the parcel or surrendering the Basis of Design.
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.