AI for schools: a complete guide

A school adopting AI faces about eight decisions. They arrive in a predictable order, most of them are settled badly by default rather than deliberately, and the expensive mistakes are all made early. This walks through them in sequence.

Decision 1: permit, ban, or ignore

Ignoring is the default and the worst of the three: students use AI, the school has no position, and staff each improvise a different rule.

A ban is honest and does real work — it keeps AI out of assessments meant to be unaided and gives staff a line to hold. What it does not do is stop use, because students have phones. Its measurable effect is that use moves out of view, on tools the school has not filtered.

Permitting one filtered tool gives the school something to point at, which is worth more than a prohibition it cannot enforce. It is also the only option that lets the school teach anything about how the tools fail.

Decision 2: which tool

The properties that matter are narrow. Can the school write its own blocked topics? Do those apply to image and video, not only chat? Does filtering run on the server, so it follows students home? What happens when the safety check is unavailable? Can staff see what was blocked?

Everything else — model quality, interface, integrations — is real but secondary, because a tool that fails these cannot be adopted at all.

Decision 3: the content standard

This is the school's, not the vendor's, and it takes a meeting rather than a settings screen. Name the topics in the words that would actually come up, not euphemisms — a filter configured from "inappropriate material" enforces nothing.

Expect to revise it. The first version is always missing something, and the useful signal is what students actually attempted in the first term.

Decision 4: the policy

Three categories, not two: permitted, expected, forbidden. Most policies fail because they only have permitted and forbidden, and cannot express a task where the teacher wants AI used.

Push the decision to the assignment rather than issuing a blanket rule, and give staff a standard phrase for each category to put on the task itself. Also settle attribution — one sentence naming the tool, the part, and what the student changed — and make honest disclosure safe rather than punishable.

Decision 5: assessment

This is where most of the actual risk lives, and no filter addresses it. Decide which tasks measure unaided ability and make those unfakeable by design: in-class writing, a short viva on a submitted piece, work tied to something specific to your classroom.

Do not build the response around AI detectors. They measure how predictable writing is, which means they suspect careful and second-language students while a lightly edited AI draft passes. A school that disciplines on a detector score will eventually accuse a student who did nothing wrong, and that costs more than every undetected essay combined.

Decision 6: staff

Staff need three things, and a demo of the product is not among them.

• Twenty minutes actually using the tool, including trying to break the filter. Nobody trusts a control they have not tested.
• The three policy categories and the exact phrase to put on an assignment.
• One person to escalate to, and permission to say "I do not know, I will find out" to a student.

The failure mode is a policy circulated by email that nobody reads, after which each teacher improvises and students correctly conclude the rules are arbitrary.

Decision 7: parents

Tell them before rollout, not after. Say which tool, what it filters, what the school can see, and what you are asking of them at home. A parent who knows the school provides a filtered option is markedly less likely to hand over an unfiltered one.

Say plainly that the filter reduces exposure rather than eliminating it, and that there is a plan for the exception. A school that has said this in advance is in a completely different position on the day something gets through than one that promised it could not happen.

Decision 8: what you will review

Set this before launch or it never happens. Once a term is enough: what was blocked and in what categories, whether any pattern suggests a topic to add, which staff are using it and which are not, and whether the assessment changes held.

Patterns are more useful than incidents. A single blocked request is noise; the same category appearing repeatedly is information.

A realistic first term

1. Weeks 1-2: choose the tool, write the content standard, draft the policy.
2. Weeks 3-4: staff session, including hands-on time trying to defeat the filter.
3. Week 5: letter to parents, before any student account exists.
4. Weeks 6-8: one department or year group only. Small enough to fix things quietly.
5. Weeks 9-12: widen, using what the pilot taught you about the topic list.
6. End of term: first review. Expect the content standard to need revision.

The common failure is launching school-wide in week one, discovering the topic list has a gap in week three, and having no way to fix it quietly.