My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packets - 2003/02/24
MoundsView
>
Commissions
>
City Council
>
Agenda Packets
>
2000-2009
>
2003
>
Agenda Packets - 2003/02/24
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 4:46:34 PM
Creation date
8/8/2018 9:43:37 AM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Agenda Packets
MEETINGDATE
2/24/2003
Supplemental fields
City Council Document Type
City Council Packets
Date
2/24/2003
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
109
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).
Show annotations
View images
View plain text
Mounds View City Council February 10, 2003 <br />Regular Meeting Page 14 <br /> <br /> 1 <br />City Attorney Riggs indicated it does not. 2 <br /> 3 <br />Council Member Quick commented that he is not aware of many employees with a copy of the 4 <br />Charter handy to refer to and Resolution 5555 is a simple way of laying out the protocol for 5 <br />communication. 6 <br /> 7 <br />Council Member Stigney disagreed with Council Member Marty as the paragraph that he read is 8 <br />not in the Charter and that is why Resolution 5555 is needed. He then said that the interpretation 9 <br />is the problem not the Resolution itself. 10 <br /> 11 <br />Mayor Lin ke indicated there are several reprimands in files for employees talking to Council 12 <br />Members because items did not go up to Council and when it was suggested to Council that is 13 <br />when the reprimand happened because the next person up the line from department head did not 14 <br />follow through that process. He then said that there is too much room for interpretation there and 15 <br />that is why he is for rescinding Resolution 5555. 16 <br /> 17 <br />Mayor Linke indicated the policy was that Staff could talk to Council Members but Council 18 <br />could not give direction to employees other than through the City Administrator as a Council 19 <br />body. 20 <br /> 21 <br />Barbara Thomas of 5444 Landmark Circle encouraged Mayor Linke to go back through the files 22 <br />because there are only minor circumstances where that occurred. She then said she had the 23 <br />Charter in front of her and the circumstances of the birth of Resolution 5555 were shortly after an 24 <br />extended period of meeting with a facilitator because the City was having some serious issues 25 <br />with department communications and Council had constant complaints that employees did not 26 <br />know the process. 27 <br /> 28 <br />Ms. Thomas indicated that this is an area that the Charter is weak in as it says what, but not how. 29 <br />The purpose was not to in any way change or affect the interpretation of the Charter, it was a 30 <br />method to reinforce what the Charter says while explaining how to accomplish what is in the 31 <br />Charter. The Charter is bare on this and that was to allow for flexibility as the Resolution 32 <br />allowed for flexibility and interpretation. 33 <br /> 34 <br />Ms. Thomas commented that however it was interpreted whether or not Council Members agreed 35 <br />with it or not should Council choose to rescind, that puts the City in a position of needing to 36 <br />change the policy on communication. She further commented that rescinding the Resolution 37 <br />requires a good explanation of why and what changes Council Members expect and she thinks 38 <br />the employees and the residents deserve to know that. 39 <br /> 40 <br />Council Member Stigney indicated he did not want to go back to where the City was before when 41 <br />there was confusion and the Mayor was running around running the City with out Council or 42 <br />Administrator input. 43 <br /> 44 <br />MOTION/SECOND: Stigney/Quick. To Table Resolution 5944. 45
The URL can be used to link to this page
Your browser does not support the video tag.