Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Parking Drivable Surface Enforcement topic
No spam. Unsubscribe anytime.
Council weighs easing backyard parking rules while staff prepares draft options
Summary
Councilors told staff to draft revisions to the city's drivable-surface and accessory-parking rules after residents complained about enforcement of a requirement that rear-yard parking be on pavement or specified gravel; discussion touched on safety, weeds, vehicle counts and enforcement practicality.
At a Feb. 24 work session the Clinton City Council discussed complaints tied to the city’s drivable-surface rules, which require accessory parking in side and rear yards to be on hard surface or an approved depth of gravel. Several residents and council members told the mayor and staff the enforcement of that rule has become more visible since the city hired a full-time code enforcement officer.
The chair summarized constituent feedback and asked staff whether enforcement typically begins with complaints. Peter, the community development director, confirmed most enforcement actions are complaint-driven and that the ordinance requires parking areas to be accessible by a drivable surface—often interpreted to mean pavement or a specified gravel buildup.
Council members raised three concerns: whether the requirement was originally motivated by safety or aesthetics, the challenge of enforcing activity hidden behind fences, and whether targeted remedies—weed/maintenance rules or time-limited compliance extensions—could address problems without broad restrictions. One councilor said the measures exist to protect neighbors’ property values and to prevent long-term storage that leads to pest and fire risk.
Members debated whether to cap the number of vehicles a homeowner can store and whether an 'inoperable' vehicle standard should be tied to registration; staff cautioned that numerical limits on vehicles are difficult to enforce and may be perceived as limiting property rights. The council noted it generally favors more homeowner freedom unless clear safety risks or persistent blight arise.
The council asked staff to draft alternative ordinance language that addresses the fence-boundary problem, clarifies gravel/hard-surface standards, proposes reasonable compliance timelines (staff noted 14 days is a typical compliance timeframe with extensions available), and considers registration-based criteria for inoperable vehicles. No vote was taken; staff will return with draft language for council review.
What happens next: staff will prepare draft code alternatives and timelines for compliance for the council to consider.
