Lifetime Citizen Portal Access — AI Briefings, Alerts & Unlimited Follows
Subcommittee debates Chromebook policy, repair costs and device‑management practices
Loading...
Summary
The CIO explained a new middle‑school practice to keep Chromebooks on site, said Chromebooks have a five‑year lifespan and requested 1,000 student Chromebooks and 350 teacher laptops; committee members pressed for data on damage rates, recovery of repair costs and a uniform policy on accessories and color printing.
The subcommittee examined the district’s digital resource policy and an operational change: middle‑school Chromebooks will stay at school and be returned to homeroom charging stations each day, while high‑school students continue to keep devices from grade 9 through 12. The CIO said the district is requesting 1,000 student Chromebooks in the upcoming budget and that Chromebooks have an expected five‑year life cycle after which Google no longer updates the software for testing.
The CIO described current repair and loaner practices: technicians triage devices, salvage parts from retired units, and provide loaners when possible; a screen repair example cited in discussion was $50 and the district has used ParentSquare to send invoices and explore parent payment options. "We were working and we were all kinda brainstorming, and we are gonna roll out through Missus Sardinia, a bill or an invoice type thing through ParentSquare," the CIO said, proposing that parents receive direct notices and an option to pay online.
Committee members asked for data showing whether keeping Chromebooks in school improved outcomes, how many devices are being repaired versus replaced, and whether the district is recovering repair costs. One committee member described earlier problems with Yonder accessory pouches and called that rollout "an absolute mess," asking whether pouches are still handled separately from device management.
On accountability for intentional damage, committee members suggested stronger, uniform consequences and clearer data on how often the district refers behavior to law enforcement (the CIO said no law‑enforcement referrals have been made). Members also requested centralized, up‑to‑date data on device inventories and damage/collection amounts so the committee can evaluate whether requested refreshes and staffing levels are sufficient.
Next steps: the CIO will provide data on device damage/repair and collections, share the ParentSquare invoicing pilot details and propose a draft printing/copy policy for committee review.
