Laserfiche WebLink
<br />Proposed Changes to Development Contract <br /> <br />1. Change the second Whereas paragraph to reflect that the Developer has requested the City to <br />construct many of these improvements, as described in paragraph C on page 5 of the Development Contract. <br />Possible language could read as follows: <br /> <br />Whereas the Developer has requested the City to construct all surface streets, sidewalks, curb and gutter, <br />recreational trails, storm sewer, drainage facilities, water main and sanitary sewer facilities, hereinafter <br />referred to as "Street and Utility Improvements; and Whereas the Developer and the City desire to establish <br />financial responsibility for the Street and Utility Improvements; and <br /> <br />2. Insert a new paragraph to deal with the fact that Ground Development is not also the builder. <br />Landscaping is put in by the builder, and Ground Development will require the builders to do the landscaping as per <br />the approved landscaping plan. The proposed paragraph is as follows: <br /> <br />Landscaping. The Developer shall require all builders within the subdivision to install such landscaping as <br />required by Development Covenants or City ordinance 38.01-5 whichever is more restrictive. <br /> <br />3. Request changing paragraph B.2.a.iii (on page 3) to simply have the monumentation done within <br />180 days after filing the final plat. <br /> <br />4. Clarify the landscaping requirements in paragraph B.2.a.v (on page 3) by deleting "other <br />requirements" and inserting "Developer's approved landscape plan." <br /> <br />5. Clarify the "increments" in paragraph B.2.c.iii either by providing that the increments are "as set <br />forth in Developer's Phasing Plan", or by inserting "Engineer" after the word "City", to give a particular individual <br />responsibility for designating the increments. <br /> <br />6. Change paragraphs B.2.e and f (on page 4) to insert "or surety bond" after "Letter of Credit" each <br />time it appears. Change the 150% to a more standard 110%. <br /> <br />7. Add the new statutory requirement relating to special assessments into paragraph c.. Possible <br />language is as follows: <br /> <br />As provided by Minn. Stat. 9462.3531, this waiver of rights of appeal is effective only for the amount of <br />assessment estimated in the Feasibility Report. <br /> <br />8. <br />$12,500. <br /> <br />Clarify the last paragraph of paragraph C to indicate that the cash escrow is in the amount of <br /> <br />9. Add language to paragraph C explaining the formula for dividing the special assessments between <br />the benefitted properties. This change is due to the new statute (Minn. Stat. 9462.3531), which does not allow the <br />City to simply put the developer's estimated assessment in the contract, but rather places a cap on the City's <br />assessment authority. Weare proposing language which leaves full authority with the City Council, rather than <br />risking have conflicting provisions in the City Council's Assessment Role and in the Development Contract. Such <br />language could be as follows: <br /> <br />Special assessments shall be divided between the benefitted properties based on the formula and approach <br />approved by the City Council in its Assessment Role for Pheasant Marsh. <br /> <br />10. Change paragraph E, due to the new statute, to begin as follows: "Except as limited by Minn. <br />Stat. 9462.3531, the Developer. . ." <br /> <br />11. Clarify paragraph I to indicate that the Developer still may sell lots to builders. Such language <br />