An AI steering group sounds like something only large trusts need. In fact, a small group of four or five people is the simplest way for a single school to make good AI decisions and keep them moving. Here is how to set one up.
Why have one?
AI touches teaching, workload, data protection and safeguarding at once. Left to one person, it either stalls or becomes an IT project. A small group keeps the right people in the room and gives governors one clear point of accountability. For trusts, see AI steering groups in multi-academy trusts.
Who should be on it
- A senior leader as chair — often the deputy or the head.
- The DSL — for safeguarding and filtering and monitoring.
- The school business manager or office lead — for admin and data.
- One or two teachers — ideally an enthusiast and a sceptic.
- IT support — attending when needed.
- Optionally, a link governor.
Four to six people is plenty. The DPO does not need to attend every meeting but should review decisions involving personal data.
Terms of reference
Keep them to half a page:
- Purpose: to make sure AI is used safely and effectively to support teaching and reduce workload.
- Responsibilities: AI policy, approved tools list, training plan, risk and incident review.
- Meetings: half-termly, 45 minutes.
- Reporting: termly update to governors.
Want a straight answer for your school?
Ask me anything about AI in your school — policy, tools, training or safeguarding. I reply personally, usually the same day.
A first-year agenda
- Autumn 1: Audit current AI use (anonymous staff survey). Agree the approved tools list.
- Autumn 2: Approve the AI policy and staff agreement. Brief governors.
- Spring 1: Deliver staff training on the approved tool. See AI CPD for teachers.
- Spring 2: Pilot AI on two workload tasks — for example, reports and letters.
- Summer 1: Review the pilot and the filtering and monitoring arrangements. See KCSIE filtering and monitoring.
- Summer 2: Annual policy review and next year's plan.
Reporting to governors
A one-page termly update is enough: what was decided, what was delivered, any incidents, and what is next. See AI for primary school governors and governor briefing sessions.
Keep it light
The group exists to make decisions and remove barriers, not to create paperwork. If a meeting has nothing to decide, cancel it.
A sample staff survey
- Which AI tools, if any, do you use for school work?
- Which account do you use — school or personal?
- What tasks do you use AI for?
- Which tasks take you the most time each week?
- How confident do you feel using AI safely? (1–5)
- What training would help most?
Keep it anonymous — staff are more honest about using personal accounts when they are not named.
What good looks like after a year
- An approved AI policy and staff agreement.
- A short, clear approved tools list.
- All staff trained on one tool.
- Measurable time saved on at least two tasks.
- AI covered in the filtering and monitoring review.
- Governors briefed each term.
Frequently asked questions
Does a single school need an AI steering group?
A small group of four to six people is a simple way to make good AI decisions, covering teaching, workload, data protection and safeguarding together.
Who should be on a school AI steering group?
A senior leader, the DSL, the school business manager, one or two teachers, IT support when needed, and optionally a link governor.
How often should an AI steering group meet?
Half-termly for about 45 minutes is usually enough.
What should the group do first?
Audit current AI use with an anonymous staff survey and agree an approved tools list.
How should the group report to governors?
A one-page termly update covering decisions, delivery, incidents and next steps.