Municipal and infrastructure planning for a responsible data center project

Ask for the full project—and the evidence behind it.

A practical review checklist for local leaders evaluating land, water, power, sound, infrastructure, fiscal effects, accountability, and closure.

Local review should begin with the maximum planned buildout, not only the first phase.

Ask what will be built, which resources it requires, what changes for residents and utilities, who pays for infrastructure and services, how commitments become enforceable, and how performance will be measured after operation begins. This checklist is a decision aid, not legal advice or a model ordinance.

Return to the Resource Center

A practical review checklist.

Project definition

  • What data center type, tenant model, and computing use are proposed?
  • What are the acreage, building area, number of buildings, phases, and maximum buildout?
  • Who will own, operate, and remain accountable for the site through each phase?

Request: Concept and full-buildout plans, project narrative, phasing, ownership structure, and a schedule of assumptions requiring later confirmation.

Land, site, and neighboring uses

  • Why is this site suitable for an intensive, continuously operating use?
  • What homes, schools, parks, habitats, floodplains, wetlands, farms, and other sensitive uses are nearby?
  • How do massing, setbacks, buffers, lighting, substations, transmission, stormwater, and construction traffic fit the place?

Request: Existing-condition inventory, alternatives considered, views and sections, grading and stormwater plans, traffic analysis, landscape and lighting plans, and maintenance responsibilities.

Power and grid

  • What are average, peak, and full-buildout electric loads?
  • Has the utility confirmed capacity, timing, interconnection, and required upgrades?
  • Who pays for generation, transmission, distribution, substations, and ongoing maintenance?
  • Can the project reduce or shift load during constrained conditions?

Request: Utility capacity documentation, load profile, interconnection and upgrade plan, cost allocation, energy and emissions plan, flexibility analysis, and backup-power scenarios.

Water and wastewater

  • What are average and peak water demands for every phase and the full project?
  • What source is proposed, and how does it affect existing users and watershed conditions?
  • Which cooling modes operate under normal, hot-weather, drought, maintenance, and emergency conditions?
  • What wastewater, blowdown, temperature, chemistry, and treatment requirements are expected?

Request: Water balance, source and capacity confirmation, cooling comparison, WUE with assumptions, wastewater characterization, drought plan, metering, and reporting commitments.

Sound and vibration

  • What are the baseline day, evening, and night sound conditions?
  • Which sources operate continuously, intermittently, during testing, and during emergencies?
  • Does the analysis include dBA, dBC, frequency content, tonality, and vibration where relevant?
  • How will commissioning and complaint investigation work?

Request: Baseline study, acoustic model, source data, mitigation schedule, generator-testing plan, commissioning protocol, monitoring locations, and corrective-action process.

Air, climate, and materials

  • What routine and emergency air emissions are expected?
  • What generator testing, fuel delivery, refrigerant, and maintenance practices are proposed?
  • How will construction waste, equipment replacement, and hazardous materials be managed?
  • Which carbon claims include direct operations, purchased electricity, and construction boundaries?

Request: Air permits and calculations, operating schedules, fuel and refrigerant plans, materials and waste plan, and clearly bounded carbon accounting.

Fiscal and community effects

  • What taxes, incentives, abatements, public costs, and service demands are projected?
  • Which assumptions drive the fiscal forecast, and who independently reviews them?
  • What construction and permanent jobs are expected, with what occupations and timing?
  • Which community commitments are tied to demonstrated needs?

Request: Independent fiscal analysis, incentive documents, service-impact estimates, workforce assumptions, infrastructure responsibilities, and written commitments with schedules and reporting.

Emergency response and resilience

  • What fire, hazardous-material, severe-weather, flooding, fuel, and utility-failure scenarios have been evaluated?
  • Can local responders access the site, equipment information, and training they need?
  • What specialized equipment, staffing, mutual aid, or water supply is required—and who funds it?

Request: Emergency response and continuity plans, fire and life-safety review, responder coordination, training and equipment commitments, incident communication, and update schedule.

Accountability and closure

  • Which commitments belong in permits, development agreements, utility agreements, or other enforceable instruments?
  • What is measured, where, when, by whom, and with what public reporting?
  • How will ownership changes preserve obligations?
  • What are the repowering, reuse, closure, remediation, and financial-assurance plans?

Request: Commitment register, commissioning plan, reporting template, responsible contacts, correction and enforcement process, assignment provisions, and decommissioning plan.

The Good Neighbor Data standard.

Understand the place, set project criteria, compare design choices, commission and measure, and improve over time. The aim is not a longer checklist. It is a shorter chain between a local concern, a project decision, a measurable commitment, and a verified result.

Frequently asked questions.

What should local leaders ask first?

Begin with the maximum planned buildout: land area, buildings, electric load, water demand, cooling, wastewater, sound sources, utility upgrades, construction schedule, emergency response, fiscal assumptions, and the party responsible for each commitment.

Should a community copy another jurisdiction’s data center ordinance?

No. Other ordinances can show how peers addressed an issue, but authority, infrastructure, land-use patterns, background conditions, and community priorities differ. Local technical and legal review should connect each requirement to a documented public purpose.

How should project commitments be tracked?

Create a commitment register that identifies the obligation, legal or administrative instrument, responsible party, deadline, measurement method, reporting schedule, corrective process, and how the obligation survives an ownership change.

Is this checklist legal advice?

No. It is a decision aid. Local authority, review procedures, enforceability, and appropriate conditions vary by state and jurisdiction and should be reviewed by qualified local counsel and technical professionals.

Bring the project context.

Discuss a project