Cuyahoga County Data-Center Guide Shows How Local Governments Can Say Build It Right

BadPD source-check, June 19, 2026; source dates May 2026, June 10, and June 17, 2026: Cuyahoga County, Ohio, has put out the kind of data-center receipt package local governments should have before a developer asks for land, water, grid capacity, tax treatment, or secrecy.

The county’s official June 10 release says the Department of Sustainability created a Data Center Development Guide to help communities evaluate opportunities, understand impacts, and make informed decisions. The release says Ohio is home to nearly 200 data centers, including several dozen in Cuyahoga County, and that developers are approaching more communities as demand grows.

This is not anti-compute. BadPD’s frame stays the same: build American compute capacity, but make large-load projects prove the power, water, cooling, emergency, zoning, and public-cost math before public officials sign away leverage.

The County Is Telling Cities To Slow The Deal Down

Cuyahoga County Executive Chris Ronayne put the issue plainly in the county release: unchecked projects can drain power, water, and tax dollars without creating enough jobs or revenue. The point is not that every project is bad. The point is that every project needs receipts before it becomes politically and legally hard to stop.

The official guide gives local governments concrete tools: temporary moratoriums, zoning updates, conditional-use permits, community benefits agreements, and enforceable standards. It also tells municipalities to look for common developer signals, including vague project descriptions, “light industrial” or “technology park” labels, anonymous LLCs, large land assemblages, and 50-200+ MW utility inquiries.

No NDAs, No Verbal Assurances

The strongest part of the guide is the warning about what not to do. Axios Cleveland reports that the guide warns communities not to sign nondisclosure agreements, accept developer economic-impact projections without independent review, or rely on verbal assurances about water, energy, noise, or emissions.

That belongs in every data-center ordinance packet in the country. A verbal promise is not a cooling plan. A slide deck is not a water contract. A shell company is not public accountability. A claimed job number is not a fiscal-impact review. If a project needs public land-use approval, ratepayer-backed grid upgrades, water access, or emergency-service capacity, the public gets to see the terms.

The Build-It-Right Checklist

The county PDF says hyperscale data centers can consume more than 2 million gallons of fresh water per day, and that large facilities can pressure land, energy, and water systems while providing mostly construction-phase jobs. It also notes concerns over land conversion, noise, onsite generation emissions, utility costs, and opaque permitting.

BadPD’s practical checklist follows the same logic: how many megawatts, what interconnection upgrades, who pays for those upgrades, what cooling system, what water source, what backup generation, what battery or demand-response commitment, what noise controls, what fire-response plan, what decommissioning bond, and what community benefit is enforceable after the press release fades.

Spectrum News Ohio reports that the guide discusses water systems, electricity infrastructure, emissions, land conversion, noise, temporary moratoriums, zoning, and community benefits agreements. Axios adds that Cleveland rejected a permit for a proposed $1.6 billion Slavic Village hyperscale project and that City Council is considering a temporary moratorium. Those local details remain reported context unless and until the specific permit and council records are attached.

Confirmed, Reported, Pending

Confirmed: Cuyahoga County released the guide; the county’s official resources page hosts the Data Center Recommendations PDF; and the guide covers local context, moratoriums, zoning, community benefits agreements, developer indicators, questions to ask, and mistakes to avoid.

Reported: Spectrum and Axios report the guide’s local policy context, including Ohio’s broader data-center debate and Cleveland’s recent brake-pumping posture.

Pending: Cleveland permit records, any Cleveland moratorium bill text, project-specific Cuyahoga municipal applications, utility interconnection records, signed community benefits agreements, and any developer water or power commitments.

Cuyahoga County’s guide should be read as a warning and a model. Communities do not have to choose between no AI future and a blank-check AI future. They can demand the public ledger first, then build what can actually stand behind its receipts.

Source Trail

• Cuyahoga County official release (June 10, 2026) – County announcement of the Data Center Development Guide and official statements from Chris Ronayne and Jenita McGowan.
• Cuyahoga County sustainability resources page (accessed June 19, 2026) – Official county page listing downloadable municipal sustainability guides, including Data Center Recommendations.
• Cuyahoga County Data Center Development Recommendations PDF (May 2026) – Official county guide covering local context, moratoriums, zoning, CBAs, developer indicators, questions to ask, and what not to do.
• Spectrum News Ohio (June 10, 2026) – Local report on the guide, county statements, Ohio context, and public concerns over water, electricity, emissions, land conversion, and noise.
• Axios Cleveland (June 17, 2026) – Local report framing the guide as a playbook and noting Cleveland permit rejection and moratorium consideration as reported context.