Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Special Events topic
No spam. Unsubscribe anytime.
Marion council adopts special-events ordinance, clarifies permit scope for private events
Summary
Council adopted ordinance 4058 to formalize special-event permits and internal processes for the public square; council removed the word "residential" from one clause to avoid overreach into private-property events that do not demand city resources.
The Marion City Council voted to adopt ordinance 4058, which establishes a formal permit and application process for special events on public property and clarifies when the city will require event coordination and resources. Mayor Absher moved to approve the ordinance (with one edit) and the council approved it by roll call.
City Attorney Wendy told the council the ordinance is not intended to be a revenue measure but rather a way to ensure the city plans for safety, liability and resource allocation as events increase on the public square. "It's the ordinance and the permit is kind of the first step in this process," Wendy said, noting the city had not previously captured those procedures in a short written policy.
Council members raised questions about scope—specifically whether single food trucks or small private gatherings on commercial lots would require city permits. Several council members argued that ordinary private-property activity that does not demand city services should not fall under the permit requirement. Wendy and Mayor Absher said the ordinance will focus on events that "significantly impact the city" (for example, a large Fourth of July event) and that staff would remain responsible for determining when city resources such as police, barricades or street closures are needed.
The council agreed to strike the word "residential" from section b.5 to avoid an ambiguous interpretation that could exclude or include certain private properties unintentionally. The mayor asked staff to funnel event requests to the marketing director (Rachel) as a single point of contact for coordination.
The ordinance was adopted by roll call with four "Yay" votes and one absence. The change to b.5 and the formal permit process will be reflected in the published ordinance and permit application materials; staff will finalize the ordinance language and administrative procedures.
Provenance: Topic introduced at SEG 315; ordinance adoption recorded at SEG 628–641.
