Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Governance topic
No spam. Unsubscribe anytime.
Redmond council debates ombudsperson role, agrees to staff-crafted auto-reply and further review
Summary
Councilmembers spent an extended portion of the meeting debating a draft ombudsperson guidance document, raising concerns about accountability, when to defer to staff, rotation of the role, and the mayor-council email process; council leadership will refine the document and staff will prepare a sample auto-reply.
Redmond council members used a substantial portion of their Sept. 17 meeting to discuss and refine a draft document that would clarify the role and expectations of the council'appointed ombudsperson.
Council President Kritzer introduced the item as an effort to improve shared understanding about how the ombuds function interacts with the new legislative coordinator and with council rules. Key points raised by members included when ombuds should defer constituent inquiries to staff, how to avoid inconsistent or conflicting replies when both the mayor's office and council respond, whether the month-long rotation is sustainable, and what accountability mechanisms should exist if an ombud sends a reply that does not reflect the council's official position.
Several concrete proposals emerged in the discussion. Council members agreed by majority consensus to ask staff to implement a timely automated acknowledgement for the mayor-council inbox so constituents receive a prompt confirmation that their message was received. Council Vice President Forsyth and others expressed interest in pilot models where council leadership and the legislative coordinator would draft official responses, while some council members favored retaining the rotating ombud assignment (one or two months) because serving as ombud improved familiarity with city policies.
Concerns about accountability and independence were frequent. Council Member Fields urged consideration of outside auditing of the ombuds process and clearer mechanisms to hold council members accountable for official responses. Council Member Anderson cited email volume and the workload of responding to constituent emails as a practical constraint and suggested exploring alternative rotation frequencies. Council Member Stewart described the ombud role as valuable experience for council members and argued for retaining a council-based role while clarifying boundaries between official and personal emails.
Council leadership will consolidate the ideas discussed, coordinate with staff and the legislative coordinator, and return with a refined document and sample auto-reply for the mayor-council inbox. No final rule changes were adopted at the meeting.
