Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Meeting Procedures topic
No spam. Unsubscribe anytime.
Wayzata board presses for clearer SOP, earlier attachments and fewer "surprises" at meetings
Summary
Board members and staff discussed formalizing a 'no surprises' practice, stronger expectations for sending questions ahead, and a standard operating procedure requiring packet materials be released at least three days before regular meetings; administrators noted some late attachments are unavoidable but agreed to tighten processes.
Board members devoted significant time to governance practices aimed at reducing last‑minute surprises at meetings and improving transparency. The chair and several members urged colleagues to send substantive questions ahead of meetings and to use committee work sessions for deep dives so regular meetings can proceed efficiently. "As a common courtesy, if you're planning to vote no, can you call the chair and let them know?" one member said, explaining the goal is to surface concerns early so staff can rework or provide more information.
Administration recommended setting a consistent release cadence for board packets and noted that some attachments (for example, school presentations or final budget exhibits) may arrive late for operational reasons. Staff proposed that board packets be published to the board book no later than three days before regular meetings and that public attachments be available at the same time when not restricted by confidentiality. Members suggested codifying a standard operating procedure and including an appendix that clarifies exceptions and timelines for attachments.
Board members also discussed the tension between strict time rules (e.g., limiting member remarks by Robert—s Rules) and the need to allow longer discussion for complex topics. While some advocated time limits (e.g., 5 minutes per question), others said answers — not questions — tend to lengthen meetings and urged members to prioritize questions that benefit the broader public.
Next steps: staff will draft SOP language for packet release timelines and bring proposals (including possible wording changes to the handbook and Policy 2‑12 where relevant) to the policy committee for consideration.
