A massive data center can arrive wrapped in promises of investment, construction jobs and technological progress. But once the servers switch on, the consequences can last for decades—and the public may discover that the most important decisions were made before residents knew which questions to ask.
Beck’s central warning was neither an automatic endorsement nor a blanket rejection of data centers. Instead, he urged communities to separate documented risks from project-specific variables and unsupported fears—and to negotiate before local officials surrender their leverage.
The timing matters. Artificial-intelligence services and cloud computing are driving a new wave of enormous electrical loads. In June, the Federal Energy Regulatory Commission ordered all six regional grid operators under its jurisdiction to justify or reform the rules governing how data centers and other large users connect to the grid. FERC specifically identified consumer protection, transparency and the prevention of cost shifting as national priorities.
The first question is simple: Who pays?
A data center can require new substations, transmission lines and generating capacity. Those upgrades may benefit one enormous customer, but under a poorly designed agreement, some of the expense can flow into the rates paid by families and small businesses.
FERC now describes “cost recovery agreements” as a tool for ensuring that large customers pay their fair share—even when a proposed facility is delayed, downsized or never opens. The agency’s concern is explicit: residential customers should not be left paying for infrastructure built around a speculative project.
The industry has also moved toward specialized rate structures. The Edison Electric Institute reported in May that 23 states had approved a large-load tariff, with proceedings pending in seven more. These tariffs can require major users to provide deposits, make minimum payment commitments, accept longer contract terms or cover infrastructure costs tied directly to their projects.
Before approving a project, residents should demand clear answers:
- Does the state have an enforceable large-load tariff?
- Which transmission, generation and substation costs will the developer pay?
- Will residential customers face charges before the facility reaches full operation?
- What happens if the developer cancels the project or uses less electricity than forecast?
- Are the obligations guaranteed for the full life of the development?
Noise must be measured like noise people actually hear
Data-center noise is not limited to an occasional truck or construction crew. Cooling equipment can create a continuous low-frequency hum, while backup generators may run during testing, emergencies or extended grid outages.
That distinction matters because an ordinance written for traffic, lawn equipment or short-lived construction noise may not adequately measure persistent low-frequency sound. A facility can satisfy an outdated numerical standard while nearby residents still experience vibration, disrupted sleep or an intrusive hum inside their homes.
The World Health Organization links excessive environmental noise with sleep disturbance, hypertension, ischemic heart disease and cognitive effects. Communities should therefore require enforceable limits at the property line and inside nearby residences—not simply accept a developer’s computer model.
A serious agreement should address:
- Daytime and nighttime noise limits, including low-frequency measurements
- Independent baseline testing before construction
- Continuous monitoring after operations begin
- Limits on generator testing hours
- Mandatory mitigation and meaningful penalties when limits are exceeded
Backup power can become a neighborhood air-quality issue
Hyperscale facilities may install banks of diesel generators for emergency power. Diesel exhaust contains fine particles, nitrogen oxides and other pollutants. The Environmental Protection Agency’s health assessment recognizes diesel exhaust as a mixture that contributes to ambient concentrations of fine particulate matter, nitrogen oxides and air toxics.
Residents should ask how many generators are planned, their emissions tier, their combined permitted operating hours and whether the company expects to use them only for emergencies. Officials should also determine whether future phases could add on-site generation that was not emphasized during the initial approval process.
Water use is not one-size-fits-all
Claims that every data center consumes enormous amounts of water are too broad. So are claims that a proposed facility will have no meaningful water impact. The result depends on the cooling technology, climate, operating load and source of the water.
The Department of Energy explains that cooling-tower systems reject heat through evaporation and that consumption depends on the IT heat load and the efficiency of each cooling stage. Closed-loop, dry and hybrid systems can substantially change the tradeoff between water and electricity use.
Local officials should require the developer to identify the cooling design before approval and disclose:
- Expected daily and annual water consumption
- Maximum use during hot or dry conditions
- Whether potable, reclaimed or groundwater will be used
- How wastewater and concentrated contaminants will be handled
- Whether the company can later switch to a more water-intensive system
Construction jobs are not permanent jobs
Large campuses can support thousands of construction workers, but the permanent workforce is often much smaller. That does not make the investment worthless, but it changes how tax incentives should be evaluated.
Good Jobs First found that 11 prominent subsidized data-center deals averaged approximately $1.9 million in public incentives per permanent job. Its more recent research continues to warn that subsidy disclosure is often incomplete and that the public cost per job can be exceptionally high.
Officials should publish separate estimates for temporary construction employment, permanent employment, average wages and total public subsidies. Any incentive should include enforceable clawbacks if the company fails to deliver the promised investment or jobs.
Watch the power lines—and the fine print
A data-center operator may not possess eminent-domain authority, but the utility serving it might. If a project requires a new transmission corridor, landowners can face condemnation proceedings for infrastructure created primarily to serve a private development.
Residents should insist on knowing the planned route, who owns the infrastructure, whose customers it serves and whether alternatives were considered. Setbacks, landscaping, construction access and the effect on farms and homes should be negotiated before the project receives final approval.
Transparency is equally important. Code names, nondisclosure agreements and layered ownership structures can prevent residents from understanding who is behind a proposal. Public officials should disclose every development agreement, tax benefit, utility commitment and expansion option before voting.
Not every viral claim deserves equal weight
Communities weaken their position when legitimate concerns are mixed with claims that cannot be supported. The strongest public case rests on measurable issues: infrastructure costs, noise, emissions, water, land use, subsidies, emergency planning and transparency.
Arguments about mysterious “radiation,” secret surveillance facilities or a guaranteed regional blackout can distract from evidence that officials cannot easily dismiss. Grid reliability is a real subject for study, but it should be evaluated through interconnection studies, load forecasts and binding operating requirements—not slogans.
Fifteen questions to ask before the vote
- Who is the ultimate owner and operator of the facility?
- How much electricity will it use at startup and at full buildout?
- Who pays for every required grid upgrade?
- What financial security protects customers if the project is canceled?
- What cooling technology will be used?
- How much water will the facility consume under worst-case conditions?
- How many backup generators are planned, and what emissions standards apply?
- How often may those generators operate or be tested?
- What enforceable nighttime and low-frequency noise limits will apply?
- What are the minimum setbacks from homes, schools and property lines?
- How many permanent jobs are contractually guaranteed?
- What is the total value of every tax exemption, abatement and subsidy?
- Will any transmission route require eminent domain?
- What future expansion rights are included?
- Which promises are enforceable, and what penalties apply when they are broken?
The community’s leverage is greatest before approval
The debate should not be reduced to “technology good” or “technology bad.” Two similarly sized facilities can produce dramatically different outcomes depending on their cooling systems, utility contracts, setbacks, emissions controls and development agreements.
A community may ultimately decide that no agreement can make a proposed location acceptable. That is a legitimate conclusion. Another community may secure infrastructure investment, tax revenue and protections strong enough to justify approval. The mistake is allowing urgency, secrecy or political enthusiasm to substitute for enforceable terms.
Once the zoning changes and construction begins, the public’s bargaining power collapses. Before the first shovel enters the ground, every cost, safeguard and promised benefit should be independently verified—and put in writing.
Editor’s note: This article is an original synthesis of the supplied Plaud transcript and summary. Advertising and unrelated program segments were excluded. Key policy and health claims were cross-checked against materials from FERC, the Department of Energy, the World Health Organization, the Environmental Protection Agency, the Edison Electric Institute and Good Jobs First.
