My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2009_1207
Roseville
>
City Council
>
City Council Meeting Minutes
>
200x
>
2009
>
CC_Minutes_2009_1207
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/19/2010 1:00:00 PM
Creation date
1/19/2010 12:59:57 PM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
12/7/2009
Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
28
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, December 07, 2009 <br />Page 10 <br />Mr. Miller used, as an example, the 2010 proposed training budget amount that <br />was the same as that of 2009; and noted that the priorities for that training within <br />departments had not yet been prioritized until staff was made aware of the City <br />Council's final goals and objectives, at which time Department Heads will assign <br />priorities within that line item based on those goals and objectives. Mr. Miller <br />advised that this was applicable to each specific department for training, supplies, <br />and professional services budgets, at which time staff would then provide a line <br />item budget. <br />Councilmember Ihlan opined that she was not asking the City Council to direct <br />staff to create something new, alleging that there had to be line item number to <br />support the budget expenditure summaries provided by staff. Councilmember Ih- <br />lan noted that the City Council only had one more meeting to set the 2010 budget; <br />and opined that something was really wrong. <br />Councilmember Roe noted that the BFO process was amulti-step process, and <br />that the BFO process was not followed. for all non tax-supported programs, thus <br />that information was available based on past practice and information. Council- <br />member Roe clarified that since the BFO process was being implemented for <br />2010 for tax-supported funds, many items were represented as a lump sum and <br />were still pending (i.e., depreciation, employee health care costs), with Mr. Miller <br />needing to have direction, based on Council priorities, to allocate that total sum <br />into each department and each applicable fund. Councilmember Roe noted that <br />he understood that it was an aggregate concept from 2009 to 2010, and that was <br />sufficient for his decision-making. Councilmember Roe further noted that, other <br />funds were less complicated (i.e., Fire Relief Fund). <br />Councilmember Pust, in response to Councilmember Roe's examples, opined that <br />there remained 11 new spending areas in the 2010 proposed budget, with the ma- <br />jority not requiring staff to allocate among or within departments (i.e., Hazardous <br />and Diseased Tree Program). Councilmember Pust opined that if staff was to <br />print out the 2009 budget and supporting documents, and changed those applica- <br />ble items for 2010, including the items as amended mid-year in 2009, distributing <br />them as requested, it wouldn't require too much staff time. <br />Mr. Miller concurred that such an exercise would not be labor intensive as de- <br />scribed; however, he noted that this had been provided in the budget matrix being <br />used by Councilmembers and color highlighted as previously discussed. How- <br />ever, Mr. Miller understood Councilmember Ihlan's request was to provide the <br />detail behind the line items, which was not yet available for 2010. <br />Councilmember Pust reviewed several new line items (i.e., replacing lost State <br />Aid; Arboretum restroom) that also didn't require allocation among departments; <br />and opined that more time had been spent arguing about the request than would <br />
The URL can be used to link to this page
Your browser does not support the video tag.