AB 2266 requires the California Public Utilities Commission to bring consistency to resource valuation and compliance reporting across multiple electricity procurement programs so the state can meet short-, mid- and long‑term reliability goals more efficiently. The measure directs the CPUC to align capacity valuation methods used to set resource adequacy and procurement obligations and to consolidate compliance reporting for load‑serving entities, while also obligating the CPUC to explain when the Independent System Operator (CAISO) uses backstop procurement whether that need arose from noncompliance or methodological differences.
The bill is framed as a governance and coordination fix: it does not mandate a particular technical valuation method, but it does set deadlines and procedural rules designed to reduce duplicate processes, improve data quality, and position California to capture benefits from broader regional market participation. For practitioners, AB 2266 creates concrete rulemaking and compliance tasks for regulators and load‑serving entities and establishes a new transparency requirement tied to CAISO backstop actions.
At a Glance
What It Does
The bill requires the CPUC to use a single capacity valuation method for both resource adequacy and procurement obligations and to consolidate compliance reporting for programs under Sections 380, 399.15, and 454.52. It also requires that any compliance reporting requirement be finalized at least 20 calendar days before an LSE submits a report and mandates that the CPUC explain in its public report when CAISO exercises backstop procurement whether the cause was LSE noncompliance or methodological differences.
Who It Affects
The measure directly affects load‑serving entities — investor‑owned utilities, community choice aggregators, and electric service providers — plus the CPUC and CAISO; it also touches the State Energy Commission, developers of resources (storage, renewables, demand response), compliance teams, and ratepayers. Entities participating in or preparing for a regional energy market should take particular interest.
Why It Matters
Aligning valuation and consolidating reporting tackles overlapping regulatory processes that can inflate costs and slow decision‑making; it could materially change procurement outcomes and who bears reliability responsibility. The new CAISO backstop reporting requirement creates public accountability for whether procurement gaps reflect compliance failures or technical disagreements between agencies.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 2266 responds to a problem state lawmakers lay out in the findings: California accumulated multiple, overlapping electricity rules over decades, producing parallel compliance tracks, different resource valuation methods, and inconsistent signals for procurement and reliability. Rather than picking a technical standard, the bill tasks the CPUC with folding those parallel tracks into a single set of valuation and reporting practices so regulators and market participants operate from the same assumptions.
Practically, the bill creates two parallel workstreams at the CPUC. First, it must ensure that the capacity value — the metric used to measure how much a resource contributes to meeting demand — is the same when the commission sets both resource adequacy requirements and procurement obligations.
Second, the commission must initiate a consolidation of LSE compliance reporting for three statutory programs so LSEs submit coordinated information instead of multiple, potentially inconsistent reports. The bill adds a procedural rule that any compliance reporting requirement must be finalized at least 20 calendar days before LSE submission to reduce last‑minute changes and improve data quality.The bill also builds a transparency loop tied to CAISO’s backstop procurement.
If CAISO steps in to procure resources on a backstop basis in any year, the CPUC must explain publicly whether that intervention was driven by LSE noncompliance or by differences in how the commission and CAISO value resources. That requirement is designed to attribute causes publicly and to focus future corrections on either enforcement or methodological harmonization.Implementation will be a technical, interagency exercise: the CPUC will need rulemaking authority and likely workshops with CAISO and the Energy Commission to agree on modeling inputs, timing, reporting templates, and governance for ongoing alignment.
Load‑serving entities should expect new reporting templates, potential adjustments to procurement planning tools, and a transition timeline that culminates in alignment activities leading up to 2030. The statute preserves regulatory flexibility by stating the Legislature does not intend to prescribe a specific technical method, leaving the shape of the single valuation to agency processes.
The Five Things You Need to Know
On and after January 1, 2030, the CPUC must use the same capacity valuation method when setting resource adequacy and procurement obligations under Sections 380 and 454.52.
On or before January 1, 2030, the CPUC must initiate a process to consolidate compliance reporting for load‑serving entities covering Sections 380, 399.15, and 454.52 into a single reporting process.
Any compliance reporting requirement adopted by the CPUC must be finalized at least 20 calendar days before an LSE submits its compliance report.
If CAISO uses backstop procurement in a calendar year, the CPUC’s public report under Section 380 must explain whether the need for backstop procurement arose from LSE noncompliance or from methodological differences between the CPUC and CAISO.
The bill explicitly declines to prescribe a technical valuation method and ties the term “load‑serving entity” to the definition in Section 380.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Legislative findings and intent
This section sets out why the Legislature sees alignment as necessary: decades of successive programs produced parallel compliance systems, inconsistent resource valuation, and risks of costly backstop procurement. The findings frame the bill as a governance and coordination remedy to reduce legal and administrative burdens and to better position California for regional market participation, while warning that the Legislature does not want to mandate a specific technical method.
Single capacity valuation for RA and procurement
Subsection (a) directs the CPUC to apply the same capacity valuation method when it establishes resource adequacy and procurement obligations under Sections 380 and 454.52 starting January 1, 2030. Mechanically, this forces the commission to align modeling inputs, effective load‑carrying capability calculations, or any other valuation approach it uses across both short‑term RA settings and longer‑term procurement determinations so that the two regulatory tools operate on the same assumptions.
Consolidated compliance reporting and timing rule
Subsection (b) requires the CPUC to begin a process, by January 1, 2030, to merge compliance reporting for LSEs across Sections 380, 399.15, and 454.52 into one reporting process. It also imposes a procedural floor: the commission’s reporting requirements must be finalized no later than 20 calendar days before LSEs submit reports, a timing rule intended to limit last‑minute specification changes that could undermine data consistency.
CAISO backstop procurement accountability
Subsection (c) ties CPUC public reporting to CAISO operational actions. If CAISO exercises its backstop procurement authority in any calendar year, the CPUC must explain in its Section 380 public report whether that backstop was triggered by noncompliance by LSEs or by a mismatch in valuation methodology between the commission and CAISO. The mechanics require the CPUC to investigate causation and to make a public attribution of the reason for CAISO intervention.
Definition cross‑reference
Subsection (d) makes clear that the bill uses the existing statutory definition of “load‑serving entity” from Section 380, avoiding the need to redefine the class of regulated entities and ensuring the bill applies to the same set of utilities, community choice aggregators, and electric service providers already governed by that section.
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
- California ratepayers — By reducing duplicate compliance and inconsistent procurement signals, the bill aims to lower administrative and procurement inefficiencies that can translate into lower costs over time.
- Community Choice Aggregators (CCAs) — A single reporting template and aligned valuation reduce administrative duplication and clarify procurement expectations across programs, cutting compliance costs for CCAs that currently navigate multiple reporting regimes.
- Regulators and planners (CPUC, CAISO, CEC) — Shared valuation assumptions and consolidated reporting improve information symmetry, streamline decision‑making, and reduce the frequency of conflicting directives across agencies.
- Resource developers (storage, renewables, demand response) — Clearer, consistent capacity valuation reduces procurement uncertainty and helps developers better size and time projects for reliability markets and procurements.
Who Bears the Cost
- Load‑serving entities (investor‑owned utilities, CCAs, ESPs) — LSEs must revise internal valuation models, update procurement planning tools, and adapt compliance systems to a new consolidated reporting format, generating implementation costs.
- California Public Utilities Commission — The CPUC will absorb substantial rulemaking, interagency coordination, and IT/template development work to harmonize valuation and reporting; this may require additional staff time or budget.
- Independent System Operator (CAISO) — CAISO must engage in technical reconciliation and data sharing; if methodological alignment proves elusive, CAISO could face increased operational burdens and public scrutiny from required explanations.
- Ratepayers (contingent) — If harmonized valuation raises procurement obligations or prompts additional short‑term purchases, ratepayers could see higher near‑term costs even if long‑run efficiency improves.
Key Issues
The Core Tension
The core dilemma is efficiency versus fidelity: AB 2266 seeks efficiency by forcing agencies and market participants to operate from a single valuation and reporting framework, but that same consolidation risks obscuring meaningful technical differences among resources and shifting difficult modeling trade‑offs into a high‑stakes administrative process.
The bill trades duplication for uniformity, but uniformity is not the same as correctness. Different resource types (utility‑scale renewables, distributed solar, batteries, demand response, and imports) contribute to reliability in materially different ways; a single valuation approach that smooths those differences risks overvaluing some resources and undervaluing others unless the CPUC’s method preserves resource‑specific characteristics.
The statute's refusal to prescribe a technical method helps politically and technically, but it leaves the hardest choices to CPUC rulemaking, where stakeholder disputes over modeling inputs, coincidence metrics, and effective load‑carrying capability will be intense.
Operationally, consolidating reporting can improve data reconciliation, but it creates questions about which metrics survive. Program‑specific indicators that informed past policy choices (for example, distinct metrics for distributed resources versus generation) could be lost or deemphasized in a single template.
The 20‑day finalization requirement improves stability but could constrain rapid fixes to reporting mistakes or inhibit iterative improvements, particularly in a transition period. The CAISO backstop explanation requirement increases transparency, but it also elevates political and legal stakes: a finding of noncompliance could trigger enforcement action, while a finding of methodological difference could provoke disputes about jurisdiction, modeling assumptions, and retrospective attribution.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.