The staff AI boundaries one-pager.
One page your whole staff can actually remember. A leadership team fills it in together, in one sitting, and every blank gets a real answer. When it’s done, a teacher knows what’s allowed, what never is, and who to ask, without reading a forty-page policy. It works alongside your policy; it doesn’t replace it.
1. What AI is for here
Name the tasks where staff may use approved AI tools. Be concrete: a task a person could point to, not a category.
2. What AI is never for here
The never list is the heart of the page. Write it plainly enough that nobody can claim confusion.
3. Data rules: what never gets pasted in
Most AI trouble in schools is a data problem before it is anything else.
4. Human review: what gets checked before it ships
5. When you’re not sure, ask
6. Sign it, date it, revisit it
From The Library at School Systems Lab. If your team wants help turning this page into working practice, that’s the Lab’s staff AI readiness work. Free to use and share within your school. © Leading Bright Scholars, Inc., d/b/a School Systems Lab.
A one-pager is the start, not the policy.
- Approve the tools before you write the never list. Library No. 05, the AI tool vetting checklist and register, is the twelve-question review; Library No. 06, the generator-to-plan handoff, is the teacher habit that follows.
- The reasoning behind these boundaries, with the U.S. Department of Education and UNESCO sources, is in Brief No. 01, AI governance begins with a decision.
- For the version you can put on a leadership agenda, read a practical AI governance agenda for school leaders.
- To take a team from wary to fluent on the AI your own policy allows, that is staff AI readiness advisory. On the software side, no AI reads a student record in any ClearPath product, and the data page says so in plain language.
The rest of the shelf is in the free Library.