Rolling out AI across a school: a guide for school and district leaders
Short answer: set the policy once, decide which kinds of AI use teachers may propose at all, and start with one department for one term rather than issuing licences to every department in September. Judge the rollout by what actually gets taught, not by a usage dashboard, and ask every vendor the same data questions before the pilot starts.
1. Set the policy once, in a form the classroom can use
A policy that lives only as a PDF cannot be applied consistently. Put it in a form every plan can be checked against: approved tools, minimum age, parental consent, devices, permitted and prohibited uses, the disclosure wording students use, and the assessment windows where AI is not allowed. If you do not have a policy yet, adopt a published default as-is and revise it later.
2. Govern what teachers may propose
Leaders need a small number of controls with real reach. In Compound Intellect they are a master switch on student-facing AI, a choice of which of the four modes (Teach with AI, Teach about AI, Teacher-use only, AI-free) are available in your school, and who may join: invite-only or open, with every access change written to an append-only record.
3. Do not build a dashboard that watches teachers
A list of who is using a tool is one step from a list of who is judged by it, and teachers know it. Compound Intellect's administrator console deliberately does not show which classes a teacher holds, what they planned, opened, generated or taught, how often they sign in, or any figure derived from those, including an anonymous one. Trust is what makes the cautious teachers try it.
4. Roll out one department, then the next
- Create the school and name its first administrator.
- The administrator sets the policy, or adopts the Compound Intellect Standard as-is.
- They invite one head of department.
- One course is read, verified and planned by the teacher who wrote it.
- The term is taught, and you look at what actually gets used.
- You export everything, or end it, whenever you like.
One department teaching from a plan all term tells you more than six departments with a licence.
5. Ask every AI vendor these data questions
- Are uploads checked for student information before they are stored, and does that check avoid copying what it finds?
- Can anything we upload be used to train a model? On whose terms?
- Can we export everything we own as readable files, and erase it with a record of what was destroyed and when?
- Who are your subprocessors, what does each see, and where are they?
- What can our administrators see about individual teachers?
Compound Intellect's answers, and its schedule of data generated from the code, are on the Trust page; the compliance pack is sent on request with no NDA and no sales call first.
Related: Student data privacy and AI · A guide for parents · 12 questions to ask an AI vendor · A free AI policy for schools · How to turn a school AI policy into classroom practice · Pricing · AI in education statistics 2026
Questions schools ask
- How should a school start implementing AI?
- With one department and one term. Set or adopt a policy, invite one head of department, have one course read, verified and planned by its teacher, teach it, and look at what was actually used before expanding.
- Can administrators see what teachers do in Compound Intellect?
- No. The administrator console sets policy and manages access. It does not show which classes a teacher holds, what they planned or taught, or when they last signed in, on purpose.
- How is Compound Intellect priced?
- Per department per year, not per teacher or per student. The pilot is one department for one term, free, with no card.
- Does Compound Intellect integrate with our LMS or SIS?
- No, deliberately. Those systems hold student records, and Compound Intellect has no business there.
The pilot is one department, one term, free and with no card. You keep every plan, package and resource whatever you decide afterwards.
Talk about a pilotbasharat@compound-intellect.com