Seven new California laws turn the data center permit into a contract

Gov. Gavin Newsom signed seven bills into law on Monday that change what a data center has to prove before California lets it be built: what it pays toward grid upgrades, what it discloses about energy and water, and whether it can still claim a blanket environmental exemption on its way through review. The governor's office describes the package as requiring data centers to pay their fair share of grid update costs, report water use to local governments, and give up eligibility for those exemptions, with energy, water, workforce and land use made visible so communities can weigh a project's costs and benefits rather than absorb them. Newsom put the intent plainly: communities, he said in a statement, are left dealing with higher electricity demand, grid constraints, water use and pollution, and Californians should remain in the driver's seat.

SB 886 and SB 887 carry the cost side. Data centers must pay all infrastructure upgrade and generation costs, take on a larger share of wildfire mitigation and liability costs, and submit to environmental review; the bills' sponsor, state Sen. Steve Padilla, said in a news release that they rank among the strongest data center ratepayer protections in the country and will ensure local communities have a say in projects. SB 1168 routes the same question into a regulatory proceeding, directing the California Public Utilities Commission to examine data centers' energy use and to make sure they pay for transmission and distribution upgrades and load increases. State Sen. Jerry McNerney, the bill's sponsor, put the ratepayer worry bluntly: "Californians' utility bills are already among the highest in the nation, and the rapid growth of data centers is threatening to send rates through the roof."

AB 1577 supplies the measurement instead of the bill, requiring monthly reports of a data center's energy consumption and efficiency metrics to the California Energy Commission and estimated energy usage to local agencies as part of permitting. AB 2383 rewards developers that run clean generation on site, which Assemblyman Rick Chavez Zbur described as a way for the state to plan responsibly for its grid while keeping electricity costs down for consumers. AB 2469 and AB 2619 tighten oversight of data center water use.

Los Angeles County's planning director had already imposed a temporary ban on development of large-scale AI data centers in unincorporated areas, according to multiple news reports—the county-level version of the leverage SB 886 and SB 887 have now written into state law, and a display of what local say looks like when exercised by a planning department rather than a state commission. California holds 296 data centers, the third-highest count in the U.S. according to Data Center Map, and the counties hosting them now have both a documented basis for argument and the paperwork to press it.

Last week this publication covered the laws' cost side—that they put transmission, generation and wildfire-liability costs on developers and made monthly energy reporting a permitting condition—and today's coverage fills in the consent machinery that sits on top of it. Delaware got there first in August, requiring hyperscale developers to bring their own clean power, fund grid upgrades and forgo job-creation tax credits, a model we judged likely to be copied. California has copied it and gone further. The case for reading the permit as the scarce asset is not new here either: Digital Realty's Ankara joint venture rested on the argument that in a new market the scarce input is a partner who has cleared ground, power and permits, and California has now made that argument in its home market, where the counterparty is a county planning department.

Reading AB 1577 as compliance overhead would be the expensive error. Monthly energy and efficiency filings are the raw material of rate design, since a load class for large customers cannot be built without knowing what those customers draw, and the commission that SB 1168 sends looking for data center energy consumption now has a stream of filings arriving every month. The bills hand Sacramento the instruments to price the load, not merely to bill it. A developer that builds metering, water accounting and on-site generation into the design goes through the process with a record; one that treats the package as litigation risk goes through it with an adversary. AB 1577's monthly filing may become California's load-class docket in all but name long before any formal rate case concludes.

AB 2383 is the one provision that cuts against the cost narrative. On-site clean generation is the single lever that reduces the local costs cities are objecting to, which suggests the state is trying to relocate the buildout inside the fence line rather than stop it. If that read holds, California's growth concentrates in projects that can carry their own generation and publish what they consume, while marginal projects that need the grid's help and the community's goodwill go looking for a friendlier interconnection queue. Consent keeps setting the terms of these trades, and the seven bills make the scorecard part of the permit—exactly where the scorecard argument has always pointed.

The CPUC proceeding under SB 1168 will decide the split between developer and ratepayer; whether Los Angeles County's temporary pause in unincorporated areas is extended is the other variable. A county-level hold with no statutory clock attached is the hardest version of this policy for a developer to plan around, and it was in place before any of Monday's bills were signed.