AI Governance Framework: A Practical K-12 Guide

Short answer

How to build an AI governance framework for schools

An AI governance framework for schools is a short, shared structure for making AI decisions. It covers eight parts: purpose and principles, ownership, tool review, data and privacy, classroom use, visibility and review, training, and communication. Each part names an owner, a simple rule and a review point, so decisions stay consistent as new tools and questions arrive.

Use this page as part of a connected review: understand the purpose, consider the people affected, check the relevant safeguards, and follow the related routes for practical next steps.

Most schools already make AI decisions, often one at a time and under time pressure. A framework turns those scattered choices into one steady way of working. It does not need to be long or formal. It needs to be clear enough that a teacher, a leader and a parent would all describe it the same way.

The eight parts of a school AI governance framework.

The first two parts set direction. Purpose and principles explain why the school uses AI at all, for example to support learning and reduce routine work for staff, and what it should never replace, such as a teacher's judgment or a student's own thinking. Ownership names who is responsible for each decision. Without these two parts, everything else becomes a list of rules with no reason behind them and no one to ask.

The next three parts deal with tools and their use. Tool review is the short path every new AI tool follows before anyone uses it with students. Data and privacy describes what information may go into which tools, and how the school checks that tools fit laws such as FERPA, which protects the privacy of student education records, and COPPA, which covers online services that collect personal information from children under 13. Classroom use sets out when and how students and staff may use approved tools.

The last three parts keep the framework alive. Visibility and review describe what the right adults can see about AI use and how often the school looks back at what is working. Training makes sure staff understand the framework and feel confident using it. Communication keeps families and students informed in plain language. Confirm legal details with your privacy reviewer, counsel or state guidance, since the framework should point to them rather than restate them.

How the parts connect during a real school term.

Imagine a high school science teacher who wants to use an AI tool that gives students feedback on lab reports. Under the framework, she sends a short request to the person who owns tool review. That person checks the request against the school's purpose: does this help students learn, or does it do the work for them? Then the privacy owner looks at what student information the tool would collect and whether its terms fit the school's rules.

If the tool is approved, the classroom use part tells the teacher what students may and may not do with it, and what to tell them. The visibility part means a curriculum lead can see, at a sensible level, whether the tool is being used as planned. At the end of term, the review group asks whether it helped. Training picks up anything staff found confusing, and communication tells families what was added and why.

This is the real value of a framework. Each part hands off to the next, so a single request does not depend on one busy person remembering every step. When something goes wrong, the school can see which part needs attention, rather than rewriting everything at once. It also makes the framework easier to explain. A new teacher can follow one request from start to finish and understand the whole structure in a few minutes, without reading every supporting document first.

A simple way to write the framework down.

A framework does not need special software or a long document. Many schools can write theirs on two pages. Give each of the eight parts a short heading, then answer three questions underneath: who owns this, what is the simple rule, and when will we look at it again. For example, under tool review you might write: owned by the assistant principal; every new tool answers five questions before classroom use; reviewed each term.

Keep the detail in linked documents. The acceptable use policy, the list of approved tools, the privacy checklist and the family letter can each sit in their own place, with the framework pointing to them. This keeps the framework short enough to read in a few minutes, while still showing how everything connects. When a linked document changes, the framework itself rarely needs to. Only the owner of that part updates their document and notes the change in the decision record.

Test the draft before you share it. Take a recent real request, such as a teacher asking about a new tool or a parent asking how their child's information is protected, and walk it through the framework step by step. If you cannot tell who acts next, that part needs a clearer owner or rule. If two people both think they act next, agree which one does. A short test like this often finds more gaps than a long discussion.

Common framework mistakes and what good looks like over time.

One common mistake is copying a long framework from somewhere else without adapting it. It may cover every part in theory, but staff cannot find their way through it and nobody feels it belongs to them. Another is leaving parts blank because they seem less urgent, often training and communication. Those quiet parts are usually what decides whether teachers and families trust the rest. A final mistake is writing the framework in formal language that only its authors understand.

A third mistake is making one person own everything. In a small school that may be necessary at first, but it creates a single point where requests wait. Spreading ownership, even across three or four people, keeps decisions moving and gives each person a part they can do well. Leaders stay responsible for the whole, while others look after the details. Write the backup for each owner next to their name, too.

Over time, a healthy framework becomes quieter. Teachers know where requests go, reviews take less time because decisions are recorded, and new staff can understand past choices from the record. School-managed tools with role permissions, usage visibility and audit trails, such as Ethos Educate, can support the visibility and review parts, but the framework itself is a set of human decisions the school owns and keeps improving each term. Families notice the difference as well, because their questions get consistent answers.

Start with purpose. Agree in a few sentences why the school uses AI and what it should never replace.

Give every part an owner. Each of the eight parts needs one named person, even if one person holds several.

Keep the review path short. Decide the few questions every new tool must answer before anyone uses it with students.

Plan the review rhythm. Set a date each term to look at what changed and update the framework.

The eight parts:

Purpose, principles and named owners.

Tool review with data and privacy checks.

Classroom use with visibility and review.

Training for staff and clear communication.

Signs the framework works:

Staff know where to send a tool request.

Each part has an owner and a review date.

Families can find a plain summary.

Decisions are recorded with their reasons.

Draft. Write one short paragraph for each of the eight parts, naming an owner and a simple rule.

Test. Walk a recent real request through the draft to see where it stalls or feels unclear.

Share. Publish a plain summary for staff and families and explain how to raise questions.

Review. Meet each term to check what changed and adjust the parts that need it.

Use this guide to draft a first AI governance framework for your school or district and agree who owns each part.

Common questions

Quick answers to what schools and families ask most about this topic.