My WebLink
|
Help
|
About
|
Sign Out
Home
Minutes - Council Work Session - 09/10/2019
Ramsey
>
Public
>
Minutes
>
Council Work Session
>
2019
>
Minutes - Council Work Session - 09/10/2019
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/13/2025 12:32:14 PM
Creation date
10/11/2019 3:35:21 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Minutes
Meeting Type
Council Work Session
Document Date
09/10/2019
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
9
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
Councilmember Musgrove asked for input on the rollout on the online programs and park <br /> registration process. <br /> Parks and Assistant Public Works Superintendent Riverblood stated that the work of the <br /> employee is program development,program management, auditing, and resident interaction with <br /> only a small portion of the time spent on reservations. He noted that this position will also be a <br /> backup to the public works administrative assistant. <br /> 2.03: Discussion Regarding Processes and Procedures for Council Meetings <br /> Administrative Services Director Lasher reviewed the staff report. <br /> Councilmember Kuzma stated that the meetings are also recorded and therefore verbatim <br /> information is available on the recordings. <br /> Administrative Services Director Lasher confirmed that QCTV must keep the videos posted for <br /> three years by State Statute and the City keeps those DVD's on file for a longer period. <br /> Councilmember Heinrich stated that she would like clarity on whether the recreation specialist <br /> position is going to remain on the consent agenda for tonight's meeting and asked for that <br /> discussion to occur prior to the minutes. <br /> City Administrator Ulrich stated that the items on the consent agenda are items that have had <br /> previous discussion at a work session or are administrative/clerical issues that are not expected to <br /> have debate. He noted that any item could be proposed to be removed from the consent agenda <br /> at the regular Council meeting, should a member wish to vote against the item. He stated that <br /> staff has also amended the agenda prior to a regular meeting in order to move an item from the <br /> consent agenda to the regular agenda at the direction of a Councilmember, but noted that does <br /> require additional staff time. He stated that a deadline was previously discussed to be set as noon <br /> the Friday before the Council meeting for members to alert staff to items they may have concern <br /> with on the consent agenda, which would allow time for staff to amend the agenda and repost. <br /> Councilmember Heinrich agreed that seems to be a fair timeline. She stated that she was <br /> surprised to see the recreation specialist position on the consent agenda, as even though there <br /> was previous worksession discussion,there was not a clear consensus. <br /> Mayor LeTourneau stated that it has been the practice of the Council for a Councilmember to <br /> alert staff, even in the work session prior to the regular meeting to an item they would like <br /> moved to the regular agenda. He stated that the benefit of having the change made the Friday <br /> before the regular meeting is that the change would be made public for the residents to see. <br /> Councilmember Heinrich stated that she would like the recreation specialist position moved from <br /> the consent agenda to the regular agenda. <br /> Councilmember Riley stated that the request to have changes submitted by noon the Friday prior <br /> to the Council meeting is a good practice that the Council can strive for but acknowledged that <br /> City Council Work Session/September 10,2019 <br /> Page 5 of 9 <br />
The URL can be used to link to this page
Your browser does not support the video tag.