Littleton police brief council on automated speed enforcement, license-plate readers, drones and AI tools

City police and staff presented an informational update Feb. 4 on automated speed enforcement and a broader suite of law‑enforcement technologies, including automated license‑plate readers, drones and generative-AI report drafting. No action was requested; the council asked staff to continue research and return with more detailed options.

The session focused first on automated speed enforcement — camera-based systems that photograph vehicles for speed violations — and the legal and operational constraints municipalities face under state law. Chief Stevens told the council the Colorado statute in question (transcribed at the meeting as “CRS 424,110.52”) places limits on where photo‑based speed enforcement can operate, requires public notice and signage, and caps fines for civil citations in most locations.

Chief Cory Stevens (Chief Stevens) said the law allows automated enforcement in specified corridors, school zones and construction zones but imposes requirements such as permanent signage for designated corridor locations and reporting of citation counts and revenues on a municipality’s website. He summarized other statutory constraints: the registered owner of a vehicle cannot be compelled to identify the driver in many automated‑enforcement cases; civil citations cannot lead to driver-point penalties at the DMV; and municipalities cannot pay vendors on a per‑citation basis. “The state established a maximum fine of $40,” Stevens said, adding that fines can be doubled in some school or construction zones and that counties and cities must take care in structuring administrative fees and services.

Stevens and staff reviewed equipment options from vendors in the market (Traffic Logix, Genoptic and VeriMobility among those discussed), explained differences among trailer, pole‑mounted and vehicle‑mounted units, and described trade‑offs between purchasing and leasing. The chief noted staffing and administration costs beyond equipment: any photo enforcement system requires human review of captures and a back‑end process to verify plate data, generate mailings and manage appeals. He said vendors’ service models and minimum fees can make cost recovery difficult under the statute’s fine limits: “I think they spent approximately $600,000 on the program, and the program violations generated about a hundred thousand, hundred and 50 thousand,” he said, describing a neighboring city’s pilot that did not meet financial expectations.

Council members raised safety and privacy concerns and asked about efficacy. Chief Stevens said evidence is mixed: some programs reduce speeds at deployment sites but effects can decline over time, and photo enforcement can produce unintended driving behavior (for example, sudden braking at yellow lights in older photo‑red‑light programs). He also described operational questions the council would need to answer before adopting a program: where to place devices (Santa Fe was cited as an example of a high‑speed corridor), what violation threshold to set for citation, whether equipment can limit operation to defined school‑zone hours, and how the city would staff citation verification and potential court hearings.

The presentation moved on to automated license‑plate readers and related private‑sector systems such as Flock Safety. Chief Stevens described ALPR as a force multiplier for investigations and real‑time alerts: cameras can return hits when a plate associated with a suspect vehicle passes a camera, and agencies with access to the shared data sets can receive near‑real‑time notifications. He noted the principal cost driver in ALPR programs is access to data and long‑term storage; municipalities frequently negotiate subscriptions that provide access to privately owned camera networks and shared databases. Stevens warned that vendor consolidation and changing commercial terms can complicate long‑term access to data.

Stevens also described expanding use of drones in policing. The department is using drones for search and rescue, scene documentation (3‑D crash reconstruction), tactical situational awareness and public‑safety monitoring at large events. He said drone costs have fallen while capability has increased and that the department is pursuing Federal Aviation Administration waivers that would enable “drone as first responder” deployment, allowing a drone to reach a scene ahead of officers in some calls.

On generative AI, Stevens described Axon’s Draft 1 tool as a possible way to reduce officer report‑writing time by transcribing body‑worn video and drafting structured reports for officer review. He said the product requires officer verification before submission and that early users have reported a large reduction in time spent drafting reports — a percentage figure from a peer agency was shown during the presentation — but emphasized safeguards and departmental control would be needed before broader use.

Council members signaled interest in continued study and a data‑driven approach. Several asked for a follow‑up that would include fiscal estimates, deployment plans for corridors favored by council and pre/post speed monitoring to assess efficacy. No procurement or pilot was approved at the meeting; staff said they would return with additional analysis and possible pilot options.