My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
6.7. SR 10-08-2012
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
2011 - 2020
>
2012
>
10-08-2012
>
6.7. SR 10-08-2012
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/5/2012 10:19:56 AM
Creation date
10/5/2012 9:57:27 AM
Metadata
Fields
Template:
City Government
type
SR
date
10/8/2012
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
4
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
If the Council would like to look closer at Option 2, staff should be directed to bring back specific <br /> information and model policies for the consideration of the Council in the coming months. This large of <br /> shift in policy direction would come back to the Council for discussion ahead of a public hearing process <br /> which will take several months. <br /> Assessment Manual Policy Updates <br /> The existing Assessment Manual was last updated in 1989. There have been some modifications to the <br /> policies since the 1989 update that need to be worked into the formal manual. Staff is proposing a full <br /> update to the manual. Staff has identified a list of policy questions to be considered as follows: <br /> 1) Past practice has been to assess properties on a per unit basis as the primary method for <br /> calculating assessments. Does the Council want to continue this practice? <br /> 2) There is some ambiguity in the current manual about how assessments are calculated for <br /> corner residential lots. How should residential corner lots be treated? <br /> 3) Current practice has been to charge residential properties a flat fee for overlays. Most recently, <br /> for the 2008 project,this fee was $1,963 per unit. This assessment is intended to cover 100% <br /> of the costs of mill and overlay projects per current practices. Should mill and overlay <br /> improvements continue to be assessed at 100% of the project costs? <br /> 4) Current practice has been to assess street reconstruction projects a flat fee for the <br /> reconstruction of a residential street. The summation of all the assessment charges has been <br /> near 1/3 of the total project costs. The remaining 2/3 has been funded through bonding, <br /> state aid funds and the Street Improvement Reserve Fund. Should reconstruction projects <br /> continue to be assessed at 33% of the project costs, or should it be increased to sustain the <br /> Street Improvement Reserve Fund? <br /> 5) Currently there is no policy in place for full depth reclamation type projects. These projects <br /> are more costly than a mill and overlay but do not go as far as a full reconstruction. What <br /> percentage should full depth reclamation projects be assessed? <br /> 6) Assessment terms have varied significantly from project to project in the past. Staff is seeking <br /> guidance on specific terms for different assessments. In general,past reconstruction projects <br /> have been payable for up to 10 years and overlay projects have been payable for up to five <br /> years. <br /> 7) The current Assessment Manual does not provide guidance on what properties are exempt <br /> from assessments. The revised draft Assessment Manual has been prepared to clearly state <br /> that cemeteries are exempt from assessments according to state law. Staff is looking for <br /> direction on other properties the Council feels should be exempt including, city facilities, city <br /> parks, state, county, school, and church properties. <br /> FINANCIAL IMPACT <br /> There is no financial impact associated with the discussion of this item. <br /> ATTACHMENTS <br /> ■ Street/Capital Improvement Budget <br /> Action Motion by Second by Vote <br /> Follow Up <br /> paw IaIa 0 <br /> NAT- URA <br />
The URL can be used to link to this page
Your browser does not support the video tag.