Every Illinois school board now has a clear assignment. Public Act 104-0657, which Governor Pritzker signed on July 28, requires each board to adopt and implement a wireless communication device policy on or before the beginning of the 2027–28 school year. At a minimum, the policy must prohibit students from using covered devices during school time, with exceptions the law spells out, and the statute defines school time as the full day from arrival to dismissal, including recess, lunch, and passing periods. ISBE has posted the template the law called for, its Model Cell Phone Policy dated August 2026, and many districts will build from it. Districts that already had a policy limiting devices for most or all of the day before July 28 may keep it through 2030–31, so it is worth confirming which clock your district is on.
I expect nearly every district to meet the requirement. A board can adopt a compliant policy in a single meeting, and the template does much of the drafting. That is a sensible design for a statute. It is also why compliance, by itself, tells a board very little. On adoption day the policy is finished, and nothing has yet happened in a classroom.
What the definition includes, and what it sets aside
The statute’s definition of a wireless communication device is broader than the phrase “cell phone ban” suggests. It names cellular telephones, tablet computers, laptop computers, gaming devices, and wearables such as smartwatches. Then it sets a large category aside: “‘Wireless communication device’ does not include any device that a school district or teacher has directly issued to, provided for, or required a student to possess and use for educational purposes.”
I do not read that exclusion as a mistake. Schools issue laptops and tablets because instruction runs on them, and a law that swept district devices into a bell-to-bell prohibition would have made much of the school day unworkable. The consequence is still worth stating plainly. In a one-to-one district, the device a student uses most during the school day is the one the law does not reach. The phone goes into a locker or a pouch, and the Chromebook stays open on the desk in the same class.
The state has already named the second problem
ISBE’s model policy says as much, though it is easy to read past. Before the template language begins, the document summarizes early findings from Phones in Focus, a national survey of educators about school phone policies. One of those findings carries the heading “Laptops present a new challenge for distraction.” On average, teachers in the survey estimate that 1 in 3 students are using laptops at school for nonacademic purposes like texting or social media.
That number deserves a careful reading. It is a teacher estimate rather than an observation, and the February release reported findings to date, with data collection continuing through the end of the school year. Even so, Angela Duckworth, who leads the study, added a detail in the February announcement that matters for Illinois districts: “this number doesn’t seem to depend on the school cell phone policy.” If that pattern holds, a phone policy alone should not be expected to move it. The state named the laptop problem in the same document that directs districts to solve the phone problem.
Compliance is a record, not a result
None of this is an argument against the law, or for one kind of policy over another. A district adopting a bell-to-bell policy for the first time and a district revising one it already has face the same question. The concern behind the law is real. Pew Research Center found that 72% of U.S. high school teachers call cellphone distraction a major problem in their classrooms, and a calmer room is an outcome worth having. My concern is narrower. A policy vote produces a record that a decision was made. It does not, on its own, produce evidence about learning. I lead technology for a K–8 district that will implement this same law, and the views here are my own.
The statute already gives boards a return date. Each board must review its policy at least once every three years, engage the teachers’ bargaining agent, administrators, and parents or guardians, and “consider any available data on the enforcement” of the policy. Enforcement data is useful. It can show how many devices were collected, how much staff time enforcement takes, and how often exceptions are requested. All of it measures implementation. If that is the only data on the table at the first review, the board will learn whether the policy was followed and very little about whether students are thinking more carefully than they were before.
So the question I would put to a district team is a simple one. What will you have in front of you at that first review that says something about learning, and about which devices?
Three channels, one decision
The tool I have found most useful for that conversation is a crosswalk that traces the same questions across three channels: personal phones and wearables, district-issued devices, and the generative AI features built into approved platforms. Public Act 104-0657 regulates the first, exempts the second, and does not mention the third.
Reading across a single row tends to surface the real policy. Take the question of who actually decides. For phones, a board votes in public, working from the ISBE template, and there is a record and a date. For district devices, decisions usually happen through procurement and refresh cycles, with no public vote. For AI features, the decision is often a vendor’s, made when a feature ships enabled in an update and no one in the district chose it. Three decision-makers, three levels of scrutiny, and the same student on the other end.
Another row asks which check nobody has run. For phones, it might be whether requesting an exception requires a student to disclose personal circumstances in front of a class. For district devices, it might be whether the instructional rationale that justified the one-to-one program still describes what happens on those devices. For AI, it is opening the approved platform as a student and watching what it offers first. That takes a few minutes, and few districts I know of have done it.
The full Policy-to-Practice Crosswalk, eight questions across the three channels with a 40-minute protocol for running it in a cabinet meeting, is free to use. So is an annotated Illinois resource set that notes, for each source, what it supports and what it does not. That second note matters more than it looks. Board presentations rarely go wrong because a study is fake. They go wrong because a real study is asked to carry more than it can.
The workshop
On October 27, from 9:00 a.m. to noon Central, I am leading a three-hour online workshop with PD365, What Your Phone Policy Cannot Do: The Friction Audit, for district teams working on their Public Act 104-0657 policies. We will work through the policy context, a framework for telling productive difficulty apart from barriers that only exclude, a district audit across those three channels, and a rationale a team can take to its board. The session is built to be as useful to a district adopting the ISBE template as to one revising a policy it already has.
Two things make the session more useful if you bring them: your draft policy or the ISBE template, and the name of your district’s approved AI or writing platform. Registration, including the on-demand recording, is through PD365. The session materials are public at minerclass.github.io/pd365-friction-audit.
The phone policy is the part of this work the state could write for us, and it has. What happens on the other two channels is still ours to decide. The three-year review is a chance to show that we decided it on purpose.
For the longer argument behind this post, see The Pouch and the Bypass.
Sources
Hatfield, J. (2024, June 12). 72% of U.S. high school teachers say cellphone distraction is a major problem in the classroom. Pew Research Center. https://www.pewresearch.org/short-reads/2024/06/12/72-percent-of-us-high-school-teachers-say-cellphone-distraction-is-a-major-problem-in-the-classroom/
Illinois State Board of Education. (2026). Model cell phone policy. https://www.isbe.net/Documents/Model-Cell-Phone-Policy.pdf
Miner, M. J. (2026). The friction audit: What your phone policy cannot do [Workshop materials]. GitHub. https://minerclass.github.io/pd365-friction-audit/
Phones in Focus. (2026, February 27). First-of-its-kind national educator survey reveals both promise and peril in school cell phone policies [Press release]. Gerald R. Ford School of Public Policy, University of Michigan. https://youthpolicylab.umich.edu/news/2026/first-its-kind-national-educator-survey-reveals-both-promise-and-peril-school-cell-phone
Pub. Act No. 104-0657, 2026 Ill. Laws (S.B. 2427). https://ilga.gov/legislation/PublicActs/View/104-0657