Laserfiche WebLink
t Metropolitan Council Local Planning Handbook 1 Section 1. Metropolitan Planning Overview <br />Within 60 days after the Metropolitan Council resolves to require a <br />plan modification, the community or county government must <br />respond with either a letter of agreement or notification that it <br />intends to contest the requirement. Minnesota law specifies a course <br />of action for contesting a required plan modification. <br />The Metropolitan Council's sector representative assigned to each <br />municipality works closely with the community's planning staff as the <br />local unit develops a comprehensive plan update that meets the <br />criteria of statute and Metropolitan Council policy and meets with the <br />approval of affected jurisdictions. <br />See the review process and timelines for both updates and <br />amendments outlined in a table. <br />The reviewer The initial review determines if the comprehensive plan update <br />determines includes all the elements required by statute and Metropolitan <br />completeness Council policy in sufficient detail to determine conformance with <br />regional systems and consistency with Council policies. The <br />Metropolitan Council staff strives to do this within 15 days after the <br />Council receives the plan update. <br />• If the submittal contains all the information required to review <br />a comprehensive plan, the municipality is notified that the plan <br />is complete. <br />• If the submittal does not contain all the information required to <br />review a comprehensive plan, the municipality is notified that <br />the plan is incomplete. The notification to the municipality will <br />identify the missing information. <br />If information must be added, it is submitted directly to the Principal <br />Reviewer and the determination of the plan's completeness is <br />repeated. <br />Minn. Stat. Sec. 483.866 <br />http://www.metrocouncil.orq/plan <br />ni no/assistance/staff.htm <br />http://www.metrocounci1.orq/plan <br />ni no/LPH/reviews.pdf <br />June 2008 1 -17 <br />