AB 1305 would require every California air pollution control and air quality management district to publish, using a template developed by the state Office of Data and Innovation, an online map of permitted facilities tied to active permits that require or previously required one or more emission reduction credits. The template must be designed with input from local community groups and must present permit data in a standardized, visually accessible way that supports real‑time monitoring and third‑party analysis.
This bill matters because it shifts the informational burden for permit oversight: rather than relying solely on agency inspections, communities and external analysts would get structured access to the permits, the credits used, and the emissions control technologies promised. That transparency can strengthen local accountability and research, but it also creates technical, resource, and confidentiality questions for districts and permittees — and the text contains no implementation timeline or explicit protections for confidential business information.
At a Glance
What It Does
The bill directs the Office of Data and Innovation to design a uniform website template and requires each air district to publish a map of permitted facilities for active permits that require or required emission reduction credits. District maps must include specific data fields such as site address, permitholder contact, parent organizations, equipment/process descriptions, credits used, and the BACT/BARCT or other control measures tied to the permit.
Who It Affects
Directly affected are California air districts (responsible for implementing and hosting the maps), operators of facilities holding permits that used emission reduction credits, and the Office of Data and Innovation (responsible for template design and community consultation). Indirectly affected are community groups, researchers, public health agencies, and third‑party data analysts who will consume the data.
Why It Matters
The measure standardizes permit disclosure across jurisdictions, enabling cross‑district analysis and community oversight where permit terms and credit usage were previously fragmented. For professionals, it signals new compliance visibility, potential reputational risk for permitholders, and a likely need for districts to allocate technical and staff resources to publish and maintain standardized datasets.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 1305 creates two linked obligations. First, it charges the Governor’s Office of Data and Innovation (ODI) with developing a single website template that districts must use to display permit information.
ODI must consult local community groups while designing the template and is given a set of design objectives — from simplifying complex data and maximizing accessibility to enabling predictive and real‑time analysis. The bill frames these objectives as requirements for how permit information should be presented, not as optional features.
Second, air districts must publish, using the ODI template, an interactive map of permitted facilities for all active permits that may release or control air pollutants and that require or previously required the use of one or more emission reduction credits. The statute enumerates six discrete data elements the map must include: site address; permitholder contact information; business and parent organization names; description of the permitted equipment or process; a list of credits used and the emissions quantities allowed; and any BACT, BARCT, or other emissions control measures specified by the permit.The bill does not prescribe a deadline or phased rollout for compliance, nor does it create a centralized state host for the district maps — each district must post the map on its own website using the template.
It also contains a reimbursement clause that says no state reimbursement is required because local agencies can levy fees sufficient to cover the work. The text does not include explicit rules for handling confidential business information, verification requirements to ensure that permit conditions are being implemented, or standardized definitions for phrases like "active permit" or what constitutes sufficient "real‑time monitoring." These omissions will drive much of the implementation work and potential disputes between districts, permitholders, and community stakeholders.
The Five Things You Need to Know
The Office of Data and Innovation must develop a single internet website template and consult local community groups about its design goals.
Each air district must post an interactive map for all active permits that require or previously required one or more emission reduction credits, using the ODI template.
The map must include six core data elements: site address; permitholder contact; business and parent names; scope/description of equipment or process; list and quantity/type of credits used; and any BACT/BARCT or other control measures required by the permit.
The bill does not set a compliance deadline, nor does it create a centralized state portal; districts host the maps on their own websites.
A reimbursement clause asserts the state need not reimburse local agencies because districts can charge fees sufficient to pay for the mandated program.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Legislative findings and policy rationale
This section summarizes why the Legislature believes standardized permit disclosure is necessary: disparate monitoring capacity, concentrated pollution impacts on disadvantaged and tribal communities, and a lack of public mechanisms to verify that BACT/BARCT commitments are implemented. In practice, the findings set the policy frame that transparency and community empowerment justify the regulatory change, which can influence how aggressively stakeholders push for detailed technical features in the template and data release.
Office of Data and Innovation template development and community consultation
Subsection (a) assigns ODI the job of building the website template and requires ODI to consult local community groups on design. The statute lists specific design objectives — simplify and visualize complex data, reveal trends, enable data‑driven decisionmaking, maximize accessibility, make real‑time monitoring possible, enable predictive tools, and enhance storytelling — which will shape ODI’s technical specifications. Practically, ODI will have to translate these high‑level goals into concrete data schemas, visualization standards, accessibility features (e.g., screen‑reader support, language options), and API or download formats for third parties.
District obligation to publish maps and the six required permit data fields
Subsection (b) requires each district to use the ODI template to publish a map of permitted facilities for active permits that may release or control pollutants and that require or required emission reduction credits. It enumerates six required items: site address; permitholder contact; business and parent names; description of equipment/process; credits used with types and quantities allowed; and any BACT, BARCT or other control measures specified by the permit. This fixes a minimum disclosure floor but leaves districts to resolve data extraction from permit files, geocoding, and presentation nuances such as how to display aggregated versus unit‑level credit usage.
No state reimbursement required
Section 3 cites the constitutional reimbursement rules and concludes that the state does not owe reimbursement because districts can levy fees to pay for the program. This is a common legislative drafting device that shifts the fiscal burden to local authorities unless they successfully challenge it. For districts, the clause means they will need to budget for template adoption, data preparation, site hosting, and ongoing maintenance — either through existing fee schedules or new charges.
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
- Frontline and disadvantaged communities — gain structured, searchable access to permit terms, credits used, and control technologies, enabling community monitoring and advocacy where local inspections are limited.
- Environmental justice and community organizations — receive a standardized data platform to track permit activity across districts and build cases for enforcement or policy change.
- Researchers and public health analysts — get machine‑readable, spatially consistent permit data that supports cross‑district studies of exposure, permitting trends, and correlations between credits and local air quality.
- Journalists and watchdogs — obtain a single, predictable format for uncovering patterns, such as clusters of facilities using credits or recurring control‑technology gaps.
Who Bears the Cost
- Air pollution control and air quality management districts — must extract, normalize, geocode, host, and maintain permit data in the mandated template, plus consult with communities; those activities require staff time, technical infrastructure, and possibly new fee structures.
- Permitholders (facility owners/operators) — face increased public visibility of permit terms and credit usage, raising reputational risk and the potential for community pressure or legal scrutiny if permit conditions are perceived as inadequate or unenforced.
- Office of Data and Innovation — must design a usable template, conduct community consultations, and produce technical specifications and guidance; ODI may need resources to run a robust stakeholder process and produce accessible tools.
- Local governments and ratepayers — indirectly, because districts are expected to fund implementation through fees, which could lead to higher permit or service charges that ultimately fall on facility operators and potentially on local taxpayers or customers.
Key Issues
The Core Tension
The bill pits the legitimate public interest in standardized, accessible permit data against the practical costs and legal complexities of producing accurate, timely, and non‑confidential datasets: greater transparency empowers communities but imposes technical, financial, and potential privacy burdens on districts and permitholders — and disclosure without verification may produce false confidence or adversarial outcomes.
The bill prescribes what data fields must appear and what high‑level design goals the template should meet, but it leaves crucial implementation mechanics undefined. It does not set a timeline for ODI to deliver the template or for districts to publish maps, nor does it require centralized hosting, standardized data formats (beyond the template), or independent verification that disclosed permit conditions are being complied with.
Those gaps mean outcomes will vary by district capacity: well‑resourced districts may publish robust, regularly updated maps, while underfunded districts could post minimal or stale datasets that still create community expectations they cannot meet.
A second tension involves confidentiality and legal exposure. The statute requires disclosure of permitholder contacts, parent company names, and credit quantities but does not carve out protections for confidential business information (CBI) or define how to reconcile state “public record” obligations with trade‑secret claims.
That omission could trigger disputes or redactions that undercut the standardization goal. Finally, increased disclosure shifts monitoring duties toward communities and third parties: transparency does not equal enforcement.
Without clearer standards for data quality, update frequency, or verification, the maps could encourage activist or litigation responses based on incomplete or misinterpreted data, creating reputational and legal risks for permittees and administrative burdens for districts.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.