Laserfiche WebLink
<br /> <br /> <br />Administrative Variance Report <br />December 3, 2003 <br />Page 2 <br /> <br />2) Application Review – Many cities allow the Community Development <br />Director to grant administrative variances. In some cities, the request is <br />reviewed by three members of the staff, and yet in others by “qualified staff”. <br /> <br />3) Requirements for Approval – White Bear Lake, MN, and a few other cities <br />require written consent to the variance from adjacent landowners. Many <br />cities require that the City or the applicant notify the adjacent neighbors and <br />allow ten to fourteen days for the neighbors to respond. In addition, many <br />cities require that the neighbors be informed of the decision made. If <br />neighbors object, the applicant needs to apply for a formal variance. These <br />requirements are in addition to proving a hardship and meeting the variance <br />criteria, as evaluated by staff. <br /> <br />4) Denial and Appeals – All cities will allow a resident to apply for a formal <br />variance if Staff denies the request. The applicant may also appeal to the <br />Planning Commission if they disagree with conditions required by Staff. <br /> <br />5) Fee Requirements – There was a wide range of fees charged for <br />administrative variances. The range went from $15 in White Bear Lake, MN <br />to $227 in Boulder, CO. For a formal variance, Mounds View charges $150 <br />for properties in R-1 and R-2 districts and $325 for properties in all other <br />districts. <br /> <br /> <br /> <br />Recommendation: <br /> <br />Staff is seeking input from the Planning Commission as to whether the Commission is <br />interested in developing a process for administrative variances. If interested, please <br />direct Staff to further investigate the possibility or begin writing a code amendment. If the <br />Planning Commission chooses to recommend a code amendment, decisions must be <br />made by the Commission in regards to the five topics addressed above. <br /> <br /> <br /> <br />Respectfully submitted, <br /> <br /> <br />Kristin Prososki <br />Planning Associate <br /> <br />