What Distinction Does the Letter Draw Between Recreational and Instructional Technology?

The letter is explicit that recreational technology and instructional technology should not be evaluated by the same yardstick. A student scrolling on a phone after school and a student using a diagnostic assessment tool that gives a teacher real-time information about a reading gap are not the same use of a screen, even though both involve one. As the letter puts it, the question districts should be asking is not whether teachers and students use technology, but whether the specific technology they’re using improves learning and academic outcomes.

That reframing does real work. It gives district leaders language to defend genuinely useful tools against blanket screen-time policy, while still giving them permission to be skeptical of tools that can’t demonstrate value. It also puts the burden of proof back where it belongs: on the product, not the device.

It’s worth saying plainly that the underlying concern the letter is responding to is a legitimate one. That sentiment isn’t in tension with the Department’s letter — it’s the exact tension the letter is trying to resolve. Educators aren’t anti-technology. They’re asking for the same thing the Department is now asking for: proof that a given tool is worth the screen time it asks for.

What Is the Department Asking of Edtech Vendors?

The most concrete section of the letter is a short list of expectations for education technology providers. States and districts, it says, should expect vendors to publish rigorous, independent evaluations of product impact whenever feasible; share implementation guidance grounded in effective classroom practice; be transparent about capabilities and limitations; and continuously improve products using evidence from real classrooms.

None of that is abstract. It’s a checklist, and it maps almost exactly onto the case LXD Research has been making to edtech companies for years: a vendor claim is not evidence, and a demo is not a study. The letter even flags procurement experiments already underway in Louisiana, Arkansas, Indiana, Michigan, and Texas that build shared performance measures and outcome expectations directly into vendor contracts — the same outcomes-based contracting model where districts hold back a meaningful share of payment until agreed student results show up. Those models started with tutoring services and are now extending into edtech more broadly — a preview of where evaluation criteria are headed for every state watching those pilots.

For a founder or product leader reading this letter, the practical takeaway is straightforward: the market is moving toward requiring exactly the kind of third-party, ESSA-aligned evidence that used to be a differentiator and is becoming table stakes. As we noted in a recent look at the state of the edtech market, most products still don’t have that evidence in place — which means the letter is less a warning to well-documented products and more an early-mover advantage for the companies that build the evidence base now, ahead of the requirement.

Why Does the Letter Call Evidence-Building a Shared Responsibility?

The letter closes on a point that’s easy to skim past but shouldn’t be: it frames evidence-building as a shared responsibility across states, districts, educators, families, researchers, and providers, not something any one group can solve alone. Districts can’t procure their way to good outcomes if no vendor can produce credible evidence. Vendors can’t produce credible evidence without educators and researchers willing to test claims transparently. And none of it works if the standard for “evidence” is left vague enough that any white paper counts.

If you’re a product leader trying to figure out where your evidence currently stands, or a district administrator trying to evaluate a vendor’s claims against this new guidance, that’s exactly the conversation worth having now, while the field is still figuring out what “meeting the standard” will mean in practice.