When reviewing a proposed board policy, it's crucial to distinguish between strategic goals and operational guardrails to ensure effective governance. When you read a policy, ask: does this describe an outcome we want to achieve, or a boundary we won't cross? A strategic goal states what success looks like for students. An operational guardrail states what decisions the superintendent may not make. The words "shall," "will," "may not," and "shall not" are clues, not rules—context matters more than the modal verb, and you can determine that context by asking whether the statement describes a desired end state or a prohibited action.
The distinction matters because boards that conflate goals with guardrails fail to govern effectively: goals without clear guardrails can lead to mission creep and superintendent overreach, while guardrails without clear goals can leave districts without direction. Goals need monitoring for progress; guardrails need monitoring for violations. A common mistake is writing a goal that sounds like a guardrail, "Our district shall improve reading scores", when you mean a measurable target with a timeline. We recommend to make goals specific enough that you can track them year over year, and make guardrails clear enough that they constrain decisions without dictating day-to-day implementation details.
In practice, you'll often see this when a policy lands on your agenda—whether it arrives from a committee, a superintendent recommendation, or a community petition. If it reads like a project plan with benchmarks and dates, your role is to approve the direction and then receive quarterly progress reports. If it reads like a constraint, prohibiting certain disciplinary actions or mandating specific parent notification timelines, your role is to set the boundary and then receive reports only when someone crosses it.
some policies do both. A literacy initiative might state a goal ("80% of third-graders will read at grade level by 2027") while also including guardrails ("the district shall not adopt curricula that have not been evidence-reviewed"). When a single policy contains both elements, treat them as separate governance objects. Approve the goal as a strategic direction and approve the guardrail as a boundary, then monitor them differently. If your board's parliamentary procedures allow amending motions to separate these elements, do so. Otherwise, note in your meeting minutes that you are approving two distinct governance acts and track them separately going forward.
- Before you vote on any new policy, underline every "shall," "will," "may not," and "shall not." This simple test forces you to identify every binding statement in the document and decide whether it describes a target or a limit. Mark each as either a goal-statement or a guardrail-statement.
- If you find more than two goal-statements in one policy, ask the sponsor to split them. A policy that tries to accomplish too many things at once loses focus and dilutes board attention. Limiting goals to two per policy forces the board to prioritize and be explicit about what matters most in a given governance cycle, which improves both oversight and accountability.
- When a goal comes to your monitoring agenda, ask: "What data will we see, and how will we know if we're behind?" When a guardrail comes to monitoring, ask: "What happens when someone crosses this line, and who decides?" If the answer is unclear, work with the superintendent to establish a clear enforcement protocol before the next cycle.
- At your next one-on-one with the superintendent, ask directly: "What would you need from the board to make this goal achievable?" This surfaces resource gaps early.
- Review your existing policies using the underline test. Move any goals that read like guardrails back to the board's policy committee for rewriting. Move any guardrails that read like goals back to the committee for clarification. This is not a one-time exercise—your governance clarity improves with each policy cycle.