SB 1219 adds a new Section 384.6 to the California Public Utilities Code that creates a clear, expedited process for investor‑owned electrical and gas corporations to seek CPUC approval to discontinue administration of energy‑efficiency programs or whole portfolios when those programs fail specified performance tests. The bill directs the commission to act within a set timeline and anchors discontinuance authority in three statutory criteria.
This matters because the proposal shortens the path to closing rate‑funded programs and embeds a presumption that poorly performing programs should be allowed to end. That changes the balance between long‑running, ratepayer‑funded public purpose programs and utility discretion, with consequences for program implementers, ratepayers, CPUC workload, and long‑term resource planning.
At a Glance
What It Does
The bill adds Section 384.6, which requires the California Public Utilities Commission to consider and approve an electrical or gas corporation’s application to discontinue administration of an energy‑efficiency program or an energy‑efficiency portfolio within 180 days of filing if the utility demonstrates one of three statutory grounds: lack of cost‑effectiveness under PUC metrics, lack of reliability, or (for electrical corporations) that the program is not being used to meet unmet needs in the utility’s integrated resource planning (IRP) framework.
Who It Affects
Directly affected parties are investor‑owned electrical and gas corporations that run rate‑funded efficiency programs, third‑party program implementers and contractors paid from those programs, and CPUC staff who must process and decide applications on a compressed schedule. Indirectly affected are ratepayers who fund these programs and agencies that administer complementary local or low‑income initiatives.
Why It Matters
By codifying an expedited discontinuance route, the bill can accelerate program closures and reallocate ratepayer funds away from programs the utility deems ineffective. It also tightens the link between IRP outcomes and energy‑efficiency administration for electrical utilities, potentially changing how utilities prioritize efficiency in resource planning.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 1219 creates a statutory mechanism for utilities to stop administering energy‑efficiency programs more quickly than under current practice. A utility files an application with the CPUC asking to discontinue administration of a named program or an entire efficiency portfolio; the commission then has a fixed window in which to act.
The petition route is not open‑ended — the utility must show one of the bill’s three reasons for discontinuance.
The bill’s three reasons are stated at a statutory level rather than by listing technical tests. It refers to “cost‑efficiency metrics commonly utilized by the Public Utilities Commission,” which means the agency will rely on its existing measurement tools to judge whether a program’s benefits justify its costs.
For reliability, the statute defines a shortfall standard: a portfolio is “not reliable” if its forecasted cost‑effectiveness or total system benefits falls materially below forecast for at least two years within a four‑year cycle. For electrical corporations, there is an additional practical test tied to integrated resource planning: if the program is not being used to meet identified unmet resource needs in the utility’s IRP, that supports discontinuance.Practically, approval within the bill’s deadline would allow a utility to stop administering a program (which can mean stopping new enrollments, winding down implementation, and reallocating staff or funds).
The bill also carries an unusual enforcement and fiscal footprint: the legislative digest states that a violation of a commission order implementing this provision would be a crime, which triggers state‑mandated local program considerations; the bill then contains an express statutory finding about reimbursement that points to criminal‑penalty‑related costs as the reason no state reimbursement is required. That raises prosecutorial and local‑agency cost questions not addressed in the operative text.In short, the statute swaps a slower, arguably more deliberative closure process for a compressed, utility‑initiated track that ties discontinuance to familiar PUC measurement tools, forecast performance in multi‑year cycles, and IRP alignment for electrical utilities.
The operational details—what evidence satisfies the tests, how the CPUC weighs competing public‑interest goals, and how ongoing contracts or low‑income services are handled—will be resolved in practice during CPUC implementation and casework.
The Five Things You Need to Know
SB 1219 adds Section 384.6 to the Public Utilities Code to create the new discontinuance pathway.
The commission must consider and approve a utility’s application to discontinue administration of an efficiency program or portfolio no later than 180 days after filing.
The bill lists three statutory grounds for discontinuance: (a) the program is not cost‑effective under PUC metrics, (b) the program is “not reliable” under a multi‑year forecast shortfall test, and (c) for electrical corporations only, the program is not being used to meet unmet IRP resource needs.
The statute defines “not reliable” as a forecasted cost‑effectiveness or total system benefits result that falls significantly under forecast for at least two years within a four‑year cycle.
Section 2 of the bill says no state reimbursement is required under Article XIII B, explaining that any local costs arise from changes related to crimes or infractions tied to enforcement of commission orders.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Establishes a fast‑track discontinuance process
This provision is the core of SB 1219. It directs the CPUC to consider and approve applications from electrical or gas corporations that request to stop administering an energy‑efficiency program or an entire portfolio. The statute frames the process as consistent with existing chapter timelines for consolidation or closure of other programs, signaling the legislature’s intent to treat discontinuances as an administrative rather than purely policy deliberation. For practitioners, the practical effect is an expedited docket and a statutory expectation that the commission will not indefinitely delay utility closure requests.
Cost‑effectiveness ground
Subsection (a) lets a utility seek discontinuance if the program is “not cost effective in accordance with cost‑efficiency metrics commonly utilized by the Public Utilities Commission.” That language imports the CPUC’s existing analytical framework without enumerating tests in the statute, meaning the commission will apply its standard metrics (and any established tests or avoided‑cost assumptions) when weighing an application. For compliance officers and evaluators, the key takeaway is that cost‑effectiveness analyses and underlying assumptions will be central evidence in any discontinuance filing.
Reliability ground with multi‑year shortfall standard
Subsection (b) defines “not reliable” by reference to forecast performance: a portfolio qualifies if its forecasted cost‑effectiveness or aggregate system benefits fall materially below forecast for at least two years within a four‑year cycle. That is a concrete, time‑based trigger meant to prevent one‑off poor years from forcing closure while still allowing sustained underperformance to warrant discontinuance. The provision creates a measurable standard but leaves key terms—what constitutes a material shortfall or how forecast variability is normalized—for the CPUC to clarify in implementation.
IRP alignment for electrical corporations
Subsection (c) gives electrical corporations an additional, planning‑based ground: if the program is not being used to meet unmet resource needs in the utility’s integrated resource plan, the utility can justify discontinuance. This links energy‑efficiency program continuation to utility resource planning choices, effectively requiring programs to demonstrate operational value within a utility’s IRP portfolio to survive.
Reimbursement and criminal‑penalty framing
Section 2 addresses state reimbursement under Article XIII B and explicitly states no reimbursement is required because any local costs would stem from the bill’s creation or modification of crimes/infractions, citing Government Code Section 17556. The legislative digest also asserts that violating a commission order implementing this law would be a crime. That combination flags enforcement and local‑government cost issues as part of the statute’s implementation footprint even though the operative text does not create a new criminal sanction itself.
This bill is one of many.
Codify tracks hundreds of bills on Energy across all five countries.
Explore Energy in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Investor‑owned electrical and gas corporations: The bill gives utilities a predictable, expedited regulatory pathway to stop administering programs they judge to be underperforming, reducing the regulatory uncertainty and delay that can accompany program closures.
- Ratepayer oversight groups focused on eliminating waste: Advocates who prioritize removing inefficient rate‑funded spending can use the statute’s grounds and timelines to push for faster program rationalization and reallocation of funds.
- CPU C decision‑makers seeking clearer statutory direction: Commissioners and staff gain a statutory deadline and criteria that can streamline docket management and reduce prolonged litigation over whether a program should remain administratively active.
- Utility planning teams: By linking one discontinuance ground to IRP use, the bill creates a clearer operational incentive for planning staff to either integrate efficiency into resource portfolios or justify program termination.
Who Bears the Cost
- Program implementers and contractors: Third‑party vendors and local administrators stand to lose ongoing contracts and revenue streams if programs are closed under the expedited process, and may face abrupt wind‑downs or termination costs.
- Low‑income and targeted program beneficiaries: When a rate‑funded program is discontinued, services that reached low‑income households or vulnerable groups could be curtailed unless replaced or preserved by other funding sources.
- CPUC staff and case teams: The commission must process discontinuance filings within 180 days, creating a compressed review workload that can strain staff resources and evidence‑gathering capacity.
- Local agencies, law enforcement, and prosecutors: The bill’s legislative findings about criminal enforcement and the fiscal clause imply potential enforcement activity tied to commission orders; that can impose prosecution and court costs on local entities even though the statute itself avoids an explicit funding obligation.
Key Issues
The Core Tension
The bill forces a trade‑off between quickly removing inefficient, rate‑funded programs (protecting ratepayers from continued spending on poor performers) and preserving the public‑policy role of energy‑efficiency programs that produce long‑term or non‑market benefits; compressed timelines and ambiguous statutory tests lean toward expediency and utility discretion, but that efficiency can come at the cost of careful evaluation, stakeholder input, and protection for programs serving harder‑to‑measure public interests.
Two implementation risks stand out. First, the statute relies on catch‑all language—“cost‑efficiency metrics commonly utilized by the Public Utilities Commission” and a “significant” shortfall standard—without defining evidentiary thresholds, burdens of proof, or remediating processes.
That vagueness hands substantial discretion to the CPUC in interpreting the tests and opens the door to litigation over methodology (for example, disputed avoided‑cost assumptions or attribution of savings). Second, the 180‑day approval window compresses technical review, dispute resolution, and stakeholder consultation into a short timeline; that can lead to procedural shortcuts, higher contestation over the sufficiency of evidence, or decisions that prioritize speed over robust analysis.
A separate but related tension concerns enforcement and fiscal consequences. The legislative digest’s assertion that violating a commission order implementing this provision would be a crime changes the stakes for utilities and local actors, but the operative text does not set out a new criminal statute.
That mismatch raises questions about how enforcement would work in practice, whether prosecutions would be likely, and which local agencies would carry fiscal burdens for criminal enforcement. Finally, tying program continuation to IRP alignment risks sidelining programs whose benefits are long‑term, diffuse, or sectoral (for example, market‑transformation pilots) that may not register as meeting near‑term IRP unmet needs yet still serve public policy goals.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.