California bills the 25MW load, draws the disclosure line at 10MW
Seven laws shift grid costs onto operators, put water use under oath, and trade the blanket environmental exemption for a fast lane that runs through engineering.
California has put a figure on what counts as a large data center, and that figure is 25 megawatts — the line above which Governor Gavin Newsom's seven signed bills shift the cost of serving the biggest facilities onto their operators, place the rest under new power and water reporting rules, and end the blanket environmental-review exemption the industry has used to move quickly through state approval.
The state's load growth has outrun the rules written to manage it, and the package is the legislature's attempt to close that distance. Three of the bills settle who pays, and all three bear on facilities with capacity of 25MW or more: SB 1168 requires data centers to absorb the cost of their own energy use and any utility infrastructure upgrades their demand requires; SB 886 directs the California Public Utilities Commission to write power rates for data centers that cover grid connection and electricity costs; AB 2383 carries the same cost-shifting principle as a companion measure.
Three others govern what the state gets to see: AB 1577 has the California Energy Commission build a registry of data center electric infrastructure costs, AB 2619 requires operators to report their water use under penalty of perjury, and AB 2469 attaches an estimate of water use to business license applications and renewals while making operators financially responsible for new infrastructure the load requires. The seventh, SB 887, withdraws data centers' eligibility for blanket environmental review exemptions and offers fast-tracked approval to facilities that meet state water and energy conservation standards.
The authorship is one-sided and the framing is national: Democratic members of the legislature authored every bill in the package, with AB 1577 coming from assemblymember Rebecca Bauer-Kahan of Orinda. Newsom set the laws against federal deregulation, saying California is “laying the groundwork for a stronger approach” and that “those profiting from data centers aren't doing so at our expense.”
A threshold moved twentyfold
The numbers that decide how much of this the industry actually feels sit in the disclosure bills, and one of them was rewritten in committee: the CEC reporting mandate excludes any facility with electrical capacity below 10MW, a threshold raised from 500kW — twenty times the original floor — while the rate classes begin at 25MW. A facility sitting between the two numbers falls inside the registry while escaping the new rate class, visible to the state and not yet priced by it. California wants eyes on the mid-market and has chosen to charge only the top of it, a rate design that reads as built for load able to carry an interconnection's full cost rather than for the smaller facilities the registry will now catalog.
The perjury requirement is the provision that changes behavior: a registry that operators populate under oath is a document a lender can lean on, while a voluntary sustainability report is not, and the gap between those two things is what separates a compliance regime from a communications exercise. AB 2469's placement at the business license counter follows the same instinct, giving counties a recurring checkpoint where the operator is already asking for something and making the disclosure a local filing rather than a statehouse formality.
As this publication noted when the package cleared, the laws hand counties leverage that capital used to route around. Consent is the product in every data center trade, and a scorecard regime makes performance disclosure the next permit — California has built the scorecard with an oath attached and a license renewal to keep it current. The numbers it produces may become the comparable that lenders and planners both reach for, the way an interconnection queue position already prices ahead of the electrons.
SB 887 makes the trade explicit: the blanket exemption goes, and facilities that meet the state's conservation standards get a faster path through review. Speed is now priced in engineering rather than in fees, which moves water and energy design out of community relations and onto the construction schedule. A project that misses the standards keeps its right to build, and the slower timeline that comes with it.
A statute that orders the commission to create a rate class is a promise; a rate schedule with a cost-allocation method and an effective date is a price.
Three rulebooks, one commission
All of it lands at the CPUC, which is already carrying two versions of the same question. SB 886 asks for a new customer class and the rate design to serve it, while the commission's general rate case plan — the framework last rewritten in 2007 — is being reopened with cost transparency, affordability and performance-linked compensation inside the docket where regulated returns get decided; the cost-shifting statutes say who should pay, and the rate case rewrite decides how the bill gets assembled and what a utility earns delivering it. AB 192, which puts state capital into CAISO-solicited transmission, adds a third track to the same set of wires, though its guidelines do not land until the end of 2027.
None of that settles whether the load gets built. A published cost allocation is more useful to an underwriter than an unquantified subsidy, and a water number an operator has sworn to is more workable than one a developer published itself, which is why the filing matters more than the charge. What cannot be modeled is a rulebook still being written, and California now has three in motion at once.
The rates themselves do not exist yet. A statute that orders the commission to create a rate class is a promise; a rate schedule with a cost-allocation method and an effective date is a price. The first tariff adopted under SB 886 will settle whether California's grid bill is large enough to move a siting decision or small enough to be absorbed, and every state with a strained queue that lifts the framework will lift that answer along with it.