For jurisdictions considering automated traffic enforcement, the real challenge isn’t launching a pilot. It’s knowing how to turn that pilot into a credible, long-term safety program. The municipalities that succeed understand one thing early on: a pilot is not a trial run for technology. It is a trial run for policy, operations, and public trust.
Across North America, automated speed enforcement programs tend to follow a common lifecycle. When done well, this progression creates durable programs that scale responsibly and withstand public, political, and legal scrutiny. Successful examples such as Albuquerque and Fairfax County illustrate how cities move from proof of concept to permanent deployment.
Phase 1: Establish authority and define the rules of the pilot
Every successful program starts with governance. Before cameras are installed, cities confirm enabling authority at the state level and adopt local ordinances or administrative rules that define where enforcement can occur, how violations are issued, and how drivers can contest citations.
Fairfax County’s school-zone speed enforcement program launched explicitly as a pilot in early 2023, with an initial deployment of cameras at a limited number of school-zone locations. From the outset, county officials were clear that the program was designed to test effectiveness and inform future policy, not to roll out at scale immediately. Public communications outlined when cameras would be active during school-zone hours, the speed thresholds that would trigger enforcement, and how warnings and citations would be issued and processed. By framing the initiative as a time-bound, data-driven pilot, the county created room to evaluate outcomes, engage the community, and make evidence-based decisions about expansion, rather than locking itself into an inflexible model. This step is foundational. Clear rules protect the city, guide vendors and law enforcement partners, and give the public confidence that enforcement is predictable and fair.
Phase 2: Prove the safety need with baseline data
A pilot must be anchored in evidence. Before enforcement begins, cities typically collect baseline data such as average speeds, the percentage of drivers exceeding the limit, crash history, and school-zone traffic patterns. This data serves two purposes: it justifies the pilot and creates a benchmark against which results can be measured.
In Fairfax County, pre-pilot speed studies revealed widespread speeding in school zones during arrival and dismissal periods. Thousands of vehicles were recorded traveling more than 10 mph over the posted limit, providing evidence for a clear safety risk to children and staff. That data influenced site selection and gave decision-makers a factual basis for action.
Without this step, programs likely struggle later to demonstrate impact or defend expansion decisions.
Phase 3: Design the pilot for evaluation, not optics
Pilots that transition smoothly to permanent programs are deliberately scoped. They focus on a limited number of locations, use standardized signage, and define success metrics upfront, most commonly reductions in speeding and improvements in compliance.
Fairfax County launched its pilot with cameras at a small number of school zones, allowing the county to monitor results location by location. This disciplined approach made it easier to analyze trends, communicate findings to elected officials, and refine operational practices before scaling.
A pilot should answer one core question: Does this approach meaningfully change driver behavior in our community?
Phase 4: Build public understanding and trust
Public acceptance is not a byproduct of enforcement, it is an outcome of transparent communication upfront. Jurisdictions that plan for permanence invest early in education: advance signage, warning periods, clear explanations of how enforcement works, and accessible information on how to resolve citations.
Albuquerque’s automated speed enforcement program followed a structured rollout designed to balance driver adaptation with safety goals. The city began the program on April 25, 2022, initially issuing warnings from cameras deployed across key corridors and high-speed locations, giving drivers time to adjust before transitioning to full citation issuance starting September 6, 2022. This phased approach allowed residents to familiarize themselves with camera locations and enforcement criteria.
The city also publicly publishes program details, including how to pay fines, request hearings, set up payment plans, and pursue alternative resolution options such as completing four hours of community service in lieu of paying the fine. Albuquerque’s official program page provides comprehensive guidance on these options as well as data on camera deployment and citation activity, and the city continues to expand from an initial group of cameras toward a larger network of speed safety units across the city. As a result of transparent communication and visible safety improvements, city officials report that residents are not just accepting automated enforcement, they’re asking for more cameras. Albuquerque spokesperson Dan Mayfield has noted that continued demand from the community is one of the factors driving expansion plans, with the city adding additional automated speed enforcement units to cover more high-risk locations as part of its Vision Zero strategy.
Phase 5: Operate like a permanent service
Moving from pilot to policy requires operational maturity. Permanent programs demand consistent quality assurance, secure evidence handling, defined adjudication processes, and reliable customer support.
Albuquerque’s experience illustrates this shift. After launching its program citywide, the city expanded enforcement locations and refined back-office operations to handle citation processing, hearings, and customer inquiries at scale. The result is a program that functions as an ongoing public safety infrastructure, not a temporary initiative.
Phase 6: Use pilot results to justify expansion
Expansion should be data-driven and deliberate. Pilot findings, such as speed reductions, compliance trends, and operational performance, become the foundation for policy decisions, budget approvals, and long-term deployment plans.
In Fairfax County, what started in just a handful of school zones quickly showed enough impact to justify expanding the program in phases. In Albuquerque, demonstrated need and operational readiness supported growth from an initial deployment to a significantly larger network of speed safety cameras across the city.
In both cases, expansion was framed as the next phase of a measured strategy — not a sudden escalation.
The common thread: pilots succeed when cities plan for permanence
From school zones in Virginia to work zones in Washington State, red-light intersections in Chicago, and urban corridors in New Mexico, the pattern is consistent. Jurisdictions that successfully transition from pilot to permanent automated enforcement programs treat the pilot as the first chapter of a long-term operating model, based on data, transparency, and public accountability.
Pilot-to-Policy Readiness Checklist
Before launch
- Confirm state authority and adopt local ordinance or rules
- Collect baseline speed and crash data
- Define pilot locations, duration, and success metrics
During the pilot
- Implement clear signage and lead with public education
- Use a warning phase where appropriate
- Publish results and program updates
Preparing for expansion
- Evaluate speed reduction and compliance outcomes
- Validate operational workflows and QA processes
- Establish adjudication, customer service, and payment options
- Develop a phased, transparent expansion plan
When cities follow this path, automated enforcement stops being a “pilot project” and becomes what it is meant to be: a reliable, equitable tool for protecting people where risk is highest.
