Citizen Portal

Tulsa board approves 'bell-to-bell' student device policy aligned with state law

Tulsa Public Schools Board of Education · August 18, 2025
Article hero
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 board approved revised policy 2620 to align with Senate Bill 139: students must keep personal phones stowed during the school day; district devices (Chromebooks) remain authorized and limited exceptions exist for concurrent-enrollment technology.

The Tulsa Public Schools Board of Education voted to approve a revised student-device policy (policy 2620) to comply with Oklahoma's Senate Bill 139. The board approved the measure after staff explained the policy applies 'bell to bell' and extends to student-purchased laptops, which generally must be stowed; district-issued Chromebooks remain permitted for classroom instruction.

Deputy Superintendent Dr. Dodd clarified that district Chromebooks are the intended instructional device and that exceptions exist in limited concurrent-enrollment classrooms where software requires more robust hardware. "You cannot bring a laptop from home and so you have to use a district approved technology device, which our Chromebooks would be in that category," Dodd said, adding that principals and school leaders have been asked to ensure adequate device availability.

Board members asked whether teachers may ask students to use phones for classroom tasks; staff said guidance will direct teachers to use district devices and that principals will provide expectations and supports for classroom practice. The policy change passed on a motion moved by Board Member Chrisant and seconded by Ms. Smith (motion recorded during the meeting). The board cast ayes and approved the policy.

The district said it would ensure intercom and classroom phones are available so families can reach students when needed and that local exceptions (for example, TCC concurrent-enrollment requirements) will be explicitly handled in site-level guidance.