My WebLink
|
Help
|
About
|
Sign Out
Home
Minutes - Council Work Session - 10/26/2021
Ramsey
>
Public
>
Minutes
>
Council Work Session
>
2021
>
Minutes - Council Work Session - 10/26/2021
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/13/2025 11:11:19 AM
Creation date
11/29/2021 4:27:30 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Minutes
Meeting Type
Council Work Session
Document Date
10/26/2021
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
15
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
changing to an hourly rate for room rentals at City Hall and would want to speak with Staff to <br />determine what is reasonable. <br /> <br />Councilmember Specht answered that it would be worth a discussion, especially if reservations <br />could be made online. <br /> <br />Finance Director Lund stated it is recommended to introduce the changes to the rates and charges <br />on November 9, 2021 for adoption on November 23, 2021 to allow 30 days’ notice to go into effect <br />by January 1, 2022. <br /> <br />The consensus of the Council was to follow staff recommendation, with the addition of the mobile <br />home tie down fees being set at $75. <br /> <br />Councilmember Musgrove asked for clarification that in 2022, it is proposed to change rental fees <br />from the $10 flat rate to $5 per hour and the $25 rate would be resident hourly. <br /> <br />Building Official Szykulski confirmed this. <br /> <br />Councilmember Howell asked about lowering the rate for residents, noting it is a big jump to go <br />from $24 for the day, to $25 hourly, to have a bigger disparity between resident and nonresidents. <br /> <br />Parks and Assistant Public Works Superintendent Riverblood answered that this is a proposed <br />dollar increase, noting it was the nonprofits that were at the flat rate, everyone else was hourly. <br /> <br />2.02: Review 2022-2031 Capital Improvement Plan (CIP) <br /> <br />Finance Director Lund stated the Council is reviewing the first draft. She explained the priority <br />levels, noting a priority 1 is something that is within the next couple of years, Priority 2 is <br />something that is new, that has never been done before and isn’t a replacement such as the Police <br />vehicle in 2022, Priority 3 and 4 are for the remaining 8 years of the CIP, and Priority 5 is a <br />placeholder within the document. For example, the community center which is unfunded. Finance <br />Director Lund reviewed the staff report, noting this document is subject to change. She highlighted <br />the main cash flows pages and explained the CIP is a planning tool so everything that is included <br />is not adopted until it comes to the Council as individual projects. <br /> <br />Councilmember Musgrove commented that there weren’t TIF districts listed under the “sources of <br />funding.” She asked if there were any funds that qualify for any TIF district dollars, noting she <br />wanted to make sure the City was using those dollars in areas they can be used. <br /> <br />Finance Director Lund answered, the TIF cash flows are included. In regard to TIF 1 and TIF 2, <br />those were the older districts that were allowed for pooling. She explained the project for 116 was <br />allowed for funding but the County pushed that project out so it’s no longer reflected in the CIP. <br />Because of that, TIF 1 and TIF 2 do not reflect the 116 project anymore. She noted the fund <br />balances are listed and the respective cash flows. She gave the example of TIF 2 having a projected <br />balance of $1.7 million after 2021, which is because $1.5 million was added back when the 116 <br />project was put on hold. <br />City Council Work Session / October 26, 2021 <br />Page 5 of 15 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.