Understanding "Policies" at ISD No. 834

FIXING STILLWATER SCHOOLS

Log-inHome

Guide to SAPS Policy Research

There are many reasons one could have for doing research about Policies at ISD No. 834, primary among them is when an action asserted by the District to be an enforcement of policy is questionable or does not seem to be a just outcome of what is written. Sometimes, there is digging to do for related District "protocols" or "guidance" that may be relevant and related to the Policy purportedly at issue. Other times, there is a principle that seems off.

School districts are a branch of government, like all others, more local than most, so in theory, more properly directly responsive. Please send your policy suggestions or thoughts to the school board, superintendent, or the policy committee, which makes recommendations to the School Board for proposed action by the Board, which retains the final authority on all policy matters, subject to State and Federal law, throughout district operations.

When researching a policy, it is good to collect the materials pertaining to the passage of the policy, and any subsequent amendments to it, including Board Meeting Agenda and Minutes, as well as recordings of Board Meetings. The District must do more in compliance with Minnesota Open Meeting law (Minn. Stat. 13D) regarding Board and Committee Meetings; Policy Committee meetings should be recorded with readily available audio/visual made public record.

The key research tactic beyond what can be gathered from materials available at or near the surface is Minnesota Government Data Practices Act (MGDPA/DPA) requests. We have one-page summary regarding DPA requests. Generally, you can request any or all written/codified materials of the school district, with certain protections for protection of children, grades, etc. To the extent the school is carrying out government functions, all materials created in the process of that as part of any government function being carried out are to be produced upon request for copies or inspection, inspection is free, copies have employee-time or material derived cost, of which you can request estimated cost before incurring any liability, if you put that in the request.

School Board Policymaking

The District has a few hundred enumerated policies organized by categories, each is given a number between 100-999, with many newer policies using decimal places to place a related policy adjacent to a main policy on a subject. You can view all District "Policies" on the Board Policies, here, or use the table of links, below.

A note about what is and is not considered and included in this list of policy:

The word "policy," as used by the District, is limited to essentially their highest order of laws or rules governing the district, employees, and operations. There are other categories of written rules governing the district, employees, and operations, that the district does not have listed as "policies," but which govern affairs to the extent not conflicting with policies or local, state, or federal law. These include, "protocols," which are passed by the Board, and, "guidance," which may come solely from the Superintendent.

Email [email protected] to be given notices of the Policy Committee, which

Policies are organized in nine different "Policy Series." These are generally based on recommendations that most districts follow, so many school districts may have academic program policies in the "600 Series," as an example.

Click to visit the District's Policy Page or Click the Menu items below to go to a particular series:

What are current District Policies?

View the Board's 2025 Policy changes

Go to the District Policy Committee Tracker

Read our School Policy White Paper

This Draft Report reviews the facts and summarizes trends in Stillwater Area Public Schools (ISD No 834) policymaking as are clearly rooted in state and national trends, including as is directed by the statewide non-governmental organization, the Minnesota School Boards Association (MSBA). For information about the current or prior drafts, email [email protected].

window.addEventListener('vev.track', (e) => { const event = e.detail; clarity('event', event.type); if (event.data) { for (const [key, value] of Object.entries(event.data)) { clarity('set', key, value); } }