My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2017_0925
Roseville
>
City Council
>
City Council Meeting Minutes
>
201x
>
2017
>
CC_Minutes_2017_0925
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/19/2017 11:11:11 AM
Creation date
10/19/2017 11:10:23 AM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
9/25/2017
Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
29
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
Regular City Council Meeting <br /> Monday, September 25, 2017 <br /> Page 5 <br /> precluded any future discussion. Councilmember McGehee further opined that <br /> there was no reason or necessity to preclude further work, particularly with the <br /> variety of options provided by staff, including her proposed Option E. While her <br /> proposal looked like a high levy, Councilmember McGehee stated that the impact <br /> would actually result in an amount less than the City Manager Recommended <br /> Levy. In general, Councilmember McGehee stated that she wasn't pushing for <br /> any particular option, but wanted to keep all options open for further considera- <br /> tion and discussion by not having the not-to-exceed levy limit set so low it pre- <br /> cluded further discussion and additional study. <br /> Councilmember Willmus noted that the increase in the City Manager Recom- <br /> mended Levy increase, coupled with the proposed EDA levy and expected in- <br /> crease of utility rates was approximately 1.3% and in line with inflation, repre- <br /> senting a responsible total cost impact and budget option as put forward. <br /> Councilmember McGehee agreed with that statement, but also noted that it didn't <br /> address the options that had been made available. <br /> Councilmember Laliberte complimented the City Manager on his recommended <br /> budget; but reiterated past positions she'd held in being open to use of reserves for <br /> one-time expenses but not for daily operations; with this recommended budget not <br /> breaking down CIP funds still unaddressed, and allowing for use of reserves in the <br /> right way and as intended by using monies previously collected from taxpayers to <br /> do so. <br /> Speaking to comments of Councilmember Willmus specific to inflation, Coun- <br /> cilmember Etten agreed that made some sense, but clarified that part of the in- <br /> crease was for capital needs outside the General Operating budget that he'd con- <br /> sider beyond inflation. Since these needs were not taken care of in the past, <br /> Councilmember Etten stated that it resulted in the need to push above inflation to <br /> address long-term issues for the city. While recognizing Councilmember <br /> Willmus' point about inflationary levy increases as the preferred norm, Coun- <br /> cilmember Etten noted that it missed the rationale in setting the levy above infla- <br /> tion to address those issues. Specific to Councilmember Laliberte's comments, <br /> Councilmember Etten noted that one-time expenses were no where near$800,000 <br /> and may prove a great spot for using those reserves. However, Councilmember <br /> Etten opined that those reserves may be needed and remain an unknown until later <br /> this year. With the not-to-exceed preliminary levy, Councilmember Etten stated <br /> his wish to not put the city in a corner and preferred not to pass a limited not-to- <br /> exceed number and then be unable to address issues if year-end figures came in <br /> above current expectations. <br /> With the cash carry forward fund, Councilmember McGehee opined that it <br /> seemed to be a more responsible use of reserves and would be viewed differently <br /> from an accounting standpoint. <br />
The URL can be used to link to this page
Your browser does not support the video tag.