In partnership with
⚡ THIS WEEK'S SIGNAL
Every state now agrees on the principle: when a data center shows up, the data center pays for the grid it demands — not the family down the road. About one-third of the data center energy bills enacted this biennium say exactly that. The catch is that no two states agree on what "pays" means or when it kicks in. The principle is settled. The mechanism is fifteen separate arguments. And that gap is the part investors can't price.
━━━━━━━━━━━━━━━━━━━━━━━
📰 MAIN STORY
State legislative sessions are wrapping up, and a clear trend leader has emerged in energy policy. About one-third of the data center energy bills enacted this cycle now carry ratepayer protection language — provisions requiring the facility to fully fund its own demand and the grid buildout that comes with it. MultiState pulled five of these laws side by side this month, and the useful thing isn't that they exist. It's that they don't match.
Look at what each player is actually optimizing for and the divergence makes sense. State legislators want the jobs and the tax base without a voter revolt over electric bills — so they want a cost wall, but one calibrated to their own politics. Operators want predictability they can underwrite across a multi-state pipeline. Utilities want to recover what they spend without eating stranded-asset risk if a facility downsizes or walks. Each state wrote the rule that served its own constituency first. Nobody coordinated, because nobody had a reason to.
Here's where it gets sharp. South Dakota's rules trip at 10 MW. Alabama's don't engage until 150 MW. That's a fifteen-fold spread on the same question. A facility large enough to be regulated as a major load in Sioux Falls is small enough to be effectively invisible one state line south. And on the cost side, Florida itemizes exactly what the operator owes — connection, incremental transmission, incremental generation, O&M — while Alabama just requires recovery of "all incremental service costs" and leaves the definition open. One state hands you the bill. The other hands you a lawsuit waiting to happen over what's on it.
The five, for the screenshot:
South Dakota (SB 135) — 10 MW threshold. Separate terms and conditions for data centers; recovers stranded costs if the facility departs or cuts load.
Nebraska (LB 1010) — 20 MW. Authorizes public power suppliers to negotiate rates — doesn't require it.
Tennessee (HB 1847) — 50 MW projected within three years. Standard utility ratemaking; bars the utility from absorbing infrastructure cost.
Florida (SB 484) — 50 MW, with co-location restrictions. PSC-established tariffs and an itemized cost list; nonpayment risk can't fall on the general ratepayer body.
Alabama (SB 270) — 150 MW. PSC contract-by-contract review; open-ended cost standard with a "benefit other retail customers" clause.
Two roads from here. Scenario A: 2027 sessions copy Florida — itemized cost categories, PSC tariffs — and compliance becomes something you can model state by state. Investors get a priceable patchwork, which is annoying but workable. Scenario B: more states land on Alabama's open-ended language, and the definition of "incremental cost" gets settled one contested PSC proceeding at a time. Then every large interconnection becomes a bespoke legal fight, and "who pays" stays unpriceable through the back half of the decade.
The one thing to watch: Alabama's first contract-by-contract review under SB 270. That proceeding is where "all incremental service costs" stops being a phrase and becomes a number — and it'll tell you which road the open-ended states are actually on.
━━━━━━━━━━━━━━━━━━━━━━━
The best prompt engineers aren't typing. They're talking.
Power users figured this out early: speaking a prompt gives you 10x more context in half the time. You include the edge cases, the examples, the tone you want — because talking is fast enough that you don't skip them.
Wispr Flow captures everything you say and turns it into clean, structured text for any AI tool. Speak messy. Get polished input. Paste into ChatGPT, Claude, Cursor, or wherever you work.
89% of messages sent with zero edits. 4x faster than typing. Works system-wide on Mac, Windows, and iPhone.
━━━━━━━━━━━━━━━━━━━━━━━
⚡ QUICK HITS
New England Asks for a Raise While Writing $1.5B in Refund Checks: Eversource, Avangrid and other New England transmission owners asked FERC on April 30 to lift their base ROE to 11.39% — six weeks after the agency cut it to 9.57% and ordered roughly $1.5 billion in refunds to ratepayers going back to 2011. The regional governors, including New Hampshire's Kelly Ayotte, have publicly urged FERC to reject it, which makes this the cleanest live test of who absorbs the cost of grid expansion: investors or customers. Utility Dive
Governors Stop Moderating: Illinois's Pritzker is pausing data center tax incentives July 1 and pushing for ratepayer and water protections in the fall veto session; Texas's Abbott sent the PUC a letter directing it to keep data center costs off residential bills ahead of the 2027 session. For years governors mostly vetoed restrictions — this is the posture flipping in real time, in both red and blue states. MultiState
The Biggest Grid Take-Private Hits a Speed Bump: AES shareholders filed two complaints to block the $33.4 billion sale to BlackRock's GIP and EQT, disclosed in a June 12 SEC filing, seeking more deal information before any vote. The transaction — expected to close late 2026 or early 2027 — is the marquee case of private capital buying utility-scale generation, and litigation is the first sign that shareholder consent may not be a formality. Power Technology
New York Could Be First to Hit Pause: A statewide data center construction moratorium has passed both houses of the New York legislature and is awaiting the governor's signature; if signed, it would be the first such moratorium to actually take effect, after Maine's passed but was vetoed. For developers, it's the difference between "states are talking about pausing" and "a major market just closed the door." TECHi
━━━━━━━━━━━━━━━━━━━━━━━
🔧 TOOL / RESOURCE OF THE WEEK
MultiState Policy Watch: Data Centers — a subscription tracker covering state data center legislation across energy, water, zoning, and tax. It's the cleanest way to watch the ratepayer-protection patchwork move bill-by-bill before it hardens into the compliance map your pipeline has to live inside. → multistate.us
━━━━━━━━━━━━━━━━━━━━━━━
💬 CLOSING THOUGHT
The "polluter pays" instinct has fully arrived in grid policy, just rebuilt as "the load pays." That's the easy part, and it's basically won. The hard part is that fifteen legislatures answered the same question without comparing notes, so a build that's clearly regulated in one state barely registers next door. If the cost definitions converge, this becomes underwritable. If they don't, every interconnection turns into its own negotiation. So I'm curious: in your state, does the threshold-and-cost debate happen before the first big project files, or only after the bills land? Because the order seems to decide everything.
