AB 941 adds a new Chapter 8.5 to the Public Utilities Code to impose a shortened, structured CEQA process for electrical infrastructure projects the applicant designates as “priority projects.” The bill directs the California Public Utilities Commission (PUC) to review completeness, issue a preliminary ruling that sets scope and schedule, and make a determination on certification of the environmental impact report within a statutory window.
The measure matters to utilities, developers, regulators, and communities because it replaces open‑ended CEQA timelines with firm deadlines and a tightly sequenced cure process: PUC staff must flag application deficiencies quickly, applicants have a short period to fix them or explain why they cannot, and the commission must act on the EIR within a set number of days after deeming an application complete. That changes how permitting teams should prepare applications and how agencies will allocate review capacity.
At a Glance
What It Does
The bill requires applicants to label certain electrical projects as priority projects and justify the designation in their PUC application. PUC staff must review applications within 30 days, applicants must remedy deficiencies in 60 days (or explain why they cannot), and the commission must decide whether to certify the EIR within 270 days of deeming the application complete, with the commission issuing a preliminary ruling that sets scope and schedule.
Who It Affects
Investor‑owned utilities, independent transmission developers, PUC staff and commissioners, lead CEQA agencies, local governments, and communities affected by transmission and substation siting. Environmental and community groups that participate in CEQA review will also see compressed timelines.
Why It Matters
This creates a predictable, expedited track for high‑priority electric projects, shifting the permitting calculus toward more rigorous up‑front application preparation and faster agency decision‑making. That could accelerate grid upgrades but also compress public participation and review capacity.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 941 creates a statutory fast lane for electrical infrastructure projects that applicants designate as “priority projects.” An applicant must explicitly identify a project as a priority project in its PUC application and state the basis for that designation. Once filed, PUC staff get 30 days to review the application and point out any missing information or data.
The applicant then has 60 days to either supply the missing material or explain in writing why it cannot do so.
If the applicant cures deficiencies or explains why it cannot, the bill requires the PUC to treat the application as complete and to issue a preliminary ruling that spells out the scope of environmental review and a schedule for completing the process. From that point the commission must make a determination on whether to certify the environmental impact report within 270 days, subject to whatever exceptions the statute itself allows.
Those time limits are statutory, not merely agency targets, so they change the legal cadence of CEQA review for these projects.The bill rides atop existing PUC authority that already controls when utilities may begin construction by issuing certificates of public convenience and necessity and recognizes that some modifications to existing facilities are already exempt from certificate requirements. It also relies on existing criminal penalties for violating PUC orders: failing to comply with commission actions implementing this new Chapter 8.5 would fall into the class of violations that carry criminal exposure under current law.
The statute, as presented, also notes that its changes trigger a state‑mandated local program but asserts no state reimbursement is required under the listed constitutional provision.Practically, the law forces project sponsors to invest more time and detail into initial filings and pushes the PUC to front‑load review work. For agencies and stakeholders used to flexible CEQA timelines, this imposes compressed windows for technical review, public input considerations, and interagency coordination.
The text reserves unspecified exceptions to the 270‑day deadline, which means there will be boundary questions about when the expedited schedule pauses or extends.
The Five Things You Need to Know
The applicant must identify a project as a “priority project” in its PUC application and explain the basis for that designation.
PUC staff must review an application for a priority project within 30 days and notify the applicant in writing of any information or data deficiencies.
After a deficiency notice, the applicant has 60 days to correct the deficiencies or explain in writing why it cannot do so.
The commission must deem the application complete with a preliminary ruling that sets the scope and schedule, and it must determine whether to certify the EIR no later than 270 days after deeming the application complete (subject to the bill’s unspecified exceptions).
Violations of commission actions implementing these requirements fall under existing law that treats breaches of PUC orders as crimes; the bill creates a state‑mandated local program while stating no state reimbursement is required.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Priority project designation and application requirement
This provision requires the applicant to flag an electrical infrastructure project as a priority project within its PUC filing and to state the factual basis for that designation. Practically, that moves the designation decision from the agency to the applicant and creates a new upfront obligation for filings: permit packages must include a short legal and factual justification for why the project qualifies as priority. That documentation becomes the trigger for the compressed review track.
30‑day staff completeness review and written deficiency notice
PUC staff must perform an initial completeness review within 30 days of filing for priority projects and provide a written list of any missing information. This is a hard, short timeline that forces staff to triage applications quickly. The practical implication is that agencies will need checklists and standardized intake procedures to meet the deadline; applicants must prepare filings to survive a rapid scrutiny or risk receiving a formal deficiency notice that starts the cure clock.
60‑day cure window or written explanation
After receiving a deficiency notice the applicant has 60 days either to cure the defects or to file a written explanation of why it cannot cure them. That creates a binary compliance mechanism: either the package becomes complete quickly, or the applicant must document continuing gaps. The statute does not, in the text provided, specify detailed standards for adequacy of cures, which leaves room for follow‑up disputes and administrative determinations about whether the cure satisfied the notice.
Deem application complete and set scope and schedule
When the cure period resolves, the PUC must deem the application complete and issue a preliminary ruling that defines the scope of the environmental review and sets a schedule. That ruling effectively fixes the boundaries of analysis and the timeline for agency action. For compliance officers and outside counsel, the preliminary ruling will be the key document to track because it replaces open‑ended scheduling with a commission‑issued roadmap.
Statutory deadline to decide on EIR certification; enforcement consequences
The commission must determine whether to certify the EIR no later than 270 days after deeming the application complete, except for exceptions the bill references but does not detail in the text provided. Because failing to follow PUC orders is already a crime under California law, actions implementing these deadlines carry potential criminal consequences for those who violate commission directives. The combination of a statutory deadline and existing criminal penalties raises enforcement stakes if parties seek to obstruct or ignore PUC scheduling.
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
- Investor‑owned utilities and independent transmission developers — They gain a faster, predictable timeline for environmental review that can shorten project delivery schedules and reduce permitting uncertainty.
- Grid operators and planners (e.g., CAISO) — Accelerated permitting for priority projects can speed the deployment of transmission and substation upgrades needed for reliability and integration of clean energy resources.
- Project financiers and procurement teams — A fixed schedule reduces timeline risk, which can lower financing costs and improve bid competitiveness for projects with time‑sensitive value.
- State energy policymakers — Faster permit decisions create a clearer pathway to meet statutory clean energy and reliability goals by reducing one source of project delay.
Who Bears the Cost
- California Public Utilities Commission and its staff — The agency must front‑load intake and review work on compressed timelines, requiring staffing, process changes, and possibly overtime or reallocation of resources.
- Local lead CEQA agencies and technical reviewers — Shorter review windows constrain technical analysis, interagency coordination, and opportunities for stakeholder consultation, increasing operational strain.
- Community groups and environmental advocates — Compressed schedules and preliminary rulings that lock scope can limit time for meaningful public engagement and detailed comment on impacts.
- Applicants who file incomplete packages — While applicants ultimately benefit from the fast track if they prepare well, those that don’t will face the administrative cost of cure cycles and potential legal exposure if disputes arise about completeness.
Key Issues
The Core Tension
The bill forces a classic policy trade‑off: accelerate critical electrical infrastructure by imposing firm deadlines and an applicant‑driven priority track, or preserve the slower, deliberative CEQA process that allows more extensive technical review and public participation; speeding up approvals reduces schedule risk but risks shallower review, constrained stakeholder input, and higher administrative and litigation friction.
AB 941 substitutes time limits and an applicant‑driven priority label for the more flexible CEQA cadence typically set by lead agencies. That creates a tension between predictability and thoroughness: shorter, statutory deadlines reduce schedule risk but risk compressing technical review and public participation.
The bill text, as presented, references unspecified exceptions to the 270‑day certification deadline; those carveouts will likely be the locus of future interpretive battles (for example, over federal permits, tribal consultation, or complex multi‑agency reviews that already take longer). The absence of objective statutory criteria for designating a priority project — the designation is made by the applicant and supported by a statement of basis — raises questions about potential over‑designation and gaming of the expedited track.
Another implementation challenge is enforcement and administrative burden. The commission must meet a 30‑day intake window and then coordinate cure determinations, preliminary rulings, and a 270‑day EIR decision.
Meeting those milestones will require standardized application checklists, clear adequacy standards, and potentially new staffing. The law also leverages existing criminal penalties for violating PUC orders, which increases the stakes of administrative decisions but risks criminalizing procedural noncompliance or narrow technical disputes.
Finally, the interplay between this new chapter and established CEQA practices — local agency discretion, public review periods, and judicial review — is uncertain; compressed administrative timelines often shift contestation into litigation, which can paradoxically delay projects despite front‑loaded deadlines.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.