Related
AI governance roles and responsibilities
Who owns which decisions, inside and outside the committee.
How to form an AI governance committee for your school: who should sit on it, how often to meet, a first-meeting agenda, and how to record decisions.
Short answer
To form an AI governance committee, invite five to eight people: a senior leader as chair, the privacy or technology lead, two or three teachers, a student support lead, and family or student representatives. Meet monthly at first, then each term. Agree a clear purpose, a simple way to make and record decisions, and a plan to review AI policy and tools regularly.
Use this page as part of a connected review: understand the purpose, consider the people affected, check the relevant safeguards, and follow the related routes for practical next steps.
AI decisions do not belong to one person. A teacher sees how tools work in class, a privacy lead sees the agreements, and a family sees how it all feels at home. A governance committee brings those views together in one place, so decisions are better informed and easier to explain. It does not need to be large or formal to be useful.
Who should sit on the committee, and why each voice matters.
The strongest committees bring together people who see AI from different angles. A senior leader chairs the group and can turn decisions into action. The privacy or technology lead understands how tools handle information and what agreements say. Teachers from different grades or subjects know how AI actually shows up in lessons, planning, and grading. A counselor or student support lead makes sure student wellbeing is part of every decision, not an afterthought.
Family and student voices matter just as much, even if they take part differently. A parent representative can say whether the school's explanations make sense and what families are wondering about. Older students can describe how they use tools in practice, which is often different from what adults expect. Some schools also invite a librarian or a learning support teacher, who often hear questions about AI before anyone else does. Bringing these voices in early tends to make later decisions easier to explain.
Aim for five to eight people. With fewer, important views tend to be missing. With many more, meetings become hard to schedule and slow to decide. If more people want to help, invite them to join a short working group on one task, such as staff training or family communication, and ask that group to report back to the committee.
Running the first meeting.
The first meeting sets the tone, so keep it focused. Start by agreeing the committee's purpose in a sentence or two, such as: "We guide how our school chooses, uses, and reviews AI tools so they support learning and protect students." Then agree the scope: which decisions the committee makes itself, which it advises on, and which stay with named staff members. Writing the scope down early prevents later confusion about who should have decided what.
Next, take stock. List the AI tools already in use, including free tools individual teachers have found, and note which have been reviewed. Look at the current AI policy, if there is one, and list the open questions staff and families have raised. This picture often surprises people, and it gives the committee its first set of priorities without anyone having to invent them. It is fine if the list is untidy at first. The point is to see the whole picture.
Close by agreeing how often you will meet, how decisions will be recorded, and what you will share after each meeting. Leave with two or three actions and a named owner for each. A first meeting that ends with clear next steps builds confidence that the committee will be useful, rather than one more meeting on an already full calendar. Send members a short note within a day or two so the actions stay fresh.
How decisions are made and recorded.
Agree in advance how the committee decides. Many school committees aim for agreement after discussion, with the chair making the final call if agreement is not reached. Write this down in a one-page charter, together with the committee's purpose, members, and meeting rhythm. When everyone knows the process, disagreements are easier to work through and decisions feel fairer to the people affected by them.
Record every decision in a simple decision log: the date, the question, what was decided, the main reasons, and who will act. For a tool request, an entry might read: approved for staff lesson planning only, not yet for students, pending a data privacy agreement. Short entries like this are quick to write and very helpful when someone later asks why a choice was made. Keep the log somewhere every member can reach, and look over it briefly at the start of each meeting.
Share a brief summary after each meeting. Staff want to know which tools are approved and what has changed. Families want to know that someone is looking carefully. A few lines in a staff bulletin or family newsletter is often enough, and it shows that the committee's work leads somewhere people can see. Over a year, these summaries also become a simple record of how the school's thinking has developed.
Keeping the committee light, especially in small schools.
A committee should save time, not create work. Keep agendas short and send any papers in advance, so meetings are for deciding rather than reading. Handle simple requests between meetings through the named owner, then note them at the next meeting. A standard tool request form helps too, because every request then arrives with the same information and can be answered faster. Many committees also keep a standing agenda, so members know what to prepare.
Imagine a small rural school with a dozen staff. Its committee is the principal, one teacher, and the part-time technology coordinator, with a parent invited each term. They meet for forty minutes twice a term, keep their decision log in a shared document, and ask students for feedback through a quick class survey once a year. The structure is light, but every AI decision has a home and a record. When a bigger question arrives, such as whether to offer an AI study tool to students, they add an extra meeting and invite a few more voices.
As the school's AI use grows, the committee can grow with it, adding members or working groups when they are needed. What matters over time is not the size of the group but its habits: clear roles, regular meetings, written decisions, and an honest look at what is working and what needs to change. Many committees also pause once a year to ask whether the right people are in the room and whether the meeting rhythm still fits.
Keep it small. Five to eight members is usually enough to bring different views and still make decisions.
Choose a clear chair. A senior leader who can act on decisions should lead the group.
Set a rhythm. Meet monthly while the work is new, then move to once a term.
Agree how to decide. Settle in advance whether you aim for agreement or a vote, and who has the final say.
Who to invite:
A senior leader to chair.
The privacy or technology lead.
Two or three teachers from different grades.
A family voice and, where suitable, a student voice.
First meeting agenda:
Agree the committee's purpose and scope.
List the AI tools already in use.
Review current policy and open questions.
Set the meeting rhythm and decision log.
Invite. Ask members personally and explain the time commitment clearly.
Charter. Write a one-page note of purpose, membership, and decision process.
Meet. Hold the first meeting with a short, focused agenda.
Report. Share a brief summary of decisions with staff and families after each meeting.
Use this guide to set up your school's AI governance committee, plan its first meeting, and keep it running without adding heavy workload.
Related
Who owns which decisions, inside and outside the committee.
Related
The structure your committee works within.
Related
A plain-language introduction for your first meeting.
Quick answers to what schools and families ask most about this topic.
A senior leader as chair, the person who looks after privacy or technology, a few teachers, a counselor or student support lead, and family representatives. Older students can join or be consulted. Different views help the committee notice questions any one role might miss.
Monthly is helpful in the first few months while tools and policy are being set up. After that, once a term is usually enough, with an extra meeting when a new tool, new guidance, or a significant concern needs a timely decision.
A small school may not need a formal committee, but it still benefits from a small group with clear roles. Three people meeting a few times a term, with decisions written down, can do the same job well.
Typically it approves or declines AI tools, reviews the AI policy, looks at concerns and patterns, plans training, and decides what to tell families. Day-to-day questions can stay with named owners, with the committee reviewing them at its next meeting.
Where it suits their age, yes. High school students often give clear, practical feedback on how tools are really used. In younger grades, a short student survey or class discussion can bring their voice in without asking them to attend meetings.