Free resources are going live: 63 ready to download — free, no registration.Free resources →
BeetsAI
English中文

P1-S6 School planning: a school AI incident log and reporting template (six columns, three levels, one route)

  • StageP1-S6
  • SubjectSchool planning
  • Learning strandfundamental operating principles of AI / human-AI communication and collaboration / reflection on the application of AI
  • Official documentsBlueprint for Digital Education Development in Primary and Secondary Schools · AI Literacy Learning Framework for Primary and Secondary Schools · Guide to Using AI in Teaching in Primary and Secondary Schools · EDB Circular No. 156/2026
  • Time to set upOne 60-minute admin meeting to set it up; one page on the day of any incident; five minutes at each meeting

What an incident actually needs is not a review report but a sheet already printed, with six columns on it. This page gives a school a six-column incident log, three levels of escalation, one reporting route from whoever found it to the principal, and three points in time: the same day, three working days, and each meeting.

Two simple faceless colleagues standing on either side of a pale long table with one completely blank sheet and a deep red pen on it, the colleague on the left holding up a blank card, the one on the right carrying a royal blue folder under an arm.
  • EquipmentEditable Word document; the one-page log photocopies on its own; keep a stack with the duty teacher and at the general office
  • Version1.1
  • Last updated2026-11-13

What an incident actually needs is not a review report but a sheet already printed, with six columns on it: short enough to finish, so it keeps up with the day.

What this solves

Once a school uses AI, the incidents are a mixed bag: a screenshot forwarded to the wrong group, a generated passage nobody checked, an account several people share, a pupil’s photograph uploaded to a tool the school never approved. What is hard is rarely the incident itself. It is the sheet of paper afterwards:

  • There is no sheet. Each time someone starts from nothing, writes it differently, and six months later nobody can tell what was done or who followed it up.
  • The sheet has fifteen columns. The more columns there are, the less likely anyone fills it in that day, and what is left is a verbal handover, which leaves nothing behind.
  • It reads like a personnel record. A name goes in, a remark goes in, and the next incident goes unreported — and an unreported incident is the real risk.
  • Nobody knows who to tell. The staff group chat fills with “what now”, and the circle of people who know widens with every question asked.

This page does one thing: a six-column incident log, and one reporting route that runs from whoever found it to the principal. It does not redesign the risk register, and it does not set the procedure for one particular kind of event. Those two are separate pages, and the boundary is written out below.

The boundary first. The six columns, the three levels, the one route and the three points in time are a suggestion from this resource. They are not a requirement set by the Education Bureau, and a school may adapt them; if it adopts them, it should say so as a school arrangement. This page quotes no article number from any law and offers no legal analysis. Where personal data, images or anything published outside the school is involved, the wording is always “followed up under the school’s own data protection arrangements” — no authority is named and no deadline is given, because those differ between schools and a figure printed here would mislead.

Purpose

Once it is set up, a school will be able to:

  1. Write any kind of incident onto one page of the same six-column log: date and time, what was involved, immediate action, who was told, follow-up and owner, closure and review date.
  2. Decide within five minutes, using the three levels, whether this stays in the classroom or goes up the line — without a meeting to argue about whether it counts as serious.
  3. Give whoever found it one fixed reporting route, so the next call is obvious; no second channel exists beside it.
  4. Turn “by when” into three checkable statements: the same day, within three working days, and at each meeting.
  5. Join the log up with the documents the school already has — the risk register, the harassment procedure, the responsibility table — each doing its own part, none repeating another.

The values behind it are the same three learning strands of AI literacy (the fundamental operating principles of AI, human-AI communication and collaboration, and reflection on the application of AI): a log is not there to pin something on a person, it is there so the next time has something to compare against, and so a teacher dares to use the tool and a pupil dares to try.

How to use it

The file is one Word document in five parts: the six-column log (photocopiable on its own), the three levels, the one reporting route, the three points in time, and review and close-out — plus a one-page script for the set-up meeting. Set it up in a single 60-minute admin meeting, then fill one page on the day of any incident.

Step 1: six columns, and no seventh

Six columns, fixed. The more columns there are, the less likely the page is filled that day; anything that does not fit goes into one line of notes at the foot of the page, not into a new column.

Column What goes in it What does not
1 Date and time When it was found, to the hour and minute Not “today” or “yesterday”
2 What was involved One sentence: which kind of tool use, which people or which kind of data No pupil’s name, class or seat number; no make or model of any tool
3 Immediate action What was actually done that day: stopped using it, closed the sharing, suspended the account, preserved the records Not “handled” or “followed up”
4 Who was told A post and a time, e.g. “duty teacher 10:20”, “panel head 10:35” No names, and no phone numbers
5 Follow-up and owner The next action, the post that owns it, the day it is due Not “to follow up later”
6 Closure and review date The closing date, and when this page will be taken out and read again Not “closed” with no date beside it

Columns four and six are the two most often skipped and the two that earn their place: column four shows someone picked it up that day, and column six shows the page will not sit in a drawer for ever. The whole log is unnamed, unscored, and is not a reward, punishment or personnel record — posts and times only.

Step 2: three levels, and only three

The level answers one question: can this be dealt with inside this lesson, or does it already involve other people?

Level What it is What happens that day
One — dealt with in the classroom One lesson, one group, one operation already stopped; nothing left behind, nothing left the room The teacher deals with it and fills one page that day; nothing goes up the line, but the page goes to the panel head for filing
Two — a class, or several people It has spread to a class, several classes or several colleagues; or it involves material already issued or already displayed The duty teacher tells the panel head or the pastoral team at once and that team decides the next step; one page is filled that day
Three — personal data, images, or anything published Pupils’ personal data, a photograph or a face, or content that has left the school or might Tell the vice-principal or principal at once, and use the wording “followed up under the school’s own data protection arrangements”; fill one page that day and preserve the existing records

The three levels are not a score and they are not added up: an incident that fits two levels is handled at the higher one. The level decides who is contacted next, not how serious the incident was — how serious it was is usually only clear afterwards.

Step 3: one reporting route, and only one

Four stations, fixed, in one direction only:

First responder → duty teacher → panel head or pastoral team → vice-principal or principal

  • The first station is the first responder: any colleague, including a teaching assistant, a library colleague or a caretaker. Their job is exactly three things — stop, preserve, tell — and not to judge how serious it is.
  • The second station is the duty teacher, who confirms it has stopped, fills columns one to three, and sets the level.
  • The third station is the panel head or pastoral team, who handle level two and decide whether a lesson needs adjusting, re-teaching or a parent contacted.
  • The fourth station is the vice-principal or principal, who handle level three and decide how far the rest of the staff are told.

Beside this route there is no group chat, no second form and no “let me ask a friend first” channel. One page is held by one post; anyone else who needs it asks that post.

Step 4: three points in time, and only three

Point in time What must be finished
The same day It has stopped; columns one to four are filled; the level has been set and the right station told
Within three working days The action in column five is done or scheduled; column six carries a closing date or a review date; a parent who needs to know has been contacted
Each meeting Every open page is looked at once: the date, the owning post, the next action; closed pages are marked closed

These are floors, not ceilings: it can all be done faster, but the three points cannot all pass with column five still blank. “The same day” counts from the moment it was found, not from the moment a meeting starts.

Step 5: review and close-out

Once a month, a named post writes three lines — how many pages this month, how many at each level, and the average days to closure — and reads them at the admin meeting. Three lines of numbers only: no names, no classes, no comparison between teams.

Before the end of the school year, the twelve sets of three lines are read together: which level was commonest, which kind was commonest, which point in time slipped most often. Those three answers are the list for next year — possibly where the levels divide, possibly one station on the route, possibly how long a page is kept — its retention period — or possibly how one kind of tool is used. The review exists to change the process, not to grade a colleague.

Three pages, three jobs

The boundary between this page and two others is written here, and none of the three can stand in for another:

  • The risk register handles risk before the event. It carries the ten risks, the eight columns and the three steps; this page handles the record after it — the sheet any incident leaves behind, which the register has no format for.
  • The harassment procedure handles one particular kind of event. It has a four-step procedure and a first-24-hours timeline; this page is the sheet every kind of event has to leave, including events that are not harassment. For harassment, use that procedure and log it on this page.
  • The responsibility table handles “who accounts for it”. It asks which position explains what to which other position; this page records only what happened and what was done, and never who should explain it to whom.

In one line: the register says what might happen, this page says what did, and the other two say how that kind of thing is handled and who accounts for it.

How the 60 minutes is spent

Time What happens
5 minutes Opening: one sheet, no new system; state that the counts are fixed — six columns, three levels, one route, three points in time
15 minutes The six columns: read each one and fill a page together from one fictional example
15 minutes The three levels: level three fictional examples, and confirm that an incident fitting two is handled at the higher
10 minutes The route: write the four stations into the document and confirm a named post at each
10 minutes The three points in time: check the school calendar and write down which meeting “each meeting” means
5 minutes Close-out: how many copies, where they live, and which post reads the three lines each month

All of it inside 60 minutes, with no workshop. Every example is fictional and has nothing to do with any real school, pupil or event.

Review checklist

Before the meeting ends, check each item:

  • The log has six columns and no seventh has been added.
  • All three levels are present and no fourth has been added; the rule that an incident fitting two levels is handled at the higher one is written in.
  • There is one reporting route, all four stations are present, and each carries a post rather than a name.
  • All three points in time are present — the same day, three working days, each meeting — and “each meeting” names a real meeting.
  • No pupil’s name, class or seat number appears anywhere; posts and times only.
  • There is no score, grade or comment anywhere, and the log is not a reward, punishment or personnel record.
  • Anything involving personal data, images or publication outside the school is worded “followed up under the school’s own data protection arrangements”.
  • Nothing names an authority or a deadline for reporting outside the school.
  • No tool make, model or supplier is named anywhere.
  • The page states that this is not a requirement set by the Education Bureau, and that the six columns, three levels, route and timings are a school-level suggestion.
  • The three-page boundary is on the page: the register before the event, the harassment procedure for one kind of event, the responsibility table for who accounts for it.
  • The monthly three lines and the yearly review are written in, with the post that owns them.

Files

School AI incident log and reporting template (editable Word document)

Five parts: the six-column log (one page, photocopiable on its own), the three levels, the one reporting route, the three points in time, and review and close-out — plus a one-page script for the 60-minute set-up meeting. The counts are fixed inside the document — six columns, three levels, four stations, three points in time — so a school fills in the content without changing the structure. The Chinese and English files each photocopy on their own and are usable as they come off the copier.

Official documents

Every resource in this library is written to the AI Literacy Learning Framework for Primary and Secondary Schools and falls within the policy scope of the Blueprint for Digital Education Development in Primary and Secondary Schools.

This resource maps to:

  • Blueprint for Digital Education Development in Primary and Secondary Schools (three-fold leaflet, p.2): overall objective 3, enhancing infrastructure and resource provision, asks for a digital education environment that is safe and efficient. This page turns “safe” into a sheet that can be finished on the day.
  • Supplement I: AI Literacy Learning Framework for Primary and Secondary Schools (p.1-4): sets out the three learning strands and progression across four learning stages. Column two asks which kind of tool use was involved, so that an incident can be traced back to the learning and teaching it touched.
  • Supplement II: Guide to Using AI in Teaching in Primary and Secondary Schools (p.2-4): asks a school to set its own arrangements for using AI tools, with the teacher as the professional gatekeeper. The one reporting route here is that gatekeeping written as four stations.
  • EDB Circular No. 156/2026 (paragraph 2): requires a school, in the 2026/27 school year, to build digital education into the School Development Plan and/or the annual school plan, set a school-based implementation strategy, and review the results in good time so that the whole thing keeps improving. The exact wording is quoted verbatim in the Chinese edition of this page. The “each meeting” line and the yearly review are where that instruction lands inside a school.
  • EDB Circular No. 156/2026 (Appendix 1, sections 2 and 4): builds digital education into the School Development Plan and sets a school-based timetable, and asks for critical discernment, the ability to identify error and false information, and compliance and safety. (Appendix 2, item 4, student section) asks schools to teach pupils to protect personal privacy, respect intellectual property and hold to academic integrity, and never to use AI for cyberbullying or to generate inappropriate material — again quoted verbatim in the Chinese edition.
  • EDB Circular No. 156/2026 (Appendix 3, unit 2 and basic unit 2): the table fields in those two units cover school-based guidelines, an approval process and a code of use, and identifying risk with the direction of response. This page does not rewrite either table; it carries only the direction — identify first, then respond — into the levels and the route.

Learning strand: fundamental operating principles of AI / human-AI communication and collaboration / reflection on the application of AI

Official documents page: https://www.edb.gov.hk/en/edu-system/primary-secondary/applicable-to-primary-secondary/it-in-edu/debp.html

This page is an independent Beets teaching resource, not an official EDB document. The six-column log, the three levels, the one reporting route and the three points in time are a suggestion, and a school may adapt them. This page quotes no article number from any law and offers no legal analysis.

Feedback

If you have any comments or questions about this resource, or an idea for the next one, tell us on the feedback page.

Related resources

Reuse

Download and adapt these resources freely for teaching; please keep the attribution.