This is a policy snapshot, not legal advice. Check the current state source and your district's adopted policy before acting.
School phone policy guide · Updated August 17, 2026
Phone bans can work. Implementation determines whether they do.
Banning phones causes an increase in disciplinary issues in year one as kids look for loopholes, then stronger benefits for student engagement & wellbeing in year two. Clear rules, administrator support, and inaccessible storage options correlate strongly with success.
Where things stand
State rules moved faster than the evidence
Education Week counted at least 38 states plus D.C. requiring districts to restrict phones in its June 2 tracker. NCSL's broader July 15 count found 42 states plus D.C. and Puerto Rico with some enacted phone-related legislation—including guidance and funding, not only bans. Those totals are compatible because they answer different questions.
38 + D.C.required a restriction in Education Week's June snapshot
42 + D.C.had any enacted legislation in NCSL's broader July snapshot
22states enacted phone-related school laws during 2025 alone
State synthesis: Education Week tracker, NCSL enacted-legislation table, a 2025 NYU policy review, and later official state updates where noted.
What the research shows
Two credible studies, one consistent timeline
The headlines looked contradictory. The underlying findings are less so: restrictions reliably reduce phone use, year one is disruptive, and later benefits are real but not universal.
Meaningful gains under unusually high prior phone use
- Building-level phone activity fell by about two-thirds.
- Suspensions rose 25% at first; the increase was especially pronounced for Black students, then faded toward baseline.
- Average test scores rose about 1.1 percentile points in year two, with larger gains in higher-use schools and later testing periods.
- Unexcused absences declined and may explain part of the academic gain.
Less phone use, modest average downstream effects
- Pouches substantially reduced phone use.
- Discipline rose and well-being fell in year one; discipline later faded and well-being turned positive.
- Average test-score effects were near zero: modestly positive in high school, especially math, and slightly negative in middle school.
- No detectable average effect on attendance, self-reported attention, or perceived online bullying.
Implementation checklist
What strong plans have in common
Inaccessible, off-person storage
Secure pouches, phone lockers, or supervised collection remove the constant temptation. A phone in a pocket or backpack leaves every teacher negotiating access.
One clear rule, backed by administrators
Teachers need a consistent response and immediate support. “Educational purposes at teacher discretion” recreates the argument the policy was meant to end.
A two-year commitment with an early safety check
Expect workarounds, frustration, and higher discipline in year one. Review disparities early, but evaluate climate and well-being over long enough to see the second-year pattern.
Narrow, protected exceptions
IEPs, Section 504 plans, medical and assistive technology, translation, caregiving, and true emergencies need explicit paths—and staff training that prevents wrongful discipline.
Real operations and family communication
Budget storage, staff time, arrival and dismissal, forgotten or damaged devices, and a reliable way for parents and students to reach one another during the day.
Measurement beyond test scores
Track phone use, engagement, well-being, discipline by student group, attendance, teacher burden, exceptions, and implementation failures. Include student and family feedback.
The Phone-Free Schools State Report Card is an advocacy scorecard, not a causal study, but its strongest design distinction—full-day rules with inaccessible storage—matches the implementation problem visible across field reports. North Dakota's law also provides a concrete model for inaccessible storage, protected exceptions, and annual outcome reporting.
Where plans fail
A rule without a system becomes conflict
- Accessible phones: backpacks, pockets, burner phones, smartwatches, and broken pouches keep the enforcement contest alive.
- Teacher-by-teacher exceptions: inconsistent rules frustrate students and make strict teachers absorb the conflict.
- Understaffed logistics: collection and dismissal lines can consume time and create lost-device disputes.
- Ignoring district devices: unrestricted Chromebooks can reproduce messaging, games, social media, and AI distraction.
- Exclusionary discipline: suspensions for foreseeable first-year resistance can compound racial and disability disparities.
- Unkept academic promises: the national evidence does not support guaranteeing higher scores or attendance.
Families and students
Support depends on how the question is asked
Adults supporting in-class bans
Pew's May–June 2026 survey found broad support for classroom restrictions.
Adults supporting all-day bans
For the first time, support narrowly exceeded opposition—but it remained close, not a mandate.
Teens preferring some restriction
The Brookings/USC survey found support for some limits, even as many teens still used phones against the rules.
Teens opposing all-day bans
Pew found much stronger opposition when the question removed access at lunch and during passing periods.
The gap is not noise. Many students accept a classroom rule and resent losing every unstructured moment. Many parents support restrictions in principle and still want reliable emergency access for their own child. A durable policy answers those concerns operationally instead of dismissing them.
Pew adults, July 2026 · Pew teens, January 2026 · Brookings/USC survey
Source library
Go to the evidence, not the headline
National pouch studyNBER Working Paper 35132 · April 2026
Florida district studyNBER Working Paper 34388 · October 2025
Enacted state legislationNCSL · updated July 15, 2026
State restriction trackerEducation Week · updated June 2, 2026
New York educator survey585 voluntary responses · June 2026
State policy scorecardAdvocacy coalition · storage and implementation rubric