Committee hears update on automated speed-enforcement pilot; vote called, result not recorded

The Transportation Committee on Sept. 10 received a staff update on the city’s automated speed-enforcement pilot and discussed next steps including site selection, data storage and a contract timeline. Committee members questioned how quickly the cameras could be activated and what safeguards would govern use of license-plate and personal data.

The city presentation began when staff introduced an update on item 0.9, described in the agenda as “an LTUT report updating an implementation plan for the automated speed-enforcement pilot.” Transportation staff said they had completed an initial meeting with a consultant, reduced a preliminary list of candidate locations from 300 to 125 and expected to finalize locations next month. Staff said they had given consultants criteria to consider equity, safety and site constraints when selecting locations.

A public commenter, Fredt, identified in the meeting as director of LA Advouskac (known as SAVE), praised the program’s goal to reduce driver speed, saying, “Safe ha estado registrando el progreso de todos los Safe proyectos y que estamos que están moviéndose rápidamente hacia la implementación.”

Committee members pressed staff on the project schedule and contracting. Staff said vendor selection occurred in June and that final contract signatures were expected within days of the meeting; staff planned a two-week internal review by the city attorney and the city contracts team before returning a final contract. Asked why activation could take six to 18 months, staff explained that joining another city’s procurement could shorten the timeline but that six months was the earliest realistic activation window; in a slower scenario staff said activation could slip to June or July 2026 “in the worst case.”

Members also asked whether civil-liability histories at candidate locations were being considered; staff said they were not reviewing settlement amounts directly but were using collision histories and patterns of high speeds and serious collisions as part of the corridor selection criteria. On data security, staff said license-plate data and other registration information could be retained up to 60 days under the proposed policy, access would be limited to authorized, trained city employees and the city would not sell personal data.

Before ending the item a member moved to approve staff recommendations and the clerk was asked to call the roll on item 0.9. The meeting transcript does not record the vote result for item 0.9.

The exchange included requests from committee members for additional analyses: a request to consider civil-liability records as an indicator when prioritizing locations, and a request for staff to accelerate activation where possible to better align with the pilot window.

Looking ahead, staff said they would return the contract for legal review and bring additional materials, including their impact analysis and final site list, to the committee for subsequent action.