AB 1761 adds Section 365.4 to the California Public Utilities Code and directs the California Public Utilities Commission (CPUC) to ensure that the data underpinning any calculation methodology used to set charges for customers of load‑serving entities is available to load‑serving entities and to ratepayer advocates. The bill targets calculations used to recover the cost or value of contracts or resources owned by an electrical corporation.
The change centralizes transparency: it forces the disclosure of underlying inputs and models so those who pay the charges or represent them can review the basis for valuations and allocations. The bill also contemplates confidentiality procedures for truly market‑sensitive information and allows parties to agree on data‑sharing practices at the start of a proceeding.
At a Glance
What It Does
The bill requires that all data relied on in any decision, ruling, proposal, or analysis that supports a calculation methodology for charges to recover costs or value of electrical‑corporation‑owned contracts or resources be provided to load‑serving entities and ratepayer advocates. It mandates public disclosure where possible and permits limited disclosure of market‑sensitive data to a nonmarket participant reviewing representative under a commission‑approved nondisclosure agreement.
Who It Affects
Directly affected parties include investor‑owned electrical corporations that own contracts or resources, load‑serving entities (LSEs) that pay or allocate those charges, CPUC staff and commissioners who adjudicate values, and ratepayer advocacy organizations that review filings on behalf of customers. Third‑party consultants and court‑approved nonmarket participant reviewers will also be engaged where confidentiality limits public release.
Why It Matters
Professionals should watch this bill because it changes the evidentiary landscape of ratemaking: advocates and LSEs will get earlier and fuller access to the inputs behind valuations, which can change negotiation leverage and litigation strategy. At the same time, the bill raises practical questions about what counts as market‑sensitive, how NDAs will be managed, and the IT and legal costs of delivering data in native formats.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill creates a straightforward but consequential obligation for the CPUC: when the commission or any party relies on data to design or apply a calculation method that determines a charge passed to customers of a load‑serving entity — for example, methods that allocate the cost or value of a power purchase contract owned by an electrical corporation — the underlying data must be made available to LSEs and to ratepayer advocates. That availability is meant to let those parties replicate, challenge, or otherwise examine the factual bases that produce dollar amounts on customer bills.
Implementation is procedural. The bill instructs the commission to ensure the data meet certain accessibility standards: public disclosure except where material would harm market participants, in which case the bill limits access to a designated nonmarket participant reviewer under a commission‑approved nondisclosure agreement.
It requires the data be produced in native file formats to preserve usability and notes that parties can adopt mutually agreed data‑sharing practices at the outset of a proceeding to satisfy timing and delivery obligations.Those process elements shift front‑end work onto utilities and the commission. Utilities will need to inventory and tag which inputs support a calculation methodology, determine what is market‑sensitive, and prepare native‑format exports.
The commission will need procedures and templates for approved NDAs, a mechanism to designate nonmarket participant reviewers, and guidance on when mutual data‑sharing agreements are acceptable. The bill also includes a standard fiscal clause stating no state reimbursement is required because the measure creates or changes criminal provisions tied to enforcement of commission orders, which links the disclosure regime to the existing criminal enforcement framework for violations of commission rules.
The Five Things You Need to Know
The bill adds a new Section 365.4 to the Public Utilities Code requiring the CPUC to make underlying data used in any calculation methodology for charges that recover costs or values of electrical‑corporation‑owned contracts or resources available to LSEs and ratepayer advocates.
Public disclosure is the default; ‘‘market‑sensitive’’ data may be withheld from the public but must be disclosed to a nonmarket participant reviewing representative under a commission‑approved nondisclosure agreement.
The bill requires data to be provided in native file formats so recipient parties can analyze and reproduce calculations rather than relying on static summaries.
Disclosure to LSEs and ratepayer advocates must occur concurrently with any proposal, analysis, or commission‑adopted outcome; parties may instead use mutually agreed data‑sharing practices established at the start of a proceeding to satisfy this timing requirement.
A fiscal clause states no state reimbursement is required because the act involves creation or modification of criminal provisions tied to enforcement of commission actions (i.e.
violations of commission orders remain criminally enforceable).
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
CPUC duty to ensure data availability for calculation methodologies
This subsection imposes the core obligation: the commission must make all data relied on in any decision, ruling, proposal, or analysis that determines or applies a calculation methodology for charges to recover costs or value of electrical‑corporation‑owned contracts or resources available to load‑serving entities and ratepayer advocates. Practically, that means the CPUC’s oversight now explicitly covers the transparency of inputs and models used to calculate pass‑through charges and resource valuations; parties that previously saw only summaries or redacted exhibits can press for the underlying spreadsheets, models, and datasets.
Default public disclosure with a narrow confidentiality path
This paragraph makes public disclosure the baseline, but recognizes bona fide market harm risks. Where data are genuinely ‘‘market‑sensitive,’’ the bill limits public release and instead requires disclosure to a nonmarket participant reviewing representative under a reasonable, commission‑approved nondisclosure agreement. The provision tasks the CPUC with approving the NDA framework and with identifying which types of information merit restricted access — a substantive judgment that will shape how much material ends up in the public domain.
Timing and alternatives for meeting disclosure obligations
The bill requires that disclosures be made to LSEs and ratepayer advocates concurrently with any proposal, analysis, or commission outcome that relies on the data. To avoid rigid process traps, it permits parties to adopt mutually agreed data‑sharing practices at the outset of a proceeding as an alternate means of compliance. That allowance creates room for case‑by‑case scheduling or staged releases but also places an onus on parties to negotiate efficient data transfer protocols early in a proceeding.
Native file format requirement
This short but operationally significant clause obligates providers to supply data in native file formats rather than PDF or image copies. Native files preserve formulas, metadata, and machine‑readable fields, which is essential for meaningful review, replication, or audit. Utilities and their vendors will need repeatable export processes and security controls to deliver sensitive native files without exposing confidential systems.
No state reimbursement and criminal enforcement context
The bill’s fiscal section states no reimbursement is required under the California Constitution because any local costs result from the law’s effect on criminal or infraction provisions tied to enforcement of commission orders. In practice this ties the disclosure regime back into the CPUC’s existing criminal enforcement framework for violations of its orders, and it signals that noncompliance with commission directives implementing this section could carry the same enforcement consequences as other PUC infractions.
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
- Load‑serving entities (investor‑owned, municipal, and community choice aggregators) — they gain earlier and fuller access to the inputs behind charges and valuations, allowing for independent replication, more informed procurement and allocation decisions, and stronger challenges to disputed cost allocations.
- Ratepayer advocates and consumer representatives — access to native‑format inputs and models improves their ability to assess whether charges are reasonable and to present technically grounded challenges during proceedings.
- Residential and commercial customers represented by advocates — indirect beneficiaries because more transparent data makes overcharges or overvaluations easier to detect and contest, potentially reducing costs passed through to customers.
Who Bears the Cost
- Electrical corporations (utilities) — they must prepare, review, and manage broader disclosures, implement export processes for native files, classify market‑sensitive material, and negotiate NDAs or data‑sharing agreements, increasing legal, IT, and administrative costs.
- CPUC staff and administrative units — the commission must develop NDA templates, vet nonmarket participant reviewers, adjudicate confidentiality disputes, and monitor compliance, requiring staff time and possibly new process rules.
- Nonmarket participant reviewing representatives and third‑party consultants — these reviewers assume responsibility for handling confidential market data under NDA and may face legal exposure and costs in reviewing sensitive commercial information.
Key Issues
The Core Tension
The bill pits two legitimate goals against one another: ensuring meaningful transparency so LSEs and advocates can verify and challenge the numbers that produce customer charges, versus protecting market operations and confidential commercial information and avoiding excessive administrative and cybersecurity burdens. There is no mechanical fix; choosing where to draw the line between public disclosure and protected data will determine whether the bill produces genuine oversight gains or simply shifts disputes into resource‑intensive confidentiality fights.
The bill sharpens transparency but leaves several key implementation questions unresolved. First, it does not define ‘‘market‑sensitive’’ beyond the general exception, leaving the CPUC to draw a line between commercially sensitive inputs (like bid strategies or fuel hedges) and information that should be public.
That determination will materially affect how much useful data actually reaches ratepayer advocates. Second, the NDA path depends on the CPUC approving ‘‘reasonable’’ nondisclosure agreements and designating nonmarket participant reviewers; the bill leaves procedure and standards to future CPUC rulemaking, creating a window of uncertainty about access protocols and reviewer qualifications.
Operational tensions will also surface. Requiring native file formats improves analytical fidelity but raises cybersecurity and intellectual property concerns: utilities may resist releasing proprietary models or worry about inadvertent disclosure of unrelated confidential systems.
The concurrent‑with‑proposal timing rule pushes disclosures earlier in proceedings, which supports scrutiny but may compress litigation and negotiation timelines. Finally, the linkage to criminal enforcement for violations of commission orders could deter cooperation or prompt parties to over‑claim confidentiality to avoid penalties — a perverse incentive the CPUC will need to manage through clear guidance and calibrated processes.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.