Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Code Enforcement topic

No spam. Unsubscribe anytime.

Oshkosh staff propose tiered code‑enforcement system, urge SeeClickFix and privacy changes

Oshkosh City Council (workshop) · July 9, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Oshkosh City staff presented a plan at a council workshop to prioritize code‑enforcement complaints into three tiers and to change how the city uses SeeClickFix and the case‑management system Evolve.

Oshkosh City staff presented a plan at a council workshop to prioritize code‑enforcement complaints into three tiers and to change how the city uses SeeClickFix and the case‑management system Evolve.

Sarah, Community Development staff, told the council the goal is to "create a fair and consistent response" while directing limited resources toward "highest impact" problems and improving communication and transparency. She said the city received about 2,700 SeeClickFix reports between July 1, 2024, and July 1, 2025—roughly 230 reports per month—and that the average time to close a SeeClickFix case was about 12 days.

Staff recommended a three‑tier approach. Tier 1 would include immediate health and safety hazards (examples given: severe exterior maintenance, sump pump discharges that create icy sidewalks, and exposed pools lacking required barriers) that staff would respond to same day or as quickly as practicable. Tier 2 would cover issues that could cause damage or safety risks if left unaddressed—junk and debris, more substantial zoning violations, work without permits and intermediate exterior maintenance—with an expected response within about a week. Tier 3 would cover lower‑priority quality‑of‑life issues—minor zoning violations, some parking complaints, unregistered vehicles, visible garbage cans, signage and home‑occupation complaints—that would generally receive educational outreach or a low‑touch notice rather than immediate inspection.

Sarah said SeeClickFix is primarily an intake tool and that case management occurs in Evolve. She urged the council to let staff use discretion so field crews are not required to open a full investigative record on every SeeClickFix report. "Code enforcement is a balance," she said, noting the city currently inspects each complaint to determine whether a violation exists and then opens a record when it does.

Council members raised several operational concerns: the volume of reports and staff time required to photograph and log each complaint, the risk that anonymous reports are being weaponized in neighbor disputes, and privacy issues with Evolve's public‑facing records. One council participant emphasized that the current workflow—responding in person to every SeeClickFix report and creating a full public record—can be costly and duplicative.

Staff provided category totals for the past year: parking‑related reports (more than 400), tall weeds (about 380), property maintenance (about 348), and junk/debris (about 340). Other categories that exceeded 100 reports included garbage/recycling (about 194), potholes/pavement/curb (about 158), and snow/ice sidewalk shoveling (about 101). Sarah said roughly 16 of SeeClickFix's 35 intake options currently have open cases and that the city receives many duplicate or highly localized complaints that compete for limited staff time.

On anonymity and tenant‑landlord issues, council members were divided. Some said anonymous reporting can protect tenants who fear retaliation; others argued anonymity encourages repeated, low‑priority complaints aimed at neighbors. Staff said it would research a compromise—such as restricted anonymous options for tenant safety issues—and develop an alternate confidential pathway for landlord‑tenant complaints.

Council members also raised concerns about Evolve showing photos, addresses, and names on a public site. Sarah said staff is reviewing judicial privacy requirements and Safe at Home protections as part of potential software changes.

Staff proposed exploring a coordination role or a dedicated code‑enforcement coordinator to reduce duplicative notices across multiple departments; Sarah said about nine departments and roughly 32–35 staff currently touch code enforcement in some way, equivalent to about six full‑time positions when aggregated. A single coordinator or clearer coordination protocol would aim to provide residents a unified message and reduce multiple letters from different departments about related issues.

The council generally supported the idea of tiered priorities and granting staff operational discretion guided by a clear, plain‑language mission statement and improved public education. Council members asked staff to return with drafted policy changes, recommended SeeClickFix intake adjustments, and options for Evolve's public‑facing information.

Authorities and formal actions were not changed during the workshop; staff will draft policy revisions and bring specific ordinance or administrative changes back to council for formal consideration.

Next steps noted by staff: revise SeeClickFix intake options, study anonymous reporting alternatives for tenant safety, evaluate Evolve privacy settings, prepare standard educational messaging for low‑priority complaints, and return to council with a proposed policy and implementation timeline.