Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Sewer Septic Connection topic
No spam. Unsubscribe anytime.
Resident presses city over unexpected sewer hookup, cites state law and poor notice
Summary
A Beersford resident told the council his septic system was effectively tied into the city sewer during nearby development and said he received little notice; city staff cited state law and city ordinance that generally require connections within 200 feet and agreed to an offline meeting to discuss options and exceptions.
A Beersford resident raised a prolonged dispute with city officials over a septic-to-sewer connection during public comment, saying the work removed a dry pit on city property and left him responsible for costs and uncertainty.
The resident, Brian (resident), said he recently paid about $6,000 to replace his septic system and was told verbally his septic could remain until it failed. He told the council, “I was told I had 3 weeks by you, everyone of you… and then the day before, contractors showed me bulldozing that down tomorrow.”
City staff described the legal backdrop in their reply. A city official said both “state law and city ordinance both require” connection when a property is within a short distance of a public sewer, and offered to provide the resident a copy of the applicable state rules. Staff and council acknowledged communication gaps around timing and notice; the council agreed to organize an offline meeting with the resident to clarify options and any documented exceptions.
Why it matters: connecting a private septic system to a public sewer can create new monthly charges, change who is responsible for solids handling, and require removal or alteration of on-site systems. Residents who recently invested in private systems told the council they felt blindsided when development and utility tie-ins accelerated.
What was said and what happens next: the council did not take a formal vote on the matter during the meeting. Instead, staff said they would meet offline with Brian to review the facts, share the cited statute/ordinance text, and explore possible accommodations or timelines. A city representative told the meeting, “I can give you a copy of that” when offering the state law that staff said had been applied.
Additional context: speakers and staff referenced an ongoing residential development nearby that accelerated infrastructure work after a grant became available, which council members said contributed to the faster-than-expected timeline. The city acknowledged it could improve proactive communications to affected property owners when projects that trigger utility connections are planned.
Ending: The council committed to follow up directly with the resident and to schedule a staff–resident meeting to review the legal requirements and any potential alternatives. No formal ordinance change or relief was adopted at the meeting.
