On August 20, the U.S. Department of Education put out guidance that validates something we’ve been saying for a while: the screen time conversation shouldn’t stop at minutes-per-week.

The TLDR: ED recommends a focus on quality over quantity when it comes to selecting ed-tech tools and determining their use. It all comes down to an integrated ecosystem that brings visibility, governance, and transparency to ed-tech.

In a new “Dear Colleague” letter, Assistant Secretary Kirsten Baesler urged educators to stop framing the ed-tech conversation as a simple time question and instead draw a clear line between recreational technology — the kind fueling legitimate parent concern — and instructional tools that are aligned to clear goals and implemented well. Districts, she wrote, should be evaluating whether their ed-tech investments are actually moving the needle on outcomes, not just clocking how long students are logged in.

Baesler’s letter doesn’t override state laws or district screen-time caps already on the books in places like Iowa, Los Angeles Unified, or Hillsborough County. But it does reframe the question districts should be asking heading into this school year — and it hands them a mandate that’s actually harder to fulfill than a simple time cap.

The five questions the letter puts on the table

Alongside the letter, the Department released a five-question test it wants every ed-tech product to be able to answer before it lands in front of students:

1. What learning problem does it solve?
2. When should it be used?
3. For whom should it be used?
4. For how long should it be used?
5. What evidence demonstrates that it improves learning?

These aren’t questions you answer once at purchase and file away. Vendors will always have a confident answer for question one. The other four — when, for whom, for how long, and with what evidence — are usage and outcomes questions. They can only be answered with real classroom data, revisited over time, not a spec sheet from the RFP.

The catch: you can’t manage what you can’t see

Here’s the problem every superintendent and CTO runs into the moment they try to act on this guidance: quality over quantity is only possible with visibility.

You cannot evaluate whether ed tech is “purposeful, instructionally sound, and contributing to measurable outcomes” — Baesler’s own words — if you don’t know:

• How much time students are actually spending on any given platform, by grade, classroom, or student
• Where that time is going — is it landing on the district’s vetted instructional tools, or drifting into recreational apps, games, or off-catalog sites during the school day
• Whether the tools in use are the tools the district actually approved, or a long tail of shadow IT that crept in through browser extensions, personal logins, and unmanaged apps
• Who is using the tools and who isn’t to identify pockets of under-use or over-use against the tool’s stated goals

Without that data, “evaluate effectiveness” becomes a guessing exercise. And the second half of the guidance — the call for outcomes-based vendor contracts, rigorous third-party evaluations, and vendor transparency — is even harder to act on without a real accounting of what’s actually being used, by whom, and how consistently.

Visibility is only half the job — governance is the other half

The letter also implicitly raises a governance question districts can no longer defer: who is deciding what enters the ed-tech ecosystem in the first place, and on what basis?

A “purposeful and instructionally sound” tech environment doesn’t happen by accident. It requires:

• App vetting that goes beyond a procurement checkbox — data privacy review, instructional alignment, accessibility, cross-departmental alignment, and a clear owner accountable for the decision
• Ongoing ecosystem management, not a one-time approval — because the tools students touch shift constantly as teachers discover new apps and vendors push updates
• A feedback loop between usage data and vetting decisions — if a tool is barely used, underperforming, or duplicative of something already licensed, that should trigger a review, not just renewal on autopilot

This is where a lot of districts get stuck. They have screen-time policy on paper and a procurement process on paper, but no operational system connecting the two — no way to see usage in near real time, flag what doesn’t belong, and feed that straight back into governance decisions.

Where Lightspeed fits

This is exactly the gap Lightspeed Systems is built to close.

Lightspeed Insight gives districts the visibility the Ed Department’s guidance now effectively requires: granular data on how much time students spend, where that time is going app-by-app and site-by-site, and how usage breaks down by school, classroom, or student — the raw evidence base for any “is this tool working” conversation with a board, a vendor, or a parent.

Lightspeed Filter and MDM provide the governance layer — enforcing which apps and sites are actually reachable on district devices, surfacing unsanctioned or shadow-IT tools before they become a data-privacy or instructional-integrity problem, and giving IT and curriculum teams a shared, current picture of the sanctioned ecosystem rather than a static approved-vendor list from three years ago.

Lightspeed Classroom brings teachers into the process, where they can see approved apps, request new apps, and keep students focused with web controls for their classroom.

Lightspeed Parent Portal and Public App Lists make all of that work transparent to parents and the larger school community.

Together, they turn Baesler’s guidance from an aspirational mandate into an operational one: districts can finally show — with data, not anecdote — that the technology in front of students is purposeful, vetted, and earning its place in the day.

Want to see what visibility and governance look like together? Talk to the Lightspeed team about how Insight and Filter can help your district turn this new guidance into a defensible, data-backed tech strategy this school year.hands.