This bill adds Section 8586.10 to the Government Code, directing the Office of Emergency Services (OES), working with relevant state and local agencies, to develop a set of 'catastrophic plans.' The statute lists seven subject-specific plans that the Office must develop or adopt in coordination with the Federal Emergency Management Agency (FEMA).
The change creates a statutory baseline for statewide catastrophic planning across floods, earthquakes, wildfires, pandemics and CBRNE incidents. For practitioners, the requirement re-centers planning responsibility at OES and creates a clear list of prioritized threats that will shape exercises, resource requests, and coordination between state, local, and federal partners—while leaving important implementation details unanswered (timelines, funding, and enforcement).
At a Glance
What It Does
The bill requires OES to produce a defined set of 'catastrophic plans' and explicitly identifies seven plan topics (Northern California floods; Bay Area earthquake; Cascadia earthquake & tsunami; Southern California earthquake; wildland‑urban interface wildfire; pandemic influenza; and CBRNE incidents). It also recognizes those plans may be developed by OES, FEMA, or jointly.
Who It Affects
Directly affects OES and state agencies charged with emergency roles, county and city emergency management offices, public health authorities, first responders, and infrastructure operators in the named hazard areas; it also implicates FEMA for joint plan development or adoption.
Why It Matters
By statute-anchoring these plan types, the bill drives statewide prioritization for mitigation, exercise design, mutual aid planning, and grant applications. The law will influence where planners focus resources—even though it does not appropriate money or set deadlines for delivery.
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 single, short statutory obligation: OES must develop 'catastrophic plans' in consultation with relevant state and local agencies. That consultation requirement means OES cannot act in isolation; it will need to bring counties, cities, public health, utilities, tribal entities, and other stakeholders into the planning process.
The text does not, however, prescribe how consultation happens, who leads regional elements, or how conflicts between state and local priorities get resolved.
What the statute actually fixes is the content universe: seven discrete plan topics. That list mixes geographically specific risks (Northern California floods, Bay Area earthquake, Southern California earthquake, Cascadia tsunami) with crosscutting hazards (wildland‑urban interface fires, pandemic influenza, and CBRNE incidents).
Practically, OES must inventory existing plans, identify gaps, and either adopt FEMA products or produce state versions that align with federal frameworks. The option for FEMA involvement can shorten development time but also raises questions about whether federal templates will match California’s local authorities and operational practices.Notably absent from the text are deadlines, update cycles, performance measures, required public release, or funding.
Because the bill simply creates the duty and the topic list, OES will likely need additional direction or appropriations to deliver operational, exercised plans. For compliance officers and planners, the immediate workstream will be inventory and alignment: map local and regional plans onto these seven categories, identify lead agencies, and define interoperable protocols for communications, evacuation, sheltering, medical surge, and resource staging.Finally, the statute stops short of changing legal authority during an incident.
It does not grant OES new emergency powers, nor does it mandate that local governments adopt the statewide plan. The practical effect will depend on how OES operationalizes the mandate—through guidance, model annexes, formal MOUs, or conditional funding tied to plan adoption—and on whether the Legislature later attaches dollars, deadlines, or enforcement mechanisms.
The Five Things You Need to Know
The bill adds a new statutory provision labeled Section 8586.10 to the California Government Code creating a duty for OES to develop 'catastrophic plans.', It defines 'catastrophic plans' to include seven specific plans: Northern California Catastrophic Flood Response; Bay Area Earthquake; Cascadia Subduction Zone Earthquake and Tsunami; Southern California Catastrophic Earthquake; Wildland‑Urban Interface Wildfires; Pandemic Influenza; and CBRNE incidents.
The statute requires OES to act 'in consultation with relevant state and local agencies,' but it does not specify consultation procedures, decision authority, or dispute resolution mechanisms.
The text explicitly contemplates that the plans may be developed by OES, FEMA, or jointly, allowing for federal products to be adopted or adapted rather than created from scratch.
The bill contains no deadlines, funding appropriation, mandated update cycle, or enforcement mechanism for plan completion or adoption.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Mandate for OES to develop catastrophic plans with consultation
Subsection (a) imposes the core duty: the Office of Emergency Services must develop catastrophic plans and must consult relevant state and local agencies in doing so. Practically, this creates an obligation for OES to convene partners, but the statute does not define "relevant" agencies, specify who chairs regional working groups, or create a timeline for deliverables. That lack of procedural detail hands operational control to OES but leaves significant discretion on how comprehensive the consultation will be and how local voices are weighed.
Enumerated list of seven plan topics
Subsection (b) is purely definitional: it lists seven plans California expects to be in the 'catastrophic plans' set. The list mixes place-based plans (Northern California floods, Bay Area and Southern California earthquakes, Cascadia subduction zone) with cross-cutting hazards (wildland‑urban interface wildfires, pandemic influenza, and CBRNE incidents). Naming specific geographic plans is consequential because it signals prioritization of certain regions and hazards for statewide coordination, resource staging, and likely future grant or budget focus.
Permits OES, FEMA, or joint development
The statute explicitly allows these plans to be developed by OES, FEMA, or both. That language creates two practical paths: California can adopt or adapt FEMA-authored plans (streamlining federal alignment and potential funding eligibility) or write state-specific versions (preserving local nuance). Either path requires careful coordination to avoid inconsistent operational assumptions, conflicting authorities, or gaps where neither entity takes full responsibility.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government 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
- Residents in named high-risk regions (Northern California, Bay Area, Cascadia, Southern California): benefit from a state-directed focus that aims to close planning gaps and prioritize resources for their specific hazards.
- County and city emergency management offices: gain a clear state-level focal point and a predictable set of plan topics to align local plans, exercises, and grant applications with statewide expectations.
- Public health systems and hospitals: receive an explicit planning mandate that includes pandemic and surge events, which can support coordinated medical surge protocols and federal grant alignment.
- State policymakers and grant managers: obtain a statutory framework to justify budget requests and prioritize investments around a defined set of catastrophic scenarios.
Who Bears the Cost
- Office of Emergency Services (OES): will absorb the workload of convening stakeholders, inventorying existing plans, drafting or adopting plans, and coordinating interagency review—without funding specified in the statute.
- Local governments and tribal authorities: must invest staff time and technical resources to participate in consultations, reconcile local plans with statewide products, and potentially revise operational procedures.
- Hospitals, utilities, and other critical infrastructure operators: may incur planning and exercise costs to align with statewide plans or meet new expectations for coordination, data sharing, or mutual aid.
- State budget and appropriations process: if OES requires external support to deliver operational plans, the Legislature or the Governor will likely face pressure to appropriate new funds or repurpose existing budgets.
Key Issues
The Core Tension
The central dilemma is between the need for a standardized, statewide approach to catastrophic risks (which improves coordination, resource prioritization, and federal alignment) and the equally real need for local flexibility and resourcing—especially where local governments, tribal nations, and private infrastructure operators must shoulder planning costs without guaranteed state funding or hard deadlines.
The statute creates a directional mandate but leaves implementation mechanics undefined. There are no deadlines, reporting requirements, update intervals, or metrics for plan quality.
That gap means the law could produce anything from a set of high-level strategy documents to detailed operational plans—depending entirely on OES’s choices and available resources. For jurisdictions and agencies that must align their local plans, that variability undermines predictability and complicates budgeting for compliance and exercises.
Federal involvement is a double-edged sword. Allowing FEMA to develop or co-develop plans can accelerate delivery and align California with federal standards for funding eligibility, but it may also import federal assumptions that clash with state or local legal authorities and operational practices.
The bill also does not address legal authority during an incident, how the state will reconcile conflicting local ordinances, or how tribal sovereignty will be respected in regions with tribal lands. Finally, the statute risks duplicating existing regional plans unless OES conducts a careful inventory and explicitly maps existing products into the new framework.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.