AI Policy for Primary Schools: What It Needs to Cover

Most primary schools don't need a twenty-page AI policy. They need a short, clear document staff will actually read, and that a governor can sign off with confidence. Getting AI in primary schools right starts here — not with a tool, but with a policy that says plainly what's expected.

What a good AI policy covers

• Acceptable use — clear examples of appropriate use (planning support, resource ideas, drafting) versus inappropriate use (generating pupil reports word-for-word, inputting identifiable pupil data).
• Data protection — a plain-English statement that no personal or identifiable pupil information is entered into public AI tools.
• Safeguarding — how AI-generated content is checked before it reaches pupils or parents, and who is responsible for that check.
• Roles and accountability — usually the headteacher or a designated senior leader owns the policy, with governor oversight.
• Review cycle — AI tools change quickly; an annual review date keeps the policy honest rather than symbolic.

A common mistake

Many schools copy a policy template from another school or a MAT and never adapt it to their own context. A policy that doesn't reflect what your staff are actually doing with AI won't be followed — and won't protect you if something goes wrong. Start from how your staff currently use these tools, not from a generic checklist someone else wrote.

How long should it actually take to write?

A working first draft, covering all five areas above, typically takes a competent SLT member two to three hours to write from scratch — longer if you're consulting staff and governors properly, which you should. If that sounds like more time than you have this term, it's worth knowing that a tailored, governor-ready AI policy is included as standard with every AskColin package, drafted during your free site visit and aligned to DfE guidance, KCSiE and UK GDPR.