7.2.1 Annual Report and Meeting

Each LGU must provide a written report to the District by June 30 annually, describing how the LGU has implemented the local plan over the past calendar year.  The annual report date coincides with the submittal date for municipal separate storm sewer system (MS4) annual reports as set by the Minnesota Pollution Control Agency (MPCA).  If the MPCA should change that date, the District would adjust its annual reporting date administratively. 

An LGU may submit its MS4 report to the District as its annual report, with supplementation as needed to provide all of the information listed below.  For efficiency, the District has developed a standard report form and may adjust it from time to time to help communicate clearly to LGUs the reporting data that are needed and avoid placing unnecessary reporting burdens on LGUs.  LGUs are encouraged to use this form.  In the future, the District may determine that the standard report format should be mandatory.    Until that time, an LGU may prepare a separate report using a format of its choosing.

LGUs are encouraged to use a concise format for the annual report.  At the same time, LGUs need to provide information that is sufficient for District staff to be fully apprised of activities by, and within the boundaries of, the LGU that affect water resources and further water resource programming.  At a minimum, the annual report must cover the following for the reporting year: 

  1. The status of capital projects identified in the local water plan and any other water resource projects under LGU development or consideration, and identification of any project on which the LGU is interested in partnering with the District.
  2. Progress on each water resource issue identified in the implementation section of the local plan.
  3. The status of each action identified in the local plan as a means to contribute to the LGU’s allocated phosphorus/nutrient load reduction, the cause of any failures or delays, and any proposed changes to the LGU’s strategy for meeting the load reduction.
  4. A summary of LGU land use activity as it may affect water resources, including: (a) permit applications for land disturbance received; (b) actions taken, including any variances granted; (c) pending development or redevelopment activity not yet the subject of an application; (d) zoning changes made or requested.
  5. Additional water quality, hydrologic, wetland and floodplain data developed within the LGU.
  6. A description of stormwater conveyance/management facility construction, inspection, maintenance and repair activity, including identification of any structural changes within the conveyance system affecting hydrologic/hydraulic modeling on greater than a parcel basis.
  7. A summary of LGU housekeeping activities including salt/sand storage and use, hard surface sweeping and other public facility management activities to protect water resources.
  8. An inventory of riparian, buffer, corridor, open space and other conservation land rights acquired through dedication, gift, purchase or any other means.
  9. A summary of the LGU’s budget as it pertains to local plan implementation.

Following District staff review of an LGU’s annual report, a meeting between staff may be arranged to complete the review, bring each party up to date on the other party’s activities, and coordinate activity for the next year.

  1. District staff may have questions or need further information about matters contained in or omitted from the LGU report.  If the District perceives that LGU implementation has lagged, this would be an opportunity to discuss this, identify causes of any failures or delays, and mutually consider adjustments.  As well, LGU staff may require more information about District activities over the past year as they affect the LGU.
  2. This meeting is an opportunity for the two parties to anticipate the next year’s activity.  A mutual briefing can be provided concerning programmed or potential capital projects, land conservation interests, cost-sharing or grant opportunities, development activity and other matters that would benefit from coordination. 
  3. Pending or necessary plan amendment can be reviewed.  Minnesota Statutes §103B.235, subdivision 1, and Minnesota Rules 8410.0160 requires that each local plan be revised and approved by the District within two years of a District plan amendment that affects an LGU, or as otherwise specified in the District implementation program.  The District has adopted the two-year standard of 8410.0160, except where the plan specifically states otherwise.  Where an LGU lies partly within the District and partly within one or more other watershed management organizations, the District will require local plan revision and approval within two years for at least that part of the plan that concerns land within District boundaries.

The District will endeavor to maintain communication and flow of information between itself and its LGUs on an ongoing basis.  The Board of Managers encourages opportunities for joint meetings with city councils on specific matters or for the purpose of general communication.