Sep 26, 2026
How to Train Your Entire Staff on AI — A District Leader's Playbook
A practical guide for district leaders who need every teacher AI-literate, know where each one stands, and want a system that scales.
Sohan Choudhury | Co-founder and CEO of Flint

You have 80 teachers. Some are already using ChatGPT every day. Some are afraid of it. A few have strong opinions about why it's bad for students. One or two think it's going to replace them. The school board wants to know what you're doing about AI. Parents are asking questions at every open house.
You need everyone at a baseline. And you need to prove it happened.
This is the reality for most district leaders in 2026. The question isn't whether to train your staff on AI — it's how to do it at scale without blowing the PD budget or forcing 80 people through the same one-size-fits-all workshop.
This guide walks through the challenge, the options, and what actually works.
The problem: your staff is not one audience
The biggest mistake in AI professional development is treating all teachers the same. They're not. Any district with more than a handful of teachers has at least four groups sitting in the same building:
The enthusiasts. Already using AI for lesson planning, differentiation, grading. They've watched the YouTube videos, attended webinars on their own time, and built their own prompts. They don't need an introduction to AI — they need to go deeper, and they need their school to catch up.
The curious-but-cautious. Open to AI but haven't done much with it. They want to see how it applies to their specific subject and grade level before investing time. They'll try it if someone shows them something concrete for their classroom, not a generic demo.
The skeptics. Have real concerns about academic integrity, student dependency on AI, environmental impact, or the hype cycle. They're not opposed to learning — they're opposed to being told to adopt something they have legitimate questions about. A workshop that ignores their concerns pushes them further away.
The resistant. Don't want to engage with AI at all. Some feel it threatens their role. Some are overwhelmed by the pace of change. Some just have too much on their plate to add another thing. They need the lowest possible barrier to entry and a reason to care that connects to something they already value.
A single PD session — no matter how good the facilitator — addresses maybe one of these groups well and alienates the others. The enthusiasts are bored. The skeptics feel dismissed. The resistant are confirmed in their resistance.
What teachers are actually worried about
Before choosing a training approach, it helps to know what your staff is thinking. When teachers are asked directly about their AI concerns, here's what comes up most (based on intake data from teachers starting Flint's AI literacy course):
-
Students not learning to think for themselves — 69% of teachers selected this. The fear isn't that AI exists; it's that students will outsource the thinking that education is supposed to develop.
-
Cheating and academic integrity — 55%. Teachers want to know what counts as cheating, how to detect AI use, and what policies to set — before they bring AI into their classroom.
-
Keeping up with the pace of change — 51%. The technology is moving faster than the professional development. Teachers feel behind and don't know where to start.
-
Their own workload and time — 46%. Teachers already have too much to do. Adding AI training that doesn't directly save them time feels like one more mandate.
-
Student safety and privacy — 32%. Especially in younger grades and sensitive subjects, teachers want to know what data the AI sees and what guardrails exist.
-
Environmental cost — 32%. A growing concern, especially among science and social studies teachers who teach about climate.
-
Pressure from parents or admin — 15%. Some teachers feel caught between parents who want AI restricted and administrators who want it adopted.
-
Skepticism about the hype — 11%. A smaller but vocal group that wants evidence before enthusiasm.
Any AI PD program that doesn't address these concerns head-on will leave most of your staff partially convinced at best. The enthusiasts don't have these concerns — everyone else does.
Why traditional PD approaches don't work for AI
The half-day workshop. An outside facilitator comes in, shows some demos, talks about responsible use, and leaves. Two weeks later, 10% of teachers have tried something. The rest went back to their routine. The workshop gave everyone the same content regardless of their starting point, and there's no follow-up.
The online course mandate. You purchase seats for a platform's certification course and send an email asking teachers to complete it by a deadline. Some do it immediately. Many don't start. A few complete it the night before the deadline by clicking through. You have completion numbers but no evidence of actual learning, and no way to re-engage the people who dropped off.
The train-the-trainer model. You send two instructional coaches to a conference, and they come back to train the rest of the staff. The coaches learned a lot, but translating their experience into sessions for 80 teachers with different comfort levels is a different skill. The telephone game dilutes the content. The coaches get pulled into other priorities.
Hiring consultants. Many edtech consultants are former educators who bring deep expertise and high-touch facilitation. A multi-day engagement can be transformative for shifting mindsets and building enthusiasm. Where consultants shine is the kickoff: setting vision, running hands-on workshops, and customizing content to a district's specific context. The gap is what happens after they leave. Consultants can't be in every classroom every week. New hires who join mid-year miss the engagement entirely. The most effective districts pair consultant-led kickoffs with a self-serve course that teachers can access on their own time — so the momentum doesn't stop when the engagement ends.
These approaches each have real strengths — and most districts use some combination of them. But they share a structural limitation: they're events, not systems. They happen at a point in time and hope the learning sticks. Most don't adapt to different teachers, don't track individual progress, and don't give administrators ongoing visibility into what's working. The strongest approach is layered: a consultant or workshop for the kickoff, paired with a self-serve system that handles the day-to-day.
What a system looks like instead
The districts getting this right have moved from events to systems. Here's what that means in practice:
1. Personalization from the start
Instead of assuming every teacher needs the same thing, the system asks. What do you teach? How familiar are you with AI? What are you worried about? Then it builds a path that starts where each teacher actually is.
A math teacher who's concerned about cheating gets content about academic integrity policies, assessment design in an AI world, and how to use AI for formative assessment without enabling shortcuts. An English teacher excited about AI writing tools gets content about teaching revision with AI feedback, maintaining voice, and when AI assistance crosses the line.
This isn't a luxury feature — it's what makes the difference between a course teachers finish and one they abandon. When the first ten minutes feel relevant to your classroom, you keep going. When they don't, you close the tab.
Flint's AI literacy course does this. During onboarding, it asks teachers what they teach, their comfort level, and their concerns — then builds a personalized path and shows them what changed based on their answers. The personalization isn't happening behind the scenes; it's visible, which builds trust with the skeptical teachers who need to see that their concerns are being taken seriously.
2. Self-paced, but not unsupported
Teachers need to be able to do the training when they have time — a planning period, 20 minutes after school, a Sunday morning. But self-paced doesn't have to mean self-directed. The best systems provide a clear progression (not a menu of disconnected modules), so teachers always know what's next and why.
Two levels works well for most districts: Level 1 covers AI fundamentals, safety, and classroom applications (enough to be conversant and confident). Level 2 goes deeper into curriculum integration and pedagogical strategy. Teachers who complete both have genuine AI literacy — not just familiarity with a specific tool.
3. Admin visibility that proves it's working
This is the piece most PD programs miss entirely. As a district leader, you need to answer three questions:
- Who hasn't started? So you can nudge them before the deadline.
- Who's stuck? So you can offer support or pair them with a mentor.
- Who's done? So you can celebrate it, credential it, and report it to the board.
A dashboard that shows per-teacher progress across levels — with the ability to send email reminders to specific groups (never started, in progress, completed Level 1 but not Level 2) — turns PD from a trust-me into a show-me. When the school board asks "is our staff AI-trained?", you have an answer with names and dates, not an anecdote about that one great workshop.
Flint's admin dashboard does this. It shows each teacher's progress, links to their certificates, and lets administrators send targeted reminders. No other free option offers district-level tracking with this specificity.
4. Certificates that count
Teachers need something to show for completing the training. A certificate per level, shareable to LinkedIn, serves three purposes: it gives the teacher a tangible credential, it gives the administrator a reportable metric, and it gives the district something to present to parents and board members.
The certificate should represent actual learning, not just seat time. Courses that can be completed by clicking "next" through slides for 20 minutes produce certificates that mean nothing. Courses that require engagement with content — responding to prompts, making decisions, building something for your classroom — produce certificates worth signing.
5. Content that teaches thinking, not clicking
The most common failure in AI PD is teaching teachers how to use a specific tool instead of how to think about AI. Tools change every six months. The judgment a teacher needs — when to use AI, when not to, how to evaluate its output, how to set policies, how to talk to parents about it — that's durable.
A good AI literacy course should cover:
- What AI actually is and how it works (at a teacher-appropriate level, not an engineer-appropriate level)
- How to evaluate AI tools for classroom use
- Data privacy and student safety
- Academic integrity in an AI world
- How to write a classroom AI policy
- Concrete applications in the teacher's subject area
If the course is mostly about how to use one company's platform, it's product training, not AI literacy. Both have value, but they're not the same thing.
How to roll this out
Start with a pilot, but plan for everyone
Pick a building or a department and run the training there first. Use the admin dashboard to watch completion rates and gather feedback. Then expand district-wide with a realistic deadline and clear expectations.
Address concerns before they become objections
Don't wait for the skeptics to speak up at a staff meeting. Send a message that acknowledges the concerns directly: "We know many of you have questions about AI's impact on academic integrity, student thinking, and your workload. This course addresses each of those head-on." When teachers see their concerns reflected in the training itself, resistance drops.
Make it visible
Share completion milestones. Celebrate the first building where 100% of teachers finish. Feature a teacher who was skeptical but found something useful. The social proof matters — especially for the resistant group, who need to see that their peers are engaging, not just complying.
Don't make it a one-time event
AI is changing faster than any technology in education. A training from September will feel dated by March. The best districts treat AI literacy as a baseline that teachers build on over time — not a box to check once.
The bottom line
Training your entire staff on AI is a logistics problem as much as a content problem. The content exists — multiple good options cover the basics. The hard part is getting 80 teachers with different comfort levels, different concerns, and different schedules through something that feels relevant to each of them, and then being able to show it happened.
That requires three things: personalization (so the training meets each teacher where they are), self-paced access (so it fits real teacher schedules), and admin visibility (so you can track, nudge, and report). Most PD approaches deliver one of those. Very few deliver all three. Only one delivers all three for free. Start here →