My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2B, Council Liaison Expectations Roles and Responsibilities (2)
ArdenHills
>
Administration
>
City Council
>
City Council Packets
>
2010-2019
>
2012
>
02-13-12-WS
>
2B, Council Liaison Expectations Roles and Responsibilities (2)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/23/2024 12:19:26 AM
Creation date
6/21/2012 1:42:25 PM
Metadata
Fields
Template:
General
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
18
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
No City Council wants their Commissions or Committees to become "Yes Men" in their <br /> approach to conducting business, whereby the Council only gets recommendations that it <br /> wants to hear and does not get the true opinions of the advisory group. The Council and the <br /> Commissions/Committees always want to have similar expectations and philosophies on <br /> such issues as land development, or spending, or activities or (fill in the blank). A good <br /> time for the Council expectations to be laid out and discussed is at annual joint meetings <br /> when the Committee/Commission work plans are reviewed. <br /> The setting of the work plan should also get some discussion at this work session. For <br /> example, the Council should discuss if the work plan is set by the Commission/Committee <br /> and accepted by the Council or if the work plan is mainly set by the Council and then given <br /> to the Commission/Committee. The Council does not want its Commissions/Committees <br /> working on projects that the Council doesn't want to touch. Usually <br /> Commissions/Committees want direction on what the City Council thinks is important work. <br /> I am a big believer in ongoing communication between the Council and its <br /> Commissions/Committees. In this regard, I believe that it is important to have the Liaison <br /> report back to the Council on "what is going on at the Commission/Committee meetings." <br /> This can be done monthly or quarterly but needs to be done at a regular meeting on cable <br /> TV so that the citizens at home also have an easy opportunity to know what is happening at <br /> City Hall. Also the City Council should regularly get the Commission/Committee meeting <br /> minutes. Additionally, an annual joint meeting is always a good way to keep the lines of <br /> communication open. Since I have been with the City, the Council has not met jointly with <br /> the EDC, FPAC,the Communications Committee, or Karth Lake. The annual summer <br /> Bar-B-Q is a good communication opportunity but I don't think it takes the place of the <br /> Council discussing issues of mutual concern and saying "thank you" to the <br /> Commissions/Committees at joint meetings. <br /> Recommendations <br /> I think that the Council should establish some general guidelines for Liaisons. I think that <br /> the guidelines should lean more toward a passive role for the Liaison but also allow enough <br /> flexibility so that if the Commission/Committee is lacking leadership or direction, that the <br /> Liaison can become more engaged with the group. (The Council does not want staff filling <br /> this void and taking on this leadership role.) I say that a more passive role is my <br /> recommendation because I think that the City Council should offer overall direction to the <br /> Commissions/Committees at annual meetings by way of approving the work plan. Finally, I <br /> think that having the Liaison become a voting member of the EDC, FPAC, and the <br /> Communications Committee is worth considering. <br /> City Council Meeting P;\Admin\Council\Agendas&Packet Information\2012\02-13-12 Wk Ses\Packet Information <br /> Page 3 of 3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.