Part 4: A Responsible Neighbor: A Civic Framework for Data Center Development

A Responsible Neighbor: A Civic Framework for Data Center Development

*How cities can protect residents, preserve public resources, and still give responsible technology investment a fair path forward*

Good evening, members of the council, city staff, residents, business leaders, utility representatives, educators, farmers, workers, and members of the development community.

We are here because a large technology project has the power to change a community.

It can change the tax base. It can change the local workforce. It can change demand on the electrical grid, the water system, the road network, and the land itself. It can create opportunity for a young person who wants a skilled career close to home. It can also create anxiety for a family that depends on a private well, a retiree living on a fixed income, or a farmer who discovers that the land beside his property has been sold before he was ever invited into the conversation.

Those concerns are not mutually exclusive. They are not evidence that one side is informed and the other is unreasonable. They are evidence that this is a serious decision with serious consequences.

The question should not be reduced to whether a community is for technology or against it. We need digital infrastructure. Hospitals, emergency systems, payroll, public records, communications, education, transportation, and modern business all depend on it.

But the cloud is not weightless.

It is built from concrete and steel. It consumes electricity. It produces heat. It requires cooling. It occupies land. It connects to public infrastructure. It is located in a real place, near real homes, under the authority of real governments, and within the limits of real water and power systems.

The standard should therefore be straightforward: if a data center is going to become a community’s neighbor, it must be expected to behave like a responsible neighbor.

Begin With Respect for Every Legitimate Interest

The resident who supports the project may be thinking about a son or daughter enrolled in an electrical, mechanical, or technical program. They may see a chance for skilled work without leaving the region or taking on overwhelming debt. They may see new customers for local contractors, hotels, restaurants, and suppliers.

That is a legitimate position.

The resident who opposes the project may depend on a residential well. They may be worried about the aquifer, generator noise, construction traffic, farmland, or the possibility that household utility rates will rise to pay for infrastructure built primarily for one industrial customer.

That is also a legitimate position.

The city manager may be working under a nondisclosure agreement believed necessary to keep the project alive. The developer may be protecting a site-selection process from land speculation. The utility may be trying to serve a major new load without compromising reliability. Each party has a real interest, and each is operating under pressure.

A productive process begins when no group is dismissed as ignorant, hostile, or self-interested simply because it sees a different part of the risk.

From that point forward, however, respect must be converted into structure. Good intentions are not enough. Large infrastructure projects require rules capable of surviving deadline pressure, political turnover, market changes, and the unequal negotiating power between a small municipality and a global technology company.

The Real Issue Is Governance, Not Technology

The central policy question is not whether data centers should exist. They already form part of the physical backbone of modern society. The more useful question is how the costs, benefits, and risks of that infrastructure should be allocated.

In poorly structured deals, benefits are described broadly while burdens are assigned locally. The company serves customers across the country or around the world, but the host community supplies the land, water, electrical capacity, road access, emergency response, and political permission.

That imbalance is not automatically unfair. Communities regularly host infrastructure that serves people beyond their borders. The unfairness begins when local risks are hidden, public costs are socialized, promises are difficult to verify, and residents are brought into the process only after the important decisions have been made.

This is why the strongest civic framework begins with governance rather than branding. A project should not be judged by the size of the announced investment alone. It should be judged by the quality of the agreement governing its relationship with the community.

A billion-dollar investment can still be a poor deal. A controversial project can still become a good one. The difference lies in the terms.

Transparency Must Be Timely, Narrowly Protected, and Operationally Useful

Developers have a reasonable interest in protecting land assembly and commercially sensitive information. If a company publicly announces that it intends to acquire hundreds of acres in a specific location, speculators may drive up prices or disrupt negotiations.

That concern justifies limited confidentiality during a defined phase. It does not justify permanent secrecy around public resource consumption.

The amount of municipal water a facility will use is not equivalent to proprietary server architecture. Peak electrical demand is not the same as intellectual property. The number of permanent jobs, the duration of construction employment, the scale of backup generation, and the infrastructure expected from the public are all legitimate subjects of public review.

Disclosure must also occur early enough to matter. Notice after a land sale closes may satisfy a technical requirement, but it does not provide meaningful participation. Residents need time to understand the project, ask questions, obtain independent advice, and engage before the approval path becomes irreversible.

A mature transparency framework should distinguish among three categories:

Protected corporate information includes intellectual property, internal network design, server-floor security, and other details whose disclosure could create legitimate commercial or operational risk.

Time-limited confidential information includes land assembly and preliminary site-selection details that may require temporary protection.

Public-interest information includes projected and actual water use, electrical load, backup generation, infrastructure costs, tax incentives, permanent employment, local hiring commitments, compliance results, and public subsidies.

Once the project begins operating, public-interest commitments should be tracked on a dashboard that reports performance in plain language. Transparency should not require a records lawsuit, a whistleblower, or a crisis.

A community cannot govern what it is not allowed to measure.

Financial Responsibility Must Follow Causation

The clearest principle in the entire debate is that the party creating a major new demand should bear the cost of serving that demand.

If a data center requires a new substation, the project should pay for the substation. If it requires transmission upgrades, those costs should not be shifted to residential customers. If a water system must be expanded primarily because of the facility, the financing structure should reflect that cause.

This requires dedicated large-load utility rates rather than blending hyperscale customers into ordinary residential classes. It also requires long-term purchase commitments, capacity reservation charges, and exit provisions.

Exit protection is especially important. Utilities may build infrastructure based on an expected operating life measured in decades. If the company later abandons the project, reduces its load, or determines that the site is no longer economically useful, the remaining customers should not inherit debt for infrastructure built around a vanished demand forecast.

A well-drafted agreement therefore plans for both success and failure.

The same logic applies to public incentives. Tax benefits should not be granted primarily for announcements. They should follow verified performance.

If a company receives an incentive for creating 50 permanent jobs at a defined wage, those jobs should be audited. Temporary construction crews, subcontractors, and permanent operating staff should be reported separately. If the promised positions do not materialize, the incentive should decline, disappear, or be clawed back.

This is not an anti-business posture. It is standard performance management. Public support should purchase public benefit, not optimism.

Approvals Should Be Phased Because Risk Changes Over Time

A multi-building data center campus may be presented as a single project, but its actual impacts emerge over years. Power demand grows by phase. Water consumption changes as buildings come online. Employment claims can be tested. Noise and traffic patterns become measurable.

Approving an entire ten-year campus at the beginning gives away most of the community’s leverage before the first operating results exist.

A stronger model approves Phase 1 under a defined set of limits and commitments. These may include:

Before Phase 2 is approved, an independent review should determine whether the company complied with Phase 1.

If the commitments were met, expansion can proceed. If they were not, future permits should pause until violations are corrected and penalties are resolved.

This creates a simple but powerful principle: expansion is earned through performance.

Phased approval protects the community from granting ten years of growth on the strength of projections. It also protects responsible developers by creating a predictable path forward. A company that performs well knows what it must do to unlock the next phase.

Power Policy Should Reward Flexibility, Not Merely Consumption

The grid challenge is often framed as a need for immediate new generation. In some cases, new infrastructure will be necessary. But the existing electrical system also contains underused capacity during most hours of the year because grids are built to survive a small number of extreme peaks.

The source material describes this through the image of a highway designed for the Wednesday before Thanksgiving. The road must be wide enough for the annual surge, even though many lanes remain underused on ordinary days.

The electrical grid operates under similar logic. If a large new customer agrees to reduce or shift demand during the limited hours when the system is stressed, it may be possible to connect that load without building every proposed addition immediately.

For the developer, flexible interconnection can shorten a five-to-seven-year wait. For the utility, it improves use of existing assets. For residents, it may reduce the need for new infrastructure financed through local rates.

The contract, however, must define what curtailment actually means.

A facility should not be allowed to satisfy a reduction request by disconnecting from the grid and starting large diesel generators beside homes and businesses. That technically reduces grid demand while moving emissions and noise into the host community.

Legitimate curtailment should rely on operational flexibility: pausing non-urgent computing tasks, shifting workloads to another region, or using cleaner stored energy. Live emergency systems and critical services cannot be paused, but certain long-running workloads can be delayed briefly without harming users.

The policy objective is not to make data centers unreliable. It is to distinguish inflexible critical demand from flexible computational work and price each accordingly.

Water Policy Must Manage the Thermodynamic Tradeoff Honestly

Data centers generate heat. That heat must be removed. Cooling strategies generally shift the burden between water and electricity.

Evaporative cooling can lower peak electrical demand, but it consumes water. Air cooling can reduce direct water use, but it requires large fan systems and increases electrical demand.

This is why promises of “zero impact” are usually not serious operating standards. The impact can be reduced, shifted, timed, recycled, or mitigated, but it cannot be eliminated by language alone.

A responsible water policy begins with a hierarchy.

First, the facility should recycle water internally through closed-loop systems where practical. Second, it should use reclaimed municipal wastewater. Third, it should evaluate gray water and suitable industrial supplies. Fourth, it should capture stormwater and rainwater from roofs, paved surfaces, and solar canopies. Potable municipal water should be the last option rather than the default.

The physical design of the campus matters. A large facility creates enormous catchment surfaces. Instead of routing every storm into public drains, the site can collect water in cisterns, treat it as needed, and use it for cooling.

Timing also matters. A facility that draws heavily from municipal pipes at 6 p.m. creates a different operational problem than one that fills on-site storage between 1 a.m. and 4 a.m. Off-peak filling may not reduce annual consumption, but it can protect pressure, reduce treatment bottlenecks, and avoid infrastructure expansion driven by a few high-demand hours.

Water agreements should therefore define total volume, water type, withdrawal timing, drought conditions, reporting standards, and remedies if nearby wells or public systems are affected.

The correct goal is not a slogan. It is a measurable reduction in public risk.

Land Use Should Favor Existing Disturbance and Multiple Benefits

Large facilities require land, but not every acre carries the same public value.

States and local governments should favor retired industrial sites, closed manufacturing facilities, former power plants, existing industrial parks, and underused commercial land before converting prime farmland.

On-site generation should begin with the surfaces already created by the project. Roofs and parking canopies should be used before productive soil is covered with separate ground-mounted systems.

Where agricultural land is unavoidable, dual-use approaches can preserve some of its function. Elevated panels may allow grazing, shade-tolerant crops, or pollinator habitat. The design should avoid treating land as a blank surface whose only value is the infrastructure placed on top of it.

The same principle applies to waste heat. In colder climates, a data center continuously produces heat that is often captured only to be discarded. With the right planning, that heat can support greenhouses, hospitals, municipal buildings, or district heating systems.

These approaches do not erase the facility’s footprint. They increase the value produced by that footprint.

Workforce Development Must Be Specific Enough to Audit

The strongest argument in favor of a major technology project is often opportunity. A local student in an electrical or technical program may see a path to a stable career without leaving home.

That opportunity should be made real through enforceable workforce planning.

Developers should partner with high schools, technical programs, community colleges, and veteran transition organizations before the facility opens. Curricula should align with the actual jobs expected on site: electrical systems, controls, cooling maintenance, network operations, security, and mechanical systems.

General promises to “support workforce development” are not enough. Agreements should identify funded training seats, apprenticeship targets, interview commitments, wage standards, and permanent local hiring goals.

They should also distinguish among temporary construction labor, subcontracted services, and direct long-term employment.

The objective is not to inflate a job count. It is to build durable local capability.

Small Governments Need State and Regional Support

No local rulebook will work if a small municipality must negotiate alone with a corporation that has completed similar transactions across many jurisdictions.

The information imbalance is structural. The developer knows the tax abatements, utility rates, zoning concessions, and contract language accepted elsewhere. The town often knows only what it is being told in the current room.

States should provide independent utility counsel, grid engineers, hydrologists, land-use specialists, and financial analysts when a local government receives a hyperscale proposal. This support should be automatic and funded independently from the developer.

Regional planning is equally important. Power systems, water basins, labor markets, and transportation networks cross municipal boundaries. Developers should not be able to trigger a race to the bottom by threatening to move a few miles unless one jurisdiction weakens its requirements.

Regional scorecards can create consistent expectations for water, power, land, public cost, transparency, and community benefit.

The goal is not to make development impossible. It is to make negotiation competent.

A corporation should not receive a superior deal simply because it found the community with the smallest legal department.

A Professional Standard for Responsible Approval

A sound data center agreement should satisfy a clear set of tests.

The project should disclose the public resources it expects to consume. It should pay for the infrastructure its demand requires. It should accept dedicated utility rates and long-term financial commitments. It should use water according to a defined hierarchy. It should report actual performance publicly. It should earn expansion through compliance. It should tie incentives to measurable outcomes. It should build a local workforce pipeline. It should prioritize already-disturbed land. It should evaluate flexible power, off-peak water, stormwater capture, and heat recovery. And the local government should receive independent expertise before entering a binding agreement.

If a developer can meet those standards, the community should provide a fair and predictable path forward.

If it cannot, the community should not be pressured into carrying risks the project itself will not accept.

This is not a choice between progress and obstruction. It is a choice between unmanaged growth and governed growth.

The digital economy will continue to expand. The physical infrastructure behind it will be built somewhere. The relevant question is whether that infrastructure enters a community through secrecy, pressure, and cost shifting—or through transparency, accountability, and shared benefit.

A responsible community does not say yes to everything. It does not say no to everything.

It sets the terms under which a necessary industry can become a trustworthy neighbor.