Related
Training staff on your school AI policy
Turn staff guidance into everyday practice.
What a teacher AI use policy should cover: approved tools, student information, reviewing AI output, grading, family messages and where staff can get help.
Short answer
A teacher AI use policy gives staff clear guidance on using AI in their own work. It should name approved tools, say what student information may and may not be entered, require teachers to review AI output before using it, set expectations for grading and feedback, cover family communication, protect professional judgment, and say where staff can get help.
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.
Teachers are often asked to explain student AI rules before anyone has told them what the rules are for their own work. Without staff guidance, each teacher draws their own lines on lesson planning, feedback and family emails. A teacher AI use policy gives everyone the same fair starting point, so staff can use AI with confidence and know where the limits are.
Why staff need their own AI guidance.
It is natural to write student AI rules first, because that is where the loudest questions come from. Teachers, meanwhile, are left to work out their own practice: whether to use AI for a lesson outline, a reading passage, a report comment or a reply to a parent. Most make sensible choices, but sensible choices made separately rarely match. One teacher pastes student essays into a free tool for feedback, another avoids AI entirely, and neither knows what the school actually expects of them.
Staff guidance is not about distrust. It protects teachers as much as students. When a family asks how AI was used in their child's class, a teacher who followed written guidance can answer calmly. When something goes wrong, the question becomes whether the guidance was right, not whether one person made a poor call. Clear guidance also makes it easier for cautious staff to begin, because they can see exactly where the safe ground is.
Keep the staff guidance distinct from the student rules, even if both live in one handbook. Teachers need to know what they may do with lesson materials, student records and family messages, which is a different set of questions from what students may do on assignments. A staff section, written in the same plain language as the rest of the policy, can usually fit on two pages and still cover the decisions teachers face most often.
Student information: what may go in and what stays out.
The student information section is the heart of a teacher AI use policy, and it should be the most concrete part. One way to write it is in three groups. First, information that may go into approved tools: lesson content, curriculum materials, and student work with names removed, where the tool is approved for it. Second, information that needs extra care, such as individual learning plans or behavior notes, which should only go into tools specifically approved for that use, if at all. Third, information that never goes into any AI tool.
The third group often includes health details, family circumstances, safeguarding concerns, passwords and anything a student shared in confidence. Writing these examples down saves teachers from making a judgment call at the end of a long day. It also gives the school a clear promise to make to families. Student records are covered by FERPA, and the right approach depends on the tool and the agreement behind it, so have your privacy lead or counsel confirm the final wording.
Approved tools belong in this section too. List them by name, say what each is approved for, and explain how staff can request a new one. Think of a teacher who finds a promising tool for building reading quizzes. If the guidance says to send a short request to a named role and expect an answer within a set time, the teacher waits a few days and then uses it with confidence. If the guidance says nothing, the teacher may just start using it with a class.
Reviewing output, grading and talking with families.
Every teacher AI use policy should say that staff own what they share. If AI helps draft a worksheet, a lesson or an email, the teacher reads it, checks the facts, adjusts it for their students and takes responsibility for it. This is ordinary professional practice. A teacher would not hand out a worksheet from an unfamiliar website without reading it first, and AI drafts deserve the same care. The policy can suggest a quick check: is it accurate, is it suitable for these students, and does it sound like us?
Grading needs its own clear line. A high school English department, for instance, might agree that AI may suggest feedback wording on early drafts, but final grades and comments on major assignments come from the teacher after reading the whole piece. Students and families can rely on that. Writing the line down matters because grading is where trust is easiest to lose. A student who believes a tool graded their essay without a person reading it may doubt every grade that follows.
Family communication sits close to grading. AI can help teachers draft newsletters, translate messages and find a calmer tone for a difficult email. The policy should ask staff to review every message before sending it, keep private student details out of unapproved tools, and answer honestly if a family asks whether AI helped. A message that reads well but gets a detail about a child wrong costs far more trust than it saved in time.
Professional judgment and where to get help.
Good staff guidance says plainly that AI supports professional judgment and never replaces it. Teachers decide what their students need, which suggestions to accept and when not to use AI at all. A teacher who chooses to plan a unit entirely by hand is following the policy as fully as one who uses AI every day. Making this explicit reassures staff who feel pressure to adopt AI quickly, and it reminds keen users that the decisions remain theirs.
The final section should say where to get help, and it should name roles rather than people. Who answers a question about whether a task involves student information? Who reviews a request for a new tool? Who can a teacher talk to after an AI draft contained something inaccurate or unsuitable? A single contact point with a backup is usually enough. It also helps to keep a running list of answered questions, so each issue is settled once for everyone rather than many times in private.
Over time, the guidance should reflect what staff actually do. Each term, look at the questions that came in and the tools that were requested. If several teachers ask about the same task, the policy probably needs a clearer example. If no one has asked anything, check that staff know where the guidance lives. Staff guidance that changes in response to teachers' real work is guidance teachers will keep using.
Name approved tools. List the tools staff may use for school work, and explain how to request a new one.
Sort student information. Say which kinds of student information may go into approved tools, and which should never be entered at all.
Keep teachers responsible. State that staff review and own anything AI helps them produce before it reaches students or families.
Set grading boundaries. Explain where AI may support feedback and where grades must rest on the teacher's own judgment.
Questions the policy should answer:
Which tools can I use for school work?
Can I enter a student's name or work?
Can AI help me grade?
Do I tell families when AI helped?
Signs the guidance is working:
Staff ask before trying new tools.
The same question rarely comes up twice.
Family messages are reviewed before sending.
Teachers can explain the grading rule.
Draft. Write the staff guidance around real weekly tasks, with a few teachers in the room.
Check. Have the privacy lead confirm the student information rules before the guidance is adopted.
Share. Introduce it with everyday examples, and point new staff to it when they join.
Refine. Collect staff questions each term and add the answers to the guidance.
Use this guide to draft or review the staff section of your school's AI guidance, covering the decisions teachers make every week.
Related
Turn staff guidance into everyday practice.
Related
How to choose the tools staff guidance points to.
Related
How student privacy law applies to AI tools.
Quick answers to what schools and families ask most about this topic.
Approved tools and how to request new ones, which student information may be entered, a requirement to review AI output, expectations for grading and feedback, guidance on family communication, a statement about professional judgment, and a named place to get help.
Only into tools the school has approved for that purpose, and only the information a task needs. A sensible default is to ask teachers to remove names and identifying details where possible. Confirm what applies with your privacy lead, since how FERPA applies depends on the tool and the agreement in place.
A school can allow AI to help draft feedback or suggest comment wording while keeping the grade itself with the teacher. The teacher should read the student's work, check any AI suggestion, and be able to explain the grade. The policy should say this plainly.
There is no single rule, but openness builds trust. A good starting point is to ask staff to review every AI-drafted message and to answer honestly if a family asks. A general family letter can also explain how staff use AI for planning and communication.
Some schools use a shared workspace. Ethos Educate, for example, is a school-managed AI workspace with AI chat, a toolkit of approved education tools, and school sign-in with role permissions and audit trails, so staff guidance can point to one approved place to work.