AB 777 mandates that investor‑owned and publicly owned electric utilities provide aggregated, ZIP‑level outage data to the California Department of Social Services (CDSS) to help the state identify households eligible for disaster nutrition assistance. The bill sets a seven‑calendar‑day response goal for outages lasting four hours or more, requires utilities to name a point of contact, and directs the Public Utilities Commission (CPUC) and local utility boards to execute agreements as needed to enable the data exchange.
The Department must use that utility data to maximize federal nutrition assistance — including automated mass replacement of SNAP, D‑SNAP, and Summer EBT benefits — and submit a legislatively required report by December 31, 2026 on steps to ensure California claims all available federal food aid. The statute limits shared data to aggregated ZIP‑level outage metrics, bars personally identifiable information, and ties use to specified disaster‑assistance purposes.
At a Glance
What It Does
The bill requires electrical corporations and local publicly owned electric utilities to make a reasonable effort to provide aggregated ZIP‑level outage data for outages of four hours or longer, and to do so within seven calendar days of a CDSS request. CDSS must use those data to pursue federal nutrition assistance and automated benefit replacements.
Who It Affects
Investor‑owned utilities regulated by the CPUC, local publicly owned electric utilities (POUs) governed by local boards, the California Department of Social Services, county human services agencies that administer CalFresh/D‑SNAP, and residents in ZIP Codes affected by outages.
Why It Matters
This creates a new operational linkage between energy outage reporting and emergency food benefit delivery, aiming to accelerate federal replacement benefits after disasters while constraining data to aggregated, privacy‑protected formats — a model other states or programs might copy.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 777 constructs a narrow data pipeline: when CDSS requests help after a disaster or mass outage, investor‑owned utilities and POUs must provide aggregated outage counts at the ZIP‑Code level so the department can identify where households lost power. The statute limits the shared fields, prohibits any personally identifiable information, and requires utilities to try to respond within seven calendar days for outages lasting at least four hours.
The law specifies what counts as the minimally necessary data: outage dates, duration in hours, the counties and ZIP Codes affected, and for each ZIP Code the total number of residential customers and the number who lost service. Utilities must designate a dedicated point of contact to receive requests and deliver the aggregated extract.
The CPUC is assigned a technical‑assistance role to help CDSS interpret utility outputs and support the department’s legislatively mandated report.On the benefits side, CDSS must leverage the utility data to maximize federally funded nutrition assistance, explicitly including automated mass replacement for SNAP, D‑SNAP, and Summer EBT (SUN Bucks). The department must report to the Legislature by December 31, 2026 with options to improve claiming of federal food aid and recommend additional oversight or actions to meet the statute’s objectives.
That reporting requirement sunsets administratively in 2030 under existing Government Code provisions.The statute contains built‑in limits: data use is restricted to the text’s stated purposes and remains subject to applicable privacy laws. The bill also contemplates memoranda of understanding or other agreements between the CPUC or local utility boards and utilities to operationalize exchanges, but it also imposes the seven‑day reasonable‑effort obligation notwithstanding other law or existing agreements.
The Five Things You Need to Know
Utilities must make a reasonable effort to provide aggregated ZIP‑level outage data for outages lasting four hours or longer within seven calendar days of a CDSS request.
Required data fields include outage dates, outage durations in hours, counties and ZIP Codes affected, total residential customers per ZIP Code, and the number of residential customers who lost service.
CDSS must use the utility data to maximize federal nutrition assistance and to seek automated mass replacement of SNAP, D‑SNAP, and Summer EBT (SUN Bucks) benefits after qualifying disasters.
Each electrical corporation and local publicly owned electric utility must designate a dedicated point of contact to receive data requests and coordinate with CDSS.
CDSS must submit a report to the Legislature by December 31, 2026 on ways to maximize federal food aid; that report requirement is administratively inoperative January 1, 2030 under Government Code rules.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions targeted to implementation
This short definitions section adopts the statutory references for “electrical corporation” and “local publicly owned electric utility,” tying chapter language directly to existing Public Utilities Code terms. That keeps the obligation squarely on entities already defined elsewhere in state law and narrows interpretive gap risk about who must comply.
Investor‑owned utilities: data scope, timing, and safeguards
This provision obligates CPUC‑regulated electrical corporations to provide aggregated ZIP‑level outage data and lists the minimum fields utilities must supply. It limits the shared information to aggregated metrics (no PII), constrains use to disaster nutrition assistance purposes, and makes the seven‑day, outages‑of‑four‑hours threshold applicable “notwithstanding any other law.” Practically, it forces investor‑owned utilities to create an export or reporting feed that can produce the required aggregation quickly while complying with privacy laws.
Publicly owned utilities: analogous duties plus notice requirement
Section 8412 parallels the investor‑owned utility duties for local publicly owned electric utilities (POUs) but routes implementation decisions through their governing boards. It also requires CDSS to notify POUs of federal requirement changes, which recognizes the two‑way nature of disaster assistance operations and keeps POUs updated when federal program rules shift eligibility or documentation needs.
CDSS obligation to use data and submit a report
This section directs CDSS to ‘maximize’ federal disaster nutrition assistance using necessary data from utilities and to pursue automated mass replacement of affected federally funded benefits. It mandates interagency contact channels with utilities, requires a legislatively prescribed report to the Legislature by December 31, 2026 listing further steps to ensure California accesses federal food assistance, and notes the administrative sunset for the reporting duty in 2030. The provision explicitly lists the benefits programs targeted for automated replacements, anchoring CDSS operational priorities.
State‑mandate and reimbursement mechanics
The bill declares no state reimbursement is required under Article XIII B for local agencies, citing exceptions such as the authority to levy service charges or the fact the bill creates or changes a crime/infraction. That language aims to limit local budgetary claims and frames the new duties as either charge‑funded or falling within existing statutory exceptions.
This bill is one of many.
Codify tracks hundreds of bills on Social Services across all five countries.
Explore Social Services 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
- Households in outage‑affected ZIP Codes — Faster identification of impacted areas increases the chance CDSS and counties can secure federal replacement benefits quickly, reducing days without accessible food resources after disasters.
- Counties and caseworkers administering CalFresh/D‑SNAP — Aggregated outage data gives local agencies a geographically precise signal for targeting outreach, organizing D‑SNAP operations, and prioritizing replacement benefit issuance without relying solely on crowdsourced reports.
- CDSS and state emergency coordinators — The data provide an operational input to pursue federal reimbursements and automated mass replacement mechanisms, potentially increasing federal drawdown and reducing state/county fiscal exposure.
Who Bears the Cost
- Investor‑owned electrical corporations — They must develop processes to aggregate and deliver ZIP‑level outage data within seven days, assign a point of contact, and ensure exports comply with privacy requirements, which creates IT and staffing costs, especially for smaller systems or those with legacy outage management systems.
- Local publicly owned electric utilities (POUs) — POUs and their governing boards face parallel obligations; some POUs operate with thin staff and will need to budget for data extraction, compliance, and coordination with CDSS.
- County human services agencies — While the statute helps targeting, counties still must stand up D‑SNAP operations, intake capacity, and outreach to households identified through ZIP‑level signals; those operational costs may not be fully federally reimbursed immediately.
- CPUC and state agencies — The CPUC must provide technical assistance and may need internal staff time to negotiate MOUs, advise CDSS on data formats, and resolve disputes, creating administrative costs that are not explicitly funded.
Key Issues
The Core Tension
AB 777 balances two legitimate goals — speed of assistance after power loss and protection of customer privacy/utility operational capacity — but those aims pull in opposite directions: delivering timely, targeted federal benefits favors finer, faster data sharing, while privacy and utilities’ IT limits favor conservative, slow approaches. The statute tries to thread that needle with narrow, aggregated data and “reasonable effort” timing, but that compromise leaves open disputes over standards, enforcement, and whether the data will actually produce faster benefit delivery in practice.
The bill resolves a practical coordination gap between utilities and social‑service delivery, but it does so by imposing a narrow, time‑bound data obligation on utilities with limited guidance on data format, transmission method, or validation standards. That leaves CDSS and utilities to negotiate technical details under MOUs or informal channels; absent standard schemas and automated feeds, the seven‑day target could be unrealistic in complex outages.
The statute’s “reasonable effort” language helps utilities argue against strict liability for late or imperfect responses, but it also creates uncertainty for CDSS about enforceability and timelines in the moments when speed matters most.
Privacy and permissible‑use rules are central yet underspecified. By restricting data to aggregated ZIP‑level metrics and prohibiting PII, the bill reduces many privacy risks, but ZIP‑level granularity can still create re‑identification risks in low‑population areas or for special‑needs facilities.
The bill subjects data to “applicable privacy laws” but does not require an independent privacy impact assessment, a retention schedule, or explicit audit rights. Finally, the department’s ability to trigger automated mass replacements depends on federal program rules and systems; utility data may improve targeting, but federal eligibility, documentation requirements, and administrative thresholds could still block or delay automated benefit flows.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.