Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the School Policy Cellphones topic

No spam. Unsubscribe anytime.

Board approves statewide-aligned limits on student cellphone use; purchase of locking bags deferred for public work session

AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

The Lake Havasu Unified School District governing board on July 10 approved revisions to the student code of conduct that restrict student use of cellphones and other wireless devices during the school day to comply with Arizona law.

The Lake Havasu Unified School District governing board on July 10 approved changes to the student code of conduct that restrict student use of wireless communication devices during the school day to comply with Arizona law.

Staff presented the policy change as required by state statute and cited House Bill 24-84 and ARS 15-20-0.05 in framing the district's obligations. The updated language in the student code of conduct prohibits use of cellphones and other wireless devices during the school day, including meals, passing periods and recess, except where expressly permitted by district procedure.

Student services staff outlined permitted exceptions in the proposed procedure: (1) educational use as directed by a teacher, (2) use during an emergency, and (3) use required for a student's documented medical need or Individualized Education Program (IEP)/504 accommodations. The proposal requires parents who need to contact a student during the day to call the school front office, where staff will facilitate contact.

Student services staff summarised proposed storage and handling by grade band: for kindergarten through sixth grade, devices are "discouraged" and must be off and out of sight (for example, in a backpack) unless a staff member authorizes use; for grades 7-12, staff proposed devices be powered off and stored in a locking bag during instructional time, with the bag remaining in the student's possession and unlocked at a designated exit point at the end of the day. Presenters said the bags reduce theft and damage and noted a quoted implementation cost (district estimate discussed in public comment) but said funding options, grants and a more detailed plan would be part of further discussion.

Student services presenter said the state law specifically contemplates exceptions and requires schools to adopt written procedures. The presenter read the statute's requirements and told the board the measure is aimed at limiting non-instructional social-media access during the day.

Board members, staff and public speakers debated trade-offs: parents and some board members said phones can be important for emergency contact and for parents of children with documented medical needs; teachers and administrators described classroom disruption and safety concerns and said the policy aims to centralize communications through the front office during incidents. One high school administrator described a pattern of technology violations at the high school and urged policies that reduce distractions and year-over-year incidents.

On the specific proposal to purchase locking bags from a private vendor, board members asked for more public engagement and a cost-benefit review. The board voted to remove agenda item 6.4 (the bag purchase) from the action calendar and asked the superintendent's office to schedule a public work session and to explore funding options, vendor demonstration, and broader community feedback before committing district funds.

The board then adopted the revised student code of conduct (agenda item 6.3). The code change is in effect as board policy; staff will return with procedures for implementation and with a public work session on the locking-bag option.

Provenance: student code language and proposed procedure read by district student services staff (transcript start 01:13:51); board vote approving the code appears in the meeting record later that evening (transcript start 01:40:08).