AB 1379 authorizes a pilot program for automated speed enforcement in seven named California jurisdictions, letting local departments of transportation deploy fixed or mobile speed safety systems on certain high‑risk streets and school zones. The bill pairs deployment permissions with upfront public notice, an impact report and use policy, strict signage and inspection rules, limits on where systems can be used, and protections for photographic and DMV data.
For practitioners, the bill creates a detailed compliance framework: population‑based caps on the number of cameras, mandatory public review and consultation, specific evidence and data‑retention rules (including a prohibition on facial recognition), contract restrictions preventing per‑ticket payment to equipment suppliers, and an 18‑month maximum deployment window unless measurable speed reductions or traffic‑calming measures are achieved. That combination makes AB 1379 a template for how California might scale automated speed enforcement while trying to manage privacy, equity, and vendor‑incentive risks.
At a Glance
What It Does
Authorizes designated cities to run automated speed safety systems in safety corridors, locations with repeated speed‑contest incidents, and school zones, subject to population‑based caps and a requirement to publish a use policy and an impact report. The law mandates signage, routine calibration and inspection, real‑time notification to drivers, and tight limits on data use, access, and retention.
Who It Affects
Local departments of transportation and municipal procurement teams in the named jurisdictions, equipment manufacturers and processing vendors, drivers in affected corridors and school zones, and civil‑liberties groups that will monitor data practices.
Why It Matters
AB 1379 bundles operational controls and transparency requirements with a pilot that—if implemented—would establish a regulatory model for automated speed enforcement in California cities while testing guardrails intended to limit surveillance and perverse contractor incentives.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 1379 lets seven named California jurisdictions set up a limited program to detect and act on speeding using cameras or other electronic speed detection devices. The bill restricts where systems may operate (safety corridors, locations with documented speed‑contest incidents, and school zones) and bans their use on state routes, freeways, interstates, U.S. highways, and county roads under CHP jurisdiction.
Local departments of transportation are responsible for operating the systems and must adopt formal use policies and an impact report before implementation.
The statute requires a minimum public‑information campaign and a 30‑day public review period for both the Speed Safety System Use Policy and the Speed Safety System Impact Report. During the first 60 calendar days after a new system goes live, jurisdictions must issue warning notices rather than fines, and the first violation for drivers going 11–15 mph over the limit in a jurisdiction must be a warning.
The bill further requires signage that reads “Photo Enforced” and shows the posted speed limit within 500 feet of each system’s placement, public listing of camera locations and hours on municipal websites, and regular inspections and calibrations—with at least annual calibration by an independent lab.Data and contracting rules are detailed and restrictive. Photographic and administrative records are confidential and may be used only for authorized purposes; non‑violative images must be destroyed within five business days, and facial recognition is forbidden.
Designated jurisdictions must control contracts with equipment suppliers so that payment is not tied to the number of citations issued, though they may separately hire vendors to process notices and may compensate those processors per notice. The bill also sets technical and operational limits: systems should be angled to capture only rear license plates, notices must exclude rear window images, and a camera at a location cannot operate longer than 18 months unless the municipality documents specific reductions in speed or violation metrics or installs traffic‑calming measures.Operational oversight measures include a requirement that jurisdictions place systems in geographically and socioeconomically diverse locations and report how they complied, and mandated consultation with racial equity, privacy, and economic justice stakeholders during policy and impact report development.
The bill prescribes retention windows for evidence and administrative records, allows the registered owner or an owner‑identified driver to obtain photographic evidence, and requires that contractors treat collected data as confidential and prohibit monetization or repurposing.
The Five Things You Need to Know
Population‑based caps: jurisdictions may operate no more than 125 systems (>3,000,000 pop.), 33 systems (800,000–3,000,000), 18 systems (300,000–800,000), or 9 systems (<300,000), as measured by the 2020 Census.
Initial warnings: the municipality must issue only warning notices (not violations) for the first 60 calendar days after a new system begins enforcing at a location; additionally, a vehicle’s first violation of 11–15 mph over the limit in a jurisdiction is a warning.
Signage and inspection: each speed safety system requires a visible “Photo Enforced” sign with the posted speed limit no more than 500 feet before the unit, and units must be inspected at least every 60 days with annual independent calibration.
Data limits and privacy: photographic evidence that does not produce a notice must be destroyed within five business days, facial recognition is prohibited, and photographic/administrative records are confidential with limited retention windows tied to final disposition.
18‑month deployment rule: a camera at a specific location cannot operate more than 18 months unless the location meets one of three reduction thresholds (85th percentile speed reduction, 20% fewer vehicles exceeding the limit by 10+ mph, or 20% fewer repeat violators) or traffic‑calming measures are added.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions and covered jurisdictions
This section defines core terms—‘speed safety system,’ ‘automated speed violation,’ and ‘indigent’—and enumerates the designated jurisdictions authorized to run the pilot (Los Angeles, San Jose, Oakland, Glendale, Long Beach, Sacramento, and San Francisco). For compliance teams, the important takeaway is that the program is limited to those cities and that local departments of transportation (or equivalent administrative divisions) bear operational responsibility and legal obligations under the article.
Where systems may be used and caps on deployments
The bill restricts deployments to three kinds of locations—safety corridors, streets with documented repeated speed‑contest incidents (defined as at least four law‑enforcement responses in the previous two years), and school zones (with later school‑zone specifics). It also imposes fixed caps on the number of systems each jurisdiction may operate, tied to 2020 Census population bands. Municipal procurement and traffic planners should interpret these caps as hard ceilings that will shape any rollout plan and require careful siting decisions to meet the geographic and socioeconomic diversity mandate.
School‑zone enforcement windows and signaling
When a posted school‑zone speed limit varies by whether children are present, the bill narrows camera enforcement to specific windows (up to one hour before school, 10 minutes after start, one hour at lunch, and up to one hour after dismissal) and requires flashing beacons tied to clocks or manual activation to make enforcement times explicit. This creates operational work for school districts and traffic teams to synchronize beacons and enforcement schedules, and reduces the time during which automated enforcement can generate citations in those zones.
Signage, public listing, inspections, and driver notification
Before enforcing, municipalities must post ‘Photo Enforced’ signs no more than 500 feet ahead of a unit, publish the list of enforced streets and hours online, inspect systems at least every 60 days, and perform independent annual calibration. The statute also requires the systems to provide real‑time notification to drivers when violations are detected—language that will need specification in technical standards (e.g., whether via in‑vehicle messages, roadside feedback signs, or other methods)—and mandates retention of inspection documentation for a period after permanent removal.
Public notice, warning period, and required impact report and use policy
A 30‑day public information campaign must precede enforcement; the governing body must adopt a Speed Safety System Use Policy and approve a Speed Safety System Impact Report after a 30‑day public review. The impact report must assess civil‑liberties impacts, fiscal costs, proposed camera locations and traffic data, and explain why locations in low‑income neighborhoods are being used if deployment is concentrated there. Localities must consult privacy, racial equity, and economic‑justice stakeholders in preparing these documents, which creates formal opportunity—and obligation—for community engagement built into the approval process.
Photographic evidence, admissibility, and confidentiality
Notices of violation must include a clear rear‑license‑plate photograph and exclude rear window images; the statute also states photographic evidence ‘does not constitute an out‑of‑court hearsay statement’ under the Evidence Code. Photographic and administrative records are confidential, generally usable only for authorized program purposes, and are subject to defined retention windows (non‑cite images destroyed within five business days; other evidence and administrative records retained for limited periods tied to final disposition). Registered owners and owner‑identified drivers may obtain copies of photographic evidence, but broader public access to identifiable images is restricted.
Contracting and vendor compensation rules
Contracts with equipment manufacturers must prohibit payment tied to the number of notices issued or as a percentage of revenue; the municipality must retain control over enforcement decisions. Municipalities may, however, contract separately with independent vendors to process notices and may compensate processors on a per‑notice basis. The bill also requires contract language prohibiting vendors from sharing, monetizing, or repurposing collected data, and it demands that municipalities maintain oversight over contractor activities—an arrangement intended to limit perverse incentives but that still permits per‑notice processor payments.
Time limits, performance thresholds, and scope of images
A camera at a given location may operate no more than 18 months unless the jurisdiction documents reductions in the 85th percentile speed or 20% reductions in certain violation metrics, or installs traffic‑calming measures (which can extend operations while measures are planned/constructed). Systems must be aimed to minimize capture of unrelated persons or vehicles, focusing on rear plates. These provisions create clear, measurable exit triggers for each camera and encourage municipalities to combine engineering changes with enforcement.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation 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
- Pedestrians, cyclists, and schoolchildren in deployment corridors — the bill targets high‑risk streets and requires engineering or enforcement actions intended to reduce speed‑related collisions.
- Local departments of transportation — they gain a defined enforcement tool and a tightly specified approval process that clarifies operational responsibilities and limits liability exposure from data misuse (if policies are followed).
- Community safety advocates and municipal planners — the requirement for an impact report and stakeholder consultation gives organized groups formal leverage to influence siting and complementary traffic‑calming measures.
Who Bears the Cost
- Designated jurisdictions/municipalities — they must fund system purchases or leases, inspections and independent calibrations, public outreach, impact‑report drafting, and long‑term oversight and record‑management obligations.
- Drivers, particularly repeat violators and those in enforcement corridors — while the bill builds in warning periods and some indigency definitions, it preserves notice and fine mechanics that will impose costs on those who continue to speed.
- Vendors and contractors — equipment suppliers must accept contracts without per‑ticket payment structures and adhere to strict data‑control clauses, while processors must meet separation and confidentiality rules, increasing compliance costs and contractual complexity.
Key Issues
The Core Tension
The bill attempts to reconcile two valuable but conflicting goals: reducing speed‑related harm through automated enforcement and protecting civil liberties and data privacy. Measures that strengthen one side—longer retention for auditing, detailed public reporting, or broad access to data—tend to weaken the other by increasing surveillance or administrative burden; conversely, tight confidentiality and data constraints reduce transparency and make public accountability and independent evaluation harder. Municipalities must balance crash‑reduction goals, community equity concerns, and the practicalities of procurement and data management without creating perverse financial incentives.
AB 1379 layers detailed operational controls on an automated enforcement pilot, but those controls create difficult implementation questions. The requirement for real‑time notification to drivers is underspecified: the statute does not define acceptable technologies or standards for what counts as ‘real‑time,’ so jurisdictions will need technical specifications to decide whether a roadside feedback sign suffices or whether in‑vehicle messaging is required.
Similarly, the mandate that systems be placed in geographically and socioeconomically diverse locations and that the impact report justify concentrations in low‑income neighborhoods imposes a data‑driven obligation that can be hard to reconcile with crash‑data realities—high‑injury corridors often coincide with disinvested areas, creating predictable political and equity tensions during siting.
Data protections are robust on paper but present trade‑offs. The bill treats photographic and administrative records as confidential and limits retention, and it bans facial recognition; yet it also allows access in response to subpoenas or court orders and lets municipalities retain citation histories for up to three years.
That mix reduces the surface area for mass surveillance but leaves open targeted disclosure. Contract rules ban supplier payment based on citation counts, which reduces obvious perverse incentives, but processors may be paid per notice, reintroducing volume‑based compensation downstream.
Finally, the provision that photographic evidence “does not constitute an out‑of‑court hearsay statement” is unusual and may invite litigation over admissibility and rule‑of‑evidence interpretation, meaning courts could shape how much weight automated photos carry in practice.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.