Rolling out AI in your school, week by week

A rollout is not a purchase followed by an announcement. The schools where this goes badly almost all did the same thing — enabled everyone at once, then discovered a gap in the topic list with six hundred students already using it.

This plan assumes a term. It can be compressed, but not the pilot.

Weeks 1-2: decide and configure

Choose the tool against the properties that matter: your own blocked topics, applying to image and video, filtering on the server, failing closed, visible to staff.

Then write the content standard. This is a meeting, not a settings screen — get the people whose judgement the community trusts in a room and name the topics in the words that would actually come up. Configure it, then spend twenty minutes trying to defeat what you just configured, including in the image tool and on a personal phone.

Draft the policy in parallel: three categories, an attribution sentence, and a note on what each assignment type expects.

Weeks 3-4: staff

One session, hands-on. Give every member of staff an account and twenty minutes to use it and try to break the filter. This is the step most often cut and the one that determines whether staff trust the tool.

Then the practical part: the three categories, the exact phrase to put on an assignment, who to escalate to, and what to say to a student who asks something you cannot answer.

Expect resistance, and expect it to be reasonable. The teacher who says this will make cheating easier is not being obstructive; they are naming the real risk. Answer it with the assessment changes, not with reassurance.

Week 5: parents

Write before any student account exists. Which tool, what it filters, what the school can see, what you are asking at home, and who to contact. Say plainly that the filter reduces exposure rather than eliminating it.

Doing this before rollout rather than after is the difference between informing parents and being caught.

Weeks 6-8: pilot

One department or one year group. Small enough that a problem can be fixed without an announcement, large enough to produce real usage.

Watch three things: what got blocked and whether the categories look right, what staff are actually using it for versus what you expected, and whether anything reached a student that should not have. Add topics as you learn them — the first list is always incomplete, and finding that out with thirty students is much better than with six hundred.

Weeks 9-12: widen

Extend to the rest of the school with the revised topic list. Have the pilot staff run the session for the next group; a teacher who has used it for six weeks is more persuasive than any administrator.

Keep the escalation route obvious. Most problems in this phase are people not knowing who to tell.

End of term: review

What was blocked, in what categories, and does that suggest topics to add. Which staff adopted it and which did not, and why — non-adoption is usually a signal about training or about assessment anxiety, not about the tool. Whether the assessment changes held. Whether anything got through, and which of the three kinds of failure it was.

The four ways rollouts fail

• Everyone at once. No way to fix a gap quietly, and the first problem becomes a school-wide story.
• Policy by email. Nobody reads it, every teacher improvises, students conclude the rules are arbitrary.
• No assessment change. The tool arrives, cheating anxiety rises, staff blame the tool for a gap in task design.
• Parents told afterwards. Whatever the school did becomes secondary to the fact that it did not say.