Ohio’s power rules and a St. Louis development show what residents should examine before welcoming—or rejecting—a data center.

If a data center asks for enough electricity to justify new infrastructure, then uses far less than expected, who pays for what was built?

Ohio has put a concrete answer into a payment rule. St. Louis has negotiated its own conditions around a major development. Together, they show why the terms of an AI project deserve as much attention as the size of the investment.

The issue has moved into the election debate. Reuters reported on October 22 that opposition to data centers is drawing investor attention ahead of the midterms, with state and local decisions particularly relevant to expansion. [1]

Residents do not need to decide whether they love or hate AI before asking to see the deal. They need to know what the project brings, what it requires, and which promises can be enforced.

Ohio makes companies commit before the power arrives

In July 2025, Ohio regulators approved a settlement requiring qualifying large new AEP Ohio data-center customers to pay for at least 85% of their contracted electricity capacity even when they use less, with commitments running up to 12 years. Ohio’s Consumers’ Counsel describes the arrangement as protection against shifting infrastructure costs to other customers. [2]

AEP’s account of the approved arrangement also identifies financial-viability requirements, an exit fee, and a four-year ramp-up within the 12-year period. [3]

The distinction is important: the 85% figure concerns contracted capacity. It does not mean a company purchases 85% of every household’s electricity, or that all electricity-related expenses disappear for residents.

Think of a restaurant that reserves a large room and guarantees a minimum payment even if fewer guests attend. The guarantee helps protect the business that committed the space. A data-center payment obligation addresses a similar planning problem, although utility arrangements are more complex.

There is disagreement over this approach. Industry groups appealed the Ohio decision in November 2025, according to the Consumers’ Counsel. [2] The rule should therefore be discussed as a documented regulatory approach with a legal challenge—not an uncontested national template.

What it means for your town: Ask what payment is guaranteed, for how long, and what happens if the project shrinks or leaves.

St. Louis shows why job totals need a second look

In April, St. Louis announced conditional approval for the Armory data-center development. The city projected 200 full-time jobs across the development, including 150 in redeveloped Armory office space. That is a broader employment figure than jobs operating the data center alone. [4]

The city also identified closed-loop cooling and air-cooled chillers, water-system studies, and a decommissioning plan among its conditions. Those are announced requirements, not evidence that future operations have already met them. [4]

In September, local station First Alert 4 reported approval of a community-benefits agreement requiring at least 100 permanent jobs, with an estimated 1,000 construction jobs. It also reported nearly $16 million in developer commitments and no local tax incentives. [5]

Those figures refer to different announcements and measures. A projected development-wide total, a contractual minimum, and temporary construction employment should be presented separately.

The project is also contested. October 17 reporting described litigation involving residents, the city, and the developer. [6] That makes it particularly important to distinguish the conditions officials announced from their ultimate implementation and enforcement.

What it means for your town: Request the permanent-job commitment, its scope, the timetable, and the consequence if it is missed. Treat projected tax revenue as a forecast until it is collected.

The national power forecast is large, but it is not your bill

Lawrence Berkeley National Laboratory’s June 2026 update projects data centers could use 11.8% of U.S. electricity in 2030 in its reference case, with a wider scenario range of 9.5% to 15.3%. The estimate covers the sector, including uses beyond AI. [7]

These are projections, not current consumption figures. They establish the scale of a planning challenge; they cannot identify the effect of one facility on one household.

The Energy Information Administration explains that electricity prices reflect costs across generation and the grid, alongside influences such as fuel prices and weather. [8]

That is why an honest local analysis needs utility filings and approved rates. A rising bill alone does not establish how much is attributable to a data center. A promise that growth will benefit everyone is not a substitute for the same evidence.

Residents deserve an explanation connecting the project, the required investment, and the proposed charges.

The White House pledge needs a local paper trail

The White House’s March 4 Ratepayer Protection Pledge calls for participating companies to provide additional power resources, cover required delivery-infrastructure upgrades, and negotiate separate payment arrangements that apply even if they do not use the electricity. [9]

That is relevant to the concern communities are raising. The pledge describes voluntary negotiation of rate structures; the arrangements for an individual project still need examination.

Ask officials to identify where the relevant obligations appear: an approved rate schedule, a service agreement, a permit, or another instrument. Ask who can enforce them and what protection exists if a company cannot pay.

Ohio’s example shows how a commitment can be expressed in a specific payment rule. The St. Louis example shows why employment, cooling, and other local conditions also matter. Neither removes the need to check the documents for the project in front of you.

A community can benefit—and still negotiate hard

Supporters have a legitimate case to make when a project brings useful investment, employment, and revenue. Opponents have a legitimate basis for demanding evidence about costs and neighborhood impacts.

The useful comparison is the community’s expected position under the actual agreement. Count disclosed incentives and public expenses alongside projected receipts. Separate one-time contributions from recurring revenue. Examine what happens if construction is delayed or the facility closes early.

Water questions should address the proposed cooling design and local conditions. Noise questions should specify limits, measurement locations, and enforcement. Employment promises should identify which positions are permanent and whether there is an obligation behind the estimate.

These are questions for a particular proposal. Importing an alarming number—or a reassuring promise—from an unrelated project can obscure the decision residents actually face.

Before officials sign, ask for five answers

Ask for	Why it matters
Infrastructure costs and payment obligations	Shows who funds the connection and related upgrades
Minimum payments and exit protections	Reveals what happens if demand falls or the operator leaves
Permanent jobs and net public revenue	Separates lasting benefits from temporary work and headline investment
Water, noise, and closure requirements	Makes neighborhood protections specific enough to examine
Public reporting and enforcement	Lets residents compare commitments with performance

The Balanced Report’s view is that officials should explain these answers publicly before committing public resources. Where details must remain confidential, they should identify what has been withheld and explain how the public interest was assessed.

A community can support innovation while negotiating firmly for its residents. The test is whether the promised benefits survive a close reading of the agreement.

Before welcoming the AI boom, find out who has agreed to pay—and what happens if they do not.

Reader question: What condition would you insist on before supporting a data center near your community?

Sources

1. Reuters, Investors see risk from US midterms to AI trade as data center backlash builds, October 22, 2026. Read source

2. Office of the Ohio Consumers’ Counsel, Data Center Costs, PUCO case 24-0508-EL-ATA, update recording July 9, 2025 approval and a November 2025 appeal. OCC is the state residential-consumer advocate and a settlement supporter. Read source

3. AEP Ohio, AEP Ohio Proposal on Data Centers to Protect Ohio Consumers Adopted by PUCO, July 9, 2025. Utility’s account; used for its description of terms. Read source

4. City of St. Louis, City Approves Permit for Data Center Project, Announces Significant Conditions and Community Benefit Framework, April 21, 2026. City projections and announced conditions, not a compliance audit. Read source

5. First Alert 4, Benefits agreement approved for Armory data center, September 15, 2026. Reports the agreement’s job minimum and construction estimate; distinct from the earlier city development-wide projection. Read source

6. New York Post, St. Louis wants to build a $3 billion tech hub—but the data center anchoring it is sparking backlash, October 17, 2026. Used for reported litigation, not a conclusion about legal merits. Read source

7. Lawrence Berkeley National Laboratory, United States Data Center Energy Usage Report: 2025 Update, June 2026. Read source

8. U.S. Energy Information Administration, Prices and factors affecting prices. Read source

9. White House, Ratepayer Protection Pledge, March 4, 2026. Establishes announced commitments, not verified local compliance. Read source