My WebLink
|
Help
|
About
|
Sign Out
Home
Minutes - Council Work Session - 04/03/1989 - Special Workshop
Ramsey
>
Public
>
Minutes
>
Council Work Session
>
1989
>
Minutes - Council Work Session - 04/03/1989 - Special Workshop
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/8/2025 12:03:03 PM
Creation date
11/6/2003 3:02:06 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Minutes
Meeting Type
Council Work Session
Document Title
Special Workshop
Document Date
04/03/1989
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
10
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
comprehensive the checklists are, there will always be areas of interpretation and the need <br />for communication. Mr. Hartley stated that if there is a problem accessing City Staff, he <br />needs to know the specifics so he can correct the problem. Mr. Hartley also noted that City <br />Staff prepares agendas, almost on a weekly basis for the various boards and commissions, <br />that contain a substantial amount of information that includes a staff recommendation and a <br />typical motion; a fair amount of time is spent on structuring the meeting so that cases with <br />applicants present will be placed at the front of the agenda. Mr. Hartley confirrned that in <br />1988, City Council agreed that the implementation of an on-staff City Engineer and support <br />personnel would be reviewed in 1989. Currently, charging engineering costs to the escrow <br />account is one of the most convenient ways to bill the cost of development; the City is <br />aware of cases where charges that may not be related to the development have been passed <br />through and Staff hopes to correct those problems. In a sense, the city at large is paying <br />for most of the cost of development in the sense that on-staff personnel do not charge their <br />time for projects to the related escrow account; makers of the City Charter suggest that this <br />is in confiict with the City's governing document. The concept of an engineer/city <br />planner/economic development director position is novel and will not be ruled out. Mr. <br />Hartley stated that he feels such a position would be poor management. The idea of <br />combining the economic development director function into that of the engineer/planner <br />position, has been discussed but an economic development director does not always <br />shepherd land use applications but rather encourages applicants to come to a particular city. <br />City Staff does review issues from both the City's side and the developer's side. One thing <br />that is frustrating to staff is that individuals do not supply the information or follow the <br />process in accordance with ordinances and choose to take a different approach to seeking <br />approvals; the more this avenue is used, the more confusing the process becomes. City <br />Council determines the policies; when policies are in conflict with the way in which <br />developers choose to do a development, a request to change those policies should be <br />directed to City Council. An example of this is the park dedication ordinance; the format <br />was to review the ordinance in detail, prepare a draft ordinance and forward it to the <br />members of the development community for review. <br /> <br />Mr. Raatikka stated that it has been the City's past policy to accommodate developers, <br />even if it meant waiting until the day of a meeting to receive the information and approving <br />the request with contingencies. The City is moving away from this philosophy of <br />approving issues with contingencies. Mr. Raatikka stated that he has always been <br />accessible to the developers. A few years ago, City Council set a policy of consulting staff <br />not being accessible without prior authorization from the City Administrator. Mr. Raafikka <br />stated that he has tried to keep charges to developer accounts to a minimum. One thing that <br />will increase the engineering fees is substandard applications that require 2 or 3 reviews. <br />Another reason for rising engineering costs is the fact that contractors working for <br />developers have not been very efficient on grading streets, etc. and physical inspections of <br />the property is required. In many cases, a contractor spends 3-4 times longer than <br />necessary to pave streets; this in turn increases the City's inspection costs for the project. <br /> <br />Mr. Otto stated that it is aggravating to all involved to have cases tabled and he agrees that <br />things can be done at a staff level to bring the cases to the commissions in a better form but <br />it will require discipline on the part of the city and the applicant. Incomplete applications <br />submitted days before a meeting don't do anybody any good and end up being tabled. Mr. <br />Otto stated that he advocates the City providing a checklist indicating what the applicant <br />must provide and not accepting the application until it is complete. An engineer, a <br />community development director and a park commission all bring forth different <br />perspectives when reviewing an issue and it would be difficult to f'md one person that could <br />address all of these perspectives. There are a number of ordinances that need revising that <br /> <br />City Council/April 3, 1989 <br /> Page 5 of 7 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.