Introducing AI in a primary school isn't a single decision — it's a sequence. Schools that treat it as "let's tell staff they can use ChatGPT now" tend to get inconsistent use, nervous governors, and at least one data protection near-miss within a term. Schools that follow a clear order get workload relief without the wobble. Here's the sequence that works.
Step 1: Audit where the time actually goes
Before choosing any tool, spend a week noticing where staff time disappears. For most primary schools the answer is consistent: planning, resource creation, marking and feedback, parent communications, and report writing. You can't target AI usefully until you know which of these is your school's biggest pressure point — and it varies more than you'd expect between schools of similar size.
Step 2: Write the policy before the practice
It's tempting to let staff experiment first and formalise later, but that gets the order backwards. A short, clear AI policy — covering acceptable use, data protection and safeguarding — should exist before wider staff use begins, so everyone is working to the same rules from day one rather than unlearning bad habits later. It doesn't need to be long; it needs to exist and be understood.
Step 3: Train, don't just permit
Telling staff "you're allowed to use AI now" is not the same as enabling them to. The single biggest predictor of whether a school actually saves time is whether staff had proper, hands-on training built around real tasks — not a permission slip and a link to ChatGPT. A well-trained staff using a basic tool consistently outperforms an untrained staff with the most sophisticated platform on the market.
Step 4: Start with one task, not everything
Pick the single highest-workload, lowest-risk task from your Step 1 audit — usually parent letters or resource first drafts — and embed AI there properly before expanding. Trying to change planning, marking, reporting and communication all at once means none of them stick. One task done well becomes the proof point that brings the rest of the staff on board.
Step 5: Bring governors and parents with you
Adoption stalls when governors feel out of the loop or parents hear about it secondhand. A short governor briefing and a proactive parent communication turn AI from something that happened to your community into something you led transparently. This is also the step that protects you if anything is ever questioned.
Step 6: Review and expand
After a term, check what actually changed against your Step 1 baseline. Which tasks got faster? Where did staff hit friction? Use that to decide what to embed next. AI adoption in a primary school is a rolling process, not a one-off launch — the schools that get the most from it treat it as something they revisit each term.
Key takeaways
- Follow the order: audit, policy, training, one task, community, review.
- Train staff properly — permission alone doesn't save time.
- Start with one high-value task rather than changing everything at once.