School districts are pouring real money into AI tools, but the contracts they sign rarely prove those tools improve learning. The wider U.S. ed tech market generated nearly $48 billion in 2024 and could exceed $90 billion by 2030, according to Education Week, citing Grand View Research. Yet district officials are swamped by the volume of AI learning tools and the speed at which vendors release updates, Education Week reported Aug. 20 in a piece by Robbie Sequeira of Stateline.org.
The real risk is not one bad purchase. It's locking in a multi-year renewal for a tool that never had a defined success metric. Vendors usually understand their products far better than districts do, so districts must build their own evaluation methods. And when "AI" is sold as an add-on feature for nearly any product, translating a district's academic goal into contract requirements gets harder.
Screen-time rules shift procurement priorities
New policies are forcing districts to justify which tools earn classroom minutes. Utah became the first state to set age-based expectations for K-12 technology use, effective July 1, and Los Angeles Unified School District adopted a stricter policy for the coming school year, according to THE Journal. Those rules, though framed around time limits, quickly become arguments over evidence: which tools can show they help students learn.
THE Journal argued Aug. 25 that tallying screen time misses the point. School leaders should judge the value of each program individually. But accountability will be the hardest part next, the outlet wrote. With many existing ed tech contracts never requiring usage reporting or proof of impact, districts will need to generate their own evidence. That means usage tracking, baseline measurement, and checks on implementation fidelity.
For CIOs and instructional leaders, the takeaway is direct. Screen-time policies force districts to defend AI purchases with data, turning a teaching issue into a procurement problem with clear documentation requirements.
AI classrooms are spreading across tools, not platforms
Classroom AI use is shifting from one main site to many task-specific tools, according to eSchool News. Teachers now use different platforms to brainstorm, tailor materials, create assessments, translate messages, and review student work. eSchool News urges educators to build an "AI workflow" instead of collecting an "AI toolbox" - but that workflow introduces new integration work for IT teams.
More tools bring more accounts, data exchanges, and permission settings. Products can easily operate outside a standard LMS or SIS unless purchasing terms require SSO, rostering, and administrator reporting from the start. A Tech & Learning essay about a parent's view of a freshman's AI use makes a similar point: student habits change faster than acceptable-use policies. Districts need clear, approved ways to use AI before informal workarounds become the real system.
For K-12 leaders, that signals AI purchasing is entering a stage other enterprise software reached earlier: value claims must be specific, measurable, and defensible in an audit. The AI for Teachers Course covers the practical classroom tools that fit this shift. Start with the job, not the technology. State the academic or operational problem in one sentence, and require the vendor to tie features, rollout steps, and success measures to that problem.
Before you sign or renew an AI contract
Districts pursuing an AI for Education strategy still need to check four procurement basics.
Require per-application usage reporting. Adoption by school, grade, course, and teacher - plus patterns tied to the instructional model. Screen-time policies already cited at Utah and LAUSD make this documentation a basic defensive requirement.
Treat "workflow sprawl" as an integration requirement. Require SSO, rostering, and clear data-sharing terms for every AI product touching student information. Teachers, as eSchool News reported, use multiple tools for different tasks, and governance slips when each purchase is a one-off.
Put professional learning in the implementation plan, not the optional line. eSchool News stresses using AI to free time for human teaching work. Budget training hours with milestones, because general schedules tend to erase optional sessions.
Why this matters
For district-level employees - chief information officers, instructional leaders, technology directors - the immediate task is simple: contract renewal season. Run each AI product through the same check. Does it deliver evidence of the learning outcome it promises? Does it report usage by teacher and course? Does it integrate with existing systems? Every renewal now connects in an audit trail that state policies and board questions will force into the open. Do it now. Don't wait until the next screen-time policy appears in your state to find out your tools can't answer the question - or worse, can't pass a data review.
Your membership also unlocks:
