Backlog

Next up

In Progress

Fix to be Verified

Done

UAT Feedback

As a Program Administrator, I want Active and Confirmed Dashboard downloads to have the same fields.While investigating the SavingsDate field, we identified broader inconsistencies between the Active and Confirmed Dashboard downloads.Review the purpose of each download and define a consistent approach to:<ul><li>included fields,</li><li>naming conventions,</li><li>intentional differences, and</li><li>opportunities to align or consolidate the downloads.</li></ul>

2026 Claim Spec Update Queue

Add missing fields to the Active dash output download to match Confirmed dash download

cedars team

Program Administrators need the ability to remove previously submitted <code>ParticipantCount</code> records in cases where overriding the data is not sufficient. Currently, validation rules do not allow <code>ParticipantCount</code> values of 0, preventing the removal of records through a new upload. Update the <code>ParticipantCount</code> submission process so that each new Participant table submission replaces any previously submitted <code>ParticipantCount</code> records. Only the records included in the latest submission would be retained.

Completed

Claim Spec

2026

Participant table - add ability to remove ParticipantCount records

Feedback from Greg “The attached file downloaded from CEDARS shows the SavingsDate field at the end of the Claims table. The SavingsDate field is no longer part of the 2026 input spec but will be added to the record-level output file.”<file-preview-component data-featurebase-content-filename="Claims_2026_Inputs.csv" data-featurebase-content-filesize="32783" data-featurebase-content-filetype="text/csv" data-featurebase-content-key="64defea38b15fc2614cb036f/post/6a5ed57e13805b5912bffa25/019f826f-819d-7914-99b6-1175aa05d466/b64u-Q2xhaW1zXzIwMjZfSW5wdXRzLmNzdg.csv" src="https://64defea38b15fc2614cb036f.featurebase-attachments.com/c/post/6a5ed57e13805b5912bffa25/019f826f-819d-7914-99b6-1175aa05d466/b64u-Q2xhaW1zXzIwMjZfSW5wdXRzLmNzdg.csv?X-Amz-Expires=3600&amp;X-Amz-Date=20260827T000000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260827%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=502fda54bed00464693aaa0604cfb24c69a58ab50458d614a8e76772aded3240"></file-preview-component>Investigate if the SavingsDate output is behaving as expected for 2026

Regression testing SavingsDate

Update the <code>EquityTargeted</code> data rule description on the <a target="_blank" rel="nofollow" class="link" href="https://cedars-2.cpuc.ca.gov/claims/specification/data-rules-participant/">Participant table</a> to:<code>Number of participants qualifying as Equity Targeted. A program participant that meets the CPUC-adopted criteria for being Hard-to-Reach, or being located in a disadvantaged community, or considered underserved.</code><img data-width="100%" data-align="left" alt="" data-featurebase-content-key="64defea38b15fc2614cb036f/post/6a582900ee530504529215c4/019f685f-818f-78da-b7dd-b0b253e897c6/b64u-aW1hZ2UgKDE4KS5wbmc.png" data-featurebase-content-filename="image (18).png" src="https://64defea38b15fc2614cb036f.featurebase-attachments.com/c/post/6a582900ee530504529215c4/019f685f-818f-78da-b7dd-b0b253e897c6/b64u-aW1hZ2UgKDE4KS5wbmc.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260827T000000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260827%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=45a174c8e0637a94f9c3c9361280a755a2f02907ec6700712c04a6d7afd46547"><img data-width="100%" data-align="left" alt="" data-featurebase-content-key="64defea38b15fc2614cb036f/post/6a582900ee530504529215c4/019f685f-687d-76cc-ab91-1b18702e9a59/b64u-NjIyMzcyNjQ5LTJkNDU2N2VmLWMwM2UtNGJjNi04NGEyLTNhOWI0MWU1YjExOC5wbmc.png" data-featurebase-content-filename="622372649-2d4567ef-c03e-4bc6-84a2-3a9b41e5b118.png" src="https://64defea38b15fc2614cb036f.featurebase-attachments.com/c/post/6a582900ee530504529215c4/019f685f-687d-76cc-ab91-1b18702e9a59/b64u-NjIyMzcyNjQ5LTJkNDU2N2VmLWMwM2UtNGJjNi04NGEyLTNhOWI0MWU1YjExOC5wbmc.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260827T000000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260827%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=2589dd3328302b7a75d73447138e2c82592ffcad71e92d2fef09b3592a6dda13">

Claim Spec - Update EquityTargeted data rule description on the Participant table

The quarterly csv files for SDGE and SCG were reordered to match the published Claims_2026_Inputs.csv document. SDGE and SCG 2026 quarterly csv files successfully uploaded to CEDARS-2. The CET returns an error when using the Measure.csv and ProgramCost.csv files from the quarterly upload. “Measure.csv: The columns are in the wrong order ProgramCost.csv: The columns are in the wrong order” This worked before the 2026 spec changes.

Re-order Claim Spec fields to match CET ordering

ecorona2

To support upstream system updates and integration activities, stakeholders have requested additional documentation showing where newly introduced input and output fields will appear within record-level downloads. In particular, Greg requested visibility into: - Which new fields have been added - The position of those fields within each record-level file - Example values for each new field - There is a strong preference for newly introduced fields to be appended to the end of record-level

Provide Record-Level Field Mapping for New Inputs and Outputs

When I try to upload a claims file with only the Measure, Claim, Site, ContactClaim, and Participant tables (i.e., without ProgramCost) as an XLSX file, I encounter a server error. I tested this with both the example claims file and some of my PA’s claims.I didn’t see any issues uploading an XLSX file with all tables or only with the ProgramCost table.New Update (7/28):The specific validation rule that triggered the error is:<ul><li><code>Participant.PrgYear must match a valid ProgramCost.PrgYear.</code></li></ul>Update this validation rule to be:<ul><li><code>Participant.PrgYear is for the current claim year.</code></li><li>This matches one of the validation rule applied to <code>Measure.ClaimYearQuarter</code></li></ul>

Unable to upload claims without ProgramCost table - Update Participant.PrgYear data rule

SoCalREN_TEC

I noticed a discrepancy with the Census Tract field requirements. The field requirement is 11 characters per the ticket (<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://cpuccedars.featurebase.app/p/geospatial-visualisation-of-claims-data">https://cpuccedars.featurebase.app/p/geospatial-visualisation-of-claims-data</a>). While the CEDARS specification page itself appears to correctly show the field length as 11 characters <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://cedars-2.cpuc.ca.gov/claims/specification/pii/site/">https://cedars-2.cpuc.ca.gov/claims/specification/pii/site/</a>, the Download All Data Rules from the specification page lists it as 10 characters (see attached images). <img data-width="100%" data-align="left" alt="" data-featurebase-content-key="64defea38b15fc2614cb036f/post/6a6b79481d88e264e6a8fc82/019fb3ce-6a73-7edf-8935-f470d30e1d47/b64u-aW1hZ2UucG5n.png" src="https://64defea38b15fc2614cb036f.featurebase-attachments.com/c/post/6a6b79481d88e264e6a8fc82/019fb3ce-6a73-7edf-8935-f470d30e1d47/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260827T000000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260827%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=e1d54c5e705f0842e8ca498bc8b1c2671f122073b1a9a878e96d9642bc1a68e9" data-featurebase-content-filename="image.png"><img data-width="100%" data-align="left" alt="" data-featurebase-content-key="64defea38b15fc2614cb036f/post/6a6b79481d88e264e6a8fc82/019fb3cc-5568-7b7d-9b7f-3229472937fe/b64u-aW1hZ2UucG5n.png" src="https://64defea38b15fc2614cb036f.featurebase-attachments.com/c/post/6a6b79481d88e264e6a8fc82/019fb3cc-5568-7b7d-9b7f-3229472937fe/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260827T000000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260827%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=ec41db21b92ec0d8bd233329cc9c8b29c3d23c64e9a5093854815bb088f6190b" data-featurebase-content-filename="image.png">Could the team please review and update the documentation as required?

Census Tract Field Requirement Discrepancy

Roopa Reddy

During Claim Spec UAT, record-level validation errors were encountered when loading Participant records with large participant counts. The system rejects records when Participant.ParticipantCount exceeds 32,767, displaying the following validation message:<blockquote>"Ensure this value is less than or equal to 32767."</blockquote>This limitation does not appear sufficient for programs with large participant populations and may prevent submission of valid participant data.Test case: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="link" href="https://cedars-2.cpuc.ca.gov/claims/upload-summary/833/">https://cedars-2.cpuc.ca.gov/claims/upload-summary/833/</a>Sample records:PGE_Res_002a|2026|Households: Participant.ParticipantCount = 57,972 PGE_Res_002d|2026|Households: Participant.ParticipantCount = 3,300,000

Participant Count Validation Error

After examining the 2026 Claims file downloaded from the CEDARS-2 Record-level Data area under the Data tab, the field “SCB Cost No Admin” is missing. The field “SCH Cost No Admin” is in the file.

Record-level Data 2026 Claims Missing SCB Cost No Admin

In our testing we compared the deemed claims CEDARS “Savings Date” column in the record-level Claims 2026 download to SDGE &amp; SCG internal systems. This revealed a large number of blank “Savings Date” values for deemed claims in the CEDARS record-level download. We believe all deemed claims should have “Savings Date” populated there.

In Testing

Savings Date missing for many 2026 deemed claims

Help Center

Improved

Fixed

Specification

Claims

Monthly Reports

Budget Filing

Security

Documents

Data & Reports

Programs

Impact Profiles

Load Shapes

cpuccedars

To Be Considered

In Review

On Hold

Planned

PCG Top Priority 

2026 Fixed Development

In Testing Queue

No Fix Required

Rejected

2027

2028

Fixed Development

Top 12

2026 CET Update Queue

Budget Filings

Impact Profiles & Load Shapes

Data Tab

Download

Accessibility

Design Upgrade

Dashboard

Reports & Documents

2027 CET Update Queue

2027 Claim Spec Update Queue

2028 Claim Spec Update Queue

Otter

Accounts & Admin

The development tasks agreed to by the CPUC data reporting project coordination group. All tickets tagged 2026

PCG Top Priority

Development Plan 2026 

This roadmap shows the proposed and confirmed updates to the Claims Specification for 2026. The board is filtered to display items tagged 2026 Claim Spec Update Queue. What the columns mean:<ul><li>Claims Specification Update These tickets are confirmed for the 2026 Claims Specification update. They have been reviewed, agreed to, with the status 2026 Fixed Development.</li><li>Claims Backlog These tickets are not yet confirmed. They are still under review or being considered and may be included in a future update. This includes items with the status To be considered or In review.</li></ul>

2028 Claim Specification Update

2027 Claim Specification Update

Claims Backlog

2026 Claims Specification Update

Claim Spec 2026

Show’s development tickets with due dates by month.

Monthly Roadmap

Tickets tagged with “Impact Profiles &amp; Load Shapes”

Load Shapes & Impact Profiles

Using our feedback portal, you can:<ul><li>Share feedback to help us improve CEDARS and CET</li><li>Request new features</li><li>Submit bug reports</li><li>Ask questions not covered in the user guide or Help center articles</li></ul>

Give us feedback

Hey {name|there}! 👋

Cedars

UAT Feedback