Data Center Community Impact: Records to Request

What Communities Should Ask Before Approving a Data Center

A community cannot evaluate a data center from a national electricity average, a promised job count, or a company sustainability report. It needs project-specific records for power, water, cooling, backup generation, emissions, land, tax incentives, construction, workforce, emergency response, and continuing public reporting.

The central question is not whether data centers are good or bad. It is whether the proposed facility's costs, benefits, dependencies, and protections are visible enough for a public decision.

National context is not a site estimate

The Department of Energy's 2024 data-center electricity report summarized Lawrence Berkeley National Laboratory scenarios for rapidly rising U.S. demand. DOE's current data-center resource hub collects later federal material.

Those sources describe a national system. They cannot establish one project's peak load, annual use, ramp schedule, grid connection, generation source, or effect on local rates.

The Government Accountability Office's 2025 assessment says estimates of generative AI's environmental effects vary because companies disclose limited information about infrastructure, energy, emissions, and water. That uncertainty is a reason to require project records, not a reason to substitute a dramatic national number.

Begin with the actual facility

The application should identify the legal applicant, property owner, operator, end user if known, site, acreage, buildings, phases, planned IT load, total facility load, operating schedule, cooling design, expected useful life, and decommissioning responsibility.

A campus announced as 100 megawatts may have a different total load once cooling, power conversion, lighting, and support systems are included. A later phase can change the impact after the first approval.

flowchart TD
    A["Proposed data center"] --> B["Power and grid"]
    A --> C["Water and cooling"]
    A --> D["Air and backup generation"]
    A --> E["Land, noise, traffic, and emergency response"]
    A --> F["Taxes, incentives, jobs, and public cost"]
    B --> G["Project-level public record"]
    C --> G
    D --> G
    E --> G
    F --> G
    G --> H["Approval terms, monitoring, and enforcement"]

Request the power record

The record should include expected peak megawatts, annual megawatt-hours, phase timing, load factor, interconnection study, utility service agreement, transmission and distribution upgrades, generation assumptions, demand-response obligations, outage priorities, and responsibility for capital and ongoing cost.

The community should be able to distinguish company-funded infrastructure from costs recovered through other customers. Confidential commercial details may need protection, but a confidentiality claim should not erase the material public allocation.

If dedicated generation is proposed, request the fuel, capacity, operating profile, construction permit, emissions controls, ownership, and retirement or conversion plan.

Request the water and cooling record

Water use depends on cooling technology, weather, workload, water quality, reuse, and operating choices. The application should state source, withdrawal authorization, peak daily and annual use, consumptive use, discharge, treatment, chemicals, sewer capacity, drought operation, and alternatives.

The record should separate potable, reclaimed, surface, and groundwater. It should show how the project performs during drought or extreme heat, when cooling demand and community water stress may rise together.

Water withdrawal, consumption, and discharge are different quantities. A large withdrawal can return much of the water. Evaporative cooling can consume water by returning it to the atmosphere. Neither should be described with a single unexplained gallons figure.

Request air and backup-power records

Backup generators can create a material local air source when installed in large numbers or tested regularly. Request the generator count, manufacturer, model, capacity, fuel, stack, emission factors, expected testing hours, emergency-use definition, permits, controls, monitoring, maintenance, and cumulative site emissions.

The Environmental Protection Agency's stationary engine compliance resources explain federal requirements for certain engines. Federal rules do not replace state and local permits.

Do not infer health outcomes from the equipment list alone. A site-specific review needs emissions, dispersion, background conditions, exposure, population, operating history, and qualified public-health evidence.

Price the public exchange

Economic-development claims should identify permanent jobs, construction jobs, wages, occupations, residency assumptions, vendor spending, tax revenue, exemptions, abatements, grants, land discounts, infrastructure subsidies, and public-service cost.

A job promise should have a date, definition, reporting method, and remedy if it is missed. Construction employment should not be presented as permanent operating employment.

Tax agreements should show the baseline, term, renewal, transfer, clawback, audit rights, and the public body responsible for enforcement.

Plan for ordinary and extreme operations

Request the fire and emergency plan, hazardous materials record, battery system design, responder access, water supply, mutual-aid requirements, evacuation or shelter assumptions, cybersecurity coordination, severe-weather plan, outage behavior, and incident notification.

FEMA's community lifelines framework can help a locality consider how energy, communications, water, transportation, safety, and other services interact during disruption. It does not replace a facility-specific plan.

Noise, lighting, traffic, construction hours, road wear, stormwater, wetlands, habitat, and cultural resources also need the records required by the site and jurisdiction.

Make approval measurable

An approval should identify which statements are enforceable, who monitors them, which data is reported, how often, where the public can see it, what counts as a violation, and which remedy applies.

Useful continuing records can include monthly electricity and water use, cooling source, generator operation, reportable incidents, employment, incentive compliance, complaints, permit exceedances, and expansion requests.

The data should be specific enough to compare the operating facility with the approved case while protecting legitimate security and customer information.

The record should be public. It should be easy to find. It should use the same units each month. Each phase should have its own line. Changes should be dated. Missing data should be marked. Claims should link to the permit or agreement that controls them.

Avoid the national-average trap

One facility can use less water because it relies on air cooling and more electricity as a consequence. Another can use reclaimed water but place new demand on treatment infrastructure. A project can create substantial tax revenue while shifting grid costs. A low permanent job count may still accompany a strategic infrastructure benefit.

Those are tradeoffs to measure, not slogans to resolve.

Episode 102 raised serious concerns about undisclosed water use and backup turbines. The public guide does not repeat specific allegations from the recording without permits, utility records, enforcement records, and qualified evidence for the named site.

The decision standard

Ask for the design basis, not only the headline. Ask who pays, who benefits, who monitors, and what happens when the project changes.

A community can support, oppose, modify, or condition a proposal. Whatever the decision, it should rest on a record that can still be audited after the ribbon cutting.

AI assisted with research organization, structure, drafting, and validation. Dalton Anderson remains the attributed author and final editorial authority. The transcript and linked public sources control factual claims. Publication remains unauthorized.