Districts check whether a platform is safe before they ask whether it will be used. That ordering has consequences. The Consortium for School Networking’s (CoSN) U.S. State of EdTech 2026 report found that 56% of districts require vendors to provide product safety information before purchase, while far fewer ask for evidence that tools are usable, grounded in research, or interoperable with existing systems. Schools are routinely locking in multi-year commitments on criteria that are far easier to verify than to teach with.
The result is a gap that doesn’t show up in budget lines but does show up in classrooms. In many institutions, a large share of purchased licenses ends up barely used or not used in meaningful ways, and where outcomes are tracked, intensity of use is only weakly associated with learning gains unless activity is structured and led by teachers. Procurement criteria that cannot predict whether teachers will integrate a tool into their daily workflows don’t just generate waste — they generate the kind where the resource exists on paper and the gap it was meant to close stays open.
Committed on Paper, Absent in Practice
Centralized EdTech procurement can create deep dependency on a single platform even when day-to-day classroom use remains shallow. Public-sector digital infrastructure history shows this pattern is not exclusive to schools: the UK Parliament’s Public Accounts Committee report “The dismantled National Programme for IT in the NHS” notes that the government “announced in September 2011 that it would dismantle the National Programme” after a centrally governed effort to standardize digital infrastructure failed to align with frontline realities — a reminder that strong central contracts cannot compensate for weak local integration.
Canvas, the Learning Management System developed by Instructure Inc., occupies a similar governance position for many U.S. institutions, often selected through formal RFPs and multi-year contracts with criteria captured in point-based feature and compliance rubrics that are easy to defend but say little about whether teachers will use the LMS for planning, assessment, and communication. In many Canvas-committed systems, usage logs consequently show only a minority of teachers regularly leveraging assignments, quizzes, or analytics, despite the institution’s structural dependence on the platform.
That shallow integration would be problematic enough on its own, but the system-level cost becomes clearer when dependency is tested. In early May 2026, the hacking group ShinyHunters exfiltrated data from Canvas, including names, email addresses, student ID numbers, and user messages; institutions such as Broward County Public Schools temporarily blocked access, and Florida International University publicly reported that Canvas was unavailable, while Instructure said availability was largely restored by May 7 and that passwords and financial information had not been taken. When a single LMS underpins coursework distribution, grading, and communication, any disruption simultaneously interrupts instruction and exposes data-governance weaknesses.
When a platform is operationally embedded but instructionally shallow, classroom teachers — whose daily integration decisions procurement processes rarely model — hold most of the unrealized potential and most of the unacknowledged risk.
The Variable Schools Keep Undervaluing
For most students, the question of whether they “use” a platform is almost entirely a question of whether their teachers do. Tools gain traction in student life when teachers assign work through them, check progress there, and talk about the results in class; platforms that rely on students independently discovering and revisiting them misunderstand how attention and time are actually allocated in schools. Teachers are the primary gateway through which institutional platforms gain or lose traction.
Recent staffing data underline how little system design reflects that reality. In CoSN’s U.S. State of EdTech 2026 report, 66% of responding districts say they have adequate staffing for core IT functions such as network administration and application maintenance, but 58% believe they are understaffed for the instructional use of technology. That gap describes a recurring pattern: schools invest to keep systems running, but not at the level needed to help teachers weave tools into lessons. Cognita’s AI-learning pilot points in the same direction; across 704 users and 2,644 sessions, the company reports that student thinking and questioning improved most when teachers were the platform’s most consistent users and guided how students engaged with it, helping surface misconceptions during lessons rather than after grading. Together, these findings show that districts tend to under-resource exactly the teacher-facing support that makes platforms effective.
Research on the “digital use divide” adds an equity dimension that is harder to engineer around. Studies of technology integration in schools consistently find that, even where devices and connectivity are broadly available, institutions serving more socioeconomically disadvantaged communities face compounded barriers — less protected planning time, thinner coaching capacity, higher staff turnover, and more frequent initiative churn — that make it harder to sustain new instructional routines. Because teacher integration depends on exactly these scarce resources, underinvestment in teacher-centered support does not just lower average impact — it concentrates the shortfall where it is hardest to make up, and does so predictably.
Why the Enthusiasm Fades — and What Would Stop It
The structural reason most EdTech tools fade isn’t waning enthusiasm — it’s a timing problem that institutional deployment rarely solves. The workload cost of adopting a new platform lands immediately; any meaningful benefit in student insight, planning efficiency, or reduced administrative burden follows weeks or months behind. Behavioral and technology-adoption research, including frameworks such as the Technology Acceptance Model and the Unified Theory of Acceptance and Use of Technology, points to three conditions that tend to separate tools that fade from those that stick: low perceived effort, high perceived usefulness with near-term payoffs visible to the teacher, and strong social and organizational support — colleagues using the tool, leadership reinforcing expectations, and practical help available when things go wrong.
Timing is the deciding factor. If friction arrives on day one but the reward shows up a month later, the habit doesn’t form — not because teachers lack commitment, but because that’s not how habit formation works. As Wendy Wood, psychologist and habit researcher at the University of Southern California and author of “Good Habits, Bad Habits,” explains, “A reward that you get, say, in a month… isn’t going to help you form a habit today.” For classroom tools, that means early interactions must give teachers fast, tangible returns on their own terms — easier planning, a clearer read on student progress, or fewer administrative steps, not a notional future gain.
Yet institutional deployment practices are rarely engineered around those habit-formation conditions. Vendor demonstrations are high-support, low-distraction events; real teacher planning time is the opposite. Vendors, it turns out, have spent considerably more time optimizing the 60-minute pitch than the 180-day rollout. Training is often front-loaded into a single in-service day, followed by long stretches in which teachers are expected to troubleshoot alone, even though national surveys show many districts have far more capacity for basic IT support than for ongoing instructional coaching. Under those circumstances, it is rational for teachers to abandon a platform that adds to their workload without clearly reducing it elsewhere.
The platforms that avoid this fade do so by design. They minimize extra steps in core teacher workflows, surface information teachers already care about in more usable forms, and treat professional learning as a built-in feature rather than an optional add-on. Whether those habits form depends less on one-off training days than on these everyday design choices — which means adoption is largely settled long before the in-service calendar is.
See also: Simplifying Business Registration in Hong Kong
What a Platform That Sticks Is Actually Built Like
An external American Institutes for Research evaluation titled “Evaluation of LAUSD’s Instructional Technology Initiative: Year 2 Report” described uneven implementation and classroom integration across schools in a large district iPad rollout, underscoring that expanding access does not on its own create stable instructional routines when training and support structures are inconsistent.
The design failure the AIR evaluation documented — inconsistent implementation support that left expanded access short of becoming reliable instructional routine — is the problem Revision Village’s School Partnership Program addresses structurally rather than assumes away. Revision Village is an online revision platform for IB Diploma and IGCSE courses; through the Partnership Program, teachers assign syllabus-aligned Questionbank items as homework or in-class practice within their existing systems, access written markschemes and step-by-step video solutions produced by experienced IB educators, and track class-level performance through analytics dashboards that highlight strengths and topics needing further work — reducing friction and giving teachers immediate, lesson-relevant feedback. That last point matters more than it sounds: an analytics dashboard sitting outside a teacher’s normal workflow is a report they mean to review; one surfaced within it is information they actually act on.
Through the same institutional agreement, students receive RV Gold access to premium resources such as full Questionbanks, mock exams, and video solutions — including shared mock assessment materials teachers can deploy across the cohort — so access is set at the class level rather than left to individual family purchases. More than 350,000 students from over 1,500 schools use Revision Village, and the School Partnership Program’s discounted cohort-wide licensing means premium features are consistently available across whole classes rather than unevenly distributed by household income. Internal reporting from Revision Village indicates that this school-based model has contributed to wider classroom integration of the platform.
For leaders making purchasing decisions, the criterion that distinguishes platforms worth committing to is whether their institutional offer makes teacher-led, cohort-wide use a default pattern — rather than assuming schools will retrofit those conditions through separate training and local workarounds.
Asking the Right Question
District procurement processes are better calibrated for justifying a purchase than for predicting whether it will be used. Safety assurances, feature lists, and compliance checkboxes document what a platform is; they say very little about what teachers will actually do with it — and the distance between those two questions is where most EdTech investment quietly underperforms. At the same time, staffing and support structures more reliably cover networks and devices than ongoing instructional coaching, and the behavioral conditions that sustain teacher habits differ sharply from the conditions under which platforms are demonstrated and sold.
A more useful evaluative frame for leaders is not simply which platform has the most content or features, but which ones are designed and supported to reduce friction in existing workflows, give teachers immediate and meaningful visibility into student performance, and embed professional development into the product rather than attaching it as an afterthought. When those elements are present, districts are less dependent on individual school capacity to translate licenses into learning.
Checking that a tool is safe and compliant is essential, but evaluating safety without evaluating usability is an incomplete accounting — and an expensive one. The third non-negotiable, whether a platform is realistically usable in the ways that matter for teaching and learning, is the criterion that most procurement rubrics skip and most adoption failures trace back to. Platforms that clear all three thresholds are the ones still embedded in classroom routines at the end of the year — not because their districts got lucky, but because someone thought to ask what teachers were actually going to do with it.
