Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Board Superintendent Roles topic
No spam. Unsubscribe anytime.
Policy committee reviews new policies defining board, superintendent roles
Summary
At its Sept. 11 policy committee meeting, Duluth Public Schools reviewed two MSBA-model policies (301 and 305) that clarify the relationship between the school board and the superintendent and assign responsibility for implementing district policy to the superintendent.
Get email alerts on the Board Superintendent Roles topic
No spam. Unsubscribe anytime.
Sept. 11 — Duluth Public Schools' policy committee reviewed draft Policy 301 (School District Administration) and Policy 305 (Implementation of School District Policy) during a first reading, discussing how the documents describe the relationship and responsibilities between the school board and the superintendent.
The committee chair opened the discussion by reading the stated purpose of Policy 301, saying the policy “is to clarify the role of the school district administration and its relationship with the school board.” Superintendent Magus told the committee the two policies “talk about the nexus between the school board and the superintendent and the administration,” and that it is the superintendent’s responsibility “to make sure that those policies are implemented, fairly and judiciously.”
Nut graf: The policies are MSBA-model documents intended to replace older 2,000-series language (for example, Policy 2055) and to make explicit how the board and superintendent will interact when seeking recommendations, background information and professional advice from administration. Committee members asked staff to clarify whether certain procedural documents would require annual board review and whether the board is expected to review the administration’s written procedures, guidelines and directives on a yearly basis.
Committee members, including Board Member Amanda Reicassel and Board Member Leffold, said the drafts align with current practice and help communicate roles to the public. Reicassel said, “I don't have any comments for improvements or edits at all. I think it's, well written, and I support it.” Members asked staff to confirm how the guidance in section C — that the school board “shall seek specific recommendations, background information, and professional advice from the school district’s administration” — should be interpreted in practice.
Staff (Patty) said the language follows an MSBA model and recommended asking MSBA for clarification about whether the model policy expects an annual, board-level review of all implementation procedures. Several members observed that some model policies are intended to be reviewed annually while others are reviewed on multi-year cycles; staff said they would seek MSBA guidance between first and second reading and bring recommended language back to the committee.
The committee also discussed the interplay between these new policies and existing documents: Policy 208 (Board Policy on Policies) and district regulations such as the employee and student handbooks. Staff reminded the committee that the district's employee and student handbooks are already subject to annual review and approval by the board and that those handbooks are tied to implementation practices described in the draft policies.
Ending: The policies will return for a second reading, with staff to consult MSBA and to propose adjusted wording about the timing and scope of board review of administrative procedures if needed.

