Setting Up a School AI Implementation Team: Roles and Running It

Last updated: 2026-07-24

Handing a HK$500,000 programme to one teacher-in-charge to juggle is a common arrangement and a common bottleneck. Three subjects, six teaching demonstrations, open lessons, sharing sessions, student activities, reports and accounts span teaching, IT and administration, and no single person carries all of that alone. Better to form an implementation team with clear roles from the start.

Why a team rather than one person

Running it through one person tends to fail in two ways. Give it to the IT lead and the programme drifts towards buying tools and installing systems, with no one following through on the teaching side. Give it to a curriculum lead and it can stall on technical support and data privacy, which are not their field. The programme's five commitments span several areas already, so several roles should share them.

The value of a team is not only the division of labour but the way members cover for one another. The teaching people raise the need, the IT person judges what is feasible, and the person responsible for privacy guards the data. Decisions then do not lean towards any single point of view, which matters for a programme that has to answer to the EDB for three years.

The members and what each is responsible for

Coordinator (overall lead)

This is a deputy head or a respected teacher-in-charge, holding the overall progress, dealing with the EDB, and connecting the AI targets to the school development plan. They do not need to be the strongest on technology, but they do need to coordinate the subject panels, push decisions through, and answer for the overall quality of the reports.

Subject representatives

Each of the three subjects sends one representative, usually the panel head or a keen teacher. They put AI-assisted teaching into practice in their own subject, produce the teaching demonstrations, and prepare the open lessons. They are the ones who actually deliver on whether the commitments are met.

IT coordinator

This person handles the technical assessment of tools, accounts and access rights, the technical liaison with vendors, and support when teachers hit a problem using something. The back-end usage data from the trial period is theirs to compile as well.

Data privacy contact

This person guards compliance with the Personal Data (Privacy) Ordinance: reviewing how tools handle student data, the arrangements for parental consent, and the keeping of records. The role is often skipped, yet it is the one most likely to cause trouble in the reports and in talking to parents.

Running rhythm: once a month

The team is best served by a short monthly meeting with a fixed three-part agenda: check progress against the annual plan, deal with the month's problems (tools, training, privacy), and settle each person's tasks for the month ahead. Keep the minutes brief but complete, because they are the raw material of the reports.

Extra planning meetings can be added ahead of an open lesson, a sharing session, or a report deadline. A monthly meeting in ordinary times, with more when things are busy, keeps the programme moving steadily better than calling people together only when something goes wrong.

How the team keeps evidence for the reports

The programme requires a separate account and record-keeping for at least seven years, and the team has to start this on day one rather than patch it together before the report. Set up a shared folder sorted by commitment, and file as you go: lesson plans, classroom photos, attendance records, student work, teacher feedback, and expense receipts.

One named person, usually the coordinator or their assistant, updates the filing list each month and checks the five commitments to see which box is still empty. By the midterm report in September 2027 and the final report in September 2028, whoever writes them faces an ordered archive rather than scraps of material scattered around.

Common questions

How many people should the team have?

It depends on the size of the school, but the core is usually five to seven: the coordinator, the three subject representatives, the IT coordinator, and the data privacy contact. A smaller school can have one person take two roles, for example the IT coordinator also being the privacy contact. The number is not the point. Whether each role has someone responsible for it is.

Who should be the coordinator?

Best at the level of a deputy head or curriculum lead, because the role coordinates work across subject panels, deals with the EDB, and connects AI to the school development plan, which needs the matching authority and a whole-school view. A colleague from a purely technical background suits the IT coordinator role but may not be right for holding the whole thing together.

We already have an IT committee or curriculum development group. Do we still need a separate team?

Not necessarily a new committee. You can name an AI implementation team within the existing structure, drawing its members from the relevant groups. What matters is clear responsibility, a fixed meeting rhythm, and someone dedicated to keeping evidence, not one more box on the organisation chart.

Sources

Want to know your school's next step?

Tell us where your school is with the funding programme. We help with evidence, from choosing tools to filing the reports.

Book a free school consultation Request a proposal