Education Department’s 5-question edtech check is now the fastest way to buy

The U.S. Department of Education is handing districts a new, simple way to say “yes” or “no” to classroom technology, and it fits on one page.

In an Aug. 20 “Dear Colleague” letter, the department told states and local school systems to separate recreational screen time from instructional technology use, then evaluate any classroom tool by five questions: what learning problem it solves, when it should be used, for whom, for how long, and what evidence shows it improves learning. The department framed the guidance as a push for instructional value, transparency, and regular effectiveness reviews, according to the agency’s press release.

For CIOs, instructional tech leaders, and procurement teams, that’s less a policy memo than a ready-made specification. The fastest path to compliance is to bake those five questions into RFP language, contract renewals, and implementation expectations, then ask vendors to produce the artifacts to prove it.

From “screen time” to “use case”: a buying checklist enters the chat

K-12 leaders have been forced to navigate a messy national screen-time debate with local politics, parent pressure, and uneven product data. The department’s letter explicitly tries to narrow that debate by saying recreational and educational technology use are not synonymous, while still acknowledging concerns about students spending too much time on screens, according to K-12 Dive’s reporting on the guidance.

That distinction matters operationally because it shifts the conversation from “how many devices” to “what tasks, what minutes, and what outcomes.” A district can cap non-instructional use without throwing out a literacy intervention tool, but only if it can define when that tool should be on, who should be in it, and how long the session should run, then show learning impact.

District Administration, covering the same guidance, emphasized the practicality of the five-question framework as a purchasing lens. In practice, the questions create a scoring rubric districts can apply consistently across very different categories, from adaptive math platforms to classroom management software.

Vendors will be asked for evidence, and for the usage telemetry to back it up

The Education Department’s letter urges districts to prioritize tools with independent evidence, review effectiveness regularly, and be willing to change course when results don’t show learning improvement, according to the department’s own release. That language lands directly on renewal cycles and multi-year license agreements.

It also raises an immediate practical question: how will districts verify “for how long should it be used” and whether it is being implemented the way the evidence base assumes? Many districts can report license counts and logins. Fewer can report time-on-task, dosage by student subgroup, or whether students are spending time in the specific lesson types tied to outcomes. The guidance’s repeated emphasis on transparency, including how much time students spend on screens and how tools are being implemented, effectively elevates product analytics from “nice to have” to “table stakes” for major adoptions.

A useful benchmark is emerging from educator sentiment data. EdTech Digest highlighted results from the 2026 Savvas Educator Index, a national survey of 1,709 public K, 12 educators. In that survey, 82% favored limiting classroom screen time, while 92% said they distinguish between passive and instructional technology use. The nuance continues in the details: 76% of K, 2 teachers preferred less than an hour of screen time daily, while more than 40% of middle and high school teachers favored one to two hours.

Those numbers don’t set policy. They do indicate how implementation battles are likely to play out in buildings, and why procurement needs to come with clear usage definitions and reporting plans. If the contract can’t describe “when” and “for how long,” schools will end up negotiating it teacher by teacher.

Federal money adds more process: proposed EDGAR changes raise the stakes for documentation

The K-12 guidance arrived amid broader changes in how education institutions may have to manage federal funding. On Aug. 24, Community College Daily reported that the Education Department proposed a sweeping update to its grant administration regulations, EDGAR, which governs most federal education grants. The proposed changes would alter how institutions find funding opportunities, document eligibility, and build grant applications.

Two operational details matter for edtech buyers who rely on grant funding. First, the proposal would move away from the longstanding requirement to announce competitions through the Federal Register, relying instead on grants.gov and other electronic platforms, according to Community College Daily. That puts more pressure on internal grant-monitoring workflows, and on the systems institutions use to track opportunities and deadlines.

Second, Community College Daily reported the proposal would ask applicants asserting nonprofit status to submit documentation that confirms that status, instead of being able to claim it without proof. For procurement and finance teams, it is another reminder that “paperwork readiness” is increasingly part of technology readiness, particularly when a district, foundation partner, or consortium structure is involved in the purchase.

Community College Daily also reported the proposal would allow ED to terminate grants for convenience if the department determines an award no longer aligns with agency priorities or program goals. Regardless of how that proposal evolves, it strengthens the case for districts and colleges to write grant-funded technology contracts with clear deliverables, implementation evidence, and off-ramps tied to objective performance and compliance requirements.

What to put into specs and renewals this fall

The Education Department’s five questions are easy to repeat and hard to operationalize unless they show up in documents that teams already use. For districts with 2026-27 screen-time limits underway or under consideration, the guidance offers a way to keep instructional tech while tightening expectations around design, training, and reporting, a stance K-12 Dive described as a defense of edtech when used for learning rather than recreation.

The immediate change is not that tools must be ripped out. It’s that the default burden of proof is shifting toward the vendor and the district’s implementation plan. The districts that move fastest will be the ones that convert the five questions into standard clauses and a repeatable review cycle, and that require usage telemetry early so “for how long” is measured, not guessed.

Questions procurement and IT teams can put to vendors now

• What is the product’s documented “intended use” in minutes per day or week, and can the platform export time-on-task and session-length reporting by grade and subgroup, aligned to that intended dosage? (This maps directly to the department’s “for how long” question, per ED’s Aug. 20 guidance.)
• What independent evidence is available for the same student population and implementation conditions, and what implementation requirements does that evidence assume, such as teacher training hours, minimum usage, or specific feature use? (The Education Department asked districts to ground selection in evidence and implementation support.)
• What does the contract treat as success at 90 days and at renewal: outcomes metrics, usage thresholds, or both, and what is the decision process if the tool isn’t improving learning? (The department’s guidance calls for regular reviews and willingness to change course.)
• If the purchase will be supported by federal grants, what documentation can the vendor provide to support eligibility, reporting, and audit readiness, and how will the district monitor grant opportunities and notices if competitions shift to grants.gov platforms as EDGAR proposals suggest, per Community College Daily?