Using AI in schools: a staff-first planning and review guide

A school can begin with a narrowly defined staff task while it decides whether any pupil-facing use is appropriate. Drafting a lesson outline from public curriculum material has different implications from uploading pupil work, generating individual feedback or allowing children to use an assistant directly.

This guide offers a planning method. School leaders should apply the education, safeguarding, data-protection and assessment requirements relevant to their jurisdiction and setting. The Department for Education's generative AI guidance applies to England; it should not be presented as the rulebook for every UK school.

Choose one staff workflow

Start with a task whose output a teacher can assess: a draft lesson structure, questions based on approved source material, a non-sensitive administrative template or a proposed set of revision activities. Use public or fictional inputs for the first exercise.

Write down the learning or administrative objective and what a good result should contain. Do not assume that quicker preparation means better teaching, that polished text suits the pupils or that a product's general demonstration proves an educational benefit.

Make professional review explicit

DfE emphasises professional judgement and the responsibility to check generated content. Its guidance also identifies risks including inaccurate, inappropriate, biased and unreliable output. Treat the draft as something to inspect, not material that can go straight to a class.

A practical review can ask:

• Does it match the intended learning objective and curriculum?
• Are the facts, examples and references correct?
• Is the language appropriate for the intended learners?
• Does it introduce misconceptions or omit important context?
• Are proposed adaptations suitable, and who will check them?
• Does the activity actually reveal pupils' understanding?

A fictional lesson-planning exercise

Give the assistant a public topic outline and ask for a short lesson structure with an explanation, two practice activities and a check for understanding. Require it to identify assumptions and refrain from inventing curriculum references.

The teacher compares the draft with the approved material, corrects errors and decides which elements are useful. Record preparation and review time separately. No pupil profiles, health information, assessment records or identifiable work are needed for this first exercise.

A suggested instruction is: “Using only the supplied public outline, draft an activity sequence for the stated learning objective. Flag missing information and assumptions. Include a question that helps the teacher check understanding. Do not claim alignment with an examination specification unless the supplied source establishes it.”

Agree information and access rules

Before real school information is used, involve the appropriate safeguarding, IT and data-protection leads. Check the supplier's account terms, age restrictions, retention, reuse, access controls and any connections to school systems. An approved brand name alone does not answer those questions.

Provide a clear route for staff to ask about a proposed use or report a concern. Do not frame teacher approval as sufficient permission to enter any pupil information into any tool. The school must establish the relevant handling and governance arrangements.

Make pupil-facing use a separate decision

Consider the age group, purpose, supervision, access and suitability of the product. DfE advises appropriate safeguards for pupil use and compliance with product age restrictions. Those considerations do not establish that every school should provide pupils with access.

If a use is approved, explain its limits in language pupils and families can understand. Keep a route to a person, and consider pupils who cannot or should not use the tool. A staff pilot should not quietly become a pupil rollout.

Follow the assessment rules that actually apply

For qualifications, use the awarding organisation's current instructions and applicable JCQ AI assessment guidance. JCQ requires assessors to accept students' own work and addresses acknowledgement and authenticity where AI is used. A school's classroom experiment must not override those rules.

Explain permitted and prohibited use for each task. Keep appropriate evidence of how work developed and follow the established process when authenticity is in question. Do not treat an AI-detector score as a complete finding of misconduct or invent new examination arrangements from a general blog guide.

Record what the pilot shows

Measure useful staff work completed, review effort, corrections and any information-handling concerns. Gather feedback about suitability for the lesson or administrative task. A positive staff experience is not proof of improved pupil attainment.

At the review, decide whether to stop, change the task or continue within the same boundary. Any move to additional data, year groups, users or connected systems requires another decision.

Use training to practise judgement

Staff training should include source checking, missing information, inappropriate commitments and when to stop. Our fictional review exercise can be adapted for an approved non-pupil scenario.

Blue Canvas can discuss practical staff AI training. Bring a task, the source material staff are allowed to use and the review standard the school expects.