Adopted August 19, 2026. The Board of Forestry approved the statewide Zone 0 regulation. It is not yet in effect: review by the Office of Administrative Law comes next. What changes, and when.

Investigation

How local Zone 0 rules actually spread in California

Status check (August 19, 2026): The Board of Forestry approved the statewide Zone 0 regulation on August 19, 2026. It is not yet in effect: the package still needs Office of Administrative Law review (including a five-day public comment period) and publication by the Secretary of State, and no compliance deadline is running yet. Separately, at least twenty-six local jurisdictions have their own Zone 0 rules in force now. See the live status tracker.

The short version

  • Local Zone 0 rules are not being invented city by city. They are model text, written once by a county fire agency and then adopted by district after district and council after council.
  • One Riverside County fence rule, Section 604.11, appears word for word in the county code and in five of its cities. Three of those cities adopted it on the same day. The code they are all amending is the 2025 California Wildland-Urban Interface Code, new this cycle as a standalone code at Part 7 of Title 24.
  • One San Diego County Zone 0 sentence appears in the county's Consolidated Fire Code, where it has been in force since April 13, 2023, and in the separate ordinances of at least two independent fire districts.
  • A fire district's version does not reach a city until that city's council votes to ratify it, and the council may modify or deny. That is Health and Safety Code section 13869.7(c), and the districts write the condition into their own ordinances.
  • This is happening during a statewide freeze on local residential building-code amendments that runs to June 1, 2031. Home hardening is one of the few things the freeze deliberately leaves open.
  • So the useful question is not "has my city council discussed Zone 0." It is what your county fire agency's model ordinance says, and whether your jurisdiction has adopted the current code cycle.

What we thought was happening

We built the register one jurisdiction at a time, and for months the picture it produced was of scattered local initiative: a fire district here, a city council there, each responding to its own fires and its own politics. That is how the coverage describes it too, when it describes it at all.

On August 24, 2026 the register went from twenty to twenty-six entries in a single day. Not one of those six adopted anything that day. What changed is that we stopped searching for the names of cities and started searching for the operative sentences, and the moment we did, the rules stopped arriving one at a time and started arriving in families.

The Riverside family: one fence rule, six Riverside jurisdictions, three adopted on one day

Riverside County's version lives at Section 604.11 of the wildland-urban interface code, added locally in three short parts. Its scope clause covers fences and gates within five feet of a building, which the text itself labels "(Zone 0)." Then:

"604.11.2 New fencing. New fencing and gates shall be constructed of a non-combustible material."

"604.11.3 Existing fencing. Fencing installed prior to January 1, 2026, may remain. Exception: The entire fencing not parallel and within 5 feet of the Building, including gates within the fencing, shall be constructed of a non-combustible material when any portion of the existing fencing within 5 feet is being replaced."

That exception reverses the state's own rule, which expressly permits combustible repairs to an existing combustible fence. And it is not one city's drafting quirk. The identical text is in force in:

  • Unincorporated Riverside County, Ordinance 787 as amended through 787.11, effective January 7, 2026, which is the source of the language
  • Moreno Valley, Ordinance 1033, adopted November 4, 2025
  • Indio, Ordinance 1824, adopted November 19, 2025
  • Menifee, Ordinance 2025-425, passed November 19, 2025
  • Norco, Ordinance 1135, adopted November 19, 2025
  • Indian Wells, Ordinance 769, adopted February 5, 2026

Read the dates. Three separate city councils adopted the same fence rule on November 19, 2025. That is not a trend spreading outward from one city; it is a county fire department's model ordinance moving through a code cycle with each council taking its turn. Two of the ordinances say so almost explicitly: Moreno Valley's and Norco's both add "Riverside County Fire Department Guidelines" as a fifth item to the four state laws that the model code's own Section 604.3 already requires vegetation to comply with. Moreno Valley's advisory notice goes further, stating that the department "has local Zone 0 requirements currently in effect for new buildings and additions to existing buildings." The county page carries the full text and three more cities we have named as leads but not yet verified.

The San Diego family, which is three years older than the statewide rule

San Diego County's version is a different sentence at a different number, and it is considerably older. The County of San Diego 2023 Consolidated Fire Code, eighth edition, effective April 13, 2023, which by its own description compiles "the County amendments to the 2022 California Fire Code and the ordinances of the unincorporated County fire protection districts," contains Section 4907.9 "Home Ignition Zones" and under it:

"Sec. 4907.9.1 Zone 0 'Immediate Zone' 0-5'. Meaning from exterior wall surface or patio, deck or attachment to building or structure extending 5 feet on a horizontal plane. This zone shall be constructed of continuous hardscape or non-combustible materials. Removal of combustible materials surrounding the exterior wall area and maintaining area free and clear of combustible materials. The use of mulch and other combustible materials shall be prohibited."

That is a Zone 0 rule in force in unincorporated San Diego County more than three years before the Board of Forestry adopted the statewide version. The same sentence appears in the separate ordinances of the Rancho Santa Fe Fire Protection District, effective January 1, 2026, and the Valley Center Fire Protection District, Ordinance 2025-68, finally adopted on October 16, 2025 by a five to nothing roll call. It also appears, word for word, in the City of Santee's separately added Section 603.5.

The dates here run backwards from the obvious story. The county's consolidated 2026 code had its first reading on February 10, 2026, but Valley Center adopted in October 2025 and Rancho Santa Fe was in force on January 1, 2026. The consolidation gathered up language that was already circulating; it did not originate it. The county page has the full account.

A warning if you go looking yourself: the section number is not the fingerprint

We found the Riverside family by searching for "604.11," which worked because every member kept the number. That method then nearly misled us. The 2025 code cycle renumbered San Diego's provision from Section 4907.9.1 to Section 604.12.1, so the same words now sit under a different number, and Rancho Santa Fe's own code-comparison table records the move. Meanwhile Rancho Santa Fe's Section 604.11 is not a fence rule at all; it is "Eucalyptus forests and oak woodlands."

Search the sentence, not the number. A model ordinance keeps its wording across adopters far more reliably than it keeps its numbering across code cycles.

The step almost nobody mentions: your council still has to vote

A fire district cannot simply impose building standards on the cities inside it. Health and Safety Code section 13869.7(a) lets a district adopt building standards more stringent than the state's, and subdivision (c) sets the price:

"The legislative body of the city, county, or city and county, may ratify, modify, or deny an adopted ordinance… No ordinance adopted by the district shall be effective until ratification by the city, county, or city and county where the ordinance will apply."

The districts know it and write it into their own text. Ventura County Fire Protection District's Ordinance 34, adopted October 14, 2025, provides that its provisions "shall apply upon the effective date of this Ordinance or upon the date of said ratification or adoption by the County or any city, whichever is later." The County of San Diego's 2023 Consolidated Fire Code recites the same rule from its side.

The clearest statement of it we have found belongs to the Moraga-Orinda Fire District, which adopted its own 2025 WUI code as Ordinance 26-02 on January 21, 2026 and published this with the notice of adoption:

"These Ordinances shall take effect thirty (30) days after their adoption; however, the building standards in these Ordinances shall not take effect within any municipality located in the District until ratified by the governing body of that municipality. The building standards in these Ordinances shall not take effect within the unincorporated areas of the District until ratified by the Board of Supervisors of the County of Contra Costa."

Moraga-Orinda Fire Protection District, Notice of Adoptions, issued January 28, 2026.

Note what the second sentence does. It is not only cities that have to vote: the unincorporated part of a district waits on the county board. So a district ordinance can be fully adopted, thirty days past its own effective date, and still be waiting on two or three separate legislative bodies before it binds anyone. That is the gap between "the district adopted a Zone 0 rule," which is what gets reported, and "a Zone 0 rule applies at this address," which is what a homeowner needs.

What gets ratified is narrower than the whole ordinance, and the narrowing is revealing. When the Ojai City Council ratified Ordinance 34 on October 28, 2025, it ratified exactly three pieces, the ones its resolution describes as amendments to building standards: Article 3 Section 903, Article 3 Appendix B, and Article 4 Section 604.11. Section 604.11 is the fencing section. The part of a district Zone 0 package that needs a city council's vote is the fence rule.

The practical consequence is uncomfortable but real: two houses a mile apart, in the same district, under the same district ordinance, can be under different law depending on how their councils voted and when. The Ventura County page tracks that roll call, and we have read exactly one of those ratifications in full so far.

Why this is happening now, when almost nothing else local is allowed to move

There is a reason all of this is landing in the same eighteen months, and it is not only the triennial code cycle. Assembly Bill 130 of 2025 amended Health and Safety Code section 17958, effective June 30, 2025, so that:

"Commencing October 1, 2025, to June 1, 2031, inclusive, a city or county shall not make changes that are applicable to residential units in the provisions adopted pursuant to Section 17922 and published in the California Building Standards Code… unless one of the following conditions is met…"

That is a freeze on local residential building-standard amendments lasting nearly six years, passed as housing-cost policy. Six conditions escape it, and two of the six are these:

"(3) The changes or modifications relate to home hardening.
(4) The building standards relate to home hardening and are proposed for adoption by a fire protection district pursuant to Section 13869.7."

Every local rule described on this page was adopted after the freeze began on October 1, 2025, and every one of them legislates on precisely the subject the freeze leaves open. Condition (4) even names section 13869.7, the fire district route these ordinances keep travelling.

We are not the only ones reading it this way, which is worth saying because everything above is us reading a statute. When the Nevada County Board of Supervisors adopted the 2025 code package on December 16, 2025, the local coverage of that meeting summarized the same provision in one sentence: Assembly Bill 130 "provides some relief by imposing a six-year moratorium on most new residential code changes, with exceptions for fire hardening and emergencies." That is a county building department's working understanding of the freeze, reported from its own presentation, and it matches ours.

Two limits, and we would rather state them than let the tidy version stand. First, we are not telling you which of the six conditions any particular council relied on: the ordinances do not recite one, and we have not asked the cities. The claim here is about subject matter, not about the legal basis any individual ordinance rests on. Second, section 17958 never defines "home hardening," so which provisions qualify is untested, and we know of no case on it. The nearest thing to evidence is that Kensington Fire Protection District's ordinance uses the phrase itself, reciting "defensible space and home hardening measures that include Zone Zero standards," which is a drafter reading the exception the way we do and is not authority.

What this means for you

If you are trying to find out whether a Zone 0 rule reaches your house, the question most people ask is close to useless. "Has my city council passed something about fences" usually gets a blank look from whoever answers the phone, because the councillor did not write it and may not remember voting on it inside a package of building code adoptions.

Ask these two instead. They have answers a clerk can actually give:

  1. What does my county fire agency's model ordinance say about Zone 0 and about fences? That is where the text comes from, and it is usually published.
  2. Has my own city or fire district adopted the current code cycle, and if it is a district, has my city council ratified the building standards? That is the date your obligations start, and it is a public record.

And if you find that your jurisdiction has adopted one of these, read the replacement trigger before you hire anyone. In the Riverside family, replacing part of a fence run within five feet obliges you to bring the whole run back noncombustible, which is the reverse of the state rule that most coverage describes.

What we still do not know

  • How many jurisdictions are in each family. We have named three more Riverside cities as leads, on meeting documents rather than codified text, and we do not add a row on a staff report.
  • Whether other counties run model texts of their own. Two families in two counties is a pattern, not a survey. On August 24, 2026 we ran the same searches against Los Angeles, San Bernardino and Santa Barbara counties, looking for a shared operative sentence or a county fire code Zone 0 section, and nothing comparable came back. That is worth exactly what it is worth: a search of code libraries and agency publications is not the same as reading those counties' fire codes line by line, which is what we did for Riverside and San Diego, and it is how we missed Riverside the first time.
  • Which city councils have ratified which district ordinances. We have read one in full.
  • Whether these Zone 0 maintenance duties reach an existing, untouched building, which several of the texts simply do not answer.

We would rather publish those gaps than let a tidy story paper over them. Our standing open questions carry the rest.

Sources

  • The register of local Zone 0 rules in force, which carries every ordinance number, adoption date and citation summarized here.
  • Health and Safety Code section 13869.7, the fire district building standards and ratification statute.
  • Health and Safety Code section 17958, as amended by AB 130 (Statutes 2025, Chapter 22, Section 29), containing the freeze and the home hardening conditions.
  • County of San Diego 2023 Consolidated Fire Code, eighth edition, effective April 13, 2023, Sections 4907.9 and 4907.9.1.
  • City of Ojai Resolution 25-37 (October 28, 2025) and Ventura County Fire Protection District Ordinance 34 (October 14, 2025), read in the City of Port Hueneme council packet.
  • Municipal codes of Moreno Valley, Menifee, Norco, Indio and Indian Wells, and the ordinances of the Rancho Santa Fe and Valley Center fire protection districts, each read at its own publisher.