Redmond police outline timeline and concerns for proposed photo-enforcement program

Redmond, Ore. — The Redmond Police Department told the City Council it has received three qualifying proposals for an automated photo‑enforcement program and expects a recommended vendor after a scoring‑committee meeting tomorrow that will lead to a formal council presentation next week.

The briefing, given by Curtis Chambers, lieutenant with the Redmond Police Department, outlined where the request for proposals (RFP) stands and what councilors should expect if they authorize staff to negotiate with a recommended vendor. "Today is unique because today is the last day for committee members to score," Chambers said. He told the council the scoring results and the vendor recommendation will be shared at the formal council presentation the following week.

Councilors and staff stressed why the program matters to Redmond: the department framed the system as a traffic‑safety tool intended to change driver behavior and serve as a force multiplier for limited patrol resources. Chambers said the department hopes to have a signed contract and begin implementation work over the summer, with equipment build‑out and community outreach running in parallel. He proposed a target operational date of Dec. 1, with the statutorily required 30‑day warning period before citations are issued.

Key details the council pressed for included accuracy testing, contract terms, vendor responsibilities and budget implications. Chambers said vendors use different camera hardware and that the selected vendor would be responsible for maintaining equipment integrity and conducting remote and on‑site testing as specified in the contract. "Our vendor will be tasked with maintaining the integrity of their program," Chambers said. He said vendors would provide testing documentation and that the city would have access to those tests.

Council members repeatedly asked whether independent or third‑party testing would accompany vendor self‑certification; Chambers said his office expects vendors to provide testing records and described that reasonable practices include periodic on‑site verification and vendor reports. He compared vendor testing to routine radar checks used by patrol officers, noting departments rely on vendor or internal testing rather than state weights‑and‑measures certification for this equipment.

On financing, Chambers said the proposals contained differing revenue‑share and fee models: some vendors propose flat monthly fees, some a hybrid of flat fees and a percentage of citation revenue. He said the city budget was left neutral this year on the assumption that the program would at least cover its operating costs. Chambers told the council that agencies elsewhere reported either net‑zero costs or net revenue over time, but he cautioned, "there's always the possibility of what we don't know." He said some citation proceeds are processed by the Justice Court and that state mandates impose deductions from citation revenue.

Councilors also asked about contract length and termination language; Chambers said typical proposals run three years with the option of two extensions and that staff will seek contract clauses such as 30‑day cause termination or a 90‑day no‑cause exit where practical. He said the city attorney will be involved in negotiations and that the final contract will return to council for approval.

Several operational clarifications followed: the department plans to assign review work to officers on light duty or a traffic‑safety staff position; vendors will host data in a cloud environment; and camera site selection will be part of post‑contract work with the vendor. Chambers said location recommendations will be refined once the vendor is selected and that community outreach would ramp up after contract negotiations begin.

The council did not take formal action during the briefing. Chambers asked for direction to present a recommended vendor and request authorization to negotiate, and he said council could stop the process at any later point before a contract is executed. The next formal steps, as described to councilors, are the scoring committee's vendor recommendation, a formal presentation seeking authorization to negotiate, contract negotiations with city attorney involvement (estimated to take about a month), and then council consideration of a final contract.

What was not decided: council did not approve a vendor, set a final budget, or adopt a contract; those items were described as future actions pending the scoring committee recommendation and negotiation. The department's presentation included multiple open items staff said would be finalized through negotiation and community outreach.

Sources: briefing by Curtis Chambers, lieutenant with the Redmond Police Department, and council questions during the informal session.