Redmond staff brief council on proposed five-year photo‑radar contract, cite safety goals and near‑neutral finances

Redmond staff presented a proposed five‑year contract with a private vendor to install photo‑radar and red‑light cameras across the city and asked council for direction to bring the contract back for formal approval.

The chief of police described the program as a behavioral tool: "the whole goal of this is... change driver behavior and improve traffic safety," and said staff intend a phased rollout. Phase 1 would place devices on city‑managed roadways — a red‑light camera at Northwest 6 and Northwest Maple, a fixed speed camera by Northwest 10th Street near Tomacau Elementary, and one portable unit to move among data‑driven hot spots. Phase 2 would target ODOT‑managed corridors such as Highway 97 and will require separate ODOT authorization and additional lead time.

Staff and city finance staff presented the vendor's operational and revenue model and a staff spot‑check of that data. Finance described a simple funnel used for budgeting: of 100 photo‑captured incidents, roughly 68 would become citations and about 51 would be paid; "about 30% of the revenues are coming to the city," staff said, and that city share is applied to vendor fees and program costs. At an 18‑month maturity point — the period staff used to gauge expected behavior change — the presentation estimated near‑neutral monthly program totals (roughly $49,000 projected receipts versus about $46,000 in program costs under the model presented).

Council members pressed operational details that affect costs: who will handle court appearances, how many staff the courts and police would need, and the timing of enforcement. Chuck Faithley, the Justice of the Peace, told council the municipal court is a county department and that the county would be responsible for court staffing; he estimated the court might need an additional 1–1.5 FTE and that officers are only required to attend hearings when a defendant pleads not guilty. Staff acknowledged an early enforcement spike is likely and stressed a built‑in pivot in the contract: the city would run a 30‑day public notice and education period before tickets are issued, review initial data 30 days after activation, and could pause or change the rollout if results warrant.

Contract structure and risk: staff confirmed the contract term discussed is five years and said the current draft contains a contract termination/removal exposure listed at $168,000. They are negotiating a different approach that limits termination/removal to a per‑camera removal fee (staff cited a target range of $7,500–$10,000 per camera); for the seven devices contemplated in Phase 1, that would translate to roughly $70,000 at the higher per‑camera figure. A vendor representative in the meeting said there would be no upfront cost to the city for site construction or back‑office development and that the vendor would retain ownership of equipment while maintaining it for the life of the program.

Data, privacy and security: vendor staff said the city would own the program data but that VeriMobility would host it on a proprietary platform under city‑specified retention rules. Staff outlined retention windows in the draft contract: violation images and related records generally retained 36 months from payment or final adjudication; non‑violation captures retained 30 days from event; warning notices retained 90 days from issuance; written correspondence retained one year; and other program records retained one year from termination. The draft also requires cyber liability insurance (staff cited $1,000,000 per occurrence and $2,000,000 annual aggregate).

Implementation timeline and next steps: staff said they plan community outreach and signage accompanying a 30‑day notice period. If council directs staff to proceed, Phase 1 city locations could be installed with a February sign/post period and citations beginning in March 2026 under the timeline presented. Staff said they will return a formal contract to a council meeting in late October or early November for approval and will use early Phase 1 data (Feb–May) to inform any decision on Phase 2 ODOT locations.

Council did not take a formal vote during the informal briefing. Staff left with direction to return a contract for consideration, armed with clarifications about staffing impacts, the negotiated termination/removal terms, data retention details and vendor insurance.