My WebLink
|
Help
|
About
|
Sign Out
Home
Search
01-08-2018 Council Meeting Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2018
>
01-08-2018 Council Meeting Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/2/2024 2:25:51 PM
Creation date
3/2/2024 11:44:46 AM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
01/08/2018
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.
/
231
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
CITY COUNCIL WORK SESSION December 4, 2017 <br />DRAFT <br /> 7 <br /> 270 <br />11. Code of Conduct Policy Update – Administrator Karlson recalled that the 271 <br />document was discussed and recommended for review at a recent council meeting. 272 <br /> 273 <br />The council reviewed the document. 274 <br /> 275 <br />Council Member Kusterman offered a recommendation on work sessions and that would 276 <br />be a time limit. Limiting the work sessions to three hours is recommended as well as 277 <br />trying to set times for agenda items. Mayor Reinert suggested that’s a good idea used as 278 <br />an outline only because sometimes the council needs to handle important business. 279 <br />Mayor Reinert said taking a break at three hours to refresh is also an option. Council 280 <br />Member Kusterman said at two hours, you could take stock and plan for the evening. 281 <br /> 282 <br />Council Member Manthey said he likes the idea of taking stock after two hours. 283 <br /> 284 <br />Mayor Reinert suggested it’s time to deal with the question of social media; would that 285 <br />belong under advocacy? When posting, members should keep in mind that they are a 286 <br />council member. Perhaps the city should look at what other groups like the council have 287 <br />done. 288 <br /> 289 <br />Council Member Kusterman mentioned respect for staff time as an area that needs 290 <br />attention. He isn’t certain that council members go through the administrator as this 291 <br />code calls for. Staff has work to do and too often they are besieged with questions that 292 <br />take them away from their work. “Staff will estimate the time commitment required to a 293 <br />council member’s question, and if deemed appropriate, report to the rest of the council on 294 <br />that commitment” 295 <br /> 296 <br />(The council recessed for a short break.) 297 <br /> 298 <br />Administrator Karlson noted a recent situation where he was put in a difficult position 299 <br />relative to seeking a legal opinion. Council Member Manthey suggested looking at other 300 <br />policies. Mr. Karlson said he thinks the language is fine but needs to be confirmed. 301 <br />Mayor Reinert said other people besides him asked about the situation; Brian Bourassa 302 <br />was mentioned. Council Member Manthey said it’s a problem for someone representing 303 <br />the city to have influence in that type of situation. 304 <br /> 305 <br />Council Member Kusterman suggested that the use of the public newsletter violated four 306 <br />areas of the code. Mayor Reinert said that is opinion. Council Member Kusterman 307 <br />suggested that it’s probably a campaign finance violation. He also noted language that 308 <br />he felt was abusive to staff. Council Member Kusterman remarked that the newsletter is 309 <br />supposed to speak for the group and not one member’s opinion. 310 <br /> 311 <br />Council Member Manthey said he was also offended by use of the newsletter. He’d like 312 <br />to see concerns discussed in this situation. He’d like to see that language updated. Can 313 <br />the council discuss individual items in the policy in order to improve it? Can “use of 314
The URL can be used to link to this page
Your browser does not support the video tag.