


Most of the AI conversation in schools right now is about students: bans, pauses, default settings, and who gets to flip the switch. We've written plenty about that, and we will again. This week, we want to talk about the other half of your district.
Take Sweet Home Central School District, just outside Buffalo. It used AI to turn a six-hour bus-routing job into a few minutes, and we'll get into how below.
Nobody is protesting that at a board meeting. It's also not common yet. In an EdWeek Research Center survey this fall, nearly one-third of district and school leaders said they don't use AI for any operational purpose. So, in today’s newsletter, let's get into what the other two-thirds are doing, and what it takes to get the rest of your staff ready.
A technical note: We’re sending this out a week early. We’re taking next week off for Thanksgiving here in the US and wanted to make sure you didn’t go two weeks without a newsletter to read.
Some folks have reached out to us asking how to subscribe themselves or their colleagues to this newsletter. Click here to do so. We send a newsletter every two weeks about the latest happenings with K-12 and AI.
IN THIS ISSUE:
Why operations (transportation, HR, and the front office) may be the easiest place to start with AI
Why AI training has to reach every department, not just classrooms

79%
State ed-tech leaders who named AI a top technology priority, up from 68% in 2025. Source
Nearly 1 in 3
District and school leaders who said they don't use AI for any operational purpose. Source
40,000+
Employee records Fairfax County Public Schools sorted into one system using an AI-built script. Source
62%
State ed-tech leaders who named professional learning a top unmet need, up from 47% last year. Source
76%
State ed-tech leaders who said five or fewer people work on ed tech in their state. Source


In Fairfax County, Virginia, the HR department used AI to write a script that sorted more than 40,000 employee records scattered across different systems and put them in order for upload into one platform, K-12 Dive reported. The district's chief HR officer admitted it isn't the most exciting use case, but said it freed his team to focus on more strategic work.
Indianapolis Public Schools built internal tools that score the first round of principal applications against the same rubric staff already used, then send qualifying candidates to a hiring committee. The district keeps personal information out of those tools, and its rule is that AI never replaces a decision. At the state level, the Colorado Department of Education worked with WestEd to help every operational team develop its own AI use cases.
As we debate the virtues and pitfalls of AI in education, none of these examples involve students and their AI usage, and each one gives adults time back for work that needs a person.
OUR TWO CENTS
I think operations is the most underrated place to start with AI, and probably the easiest to defend. Parents aren't worried about a bus route planned with AI. Board members get it right away. And the benefit shows up where people can see it: an HR team spends its time hiring instead of copying records between systems.
What I like about the Indianapolis approach is the line they drew. AI scores the first pass, and people make the call. That's a pretty good template for any department. Pick one painful, repetitive task, keep personal data out of it unless you have the agreements in place, and decide up front which decisions stay with humans.
As an aside, this is also how you build the trust you'll need for the harder classroom conversations. A district that can show its community a few boring, well-run AI projects is in a much better spot when the student questions come up.
Ask each department head to name one task that eats hours every week and doesn't touch student data.
Pick one of those tasks for a small pilot, with a clear before-and-after measure (hours, days of lead time, or errors).
Write down which decisions AI can inform and which ones stay with people before the pilot starts.


SETDA's 2026 State EdTech Trends Report came out at the end of October, and one number jumped out at me. Sixty-two percent of state ed-tech leaders named professional learning as a top unmet need, up from 47% last year, the largest increase of any need the survey tracks, according to GovTech. AI was a top priority for 79% of respondents, up from 68%. And the teams responsible for all of it are small: 76% said five or fewer people work on ed tech in their state.
If states are stretched that thin, districts can't count on outside training to reach the bus coordinator or the payroll office. Most AI training so far has been built for teachers, which makes sense, but it leaves out the people in the story above.
Tucson Unified in Arizona took a different route. When the district wrote its AI policy, it formed a task force of about 40 people, including staff from transportation, HR, and communications, and then trained those departments directly. The district's ed-tech director made a simple point: a policy written only for students and teachers misses a lot of the people who work in a district.
OUR TWO CENTS
I spend a lot of my week on onboarding calls with districts, and the pattern is pretty consistent. Teachers usually get a PD day, and principals get a session at a leadership meeting. The front office, transportation, and HR get an email and, if they’re lucky, a self-paced onboarding course.
For operational AI, that's the wrong order. The people who know where the hours go are the ones doing the work, so they need to be in the room when you pick the task and in the training when you roll out the tool. Role-specific training also takes less time than you'd think. A bookkeeper doesn't need a session on lesson-planning prompts. They need an hour on what data can and can't go into the tool, how to check the output, and who to call when something looks off.
So, if you're planning spring PD now, consider giving at least one session to a non-instructional department and building it around a task they already do,
Add non-instructional staff to your AI committee, starting with transportation, HR, and finance.
Build short, role-specific sessions on what data can go into a tool, how to check the output, and who to call when it's wrong.
Name one point person staff can go to before starting a new AI project, the way Colorado's education department did.



Newport, a computer science professor at Georgetown, argues that much modern work is busywork that looks productive, and that the fix is to do fewer things at a more sustainable pace. The book barely mentions AI. It fits this issue: before you automate a task, it's worth asking whether the task should exist at all, and what your staff would do with the hours they get back.


Chat with ClassCloud
We’re listening. Let’s Talk!
This newsletter works best when it’s a conversation, not a broadcast. If you want to talk through how any of this applies to your district specifically—or if you have feedback on what would make this more helpful—just hit reply. We read and respond to everything.

Schedule a Virtual Meeting
Thanks for reading,
Russ Davis, Founder & CEO, ClassCloud ([email protected])
Tracy Walters, Director of Customer Growth ([email protected])
ClassCloud is an AI company, so naturally, we use AI to polish our content.




