When AI policy meets the classroom
Most school AI policies are written for the inspector, not the teacher. Here's the difference — and why it decides whether a trust-wide rollout actually works.
Walk into any staffroom this term and you’ll find two AI policies. There’s the one in the shared drive — and there’s the one teachers actually follow. They’re rarely the same document.
The written policy tends to be defensive. It exists to be produced when someone asks “what’s your position on AI?” — an inspector, a governor, an anxious parent. It is careful, comprehensive, and almost entirely unread by the people it governs.
The real policy is whatever a Year 9 class and their teacher have quietly negotiated by week three. And if those two things have drifted apart, the paper one isn’t a policy. It’s a liability.
Write for the corridor, not the cabinet
A policy that changes behaviour has to survive contact with a busy Tuesday. That means it is short enough to remember, specific enough to act on, and honest about the cases everyone actually hits — a pupil who used a chatbot for their homework, a teacher who wants to mark faster, a parent who’s worried.
If your staff can’t recall the policy without opening it, it isn’t a policy — it’s an archive.
The trusts getting this right tend to lead with a handful of plain commitments rather than a twenty-page framework. Something a head of department can teach to a new starter in a corridor.
Three things a classroom-first policy gets right
- It names the grey areas. Not “don’t misuse AI,” but what counts as help versus cheating in this subject, at this key stage.
- It trusts teachers with judgement. Guardrails, not a script. The people in the room are the policy’s engine, not its risk.
- It’s a living document. Reviewed each term, because the tools change each term. A policy dated two years ago tells pupils exactly how seriously to take it.
Where this leaves leadership
The job of a senior team isn’t to author the perfect document and file it. It’s to set a small number of clear commitments, give staff the confidence to apply them, and revisit them often enough to stay honest. That’s harder than a policy PDF — and it’s the only version that works.
If you’re a trust trying to close the gap between the policy on the drive and the one in the room — or an edtech team that needs that classroom reality built into your product — that’s exactly the bridge I work on.
Let's turn the argument into the honest next step.