At almost every public hearing on a data center project, someone asks the question the room cares about most: what will this do to my electric bill?
It's a fair question, and the developer at the podium can only answer part of it. Utilities and the state commissions that regulate them largely decide the rates a household pays, the upgrades a grid needs and who covers the cost of those upgrades. Those parties are often absent from the local meeting where the question gets asked.
That leaves a gap no single party can close. As cost becomes the central question in community debates, closing it will take developers, utilities and communities working together.
A developer controls a great deal: the site, the design, the cooling system, the construction schedule and the commitments it makes to a community. What it doesn't control is the rate structure.
In most states, the commissions that oversee utilities approve the capital investments that serve new large loads and decide how those costs are allocated. Utilities forecast demand, plan transmission and propose the tariffs. Developers negotiate within those terms.
So when a resident asks about rate impacts, the developer can describe what it has agreed to pay. The rest, including how the utility will recover its costs, what other projects sit in the queue and what the next rate case will include, comes from the utility and its regulators.
Part of the difficulty is that the data doesn't settle the question. Large new loads can cut both ways. When a utility has spare capacity, added sales spread fixed costs across more usage and can lower rates; when it must build new generation or distribution, costs can rise. Researchers interviewed by NPR this month said there is no single, clean number; the effect depends on the scale of the upgrade and how a utility accounts for who uses it.
Communities are left sorting through competing claims. Some studies, such as one commissioned by Amazon, conclude that data centers cover their own power costs. Consumer advocates in other markets argue that residential customers are absorbing a share of new grid investment.
Both can be true in different places, under different rate structures. When the utility is in the room to walk through the math for that market, residents can see which situation applies to them.
The cost question increasingly has a written answer. Large-load tariffs are binding rate and service rules that set what large customers pay and the conditions under which they connect. As of May 2026, 23 states had approved at least one, with seven more pending.
The approaches vary. Oregon's new framework for facilities above 20 megawatts requires long-term contracts, customer-paid distribution upgrades and a surcharge for the largest projects. Pennsylvania's model tariff takes a "but-for" approach, assigning network upgrades to the new large customer that triggered them. These rules also shape behavior: after Ohio regulators approved AEP Ohio's large-load tariff, the utility's large-load forecast fell by half, a sign it filtered out speculative requests.
The problem is where these answers live: in regulatory dockets most residents will never read.
Without one of these parties in the public conversation, a few things tend to happen:
As we noted in The Site Selection Checklist Is Missing a Line Item, electricity cost is the largest driver of local opposition in current polling. A commitment that exists only between a developer and a utility doesn't reach the audience that most needs to hear it.
No single model fits every market, but the strongest examples share one trait: everyone who shapes the answer helps explain it. That can look like:
This is shared work. Utilities operate within rate cases, confidential customer contracts and regulatory processes. Developers balance commercial timelines. Communities have limited time and technical resources. When each brings what it can, residents get a conversation they can follow.
Smaller, distributed facilities in metro and suburban markets generally ask less of the grid than a gigawatt-scale campus. They represent a smaller share of a utility's forecast, are less likely to trigger major new transmission and can often draw on infrastructure that already serves dense commercial areas. That makes the cost story simpler to explain and easier to verify.
That is part of the logic behind RadiusDC's approach, and it's why we build coordination with utilities and local stakeholders into how we develop from day one.
A smaller load doesn't make the question go away. Every project, at any size, should be ready to show a community who pays for what, and who to ask when the answer sits outside the developer's control.
The industry has gotten better at talking about its own commitments. The next step is making sure the full answer is in the room when a resident asks what a project will cost them, with developers, utilities and regulators each contributing their part.
Communities aren't asking for perfect certainty. They want to understand how decisions get made and who makes them. When utilities, developers and communities work through that question together, the answer gets clearer and the projects built on it get stronger.
If you are interested in learning more about where RadiusDC is building or would like to chat with a member of our team, please visit www.radius-dc.com.
Jaymie Scotto & Associates (JSA)