01Student
It is 11pm. An essay is due at 8am. The approved tool is slow tonight. The phone is on the desk.
The distance between the rules a district writes and what actually happens the moment a student or staff member hits Enter.
Students and staff use AI every day, on district devices and their own. One in ten teens now do all or most of their schoolwork with a chatbot. Most districts answered with a written policy, and almost none can say whether it changes anything the moment someone opens a chat.
of teachers now use AI for school as well.
RAND, 2025of U.S. schools have no guidance for generative AI use.
RAND, 2025The real tensions in writing an AI policy, and the nuance most rules ignore.
In groups of three, we run a reasonable policy through a normal school day, live.
Where these policies fail, how districts try to enforce them, and what that enforcement costs in reliability and in people.
Students using AI for the work itself: academic integrity, safety, and the personal data they paste into a prompt.
Staff and the program you are building: teachers, counselors, and administrators putting rosters, IEPs, and records into AI, plus the internal tools a district stands up on its own data.
A program that covers one arena and forgets the other is not a program. Most policies forget the second.
Should the rules change by grade? A second grader and a graduating senior are not the same user, yet most policies treat them as one.
Find two people near you. Each takes one role and plays it honestly, pressures and all. The goal is not to design a perfect policy. It is to watch a reasonable one meet reality.
"I answer for everyone, and I cannot be everywhere."
"I want them to think, not outsource the thinking."
"I am not trying to cheat. I am trying to be done."
As a trio, agree on three AI rules you genuinely believe are smart and fair. Write them down.
Choose one everyday situation from the next exhibit. Your district on an ordinary day.
Run it through each role, then mark each rule: held, ignored, or could not tell.
Do not overthink it. The rules already in your handbook are perfect. Three that come up constantly:
It is 11pm. An essay is due at 8am. The approved tool is slow tonight. The phone is on the desk.
Before reteaching, a teacher wants the common mistakes across a stack of graded, named essays, fast.
The assignment allows AI "as a tutor." A student opens a chat to draft the introduction.
An office staffer pastes a student's records into AI to draft a letter home to the family.
A help bot appears inside a trusted, approved website and offers to "write this for you."
A department stands up an internal AI assistant trained on district files, with no review.
Run it like a real Tuesday. Be honest about what each role can actually do with the tools they have today.
The finding: when a rule was ignored, who would have known, and how? If the honest answer is "no one," write it down.
| Policy | Governance | |
|---|---|---|
| Form | A document | A system |
| Lifecycle | Written once, then static | Runs continuously |
| Tested | Rarely, until an audit | Every prompt, in real time |
| Visible at point of use | No | Yes |
| Covers staff and internal use | Seldom addressed | By design |
We keep purchasing the first and reporting it as the second. Source: Tenet, 2026.
Most use is never seen at all: personal accounts, phones, and AI that appears inside sites you already allow.
What you do see, nothing acts on in the moment. The policy is a request, and the prompt has already been sent.
Flag-only tools bury staff. 5,500 alerts in two days is not oversight, it is a backlog no one can clear.
Each earlier method guards one slice of time. Only point-of-use governance covers the moment the prompt is sent.
Two axes decide whether a rule survives a normal day: can you see what is happening, and can you act on it the moment it happens.
Blocklists chase domains. But AI assistants now spawn inside approved sites: a help bot in your student system, an AI tab in a search engine, a writing assistant inside a document tool. The domain is allowed. The AI is not governed.
The answer is not to block harder. Lock everything down and students simply leave for ungoverned devices. The goal is to make district AI usable and safe, so the governed path is the easy path. For off-network use, we partner with a home solution.
A district already running an AI-governance web filter surveyed its high school teachers before adding point-of-use governance. With the filter live:
say AI misuse is already a problem in their own classroom.
say it is a problem at home, where the filter does not reach. 61% strongly agree.
Baseline teacher survey, n = 23, grades 9 to 12, 2026. AI-governance web filter and transparency tooling already in place.
You can see the logs. Useful, but after the fact, and only if someone reads them.
You get alerts. Still after the fact, and the volume can bury the people meant to act.
It acts in the moment, at the point of use: redact, block, or hold the line as it happens.
Most tools stop at flagging and call it safety. Seeing a problem is not the same as preventing it.
One school we worked with switched on a monitoring tool that flags risky chats. In its first two days, across more than 1,500 student conversations, how many flags did it raise?
On paper, this is maximum visibility, a flag every thirty seconds. But with no realistic resources to act on them, it is as good as tracking nothing at all. Flagging told them it happened. Nothing stopped it. Visibility you cannot act on is not safety. It is noise.
The teachers who feel in control are the ones watching every session. The rest may simply not see what they are missing. Either way, a policy that runs on teacher vigilance is borrowing against the people you can least afford to burn out. Governance should carry that weight, not the teacher.
Baseline teacher survey, n = 23, grades 9 to 12, 2026.
An internal AI program is not a vendor list and a training day. The same failures appear the moment staff start working, and they carry record-level data.
An allowlist no one enforces is the Level 1 policy again, just for adults.
Rosters, IEPs, and personnel files leave through staff prompts, not student ones.
An internal assistant on district data needs the same guardrails you ask of any vendor.
A policy without enforcement
is a suggestion.
Governance inside the AI conversation, on the device, in real time, for students and staff.
Redacts names and personal data before anything reaches the AI, typed or uploaded.
District, classroom, and staff policy applied live across every major AI tool.
On-device safety detection surfaces self-harm and bullying as it appears.
26% of U.S. teens now use ChatGPT for schoolwork, double the 2023 share.
Pew Research Center, 20257 in 10 teens have used a generative AI tool; 40% used it for school assignments, and 46% of those did so without the teacher's permission.
Common Sense Media, 2024About 6 in 10 teens say their school has no rules for generative AI, or they are unsure whether it does.
Common Sense Media, 2024Teacher generative-AI use reached 83% in 2023-24, up 32 points in a year, while most schools still give minimal guidance on responsible use.
Center for Democracy & Technology, 2024With student-monitoring software, 78% of teachers said students were flagged for discipline and 44% said a student was contacted by law enforcement from an alert.
Center for Democracy & Technology, 2022OpenAI retired its own AI-text detector over a "low rate of accuracy"; such detectors also disproportionately misflag non-native English writers.
OpenAI / TechCrunch, 2023