AI Implementation in Schools: A One-Term Plan for a Small School

Spend weeks 1 to 2 auditing how staff already use AI, weeks 3 to 4 agreeing a one-page policy, weeks 5 to 10 running two small pilots, week 11 training all staff in one session, and week 12 reviewing with governors. Give every step a named owner and a budget cap before you start.

A small school has one advantage large ones do not: a head who can change a practice on Monday and see the effect by Friday. It also has a problem. There is no spare person. The plan below assumes about four hours a week of leadership time and two hours from each pilot volunteer, and it is built so that any single week can slip without breaking the term.

Follow me on Instagram@sagnikteaches

The term at a glance

This is a plan for implementing AI across a school's own work, not a guide to using it with pupils in lessons. For the wider question of what an education organisation should tackle first, see five workflows, tools and costs, and for a version aimed at education businesses that also works through one country's privacy principles, the 90-day starter plan.

Connect on LinkedInSagnik Bhattacharya

Weeks 1 and 2: audit what is already happening

Staff are very likely using AI already, on personal phones, on free accounts, with no rules. The audit finds out how, without blaming anyone. Send a five-question form, then spend ten minutes with the office manager and each phase leader.

Subscribe on YouTube@sagnikteaches

1. Which AI tools have you used for school work this year?
2. For which tasks?
3. Did you enter anything that names a pupil or family?
4. Would you use a school-approved tool if there was one?
5. What takes the most time in your week that is mostly writing?

Promise in the covering note that the audit is for finding out, not for discipline. If people think it is a hunt, they will give short answers.

A filled-in audit for a 140-pupil primary school

The audit surfaced two things worth acting on: report comments with real names going into a free tool, and meeting recordings leaving the building. Neither was malicious. Both go into the risk log, and both shape the policy in week 3. The same audit also shows the best pilot candidates: newsletter and parent email (steady, low risk) and lesson resources (high volume, no pupil data).

Weeks 3 and 4: policy, then tool

Write the policy before you choose the tool, because the policy sets what the tool has to do. Use one page. The AI usage policy tutorial has a longer structure; the school version needs only these clauses:

Approved tool: [name], school accounts only.
Never enter: pupil names, photos, special needs or health information,
safeguarding details, staff HR matters.
Allowed: lesson ideas, resource drafts, anonymised examples,
newsletter structure, admin templates.
Checking: a named member of staff reads every output before it leaves.
Disclosure: tell parents in the newsletter which jobs use AI.
Incident: if pupil data is pasted in, tell [owner] the same day.
Review: governors receive an update each term.

Notice what the policy does not do. It does not ban AI and it does not list brand names beyond the approved one. Bans send use underground, and brand lists age within weeks.

Choosing the tool in week 4

Pick one tool, and start with accounts the school already holds. A school whose staff hold eligible Microsoft 365 business or education licences already has Copilot Chat at no extra cost, covered by Microsoft's enterprise data protection when staff sign in with school accounts; one on Google Workspace for Education should read what Gemini includes and what costs extra. If you need a separate tool, ChatGPT Business and Claude Team both list at $20 a user a month billed annually ($25 monthly) with a two-seat minimum, and both state that business content is not used for training by default. Verify current terms on the vendor page before you sign.

Whatever you choose, ask the vendor in writing four things: is our content used for training, where is it stored, how long is it kept, and what happens to a leaver's chats. Keep the replies in the audit folder; the privacy terms checklist explains where to find each answer.

Weeks 5 to 10: two pilots, one risky and one safe

A pilot that only does safe work proves little about your controls, and one that only does risky work scares everybody. Run one of each. Both keep a log: date, task, minutes saved or lost, edits made, anything odd.

Pilot A: office and parent communications

The office manager and two colleagues use the tool for newsletters, reminders and standard replies. Real facts come from the school; the tool supplies structure and tone. A starter prompt with a filled-in example:

Write a 90-word parent reminder in a warm, plain tone.
Use only these facts: Year 4 trip to the farm on Thursday 12 March;
leave 9:15, back by 3:00; pack lunch, waterproof coat, named bottle;
permission slips due Monday. End with the office number placeholder.

Typical output: a friendly paragraph with every fact present. What you fix: any invented detail (the draft once added "wellies", which nobody asked for), the placeholder, and the greeting. Time saved is real but modest, about six minutes on a reminder that took ten.

Pilot B: planning and resources, no pupil data

Three teachers and a lead use the tool to draft retrieval quizzes, vocabulary lists and differentiated reading questions. The rule is simple: topic and year group go in, no child does. Example: "Draft ten retrieval questions on the Roman Empire for Year 5, three easy, five medium, two stretch, with answers." The teacher checks every answer, because the risk is a confident wrong fact. A teacher who finds one error in a ten-question set should record it; the log of errors becomes useful evidence for governors.

Example: a pilot that went wrong in week six

Illustration: a Year 6 teacher asked for "a comment for Sam on fractions" and typed the full name. The policy rule caught it within a day, because the log showed a pupil name. The fix was a template with "[pupil]" as a placeholder, and a ten-minute walk-through for all pilot staff. The incident went into the risk log, not into a disciplinary file.

Example: a resource prompt and what to fix in the answer

Write six short-answer questions on the water cycle for Year 4,
two easy, three medium, one stretch. Give a one-line answer for each.
Use vocabulary a nine-year-old reads: evaporation, condensation,
precipitation. No trick questions.

Illustrative output: six clean questions with answers. What the teacher fixes: the stretch question asked why clouds are white, and the answer given was wrong (it blamed dust rather than light scattering), and one "easy" question used the word "transpiration", which the class has not met. Two edits in six questions is the normal rate in a first fortnight, and it is why every output goes past a teacher before it reaches a classroom.

The ten-minute weekly check-in

During pilots, the deputy holds a standing ten-minute meeting: read the risk log, hear one success and one problem from each pilot, and decide one action. Keep it to ten minutes with a timer, and write the single action into the log. Short, regular and recorded beats long and occasional, and it gives you the evidence for week 12 without a scramble.

Owners, hours and the budget table

Put the money and the hours in one table before week one, so governors see the whole cost. Illustrative figures for a 140-pupil school valuing staff time at $40 an hour; replace with your own.

The hours are a cost of attention, not new money. The cash cost is the tool line and can be zero if you use accounts you already pay for. Say that to governors in those words, so nobody hears $3,490 as a bill.

Who does what when there is no spare person

In a school of 140 pupils one person often holds three roles. The danger is not overload so much as unclear ownership, so write down what each role does and, just as useful, what it does not.

If the head and data protection lead are the same person, give the link governor the job of checking that the vendor replies exist. A second pair of eyes on one document is cheaper than a mistake.

The risk log, filled in

A risk log is one table the deputy updates weekly, and it is the document that makes a governor update credible. Illustrative entries from the term above:

Read the log aloud at the start of each weekly ten-minute check-in. The point is to keep the same five rows visible so that they get closed rather than forgotten.

What parents ask, and wording that answers them

Parents rarely object to AI; they object to being surprised. Prepare short answers in the same plain tone as the newsletter paragraph, and give the office the same wording so that every reply agrees.

• "Is my child's information going into AI?" "No named pupil information is entered into AI tools. We use AI for planning and newsletters using general information only, and a member of staff checks everything before it is sent."
• "Does a computer write my child's report?" "Teachers write reports. Where a tool helps with wording, the teacher decides what is said and checks every sentence."
• "Can I opt out?" "Nothing about your child is entered into these tools, so there is nothing to opt out of. If you have a concern, tell the office and the head will reply within a week."

The first answer is only true if the policy holds, which is why the incident log matters. Do not publish the sentence until the audit and the pilots show that you can keep to it.

The newsletter paragraph itself

A filled-in version for week 8: "This term we have tried AI tools on two jobs: drafting the newsletter and preparing lesson resources. We do not put pupils' names or personal details into them, and a member of staff reads everything before it reaches you or the classroom. We will report to governors at the end of term. Questions are welcome at the office." Keep it to those four sentences.

If a week slips

Terms rarely go as planned, because of trips, illness and inspections. Decide in advance what gives. The audit can shrink to the five-question form without interviews. The tool choice can wait a week if the policy is done. A pilot can lose a week and still reach 25 uses. The staff session and the governor update cannot move, because both are fixed in the calendar and both make the work real. If you have to cut one thing, cut Pilot B's last two weeks, not the policy, the log or the governor page.

Week 11: the staff session

One session, 45 minutes, before or after school. Nobody should leave unsure of what they may do.

1. Five minutes: what the two pilots did and the numbers.
2. Ten minutes: a live demonstration with an invented pupil, showing a good prompt and a bad one.
3. Ten minutes: the policy, read aloud, with the incident story from week six.
4. Ten minutes: each person writes one task they will try and one data rule they will remember.
5. Ten minutes: questions, then a sign-off sheet for the policy.

Collect the sign-off sheets the same day. Staff who are absent get a ten-minute catch-up from the deputy within a week.

Measures that tell you whether it worked

Five measures cover a first term. Set targets in week 4, not week 12, so the outcome is not argued backwards.

A quick sum for Pilot B: 40 uses, with an average of 11 minutes saved on each, is 440 minutes, about 7.3 hours across six weeks. Spread over four teachers, that is modest, and the honest governor message is "a small, safe saving that grows as staff become fluent", not a claim of transformation.

Week 12: the governor update

Governors need one page, delivered in five minutes. A filled-in version:

Illustrative page; every figure here is invented to show the shape.

AI in school operations: term summary
What we did: audit (5 staff groups), policy adopted, two pilots.
What we found: 2 uses of unapproved tools with pupil names (stopped);
  7.3 hours saved in Pilot B; 31 minutes saved a week on parent
  communications; 0 errors reached parents.
What it cost: 83.5 staff hours; $150 in tools.
Risks open: report-writing still needs a safe workflow.
Decision needed: continue Pilot A; extend Pilot B to a second phase;
  postpone any pupil-facing use until next term's review.

Notice that the page includes a decision. Governors who are asked for a view tend to give one, and the minutes record it, which is what an inspector or a parent would later want to see.

What to leave for the next term

Do not start with pupil-facing tools, marking that affects grades, or any use involving photographs, special educational needs or safeguarding records. Each needs its own review, probably with your data lead and a specialist adviser, and each is easier once staff already trust the process. Keep the risk log open, review the policy every term, and book the first review in the diary before the term ends. If you want to repeat the process in a second phase, the first pilot tutorial shows how to scope it.

If you would like someone to help choose the pilots and draft the governor page, that is what my AI implementation consultation covers.

Questions a head teacher or governor will ask

Who should own AI in a small school?

One named senior leader, usually the head or deputy, with a second person such as the office manager or data lead. Spread ownership across committees and nothing gets done. Governors oversee, but one person must be able to answer questions on any day.

How much should a small school budget for a first term?

Mostly time: roughly 80 to 90 staff hours in all, much of it normal work done a new way, plus tool costs that can be zero if you use accounts you already hold. Set a hard cap before week one and report spend to governors at the end.

Should pupils use AI in the first term?

Start with staff-only use on tasks that involve no pupil data. Pupil use raises age limits, supervision and consent questions that need their own plan, so leave it until the staff pilots and the policy are settled.

What do we tell parents?

Tell them in plain words which jobs use AI, that no named pupil data goes into unapproved tools, and that a member of staff checks everything sent home. Add one paragraph to the newsletter and the privacy notice.

What if a pilot fails?

Stopping a pilot is a valid result. Record the measures, the reason and the date, then report it to governors alongside the ones that worked. A documented stop saves the next person from repeating it.

Further reads

• How to Pilot AI in Shadow Mode Before Customers See It — Run drafts alongside normal work before anything goes home.
• How to Roll Out an AI Policy So Staff Actually Follow It — Make sure staff actually follow the policy once written.
• Best AI Tools for Tutors: What a Private Tutor Can Actually Use — Tool options if your school also runs tutoring.
• How to Write an AI Policy for a Small Charity — A policy example from another small organisation with trustees.
• Why Your AI Pilot Stalled, and How to Get It Live — What to do when week seven loses momentum.
• AI for a Music School: Lesson Notes and Parent Emails Worked Through — A worked example of notes and parent emails.
• AI Automation for Schools: Five Office Jobs and What Each Costs — Absence reports, enquiry replies, trip paperwork, parent FAQs and letters: tools, set-up time and monthly cost for each.
• AI Chatbot for a School Website: Parent FAQs From Your Handbook — Turn a school handbook into a parent FAQ chatbot: clean the source, pick a free tier, set the rules, hand over to the office, test.
• AI Consultant for Schools: Role, Cost and How to Brief One — A head's guide: the four jobs a consultant does, published price bands, a one-page brief and questions to ask referees.
• AI Training for School Staff: Session Plan, Tasks and Handout — A ready-to-run one-hour AI session for school staff, with timings, a live demo, data red lines, practice prompts and a handout.
• Free AI Tools for Schools: Who Qualifies and What Data They Keep — A school leader's data-protection checklist for six free AI offers: who qualifies, what each says about training data, and what to ask before staff sign up.
• Can AI Draft a Headteacher Report to Governors From Your Data? — Turn anonymised attendance, progress and finance tables into a governors' report draft, with a figure-by-figure accuracy check before it goes out.
• Can AI Write School Attendance Letters? A Three-Stage Sequence — A three-stage attendance letter ladder written by AI with placeholders only, merged from the register by your office, and signed off by the head.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Microsoft Learn Copilot overview (Copilot Chat licences), Claude pricing page and an archived copy of OpenAI's business pricing page, checked 4 November 2026.