Codify — Article

California SB352 mandates community and fence‑line air monitoring in disadvantaged areas

Requires the state board to plan and target advanced community sensors, lets districts compel on‑site fence‑line monitors, publishes data online, and creates annual legislative reporting — shifting monitoring and accountability to local regulators and regulated sources.

The Brief

SB352 directs the State Air Resources Board (state board) to evaluate and roll out a network of community air monitoring systems focused on sensitive receptors and communities designated as disadvantaged. The statute defines both community and fence‑line monitoring, requires a statewide monitoring plan developed with scientific and community stakeholders, and tasks local air districts with deploying systems in prioritized locations.

Implementation is subject to available funding, but the bill sets firm operational design elements: districts may force stationary sources that affect priority locations to install fence‑line or on‑site real‑time monitoring; active community monitoring must run for a minimum five‑year period; the state board must publish data online; and it must report annually to legislative budget subcommittees with specified contents, including enforcement activities and expenditures. Those features make monitoring data more visible and create new operational and potential compliance burdens for districts and regulated sources.

At a Glance

What It Does

The bill requires the state board to create a monitoring plan and select high‑priority locations (sensitive receptors and disadvantaged communities) for deployment of advanced community air monitoring systems. Districts must install monitors in selected locations and may require on‑site fence‑line monitoring from stationary sources affecting those locations.

Who It Affects

Local air districts, stationary sources that materially affect selected communities, disadvantaged communities and sensitive receptor sites (schools, hospitals, day cares), environmental justice groups, and vendors of advanced sensing equipment are directly affected.

Why It Matters

This shifts ambient monitoring from sparse regional networks to hyperlocal, community‑focused sensing, increases publicly available air quality data, and creates a recurring reporting obligation to the Legislature — potentially altering enforcement priorities, compliance costs, and community advocacy strategies.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

SB352 sets a programmatic architecture for placing advanced air sensors where exposure risks are greatest. It begins by defining key terms—community air monitoring systems are advanced ambient sensors near sensitive receptors and in disadvantaged communities, while fence‑line systems monitor pollutant concentrations at or adjacent to stationary sources.

Those definitions frame what kinds of instruments and locations the statute targets.

The state board must prepare a monitoring plan in consultation with scientific bodies (the Scientific Review Panel on Toxic Air Contaminants and OEHHA), local air districts, environmental justice organizations, industry stakeholders, and others, and hold public workshops in the state's northern, central, and southern regions while developing that plan. Using the plan’s findings, the state board will identify the highest‑priority locations based on sensitive receptor placement and exposure burdens.

Once the board selects sites, local districts are obliged to deploy community air monitoring systems in those locations by the statutory deadlines; districts can also require stationary sources contributing to the burden to install fence‑line or on‑site real‑time monitors, taking into account feasibility and cost.The statute envisions an expanding, iterative network: the state board will select additional locations annually (subject to funding), require deployment within a year of selection, and update the monitoring plan every five years. The bill builds visibility and accountability into the program — districts must forward collected data to the state board, which must publish it on its website, and the state board must deliver an annual report to legislative budget subcommittees explaining implementation status, best practices, lessons learned, enforcement actions, outcome data, and expenditures.

The bill also gives legislators the ability to summon the state board chair and district executives to testify on implementation upon request.

The Five Things You Need to Know

1

The bill legally defines “community air monitoring system” and “fence‑line monitoring system,” tying deployments to sensitive receptors and disadvantaged communities.

2

For locations the state board designates as highest priority, districts had to deploy community air monitoring systems by July 1, 2019, and for later selections districts must deploy systems within one year of designation.

3

Districts may require stationary sources that emit pollutants into, or materially affect, priority locations to install fence‑line or other real‑time on‑site monitoring, with technical capability and cost considered.

4

Monitoring in a selected location must be active for at least five years, with the district and state board able to agree to successive five‑year extensions.

5

The state board must publish community monitoring data online and, beginning March 1, 2027, report annually to the Legislature’s budget subcommittees on implementation status, enforcement activities, outcome data, and expenditures — and officials must appear to present on progress upon committee request.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section (a)

Definitions that set the scope of equipment and places covered

This subsection supplies operational definitions for community air monitoring systems, fence‑line systems, disadvantaged communities, sensitive receptors, nonattainment pollutants, and stationary sources. Those definitions determine what technologies and locations count under the statute, and they concentrate the program on ambient sensing near hospitals, schools, day cares, and communities designated under Section 39711.

Section (b)

State board monitoring plan and stakeholder process

The state board must craft a monitoring plan in consultation with scientific panels, OEHHA, districts, environmental justice organizations, and industry, and hold public workshops in northern, central, and southern California. Practically, that requirement embeds multi‑stakeholder review and forces the board to document technological availability, effectiveness of advanced sensors, and the need for additional systems before moving to site selection.

Section (c)

Priority site selection and district deployment duties

Using the monitoring plan’s findings, the state board selects the highest‑priority locations for community monitoring and the districts containing those sites must deploy systems by the statute’s deadline. This subsection also authorizes districts to require fence‑line or other on‑site real‑time monitors from stationary sources that emit into, or materially affect, the priority locations, subject to considerations of technical capability, cost, and incremental data value — creating a conditional pathway for on‑site monitoring mandates.

3 more sections
Section (d)

Annual expansion and public hearing requirement

Subject to funding, the state board must select additional locations every year and districts must deploy monitoring within one year of selection. The state board also must hold an annual public hearing on the network’s status and recommend improvements, institutionalizing transparency and a recurring opportunity for public input and program refinement.

Section (e) and (f)

Five‑year updates and data reporting/publishing

The state board must update the monitoring plan every five years (subject to funding) and the districts are required to provide their collected air quality data to the state board. The state board’s duty to publish the aggregated data online creates a centralized public repository for community sensor outputs, which carries implications for data handling, comparability, and public interpretation.

Section (g)

Annual legislative reporting and oversight appearances

By March 1, 2027, and annually thereafter, the state board must report to legislative budget subcommittees on implementation status, best practices, lessons learned, enforcement activities, outcome data (including emissions reductions where available), and expenditures. The statute also requires that the state board chair and relevant district executives appear before legislative committees to present progress when requested, strengthening legislative oversight of the monitoring program.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Environment across all five countries.

Explore Environment 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 of disadvantaged communities and nearby sensitive receptors — they gain locally situated pollutant measurements that can reveal acute exposure hotspots and support community health responses.
  • Environmental justice and community groups — they receive timely, localized data to support advocacy, public education, and calls for enforcement or mitigation in overburdened neighborhoods.
  • Public health agencies and healthcare providers — more granular exposure data can inform health advisories, surveillance, and targeted interventions around schools, hospitals, and day cares.
  • State and local regulators — access to community monitoring data can help prioritize inspections, direct enforcement resources, and evaluate whether existing controls reduce local exposures.
  • Manufacturers and vendors of advanced sensing technologies — the law creates procurement opportunities and standards demand for sensors and data platforms.

Who Bears the Cost

  • Stationary sources affecting priority locations — the statute allows districts to require fence‑line or on‑site real‑time monitors, which can mean installation, calibration, and operational expenses for facilities.
  • Local air districts — they must deploy, maintain, and transfer data from community monitors and run public outreach and hearings, tasks that require staff, procurement, and ongoing maintenance budgets.
  • The state board — it bears planning, data aggregation, website publishing, five‑year plan updates, and annual legislative reporting responsibilities that require technical and administrative resources.
  • State and local taxpayers or funders — because deployments and ongoing monitoring are conditioned on ‘available funding,’ costs will fall on appropriations, grant programs, or reallocated district budgets.
  • Small businesses and smaller stationary sources — while the statute permits consideration of cost, the ability of districts to compel on‑site monitoring could disproportionately impact smaller operators with limited compliance capital.

Key Issues

The Core Tension

The bill pits the urgent need for real‑time, neighborhood‑level air quality visibility in overburdened communities against the technical, fiscal, and legal prerequisites for producing defensible, enforcement‑grade data: expanding monitoring and public transparency helps communities and regulators spot problems quickly, but doing it reliably and equitably risks significant costs and requires administrative capacity and clear rules that the statute largely delegates to later decisions.

The statute is explicit about goals but equivocal about funding and enforcement. Multiple provisions are prefaced with “subject to available funding,” which creates real uncertainty about how many communities will actually receive monitors and how durable deployments will be.

That caveat crystallizes a common implementation problem: the law sets programmatic expectations without securing the revenue streams needed for procurement, sensor maintenance, data quality assurance, and staff capacity.

Technical and evidentiary tensions are also central. The bill favors ‘‘advanced sensing monitoring equipment’’ but does not define performance standards, calibration regimes, or data QA/QC thresholds needed for regulatory or legal reliance.

Community sensors can be excellent for trend detection and public awareness but often require co‑location with reference instruments and robust calibration to support enforcement actions. Requiring fence‑line monitoring of stationary sources raises legal and permitting questions: how will districts translate a post‑selection requirement into permit conditions or compliance orders, and what cost‑sharing or exemption mechanics will apply?

Finally, publishing raw sensor data online increases transparency but heightens risks of misinterpretation, public alarm, and preemptive litigation without contextualized analysis and clear metadata.

Operationally, districts will face procurement, staffing, and data‑integration challenges. They must decide which sensors meet the statute’s objectives, how to manage large, continuous datasets, and how to present findings to the public in a scientifically defensible way.

The statute creates a richer evidence base for communities and regulators, but realizing that promise depends on choices—technical standards, funding commitments, and clear enforcement pathways—that the text leaves for future administrative action.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.