Ten problems on every district’s desk — and where the fixes actually live.

FutureEd’s analysis of district plans pegs roughly $5.8B of ESSER spending against mobile devices and connectivity — about 9% of the $64B they tracked. The cohort bought in 2020–2021 reaches end-of-warranty and end-of-AUE at the same moment the funding it was bought with no longer exists. Most CFOs don’t yet have a number for the gap.

Once a device hits AUE, Google stops issuing security and policy updates. The device still boots, so most inventory systems still mark it as “active.” The actual exposure — how many devices in your fleet are past AUE right now — is rarely quantified. PIRG estimates that doubling Chromebook lifespans would save U.S. school districts $1.8B nationally.

The same headcount that handled 1:1 deployment in 2020 is now responsible for the deployed fleet, the AI rollout, the cybersecurity audit, the LMS migration, and the next refresh cycle. New tools that require an agent on every device, a dedicated server, or weeks of training make the problem worse, not better.

Without a workflow that ties repairs to a specific student and asset, schools lose visibility into which devices have been to the bench three times this year, which families have been billed and which haven’t, and how much repair spend is concentrated in 5% of devices that should have been retired. PIRG also rates education Chromebook parts availability at 3.3/20, against 9/20 for non-Chromebook laptops.

The root cause is rarely “students stealing” — it’s broken assignment data. A spreadsheet that says student X has device Y was true in October and false by December, and there is no audit trail to reconstruct what happened. Google Admin shows the device exists; it doesn’t show who is responsible for it.

Most K-12 cyber incidents start with a credential or a misconfigured device, not a sophisticated exploit. When student devices share an OU and policies are managed by hand, a single misapplied policy can expose thousands of endpoints at once. Per-device policy isolation is hard to do correctly with native Google Admin alone.

The ACLU, the EFF, and several state attorneys general have publicly questioned classroom-monitoring deployments. Districts under public-records pressure are discovering that their monitoring vendor retained more data, for longer, than the contract suggested. The board-level question is shifting from “can we monitor more?” to “what is the minimum we need?”

Hard URL blocks at the district level are blunt and break legitimate research. Per-class teacher control is what teachers actually need — and what most native tools do not offer cleanly. The bar is “can a teacher see what their class is on right now, without filing a ticket?”

This issue is real and we don’t want to overclaim a software fix for it. The most defensible posture for districts is to make sure that when devices are in students’ hands they are on-task, accountable, and time-bounded — and that policy decisions are made on data, not vibes.

Connectivity is structural. Software vendors don’t fix it. What software can do is make sure the loaner pools, hotspot inventory, and check-out programs that schools run to bridge the gap actually work — and that the devices being lent out come back.