DCFR Insight 76 / Land Development · Government Relationships + Pre-Application
How Do You Work With Local Government Before Filing a Data Center Application?
Early jurisdiction engagement should surface approval criteria, infrastructure expectations, community sensitivities, and process risk while the project still has room to adapt.
Treat pre-application engagement as diligence
The starting point is not whether the parcel looks attractive. Define the business outcome the land must support and the evidence required to prove it. For this topic, the controlling inputs include planning and zoning staff, public works and transportation, and fire and emergency services. State assumptions explicitly so an early concept cannot quietly become a committed basis without validation.
Meet the people who will actually review the project
Build the evidence on one controlled site and schedule basis. Reconcile planning and zoning staff, public works and transportation, fire and emergency services, water and sewer authorities, economic development and public policy interfaces, and application procedures and adopted standards rather than allowing each discipline to work from a different boundary, phasing assumption, utility date, or campus concept. When evidence is preliminary, label its confidence level and identify the party responsible for confirmation.
Ask for criteria, not favors
A practical workflow is to map agencies and decision makers; then prepare a concise site and use briefing; then ask about approval path, studies and infrastructure; then test likely community issues; then record follow-up actions and responsible parties; then update plan, schedule and risk register. The sequence is intentionally decision-led: each activity should either confirm feasibility, expose a dependency, quantify an impact, create a mitigation, or support a commercial or investment gate.
Development Control Matrix
| Control question | Evidence required | If unresolved | Decision effect |
|---|---|---|---|
| What must be true? | planning and zoning staff + public works and transportation | Assign owner and confirmation date | Do not treat as confirmed |
| What controls timing? | record follow-up actions and responsible parties + update plan, schedule and risk register | Build downside scenario | Adjust capacity date or commercial milestone |
| What can defeat the site? | treating political support as an approval + overpromising before internal alignment | Mitigate, redesign, reprice, or exit | Escalate to investment gate |
| What can be traded? | disclosure versus optionality + early concept detail versus flexibility | Compare alternatives on one basis | Choose risk-adjusted outcome |
Planning-grade framework. Applicable law, utility rules, entitlement procedures, engineering criteria, transaction terms, and licensed-professional requirements vary by jurisdiction and project.
Bring enough information to make the meeting useful
The highest-consequence failure modes include treating political support as an approval, overpromising before internal alignment, meeting only senior officials and not technical reviewers, failing to document agency guidance, and ignoring emerging ordinance changes. Separate these from ordinary design development. A red flag belongs in the executive risk register when it can materially change deliverable capacity, approval probability, schedule, capital exposure, operations, or the ability to exit the transaction.
Capture commitments and unresolved questions
Real sites rarely optimize every variable at once. Typical trade-offs include disclosure versus optionality, early concept detail versus flexibility, community responsiveness versus operational requirements, and speed versus relationship quality. Compare alternatives against the same capacity, date, cost, and risk basis. A mitigation that solves one discipline but creates a larger entitlement, utility, construction, or operating problem is not a complete solution.
Use the feedback to change the development plan
Good government engagement reduces surprises by converting informal expectations into documented requirements, design responses, and schedule actions without making commitments the project cannot control. Record the decision, assumptions, unresolved confirmations, owner, target date, and trigger for reconsideration. That record becomes the bridge between diligence, transaction documents, entitlement, design, infrastructure delivery, construction, and future portfolio learning.
Early screening checklist
What to verify before advancing this site.
- The decision objective for Series Part 08 is explicit
- Planning and zoning staff is supported by current evidence
- Public works and transportation is supported by current evidence
- Fire and emergency services is supported by current evidence
- Water and sewer authorities is supported by current evidence
- Cross-discipline assumptions use one controlled plan and phasing basis
- Material red flags have an owner, mitigation, cost and schedule effect
- Commercial milestones do not outrun technical and entitlement evidence
- The recommendation states what would cause the decision to change
What DCFR would flag
Risks surfaced at the screening stage.
DCFR would flag any site decision where treating political support as an approval, overpromising before internal alignment, meeting only senior officials and not technical reviewers are still being treated as background assumptions rather than controlled development risks with evidence, ownership, and a decision path.
Professional confirmation required
Items requiring licensed validation.
Confirm project-specific land rights, zoning and entitlement requirements, utility capacity and agreements, environmental jurisdiction, civil and geotechnical criteria, life-safety requirements, infrastructure obligations, costs, schedules, and transaction terms with the applicable authorities, utilities, qualified counsel, and appropriately licensed design and technical professionals.
Final takeaway
Good government engagement reduces surprises by converting informal expectations into documented requirements, design responses, and schedule actions without making commitments the project cannot control.
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.