Data, fact-checked August 20, 2026

Does anyone actually inspect defensible space? CAL FIRE's own numbers say yes

Fact-checked August 23, 2026·Sources at the end of this article

Why we are showing you this

The most common thing people say about defensible space rules is that nobody enforces them. It is worth knowing whether that is true, because it changes how you weigh the cost of doing work now against the risk of doing nothing.

CAL FIRE answers the question itself. It runs a Defensible Space Public Dashboard showing inspections by county and by five-square-mile hexagon, and its own description says it exists so the public and the media can use the data. We read the underlying county layer directly on August 20, 2026, re-queried it on August 23, and got identical numbers both times; the figures below are what it returned.

Inspections are real, routine, and finding non-compliance at scale. What they are not, yet, is Zone 0 inspections.

The caveat that changes how you read every number

This is CAL FIRE's own wording, from the dashboard's configuration:

"inspection numbers included in this map only account for those done by CAL FIRE and Contract Counties within the State Responsibility Area (SRA). Some counties will have none or vastly fewer inspections than expected as they may not have regions containing SRA."

That is the same State Responsibility Area and Local Responsibility Area split that decides which Zone 0 rule will eventually reach you, and it makes county-to-county comparison close to meaningless. San Mateo County shows twenty-two inspections. That is not neglect. Almost all of San Mateo is Local Responsibility Area, inspected by local fire agencies whose work never appears here. Los Angeles County shows 810 for the same reason: most of its wildland-urban interface is Local Responsibility Area served by county and city fire departments. Nine counties show zero, including San Francisco and Sacramento.

So do not read this as a league table. We are not going to tell you which county is "more compliant," because the counties are not inspecting comparable populations under comparable programs, and a diligence ranking built on that would be exactly the kind of confident overstatement this site exists to avoid. Where one of our county pages notes where its recorded rate sits in this table, that is an observation about these records, nothing more.

Statewide, July 2026

We checked the arithmetic rather than assuming it: across all fifty-eight counties, the five outcome columns add up to the inspections column exactly, with no exceptions. So "not yet inspected" is a subset of the total, not an extra number bolted on. Setting those aside leaves 33,729 parcels actually inspected, of which 27,872 were compliant, which is 82.6 percent. We are showing that division rather than just the percentage so you can check it.

The other 17.4 percent is the part worth sitting with. Nearly 5,900 properties in a single month were found not to meet the defensible space rules that are already law, and 1,197 of them had already been found non-compliant at least once before.

Sixteen counties from the dashboard

Read across, not down. The useful comparison is a county against itself: how many of its inspected parcels passed first time.

One row does not fit the month. Santa Barbara's 6,507 is 18.2 percent of every inspection in the state and 2.6 times the next county, while fellow contract counties Los Angeles and Kern show 810 and 242. One county doing a fifth of California's monthly inspections is not credible as a month of work, so we read that row as a bulk posting covering a longer period. It stays in the table because it is what the dashboard returns, but we do not compute a compliance rate from it and neither should you. The county layer carries no date field of its own, which is why a row can disagree with the dashboard's label.

What we would and would not conclude from this

• Inspection is not hypothetical. Whatever you have heard about defensible space rules going unchecked, CAL FIRE recorded more than thirty-five thousand inspections in a single month. If you own property in the State Responsibility Area, being inspected is an ordinary event.
• Failing once is common, and it is not the end of it. The dashboard tracks first, second and third non-compliant findings separately, which only makes sense as a re-inspection ladder. Nearly 1,200 properties statewide are on at least the second rung.
• The county spread is enormous, and mostly not about diligence. Marin's inspected parcels came back compliant 55 percent of the time (1,018 of 1,835); Placer's did 61 percent (741 of 1,209); Riverside's did 88 percent (2,012 of 2,289). Before concluding anything about any of them, note that they are inspecting different kinds of property under different programs, and that Contract Counties run their own inspections and report them separately.
• We would not use this to predict Zone 0 enforcement. Nobody knows yet how the statewide rule will be inspected, because it has no effective date. See what we still do not know.

Inspections are common. Citations are almost unheard of.

The dashboard tells you inspections happen. CAL FIRE's statutory annual report, required by Public Resources Code §4137, tells you what happens next, and the answer is startling.

CAL FIRE Office of the State Fire Marshal, 2024-25 Fire Prevention Report (Public Resources Code §4137), read August 20, 2026

Three. Not three thousand, or three hundred. And the six Contract Counties that inspect alongside CAL FIRE, which between them ran a further 66,633 inspections, issued none at all. Put the two together, which is how the department states its own target, and the year runs to 315,036 inspections against three citations, about one per 105,000. All three were in the Southern Region; the Northern Region issued zero.

This is not a story about a program failing to hit its numbers. The report states the department's own target: the goals "for defensible space inspections were 250,000 and 100,000 acres for fuels reduction". On the scope that target covers, CAL FIRE and the Contract Counties together, the year came in at 315,036. It did not miss the quota. It exceeded it by a quarter and cited practically nobody, which is a choice about how the program is run rather than a shortfall.

What this does and does not tell you

• Being found non-compliant is common; being cited is not. If your worry is a penalty landing on your doormat, the record says that is rare. If your worry is fire, the citation rate is not the number that matters.
• Do not read the earlier years as a trend. Citations ran 1,049 in FY 2022-23 and 9 in FY 2023-24 before this year's 3, and it is tempting to call that a collapse. The report itself blocks that reading: "In previous reports this included Contract Counties defensible space inspections and citations, whereas those figures are now reported separately." Different universes. We are not going to draw a line through them.
• These are not Zone 0 numbers. They are inspections against PRC §4291 in the State Responsibility Area, for a year that ended more than twelve months before the Zone 0 rule was even adopted. Nobody knows yet how Zone 0 will be inspected or enforced, and this report cannot tell you. It also does not cover Local Responsibility Area enforcement under Government Code §51182 at all.
• One figure in the report disagrees with itself. The summary bullet gives 637,879 estimated eligible parcels, while the detail table's two regional rows are 375,022 and 301,857, which sum to 676,879. We use 676,879 because the arithmetic supports it and 637,879 looks like a transposed digit, and we are telling you rather than quietly choosing.

What the state's own inspection guide tells an inspector about Zone 0

There is a document behind all of these numbers, and it answers the question this site gets asked most often better than any press release. The Office of the State Fire Marshal publishes a Model Defensible Space Program and inspection guide, required by Government Code section 51182(d)(1), for cities and counties to use in enforcing defensible space. The edition on the department's site is the 2023 edition, which is to say it predates the statewide Zone 0 regulation entirely, and it already contains a section headed "Inspection Criteria for Zone 0."

Read what is in that list, and what is not. The criteria are fuel removal: remove fuels and items that could catch fire within the first five feet of or above the structure; remove fuels adjacent to or under combustible decks, porches, balconies and stairs; no combustible bark or mulch allowed; branch clearance at chimneys and stovepipes; dead and dying vegetation removed, roof and gutters included; exposed firewood relocated outside Zone 0.

Fences are not in that list. They appear a few lines later, under a different heading: "Suggestions and Education in Zone 0," where the guide says to "Replace combustible fencing, gates, trellis, and arbors attached to the 'Structure'," alongside using hardscape such as gravel or pavers and limiting combustible furniture on decks. In the state's own model program, in other words, clearing the first five feet is a criterion an inspector checks, and replacing your fence is advice an inspector gives. That is exactly the distinction this site was built to keep, and it is the state's, not ours.

Two footnotes worth carrying. The guide defines "structure," for ember-resistant-zone purposes, to include "any attached or detached deck that falls within Zone 0 and/or Zone 1," which is broader than the statute's own reference to an attached deck. And this is the layer that Public Resources Code section 4291(h) holds still: the department may not change its defensible space inspection practices and forms to implement the ember-resistant zone until the State Fire Marshal posts a written finding that the Legislature has appropriated sufficient resources. So the guide quoted here is not a historical curiosity. Until that finding appears, it is the inspection framework.

What this is not

These are inspections against the defensible space rules that are in force today, under Public Resources Code §4291. Those rules cover Zone 1 and Zone 2, the area from the structure out to one hundred feet. They do not include a Zone 0 ember-resistant zone requirement.

The statewide Zone 0 regulation was adopted on August 19, 2026 and is not in effect: it still needs Office of Administrative Law review and filing with the Secretary of State. No inspector is currently citing anyone under it, anywhere in California. If someone tells you your first five feet failed a state Zone 0 inspection, that is not a thing that can have happened yet. What can reach you today is a local ordinance, and at least thirty-five jurisdictions have one.

Frequently asked questions

Sources

• CAL FIRE Office of the State Fire Marshal, Model DSpace Inspection Guide, 2023 Edition (the model defensible space program required by Government Code section 51182(d)(1)), read August 23, 2026: the Zone 0 inspection criteria, the separate “Suggestions and Education in Zone 0” list containing the fence item, and the definition of structure including attached or detached decks

• CAL FIRE OSFM: 2024-25 Fire Prevention Report (Public Resources Code §4137)
• CAL FIRE: Defensible Space Public Dashboard (ArcGIS Experience, read August 20, 2026 and re-verified unchanged August 23; layer metadata reports last edit August 17, 2026. On the August 23 re-check we also queried the underlying feature layer directly and re-summed all fifty-eight county rows: they add to 35,817 inspections, 27,872 compliant and 2,088 uninspected, which is exactly the statewide figures quoted above, and nine rows carry zero inspections)
• Public Resources Code §4291 (State Responsibility Area defensible space)
• Office of the State Fire Marshal: Fire Hazard Severity Zones
• California Board of Forestry and Fire Protection: Defensible Space, Zones 0, 1 and 2