What shows up in a classroom is rarely a teacher’s unilateral choice anymore. Digital platforms now anchor lesson planning, assignment submission, grading, and communication—and before any of them reach widespread use, they typically pass through cross-functional institutional review: security assessments, privacy checks, cost analysis, and procurement approval.
Survey data from both sectors clarify how formal that vetting has become. In K–12, CoSN’s 2024 State of EdTech District Leadership Survey defines a “Decision-maker” as someone without whose approval “content cannot be purchased,” and shows this role governing a substantial share of instructional materials decisions. In higher education, an EDUCAUSE QuickPoll on third-party agreements reports contracting that is mostly centralized, with relatively low faculty involvement, and warns that central contracting can “limit the ability of faculty to adopt new offerings quickly.” EDUCAUSE guidance on third-party integrations likewise describes IT as a gatekeeper for the environment, linking risk, security, and procurement checks to platform access. In practice, many tools live or die at centralized approval tables long before any instructor ever opens them.
These patterns mean that tools rarely spread instructor by instructor; they move through institutional pipelines that weigh integration, cost, and compliance alongside pedagogy. In higher education, that gatekeeping combines with deep LMS integrations to create migration friction. In K–12, it intersects with districtwide licensing decisions that effectively double as curriculum choices.
Table of Contents
Lock-In and Integration Depth in Higher Education
Instructure’s Canvas illustrates how deeply a single learning management system can become embedded in higher education—and how exposed that dependency looks when things go wrong. A major breach in 2026 compromised the personal data of about 275 million users and disrupted finals week for many campuses, prompting lawsuits, a congressional investigation, and a ransom payment to restore service. Canvas serves roughly 41% of higher education institutions in North America and had been hacked three times in the past year. What the breach made visible wasn’t just a security failure; it surfaced the question of how difficult it would be for institutions to migrate away from a system this deeply embedded.
Documented LMS transitions show why switching is rarely a rapid reaction, even when risk perceptions shift dramatically. California Community Colleges implementation guidance for Canvas describes a roughly 15-month conversion process covering authentication and student-information-system integration, faculty training, course migration, and an expectation that colleges can “run both Canvas and their legacy CMS in parallel for at least two full semesters.” Appalachian State University’s IT office planned an “18-month phased approach” for its own LMS change, and a North Carolina Community College System cost analysis treats migration as a separate, material budget line.
Chloë DeShong, a business analyst with Cornell’s Academic LMS Evaluation Project, put it concisely in Cornell’s 2018 LMS report: “Given Cornell’s academic calendar and the number of courses currently relying on Blackboard, migration to a new system is expected to take 1.5 years (July 2018 – December 2019).” Replacing an LMS is typically a multi-semester operational program constrained by teaching cycles—not a procurement pivot you execute between semesters.
Courseware integrations sit on top of that substrate and compound the dependence. Macmillan Learning’s Achieve platform connects to institutional LMSs—including Blackboard Learn, Brightspace, Canvas, and Moodle—through either a basic or deep integration. Basic integration inserts a single link to the Achieve course in the LMS, enables single sign-on, and returns one gradebook column via manual sync. Deep integration supports asset-level links to individual Achieve assignments inside LMS folders, multiple gradebook columns that flow automatically into the LMS, and, in some configurations, syncing of assignment settings from Achieve into the LMS. Once instructors have built courses around those tightly linked assets, “just switching vendors” stops being a configuration decision and starts resembling a full workflow reconstruction. That’s the lock-in mechanism in plain view: the deeper the integration, the more teaching routines and contracts become structurally bound to a single vendor’s ecosystem.
When an LMS and its linked courseware are woven into daily teaching operations, replacing them becomes a risk-managed migration project rather than a simple swap. Healthcare offers a useful analogy: AHRQ’s PSNet, in its discussion of electronic health record transitions, notes that switching platforms can be “remarkably expensive” and time-consuming and that adverse events can increase during the changeover. The mechanism transfers cleanly to higher education: richer LMS–courseware integrations raise the operational stakes of switching, which shapes how institutions weigh their options after incidents like the Canvas breach.
K–12 Procurement as the New Curriculum Gatekeeper
Los Angeles Unified’s districtwide contract inventory is a working model of this dynamic in K–12. By requiring an itemized report of every classroom technology contract—and distinguishing what individual schools bought from what the central office funded—the board placed school-level selection decisions inside a formal districtwide approval frame. The cross-functional team leading this work spans instruction, IT, procurement, and legal, anchoring decisions about which platforms stay in use firmly within institutional process rather than classroom preference.
The same resolution directs officials to check whether agreements meet student-privacy standards, with updates or renegotiations on the table where they don’t. Contract compliance, not classroom trial, sets the terms—which means many teachers find out which tools are staying or going through a procurement announcement rather than a pedagogical conversation. For vendors, approved-list status is the prerequisite for any meaningful presence in schools; for teachers, the constraints typically arrive as done deals.
Central contracts can advance equity by ensuring all students in a system have access to a common baseline of digital resources, rather than leaving quality dependent on which school or classroom a student happens to occupy. The tradeoff is that standardization narrows the range of materials in active use and lengthens the feedback loop for trying or discontinuing products, especially when procurement cycles run long. The policy challenge is to use districtwide licensing to guarantee access and safeguard students without foreclosing space for teacher-informed experimentation and local adaptation.
Outcomes-Based Contracts for Instructional Fidelity
Some districts and vendors are trying to align procurement structures more directly with what actually happens in classrooms. A Digital Promise report on a Southern Education Foundation cohort of five districts used outcomes-based contracts for instructional technology, with at least 40% of contract value tied to agreed-upon targets for student dosage or usage. In the four districts examined in detail, more than half of students met provider-prescribed dosage targets; in one system, 95% did. Implementation fidelity across the cohort was described as ten times greater than what’s typical for edtech. In one district, close analysis of the data led district and vendor staff to redefine dosage—from consecutive minutes of use to lessons completed—shifting the contract’s focus toward engagement that more closely resembled actual learning.
Tying payment to dosage pushed both parties to track whether tools were actually being used, and doing so immediately required agreed-upon definitions and data pipelines reliable enough to support high-stakes measurement. Outside structured pilots, many systems lack that infrastructure—and there’s a standing risk that contracts end up measuring what’s easiest to count rather than what’s most instructionally meaningful. Designing procurement around outcomes and usage can strengthen implementation, but the work still falls on teachers to embed tools in practice in ways that go beyond checking a box.
Embedding Teacher Agency and Shared Practice in Licensing
Los Angeles Unified’s earlier iPad initiative illustrates how access at scale can fail to translate into shared practice. The district moved to end or retreat from the program after major implementation problems, including uneven classroom use and difficulty aligning devices with coherent instructional routines. A national educator census by Common Sense similarly reports that many technology products purchased by schools and districts go unused, with about one-third of teachers saying they didn’t or practically never used a provided tech product, and only about four in ten rating professional development for edtech as very or extremely effective. It’s hardly surprising some tools gather dust when teachers feel underprepared and unconvinced of their value. Procurement can put tools in teachers’ hands, but without clear expectations, shared routines, and practical training, day-to-day usage stays fragmented and some licensed products never become part of regular instruction.
Revision Village’s Approach
Revision Village’s School Partnership Program approaches licensing by building those shared workflows in from the start. It is an online revision platform for IB Diploma and IGCSE students and teachers, with structured, exam-focused resources across IB Mathematics, sciences, individuals and societies, languages, and IGCSE mathematics syllabi. Through school partnerships, institutions can secure discounted access to RV Gold so that entire cohorts use the same Questionbank of syllabus-aligned, exam-style questions, timed practice exams, and step-by-step video solutions produced by experienced IB educators. Having a shared bank of assignments and a common view of class performance gives teachers a consistent reference point for coordinating work and tracking how students are progressing. Teachers can assign Revision Village questions as homework or in-class practice, use the IB Mathematics Prediction Exams as shared mock assessments ahead of each exam session, and monitor class progress through analytics dashboards that highlight strengths and topics needing further work. In this model, the license is tied to concrete routines—shared assignments, common diagnostics, and class-level visibility—rather than just seat counts, aligning institutional purchasing with teacher agency and designed to support consistent classroom use.
Conducting the Digital Classroom Symphony
The thesis running through all of this is simpler than the machinery around it: procurement is not a backstage function in education. It determines which platforms become standard, how hard they are to exit, and whether licensed tools see regular use or quietly gather dust. The Canvas breach didn’t just expose a security failure—it exposed what happens when 41% of North American higher education builds its operations around a single integrated system that the academic calendar won’t let anyone exit quickly.
The institutions that navigate this well treat contract design as pedagogical design: asking not just whether a platform passes the security review, but whether the licensing structure actually supports how teachers teach. That means anticipating migration costs before signing, demanding usage evidence alongside security assurances, and building shared workflows into agreements rather than hoping instructors invent them independently. Teachers may not control which tools arrive in their courses, but whether those tools actually get used is still, ultimately, up to them.