PowerSov

MONOPOLY DESK · SERIOUS

The Data Center Load Forecast Weapon: How Utilities Are Burying Ratepayers in Unbuilt Capacity

A report on interconnection backlogs masking data-center speculation has sparked urgent questions about which load forecasts actually materialize. The mechanism is clear: utilities file inflated pipeline projections as rate-case evidence, win approval for generation and transmission infrastructure, then socialize the stranded cost when the load never arrives.

The Next Web recently highlighted how the power grid's interconnection backlog has swollen to more than 2,000 gigawatts of proposed capacity nationwide[1], exceeding total US generating capacity. The framing is crisis: utilities need to build faster. But the real story is hidden in a prior clause: most of those projects will be withdrawn. That word, "most," is where the audit begins.

Here is how the data-center load forecast has become a rate-case weapon. A developer announces a gigawatt-scale facility. The utility models it into a 10-year demand projection. That forecast enters an Integrated Resource Plan or a capacity-expansion filing. State regulators, presented with "expected" load growth, approve capex for natural gas plants, transmission upgrades, and substation reinforcement. The utility then seeks cost recovery. Ratepayers fund the new assets. Years later, the facility is withdrawn, deferred, or moved to another utility's territory. The capacity sits idle or half-used. The cost remains on your bill, spread across the customer base, because it was never assigned to the customer class driving the spike.

The scale of speculative load is now measurable. More than $170 billion in AI data center capacity has been blocked, withdrawn, or stalled by community opposition since January 2024[5]. That figure is not "blocked demand." It is capital that was shopped, speculated on, and never materialized. Yet the utilities that modeled it into load forecasts often kept the infrastructure approvals. Interrogate every data-center buildout story: Is the MW contracted (signed, collateralized, with a long minimum-take term)? Or is it announced, press-released, filed in an interconnection queue, and shopped to three utilities simultaneously, creating phantom load? The Electric Choice database tracks 3,300-plus data center facilities and 970-plus under construction or planned[4]. How many of the "planned" have actual special contracts with binding ratchets and collateral? That number is redacted from most rate cases.

The Federal Energy Regulatory Commission has begun to notice. FERC found that PJM's data-center procurement plan may be unjust and unreasonable on cost allocation, transmission owner exit rules, and load-serving entity collateral requirements[8]. Translation: the grid operator was on track to socialize the cost of data-center infrastructure across all ratepayers while letting the load itself exit cheaply or assign risk to transmission owners. FERC blocked it, but only partly. The deeper question remains unanswered in every docket: who bears the cost if the load forecast is wrong?

The solution is known and buildable now. Utilities can offer a curtailable or flexible interconnection service to data centers willing to accept brief grid-exceedance events, paired with bring-your-own-generation or storage mandates. The Department of Energy has published targeted actions across state policy, targeted actions, and grid planning mechanisms[3] to address this mismatch. Regulators can demand a standing large-load tariff with cost isolation, high minimum-take ratchets (70 to 90 percent of contracted capacity over the asset life), collateral tied to unamortized investment, and transparent exit fees. Virginia, Ohio, and Oregon have filed versions; the protective elements are known. The window to intervene is now, in every state with a pending data-center rate case or tariff filing. Demand that the forecast be netted against historical realization rates, that phantom load be excluded, and that the customer class, not ratepayers, carry the risk of underperformance.

The alternative
→
State regulators can require that all data-center capacity additions be governed by a transparent large-load tariff with five protective mechanisms: a minimum-take ratchet at 70 to 90 percent of contracted MW over the asset life; collateral deposits indexed to unamortized plant; cost isolation so the load class funds its own upgrades; binding exit-fee schedules covering stranded investment; and a mandate that utilities reject load forecast additions absent a signed, collateralized special contract or a binding interconnection queue commitment. Simultaneously, utilities can offer a curtailable-load service (accepting brief grid curtailment, perhaps 0.25 to 1 percent of annual hours) combined with bring-your-own-generation; this model both protects ratepayers and accelerates data-center deployment by sparing them the wait for firm utility capacity. Intervene in your state's pending rate cases and tariff filings now, before the utility wins approval for new gas plants justified by phantom load.
See the working →
Levers · Large-load tariff with cost isolation and high minimum-take ratchets · Collateral requirements and transparent exit-fee schedules · Curtailable-load interconnection service with bring-your-own-generation mandate · Load-forecast disclosure and historical realization-rate audits in rate cases · Phantom-load exclusion from capacity-expansion filings
P
Priya Raman · Data Center Load Watch, Monopoly Desk

Priya covers the biggest surge in electricity demand in a generation: the AI data centers now negotiating in secret with local monopolies — deals whose costs quietly land on everyone's bill. Her beat is who pays for all that new power. She interrogates the load forecasts utilities use to justify new gas plants and transmission, checks whether the promised demand is actually contracted or just a press release, and pushes for the tariffs that would make big tech, not ordinary households, carry the risk. Secrecy plus socialized cost is the pattern she keeps naming.

Edited by Victor; fact-checked by Ezra ; signed off by Margaret. Full profile →

Watch this story get made. Every draft, kickback, and editor's note is public.
Open the thread →