How to Audit Your School’s Digital Tools and Find What’s Holding You Back

Your school probably runs on more software than you think. According to Instructure’s data reported by Statista, the average U.S. K-12 district accessed 2,591 ed-tech tools during the 2022-23 school year. That’s up from just 300 tools in 2016-17. And here’s the kicker: Lightspeed Systems’ 2024 EdTech App Report found that only 97 of those applications account for 95 percent of actual student engagement.

So what are the other 2,400+ tools doing? Mostly sitting there. Eating budget. Creating security gaps. Confusing staff.

If you’re an educator, department head, or school admin who suspects your digital toolkit has grown into a tangled mess, you’re not imagining it. The good news: a structured audit can cut through that mess in a few weeks, not months. This guide walks you through exactly how to do it.

Why Most Schools Don’t Know What They’re Running

The problem didn’t happen overnight. It crept in.

A math teacher signed up for a free quiz app in 2019. The counseling office adopted a scheduling tool during COVID. IT approved a communication platform three years ago that half the staff quietly stopped using. Meanwhile, the district still pays for two different learning management systems because the migration from the old one “isn’t finished yet.”

This kind of tool sprawl is the norm, not the exception. A 2020 McKinsey report on K-12 education estimated that 20 to 40 percent of teacher hours go toward tasks that could be automated or streamlined with the right technology. That’s roughly 13 hours per week that could be redirected toward actual teaching. But when your tech stack is bloated and disconnected, those hours get eaten by workarounds, duplicate data entry, and troubleshooting instead.

The first step toward fixing it is admitting you don’t have a clear picture. That’s where the audit comes in.

Step 1: Build a Complete Inventory (Yes, Everything)

Before you can decide what stays, what goes, and what needs legacy modernization services to bring it up to current standards, you need a full picture of every digital tool in your ecosystem. Not just the ones IT approved. All of them.

Start by collecting data from three sources:

1. IT records. Pull your software licenses, subscriptions, and vendor contracts. This gives you the “official” list, but it’s almost never complete.
2. Staff surveys. Ask teachers, administrators, and support staff to list every app, platform, and tool they use for work. Include free tools, browser extensions, mobile apps, and anything they log into with a school email. You’ll be surprised how many tools surface that IT didn’t know about.
3. Network and browser data. If your district uses a tool like Lightspeed Systems or GoGuardian, pull usage logs. These show which platforms are actually being accessed on school devices and how often.

Once you have a combined list, organize it into a simple spreadsheet with these columns:

• Tool name
• Purpose (grading, communication, content delivery, admin, etc.)
• Who uses it (teachers, students, admin, parents)
• Cost (free, freemium, paid license)
• Last known usage date
• IT-approved (yes or no)

This inventory is your audit’s foundation. Without it, every other step is guesswork.

Step 2: Sort Tools Into Four Buckets

With your inventory in hand, categorize each tool into one of four groups. This is where decisions start taking shape.

• Bucket 1: Core tools (keep and invest). These are the platforms your school can’t function without. Your LMS, your SIS (student information system), your primary communication tool. They’re widely adopted, actively used, and supported by your IT team. If they’re working well, great. If they’re outdated or sluggish, they go on the modernization list (more on that in Step 4).
• Bucket 2: Useful but underused (evaluate). Tools that solve a real problem but only a fraction of staff actually use them. The question here is whether low adoption is a training issue, an awareness issue, or a sign the tool isn’t a good fit. Survey the people who do use it and the people who don’t. The answer is usually obvious once you ask.
• Bucket 3: Redundant tools (consolidate). This is where the biggest savings hide. Schools frequently pay for multiple tools that do the same thing. Two video platforms. Three file-sharing services. A separate app for parent communication when the LMS already has that feature built in. Identify overlaps and pick one winner per category.
• Bucket 4: Abandoned or unapproved tools (cut). If nobody has logged in for six months and it’s not legally required, cancel it. If it’s a free tool that teachers adopted without IT approval, flag it for a security review. The Lightspeed Systems report found that over 65 percent of ed-tech applications had at least one change to their data privacy policies during the 2022-23 school year. Unapproved tools with shifting privacy terms are a real liability, especially under FERPA and COPPA.

Step 3: Measure What Actually Matters

Counting logins isn’t enough. A tool can have high traffic and still waste everyone’s time if it’s clunky, unreliable, or forces teachers into manual workarounds.

For each tool in Buckets 1 and 2, evaluate it against five practical criteria:

1. Task completion time. How long does it take to accomplish the tool’s primary job? If your grading platform takes teachers 45 minutes to do what should take 15, that’s a red flag.
2. Integration with other systems. Does it connect to your LMS, your SIS, or your communication platform? Or does it sit in isolation, forcing staff to copy-paste data between systems? The CoSN 2025 State of EdTech District Leadership Report identified that the biggest barrier to interoperability isn’t a lack of agreed-upon standards; it’s a lack of understanding by leadership about how systems should work together.
3. Reliability and downtime. Ask your IT team and your teachers. Frequent crashes, slow load times, or regular outages during peak hours (report card season, testing weeks) are dealbreakers.
4. User satisfaction. A short, anonymous survey works well here. Ask staff to rate each core tool on a 1-5 scale for ease of use, reliability, and whether it actually saves them time. Don’t skip this. A tool that leadership loves but teachers dread is a tool that’s failing.
5. Security and compliance. Is the vendor SOC 2 compliant? Do they sign a data processing agreement? Are student records encrypted in transit and at rest? CoSN’s 2024 survey of 981 school IT leaders found that data protection remains their top concern, yet 61 percent of districts still fund cybersecurity efforts from general funds with no dedicated budget.

Step 4: Make a Decision Map

By now you should have a clear picture: what’s working, what’s redundant, what’s abandoned, and what’s limping along. The next step is turning that picture into action.

For each tool, assign one of four decisions:

• Keep as-is. The tool works, it’s adopted, it’s secure. No action needed.
• Train and expand. The tool is solid but underused. Invest in staff training and set a 90-day adoption target. If usage doesn’t improve, revisit.
• Replace or modernize. The tool serves a critical function but it’s outdated, unsupported, or can’t integrate with your other systems. This is where you either migrate to a modern alternative or work with a vendor to upgrade the existing platform. Schools dealing with deeply embedded legacy systems (an aging SIS that’s been customized over a decade, for instance) often find that modernization is more practical than a full rip-and-replace, because it preserves historical data and existing workflows while updating the underlying technology.
• Cut. Cancel the subscription. Notify affected users. Migrate any essential data. Move on.

Create a simple priority matrix. Plot each tool on two axes: impact on daily operations (high or low) and current performance (strong or weak). High-impact, weak-performance tools get fixed first. Low-impact, weak-performance tools get cut first. This keeps your team focused on what matters most.

Step 5: Address the “We’ve Always Used It” Problem

Here’s the part nobody warns you about: the hardest tools to cut or replace aren’t the worst ones. They’re the mediocre ones that everyone’s gotten used to.

Teachers and staff build entire workflows around familiar tools, even bad ones. They know the workarounds. They’ve memorized where the buttons are. Suggesting a change feels like adding more to their already full plates.

This is a real and valid concern. A research synthesis published in the Review of Education journal, covering 40 studies on teacher workload, found that multiple studies reported teachers working in excess of 50 hours per week, with workload increases often attributed to administrative and non-core tasks. Nobody wants to pile a software migration on top of that.

The way to handle it is to frame the audit results in terms of time saved, not tools changed. Show teachers the math. If consolidating two platforms into one saves 20 minutes per day, that’s roughly 60 hours over a school year. If replacing an old grading system cuts report-card processing from a full weekend to a single afternoon, say that. Concrete numbers beat abstract promises about “efficiency.”

Involve teachers in the selection of replacement tools, too. When people have a voice in the decision, resistance drops significantly.

Step 6: Set a Review Cycle (and Actually Follow It)

An audit is only useful if it doesn’t become a one-time event that everyone forgets about by next semester.

Set a recurring review schedule:

• Quarterly: Quick check on new tool requests and unapproved app usage. Review any vendor privacy policy changes (remember, over 65 percent of ed-tech apps changed theirs in a single year).
• Annually: Full audit using the process above. Reassess costs, usage, satisfaction, and security for all Bucket 1 and 2 tools.
• At contract renewal: Never auto-renew without checking usage data first. If a tool’s adoption has dropped below 30 percent since last renewal, that’s a conversation worth having before signing another year.

Assign ownership. Somebody (an instructional technology coordinator, a department head, even a tech-savvy teacher with some release time) needs to own this process. Audits without owners become audits without follow-through.

What a Cleaned-Up Tech Stack Actually Looks Like

When schools go through this process seriously, the results are tangible. Fewer tools means fewer passwords for staff to manage, fewer platforms for IT to support, and fewer places where student data can leak. It means teachers spend less time wrestling with technology and more time using it.

The McKinsey Global Teacher and Student Survey estimated that well-implemented technology can help teachers reallocate 20 to 30 percent of their working time toward student-focused activities: one-on-one mentoring, personalized feedback, lesson refinement. That’s the real payoff of an audit. Not just cutting costs (though that helps), but clearing the path so technology actually does what it was supposed to do in the first place.

You don’t need a massive IT budget or a consulting firm to make this happen. You need a spreadsheet, a few honest surveys, and the willingness to ask a simple question about every tool on your list: is this making our work easier, or just making our list longer?

Start there. The answers will tell you exactly what to do next.