My WebLink
|
Help
|
About
|
Sign Out
Home
Search
10-24-2016 Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2016
>
10-24-2016 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2018 9:29:54 AM
Creation date
1/6/2017 1:27:39 PM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
10/24/2016
Council Meeting Type
Regular
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
292
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
COUNCIL MINUTES October 10, 2016 <br />DRAFT <br />6 <br />Council Member Maher suggested that the policy set by the resolution would require staff process be 223 <br />developed and Mr. Grochala concurred. 224 <br /> 225 <br />Mayor Reinert asked Mr. Grochala if he has any concern that the job that has brought this policy 226 <br />forward will be done correctly? Mr. Grochala said he suspects there will be more staff involvement 227 <br />and there may be kick-back. He believes that regardless there must be that line of communication. 228 <br /> 229 <br />Council Member Kusterman recalled that staff reported that the homeowner himself applied for the 230 <br />permit. Mayor Reinert explained that staff will be held accountable for a safe end product. 231 <br /> 232 <br />Council Member Rafferty moved to approve Resolution No. 16 as amended to reflect that 233 <br />communication is required to the homeowner. Attorney Langel explained the difficulty of adding 234 <br />language that would actually serve that purpose. Council Member Rafferty withdrew his motion. 235 <br /> 236 <br />Mayor Reinert said the bottom line is to have a system installed correctly; a process including some 237 <br />city oversight seems the answer to him. Will staff put together that process? Mr. Grochala explained 238 <br />that the existing rules establish the process; additionally they would have to be clear on everyone who 239 <br />is working on the project so contact and oversight doesn’t become unclear. 240 <br /> 241 <br />Council Member Kusterman expressed concern that this action could open the process up very wide. 242 <br />Would a bonding process be appropriate? He isn’t uncomfortable opening the door for all 243 <br />homeowners to bring in unlicensed, non-bonded individuals to do this important work. 244 <br /> 245 <br />Mr. Grochala clarified that the current law allows an individual to put in their own system, without a 246 <br />bond but with a plan prepared under license. For staff, understanding who to contact is very 247 <br />important. 248 <br /> 249 <br />Mayor Reinert asked, under what the state allows are there issues that arise? Mr. Grochala said he 250 <br />doesn’t think so. Mayor Reinert suggested that the action is a resolution, presenting a policy, not 251 <br />changing regulations; perhaps the city could have discussion in the future about how this is working 252 <br />and tweak it if necessary. 253 <br /> 254 <br />Council Member Manthey suggested that he hears staff indicating concern that project standards 255 <br />could be lessened. Mayor Reinert said staff will require certain standards and enforce them and he 256 <br />feels that getting a report back on this from staff is an important element to moving forward. 257 <br /> 258 <br />Council Member Rafferty moved to approve Resolution No. 16-132, amended to require that the 259 <br />subject will be revisited at a future work session. Council Member Manthey seconded the motion. 260 <br />Motion carried on a voice vote. Council Member Maher voted “no”. 261 <br /> 262 <br />UNFINISHED BUSINESS 263 <br /> 264 <br />There was no Unfinished Business. 265 <br /> 266 <br />NEW BUSINESS 267
The URL can be used to link to this page
Your browser does not support the video tag.