Every district I talk to right now is wrestling with the same question: what AI tools are actually running on our network? Not the ones on the approved list. Not the ones IT assumes are being used. The actual, in-the-wild traffic.
That gap between what a policy says and what students and staff are doing is exactly what our AI Usage Audit report at Lightspeed Systems is built to close. I recently sat down with our Director of Product, Kate McDermott, to walk through what districts can expect to find, and I wanted to share it here.
Why “we think we know” isn’t good enough anymore
AI adoption in schools didn’t wait for permission. Teachers found tools that helped them plan faster. Students found tools that helped them study, or cut corners, depending on who you ask. Meanwhile, IT and safety teams are stuck trying to write policy for a landscape that changes every few weeks.
The AI Usage Audit gives districts a real look at what’s happening: which AI apps are showing the most use across the district, how many actual minutes students and staff are spending in them, and how that breaks down by grade band and by school. It’s not a survey. It’s not a guess based on a handful of help desk tickets. It’s what the network is actually seeing.
With or without a policy, here’s what you’ll find
If your district already has an AI policy, the report becomes a check on reality. You can pull up the specific AI tool your policy names as approved and see exactly how much adoption it’s actually getting, alongside any other tools showing up that weren’t on your radar. That second part tends to be the more useful one.
If you don’t have a policy yet, the report works the other way. Instead of trying to write a policy from a blank page, you can use the adoption and risk data to figure out which apps to prioritize first, then build guidance around what’s actually happening on the ground.
The compliance piece: knowing which apps are worth worrying about
Every app that shows up in the report gets more than a usage count. Lightspeed partners with outside security and compliance data sources to give each app a risk profile, so districts aren’t just seeing “here’s an app with a lot of users.” They’re seeing how risky that app actually is.
That combination, high usage plus a real risk signal, is what tells you where to look first. An app with heavy screen time and a shaky risk profile jumps to the top of the list. From there, a district can decide whether it needs to be blocked outright, approved and supported, or just gently discouraged while they keep watching it.
Where the surprises actually show up
I asked Kate directly: where does the report tend to reveal the biggest gap between what a district expects and what’s really going on? The answer wasn’t about any one risky app. It was about scale.
Most district leaders expect maybe one or two AI tools in active use. What they usually find is many more, even if a lot of those tools only have a handful of users each. The surprise isn’t that AI is being used. It’s how much more of it is happening than anyone assumed, and that it isn’t locked down the way people thought it was. Students and staff find their way to tools they aren’t supposed to be using, or ones nobody thought to block in the first place.
Breaking usage out by individual school adds another layer worth watching, too. It’s less of a shock and more of a useful pattern: usage often looks different building to building, which matters when you’re deciding where to focus training or tighten controls first.
Try it before you write another policy line
This is a free audit, and you only need 14 days to get a real picture of AI usage across your district. Even in that short window, districts consistently come away with more clarity than they expected.
If your team is trying to write, update, or just sanity-check an AI policy, start with the data instead of the guesswork. Request your free 14-day AI Usage Audit and see what’s actually happening on your network.
Like our content? Check out our previous Lightning Chats for more conversations on the topics K-12 leaders care about most.
FAQs
What does an AI usage audit show a district that they wouldn’t be able to see otherwise?
An AI usage audit shows which AI apps are actually being used across a district’s network, not just the ones on an approved list. It surfaces the number of active users per app, the actual minutes spent in each tool, and how that usage breaks down by grade band and by school. Districts also get a compliance and security risk profile for every app that shows up, which most schools have no way to generate on their own. Together, this gives IT and safety teams a factual picture of AI use instead of a guess based on scattered reports.
If a district already has an AI policy, how does the audit show whether that policy matches reality?
Districts with an existing AI policy can look up the specific tool their policy names as approved and see exactly how much real adoption it’s getting. Just as important, the audit surfaces any other AI apps in use that weren’t accounted for in the policy at all. That comparison, approved tool versus actual usage, is often where districts find the biggest gap between what’s written down and what’s actually happening. It turns a policy from an assumption into something that can be checked and updated.
How does the report help a district decide which AI tools to approve, restrict, or investigate further?
Every app in the report is paired with usage data and a compliance risk profile, so districts aren’t deciding blind. An app with a high number of users and heavy screen time paired with a weak risk profile should get looked at first. From there, a district can decide to block the app outright, approve and support it, or simply discourage it while continuing to monitor use. The combination of adoption plus risk is what turns a long list of apps into a prioritized action plan.
Where do districts typically see the biggest disconnect between what they expect and their actual AI usage?
The biggest disconnect usually isn’t about any single risky app, it’s about scale. Most district leaders expect to find one or two AI tools in active use and are surprised to discover many more, even if several only have a small number of users each. The bigger surprise for most teams is realizing usage isn’t as locked down as they assumed, with students and staff finding their way to tools that were never approved or considered. Seeing usage broken out by individual school adds a useful layer too, since adoption patterns often vary from building to building.
See exactly how AI is being used in your district.
Students are using AI whether you’ve approved it or not. Know what’s actually happening in your district — so you can build a governance strategy around it.
