Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Public Safety topic
No spam. Unsubscribe anytime.
Bothell council begins exploratory work on body‑worn camera program; no procurement decisions yet
Summary
Staff presented the initiation and planning phases of a proposed body‑worn camera program and answered detailed council questions about funding, privacy, data storage, policy carve‑outs and procurement timelines. Council did not vote; staff will pursue planning, community engagement and return with policy and budget recommendations.
City staff and the police chief briefed Bothell City Council on March 17 about an exploratory effort to evaluate and plan a body‑worn camera program for the police department. The presentation covered project phases, policy options, likely costs, public‑records considerations and community outreach, and the council asked technical and legal questions that staff committed to answer in future briefings.
The program as presented is in an initiation/planning phase funded in the 2025–26 budget; execution and camera procurement would require additional budget approval. The project team described a standard phased approach: initiation to set roles and charter, planning to collect requirements and develop an RFP, and an execution phase that would follow a future budget decision.
Chief Ken Suberck emphasized operational and evidentiary benefits: "Today, approximately 80% of U.S. law enforcement use body warn cameras, according to Politico," he said, arguing the devices can increase transparency, aid prosecutions, identify training needs and reduce legal risk through clearer evidence. He referenced two 2020 officer‑involved shootings where body camera footage would have been helpful: one incident relied on a patrol dashcam, another was captured on a private Ring doorbell that helped exonerate an officer.
Staff also discussed privacy and public‑records implications. Under Washington’s Public Records Act, agencies must process and often redact footage; exemptions commonly include open investigations, juvenile victims or witnesses, domestic‑violence victims, interior private residences and protected health information. Staff noted model policies (including an ACLU model) exist and that other nearby agencies (e.g., Kirkland, Bellevue, Seattle) provide tested policy options and variations such as narrow carve‑outs allowing officers to pause recording in limited circumstances (Bellevue) or a strict always‑on approach (ACLU model).
Council members pressed staff on funding and procurement: whether startup grants were available (staff said Criminal Justice Training Commission grants could cover startup costs, with ongoing program costs considered in future budget processes), data ownership and storage (department owns the data; modern systems typically use cloud storage with vendor security provisions), and whether redactions remove evidence value (staff said original footage and metadata are retained for prosecutors though public redacted copies may remove sensitive content).
Several councilors requested a deeper technical and legal briefing before any procurement: suggested followups include vendor technology deep dives for technically inclined council members, a public‑records law deep dive with the city attorney or outside subject matter experts, and community engagement plans that bring in groups such as domestic‑violence service providers, ACLU of Washington, NAMI, NAACP and equity/advisory boards.
No contract or procurement authorization was requested or approved. Staff said they will return with more detailed policy alternatives (options with and without carve‑outs), procurement requirements, a proposed public outreach plan, and budget scenarios for council review prior to any RFP or purchase.
What to expect next: staff will develop detailed requirements, convene stakeholders and present policy alternatives and budget estimates to council; any procurement or contracts above the city’s threshold will return to council for authorization.
