How to Prove Staff Were Trained on Your District's AI Policy
Most districts have an AI policy. Few can show who was trained on it. Here's what a defensible, per-person training record looks like.

Your District Has an AI Policy. Can You Prove Staff Were Trained on It?
Most districts can now point to an AI policy. Far fewer can show who was trained on it.
That gap matters more every month. When a parent complains, a board member asks, or an incident hits the news, the first question is rarely "what does the policy say?" It's "were your staff trained on it?" A PDF in the handbook and a signature from August don't answer that question.
This fall we asked school IT leaders how they track AI training. 0% keep a complete, per-person record.
70% have already been asked how staff AI use is being kept appropriate. The question is arriving before the record exists.
Why a policy alone doesn't hold up
Teachers aren't waiting for permission. 60% of teachers used AI for work last school year, and 68% had no AI training from their school or district (Gallup–Walton, 2025). So the policy is being tested every day, by people who may never have read it.
State rules are moving the same way. As we covered in what each state requires:
- Florida: districts adopt AI policies, with teachers and administrators trained on AI risks, limitations, safety and compliance, by July 1, 2027.
- Tennessee: grade 6–12 teachers complete an approved AI course by August 1, 2028.
- Ohio: every district adopted an AI-use policy by July 1, 2026.
- Texas: each district's cybersecurity coordinator completes state-certified AI training every year; training for other staff is up to the district.
The details differ. The follow-up question is the same everywhere: show us who was trained.
What a defensible training record looks like
If your board asked tomorrow, here's what you'd want to hand them:
- Training built on your own policy. Generic AI literacy is useful, but it doesn't prove staff know your rules: which tools are approved, what never goes into an AI tool, and who to call when something goes wrong.
- A per-person record. Not a sign-in sheet for one PD session. A roster that shows every staff member as certified or not certified.
- Proof of understanding, not just attendance. Short scenario checks ("A teacher wants to paste a 504 plan into a free AI tool. What should they do?") show staff can apply the rule.
- An annual acknowledgment. Policies change and tools change. A yearly sign-off keeps the record current.
- A report you can share. One page your superintendent can take to the board.
What staff actually need to know
The topics that come up again and again:
- What never goes into an AI tool: student names, IDs, grades, IEP and 504 plans, discipline records, parent contacts
- Approved tools versus personal accounts
- How to check AI output before using it
- Deepfakes, voice clones and AI-written phishing
- Disclosure, academic integrity and records
- What to do in the first hour when something goes wrong
None of these require a full PD day. They require clear examples, a quick check
How to get there before spring
The calendar still works if you start now:
- November: finalize your AI policy and approved-tool list
- Before winter break: assign training to all staff
- January in-service: staff complete and certify
- Spring semester: roster and board report in hand
How MobileMind helps
AI Safe-Use Certified trains every staff member on your district's own AI policy and approved tools in 60–90 minutes, self-paced, with no PD days or subs. Each person passes scenario checks and signs the annual policy acknowledgment. IT gets a certified / not-certified roster and a board-ready report.
It's priced per staff member, and districts often fund it through Title II or technology budgets.
See how AI Safe-Use Certified works →
Want to talk through your district's timeline?
Book 15 minutes with our team.



