AI in UK schools: leadership, literacy and policy

A pragmatic guide for SLT, governors and AI leads. What to put in policy, how to build staff AI literacy, and how to keep safeguarding non-negotiable.

Three things to get right first

1. Safeguarding – no pupil personal data in any external chatbot, ever. You need a ring-fenced, protected system that can interface with your MIS, never uses your data for AI training, and is UK GDPR and DfE aligned.
2. Policy – living documents that set the expectations and the direction the AI itself must follow.
3. Literacy – staff, and later pupils, using AI well rather than avoiding it.

Each of the three fails on its own. A policy nobody can enforce, a safe system nobody uses, or confident staff with no shared standard all produce the same outcome. They only hold together inside an Educational Intelligence (EI) Layer – the school-owned layer where the policy, the curriculum and the safeguarding position are carried automatically into every AI task a teacher runs. That is set out in full in School Educational Intelligence: what an EI layer is and why UK leaders need one.

What a workable UK school AI policy covers

• Permitted and prohibited uses for staff
• Data handling, ring-fenced against your school information system
• Disclosure expectations when AI was used in pupil-facing outputs
• Pupil-facing academic integrity rules
• CPD expectations and a review cycle – termly, not annually

The full seven-section framework, with a 90-day rollout, is in Creating a School AI Policy: a practical guide for UK leaders.

Building AI literacy that sticks

One-off INSET fails. AI literacy grows when staff use a tool weekly on real teaching tasks with clear pedagogical framing – not when they are sent on a generic course. That is far easier when the tool is already inside the software they write in; see AI in Google Docs for teachers.

Safeguarding non-negotiables

• Never use identifiers – names, SEND details or safeguarding information – in consumer LLM prompts.
• Teachers.guide applies a 24-hour data retention purge on solo teacher accounts; retention for school accounts is governed by the school's DPA.
• Role-based access for SLT, Safeguarding Leads, SENCos and class teachers.
• Pupil access via short code only – no pupil email address required.
• Optional school subdomain for clear provenance.

Frequently asked questions

Does a UK school need a written AI policy?

Yes. Schools are accountable for how AI is used on their premises and in staff workflows, and a written policy is the artefact that evidences intentional, safe use.

Who should lead AI in a school?

A named SLT AI lead, usually a deputy or assistant head with a digital remit, reporting to governors on a standing agenda item.

How do schools stop staff using unapproved AI tools?

By making the approved route the easier route. Shadow use falls when the school system is faster, safer and already knows the curriculum.

Where this fits in a joined-up school system

Policy, safeguarding and literacy converge on one question: does your school run AI, or does AI run in your school? Explore the platform overview, the leadership workflow, or how schools join.