SB 1138 California Senate · 2025-2026 Regular Session

Load-serving entities: resource adequacy requirements.

Summary
Existing law vests the Public Utilities Commission with regulatory authority over public utilities, including electrical corporations. Existing law requires the commission, in consultation with the Independent System Operator, to establish resource adequacy requirements for all load-serving entities, as provided. Existing law defines load-serving entity, for that purpose, as an electrical corporation, electric service provider, or community choice aggregator. Existing law requires each load-serving entity to be subject to the same requirements for resource adequacy, the renewables portfolio standard program, and the integrated resource planning process that apply to electrical corporations, as provided. This bill would require the commission to authorize a load-serving entity to elect to demonstrate compliance with resource adequacy requirements by selling to, or otherwise making transactions with, another load-serving entity, and would require those transactions to not represent more than 25% of a load-serving entity's compliance obligations and be of a short-term duration. The bill would require the commission to authorize those transactions to be denominated in the same unit of time used to denominate resource adequacy compliance requirements. The bill would authorize the commission to suspend or adjust that authority of a load-serving entity to sell to, or otherwise make transactions with, another load-serving entity, as specified. Under existing law, a violation of the Public Utilities Act or any order, decision, rule, direction, demand, or requirement of the commission is a crime. Because the above provisions would be a part of the act, and because a violation of a commission action implementing the above prohibition would be a crime, the bill would impose a state-mandated local program. The California Constitution requires the state to reimburse local agencies and school districts for certain costs mandated by the state. Statutory provisions establish procedures for making that reimbursement. This bill would provide that no reimbursement is required by this act for a specified reason.
Bill status passed 3 of 5 stages cleared
Introduction
Feb 2026
Committee Review
Aug 2026
Senate Passage
May 2026
Assembly Passage
Governor
Introduced Feb 18, 2026 Last action Aug 13, 2026
Maddy AI version diff · 3 comparisons

What changed between versions

04/09/26 - Amended Senate 06/15/26 - Amended Assembly · 3 edits · Jun 15, 2026
MINOR
The Assembly amended SB 1138 primarily to refine the inter-entity transaction mechanism for resource adequacy compliance. The key change reframes the 25 percent cap provision so that a load-serving entity must affirmatively elect to use transactions with another load-serving entity, and clarifies that those transactions cannot represent more than 25 percent of the entity's total resource adequacy compliance obligation. The separate 'on a short-term basis' qualifier was removed, though contracts must still be of short-term duration.
REQUIREMENT

The inter-entity transaction option for meeting resource adequacy obligations is now framed as an election by the load-serving entity rather than something the commission simply permits. The language changed from 'permit a load-serving entity to demonstrate compliance' to 'authorize a load-serving entity to elect to demonstrate compliance.'

The 25 percent cap was restructured. Previously it read that an entity could meet 'not more than 25 percent of its compliance obligation, on a short-term basis.' Now it states that 'those transactions shall not represent more than 25 percent of a load-serving entity's resource adequacy compliance obligation.' The separate 'on a short-term basis' temporal qualifier was removed, but contracts must still be of short-term duration.

TECHNICAL

The word 'permit' was changed to 'authorize' throughout the provision, and minor grammatical cleanups were made (e.g., fixing a duplicated 'load serving load-serving' in the existing law summary).

Floor votes · Senate May 19, 2026

How they voted

310
Passed · 9 other
Total votes 40
May 19, 2026
D Democratic30
30 Yea
100% Yea
R Republican10
1 Yea 9
10% Yea
Vote distribution
All Yea All Nay Mixed No data
Full legislative history

Actions timeline

Total actions
20
Key actions
8
Committee
5
Amendments
4
Aug 13, 2026
Lower · Passed
August 13 hearing: Held in committee and under submission.
lower
Jun 15, 2026
Lower · Passed
Read second time and amended. Re-referred to Com. on APPR.
lower
Jun 11, 2026
Lower · Passed
From committee: Do pass as amended and re-refer to Com. on APPR. with recommendation: To consent calendar. (Ayes 18. Noes 0.) (June 10).
lower
May 26, 2026
Committee
Referred to Com. on U. & E.
lower
May 19, 2026
Upper · Passed
Read third time. Passed. (Ayes 31. Noes 0. Page 4347.) Ordered to the Assembly.
upper
May 14, 2026
Upper · Passed
From committee: Do pass. (Ayes 5. Noes 0. Page 4266.) (May 14).
upper
Apr 16, 2026
Upper · Passed
April 20 hearing postponed by committee.
upper
Apr 9, 2026
Upper · Passed
Read second time and amended. Re-referred to Com. on APPR.
upper
Apr 8, 2026
Upper · Passed
From committee: Do pass as amended and re-refer to Com. on APPR. (Ayes 13. Noes 0. Page 3756.) (April 7).
upper
Feb 26, 2026
Committee
Referred to Com. on E., U & C.
upper
Feb 18, 2026
Introduced
Introduced. Read first time. To Com. on RLS. for assignment. To print.
upper
1 primary · 4 co-sponsors

Sponsors