Is Your Edtech Stack Getting Stagnant? Going Beyond a K–12 Edtech Audit

The renewal notice lands in your inbox in early June. It's a six-figure district-wide license for a supplemental reading tool that auto-renews in 30 days. You open a spreadsheet and find the login count, but realize you don't actually know if it reflects usage and if the tool is worth keeping.

A new tech director inherits an old stack, licenses auto-renew, tools get duplicated, and regular responsibilities dominate the day-to-day. And these commonplace occurrences can prevent slowing down to ask a central question: Does our technology actually help teachers and students?

A license report helps, but you need a more comprehensive framework to assess if your stack is helping or hindering your district and its goals.

What can you measure?

You might want to start with renewal dates and budget lines, but pause and consider usage data instead.

Pull four numbers for every tool in your stack: active users, purchased licenses, how often they’ve been used over the past 90 days, and which roles are actually logging in, whether teachers, students, or mostly admins running reports.

From there, sort your tools by instructional category, like formative assessment, supplemental curriculum, communication, or productivity, for example. You'll almost certainly find doubles: two tools that do the same job for different grade levels, or a legacy platform still running alongside its more widely used replacement. Platform redundancy means twice the cost and the possibility of inequitable outcomes if one platform has more evidence on student outcomes.

If your district doesn't have a clean way to map this out, the Building Efficient Edtech Ecosystems guide shows how districts inventory their tech stack without overwhelming their teams.

If usage tells you what's being opened, the next step is figuring out what story that data is telling.

What can’t the data tell you?

Login counts don't tell you the problems your students or teachers face once inside the platform. Look at your help desk and sort your support tickets by tool over the last school year. Look for red flags like high ticket volume on a specific platform. That won’t show up in a vendor's renewal pitch, but if a tool consistently causes problems, it eats up your team’s time on higher-value work while frustrating end users. This can also give you a data point to consider when deciding which to keep among redundant tools.

Integration quality gives you another data point. Consider these questions that reveal deeper problems:

• Does the tool connect cleanly with your SIS and LMS, or does someone have to manually enter data or create custom workarounds? 
• You can work through poor interoperability for a while, but what if the person who knows how to do that work leaves the district? 
• Or if a data import breaks in the middle of the year?

Vendor lock-in is the final piece to look at. You might be working against proprietary data formats and have limited export options. High switching costs are another flag worth documenting before renewal season. If you can't easily move your data out of a platform, the vendor may hold more power than you’d like.

Once you've mapped usage and have qualitative data points to work with, it’s time to score your stack.

How do tools score?

A scorecard doesn't have to be complicated to be useful. Four criteria cover most of what you need to make a defensible case to district leadership.

Score each tool on adoption rate, support burden, integration quality, and evidence of student impact. Not every tool will score high on all four—a niche assessment tool might have low adoption but strong outcome data, and that's worth knowing. When a tool scores low on three or four, it’s time to consider if it’s worth the low score in the other categories. If a tool is impactful and integrates well but has low adoption, you may look at training options. If a platform is widely adopted but lags in the other three areas, it may be time to look at alternatives. That's your shortlist for consolidation conversations.

Keep in mind that getting trustworthy evidence of student impact requires instructional leaders or professional researchers in the conversation. A tool your tech team can't evaluate for learning outcomes shouldn't get scored without curriculum and instruction input. Tools like LearnPlatform by Instructure help districts run evidence-based evaluations at the tool level, so those conversations are grounded in data, not opinions or anecdotes.

Even if no tools get cut this cycle, you'll have a baseline for next year's renewals and a record that makes future decisions easier.

Bad tool or bad rollout?

Before you decide to consolidate or not renew a tool, ask one more question: Did staff actually get a fair shot at using it?

Low adoption doesn't always equate to a bad product. The rollout might have happened during testing season, or training was optional (and thus, largely skipped). If a tool scores low on adoption but hits the other criteria, look at the rollout history before writing it off. Talk to a few teachers and check whether and when professional development was offered.

This distinction matters because cutting a tool your district didn't fully implement doesn't solve the underlying problem; it just restarts the procurement cycle and wastes more time and resources, while student outcomes could be better supported with stronger tools. "Is this tool being used?" is a necessary question. "Does the district have the capacity and conditions to use it well?" is just as important.

If the answer’s no, that's still useful information. It could be the right tool at the wrong time. Or teachers need more structured training. Or your stack is too big for your team to reasonably support. Either way, the conversation moves from cut-or-keep to invest-or-exit, and gets you closer to the right tech stack.
 

Start (don’t finish) with an audit

Assessing your K–12 edtech stack won't fix everything by next school year. It’s an interactive, ongoing process. A tool may be acquired, but now comes at a higher price; state requirements around accessibility or privacy shift; your district goals change focus; and the budget forecast could turn. So your process needs to be flexible, too. But you still gain a little more clarity into what's being used, what’s collecting digital dust, which tools are evidence-backed, and how much support they require from your IT team.

That clarity means renewal conversations start with workable data, and that’s worth working towards.