On October 15, Governor Josh Shapiro petitioned the Pennsylvania Public Utility Commission for formal party status in the Office of Consumer Advocate’s complaint against PPL Electric Utilities, docket C-2026-3065756. He announced the move the next day. His office says no governor has intervened in a PUC proceeding in at least 15 years, and the timing is not subtle: the announcement landed 18 days before the November 3 election, in a state where data center growth has become an affordability issue.
It is worth being precise about what the petition is, because the politics around it invite overstatement. A petition to intervene is a request to participate, not a ruling. If granted, it would let the administration present evidence, make legal arguments, and take part directly in the case. It changes no one’s bill by itself. What it does is put the governor’s office inside the room where Pennsylvania’s cost-allocation rules for large loads will be argued — and it converts an executive order into a litigation position.
What the complaint asks for
The case began on October 2, when the Office of Consumer Advocate (OCA) filed a formal complaint under section 1309 of the Public Utility Code, alleging that PPL Electric’s existing tariff rates, rules, and service are unjust, unreasonable, and unduly discriminatory because they leave existing customers paying costs caused by large data centers and exposed to service interruptions when data center demand outruns supply. The complaint runs to hundreds of pages with expert affidavits attached.
The relief OCA seeks is the most complete version of cost-causer-pays yet put before a state commission. It asks the Commission to direct PPL to establish new rate and service classifications for large data centers; to adopt tariff provisions ensuring data centers pay for all transmission network upgrade costs they cause, as well as costs associated with PJM’s Reliability Backstop Procurement and Interim Resource Adequacy Service; to require large data centers to take interruptible rates; and to adopt interconnection and load-shedding tariff provisions that protect existing customers from reliability risks created by integrating large data centers into PPL’s system.
Each element answers a different failure mode this desk has tracked. The separate class is the structural fix: a customer class of its own means data center costs can be assigned to data centers rather than spread across the classes that happen to share a tariff. The transmission provision is the but-for rule in its strongest form — all upgrade costs the load causes, not a share. The interruptible rates and load-shedding provisions answer the reliability side: when supply is short, the customer whose demand created the strain is the one curtailed first, rather than existing customers losing service.
There is a wrinkle in the complaint’s cost list worth noting. The complaint was filed on October 2, a week before FERC rejected PJM’s Interim Resource Adequacy Service proposal on October 9 on jurisdictional grounds. The IRAS ask now attaches to a program FERC has rejected, while the backstop procurement it was meant to accompany remains suspended pending a paper hearing on cost allocation. That does not moot the complaint — the transmission and class-structure asks stand on their own — but expect the parties to litigate what, if anything, the IRAS language covers going forward.
The 31.8 gigawatts
The scale of what is at stake comes from PPL itself. On its second-quarter 2026 earnings call, PPL Corporation told investors its Pennsylvania data center pipeline in advanced stages had reached 31.8 GW: more than 11 GW under signed electric service agreements, more than 6.5 GW under construction, and two data centers that began taking service during the quarter, on track for roughly 2 GW of load by 2031.
Read those numbers the way a regulator would. Only about a fifth of the advanced-stage pipeline is actually being built. The rest is signed or in earlier stages — real demand signals, but not yet load, and not yet the committed customers a cost-allocation regime can bill. That gap between pipeline and construction is precisely the exposure the complaint is about: the wires sized for 31.8 GW get planned before most of the load arrives, and who carries the cost while the pipeline converts — or fails to — is decided now, not when the facilities energize.
It is also the reason the case matters beyond PPL’s territory. PPL’s capital spending ran $2.34 billion in the first half of 2026 against $1.72 billion a year earlier, and the company has pointed to $10 billion to $12 billion of generation investment across Pennsylvania and Kentucky through 2032 as an opportunity it estimates, not committed spend. What PPL commits to wires and plants enters its regulated rate base, and this case decides who pays the return on it.
Why the governor is in the room
Shapiro’s petition rests on two interests, and both are worth stating plainly. The first is the public interest: the administration argues that existing PPL customers should not bear the costs or reliability risks of data center growth. The second is direct and concrete: Commonwealth agencies are themselves PPL customers and major consumers of electricity, giving the administration a direct financial interest in the outcome alongside its broader responsibility. The petition notes that the Commonwealth Court has long recognized the Commonwealth’s interest in participating in rate cases as a substantial consumer of utility service.
The petition also states that the intervention is timely, filed within the period allowed by 52 Pa. Code § 5.74, and that the governor will take the proceeding as it stands and accept the schedule set by the Commission or its administrative law judge — a pledge not to delay or prejudice any current party.
And the case is moving. The docket already shows a petition to intervene from CAUSE-PA, filed October 7; PPL’s motion for an extension of time, filed October 9; appearances by counsel for both sides; a prehearing conference order dated October 20; notice of an amended complaint the same day; and an extension order dated October 21. The Commission has not yet, on the public docket, ruled on the governor’s petition — but the procedural machinery is running, and the governor’s team will have to argue its way in like any other intervenor.
From executive order to docket
The petition is the litigation arm of a policy the administration announced in August. Executive Order 2026-05, Protecting Pennsylvanians from Data Center Impacts, formalized the Governor’s Responsible Infrastructure Development (GRID) Requirements, which the administration describes as the strictest data center requirements in the nation. Under those requirements, developers must pay the full cost of the new generation, transmission, distribution, and other infrastructure needed to power their projects. The order specifically directed the governor’s Special Counsel for Energy Affordability to engage with the PUC to prevent cost shifting, to develop protocols prioritizing data center curtailment when the grid is stressed, and to push for data centers to pay costs associated with PJM reliability backstop auctions.
An executive order, however, does not bind a commission, and a voluntary framework binds no developer. As of mid-September, reporting indicated no developer had signed a GRID agreement. The petition gives the order something it lacked: a venue where its principles can be argued as law, before the body that actually sets PPL’s rates.
There is a complication the administration cannot sidestep, and fairness requires stating it. Shapiro’s own team courted this boom. In June 2025 the administration announced a $20 billion Amazon investment in AI infrastructure in Pennsylvania, saying it had worked closely with local leaders and Amazon to land the deal. The governor is now asking a commission to police the costs of a buildout his administration helped recruit. Recruiting investment and regulating its costs are different jobs, and a state can do both — but it is the reason the petition reads as both policy and politics.
PPL’s answer: the tariff already does this
PPL, notably, did not fight the petition. The company issued a public response the same day welcoming the governor’s focus on shielding customers, saying it is “committed to protecting customers, maintaining reliability and ensuring that large-load customers pay the costs associated with their projects.” That is a welcoming statement, not a concession — PPL’s position is that its existing framework already delivers what the governor and OCA are asking for.
The centerpiece of that framework is PPL’s large-load tariff, Rate LP-6, which the company describes as Pennsylvania’s only PUC-approved large-load tariff, with long-term service agreements, minimum usage commitments, upfront payments for certain upgrades, financial security, and exit-fee protections. In a separate September 14 petition, PPL asked the Commission to approve a Customer Protection Transmission Rider moving transmission costs it would not have incurred without large-load connections onto LP-6 customers, with Commission consideration requested for June 10, 2027 and implementation targeted for the first quarter of 2028.
OCA is not satisfied with that answer. On October 6, it filed an answer to the rider proposal asking the Commission to send it to an administrative law judge for full evidentiary proceedings, questioning whether the proposal adequately protects shopping customers from paying transmission costs twice — once through the new rider and again through existing supplier contracts that already include network transmission charges — and whether the targeted first-quarter 2028 implementation leaves suppliers enough time to revise contracts and disclosures. The OCA also questioned whether the rider adequately assigns data center costs to the customers causing them and treats potential future PJM reliability costs.
So the docket now holds two competing architectures for the same problem. PPL’s: a large-load tariff plus a rider that moves specific transmission costs onto LP-6 customers, phased in over more than a year. OCA’s, now backed by the governor: a separate customer class, full assignment of all caused transmission costs, interruptible service, and load-shedding protections, imposed by Commission order. The governor’s presence as a party does not decide that question — but it raises the political cost of answering it the way PPL prefers.
The state-level test of a national fight
For readers of this desk, this case is the state-level test of the fight we have followed from Congress to FERC. The Senate report released October 9 found that all seven data center companies it questioned rejected the but-for standard for shared grid upgrades — and it specifically cited the Pennsylvania consumer advocate’s recommendation that a large-load customer that is the but-for cause of upgrades bear 100 percent of those costs. Now that recommendation is a live complaint, and the governor of the state has joined it. The report’s evidence is becoming a docket’s argument.
The federal track runs in parallel. FERC’s June 18 Section 206 proceedings, one per regional operator, preliminarily found each tariff lacking adequate large-load provisions and directed operators to address cost shifting, among other subjects. American Transmission Company’s October 22 FERC filing — construction-phase and minimum-charge mechanisms for large loads — is the transmission-side counterpart to what OCA is asking for at retail. The two tracks answer different halves of the same question: FERC governs the transmission tariff, the PUC governs the retail class structure and service rules.
That is why the Pennsylvania case is a test, not just a proceeding. If the Commission adopts OCA’s class structure and full-assignment rule, it will be the strongest state-level endorsement of cost-causer-pays yet — a template other commissions can cite, and a precedent developers will have to price into every Pennsylvania project. If it instead accepts PPL’s tariff-plus-rider framework as sufficient, it will signal that the existing tools, properly enforced, are the settlement.
What to watch
Five things will determine what this case becomes. The first is the intervention ruling itself: whether the Commission grants the governor full party status, and on what terms. The second is the prehearing process now underway — the amended complaint, the extension order, and whatever schedule the administrative law judge sets will fix the case’s tempo, and tempo matters when a pipeline is converting to construction quarter by quarter.
The third is the rider docket. The Customer Protection Transmission Rider and the complaint are now two tracks addressing overlapping costs; how the Commission sequences them — and whether the rider’s double-payment questions get a full hearing — will shape whether PPL’s framework survives as the settlement or gets absorbed into the complaint’s broader order.
The fourth is PPL’s November 6 business plan update, where the next pipeline disclosure will show whether the 31.8 GW figure is growing, converting to construction, or stalling. The share under construction is the number that turns an abstract cost-allocation principle into a dollar figure on someone’s bill.
The fifth is the election. Shapiro stands for re-election on November 3, and the petition’s timing guarantees it will be read as a campaign document as well as a legal one. That reading is not wrong — affordability is central to the campaign — but it is incomplete. Campaigns end; dockets do not.
Sources: Governor Josh Shapiro, petition to intervene, PUC docket C-2026-3065756 (filed Oct. 15, 2026, pa.gov); Governor’s Office, “Gov. Shapiro Protects Customers and Holds Data Center Developers Accountable” (Oct. 16, 2026, pa.gov); Pennsylvania PUC docket C-2026-3065756 (complaint filed Oct. 2, 2026; prehearing conference order Oct. 20, 2026; extension order Oct. 21, 2026); Office of Consumer Advocate, formal complaint against PPL Electric Utilities (Oct. 2, 2026, oca.pa.gov); PPL Electric Utilities response to the governor’s petition (Oct. 16, 2026); OCA answer on PPL’s Customer Protection Transmission Rider (Oct. 6, 2026); prior Fracmoo coverage: “The But-For Fight Goes to Congress” (Oct. 17, 2026), “The Transmission Side of But-For” (Oct. 23, 2026).