Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Bus Tracking App topic
No spam. Unsubscribe anytime.
Revere board weighs bus‑tracking apps amid parent demand and safety concerns
Summary
The Revere Local Board of Education heard a presentation and engaged in detailed discussion about school bus‑tracking apps, with staff urging caution over outages, costs and safety tradeoffs and the board requesting vendor cost estimates and peer‑district experience.
Revere Local school officials spent much of their June 23 meeting discussing whether to adopt a parent bus‑tracking app, hearing a technical briefing from a guest and debating tradeoffs between parent convenience and operational safety.
Mr. Nightenboff, invited to brief the board, said parents call periodically—"maybe three to five times a year"—asking whether the district will provide real‑time bus tracking. He said Revere’s mostly stable routing limits immediate gains from an app and cautioned that he has not yet seen a solution that is a "100% win for the district." He recommended limited "ping" notifications (for example, when a bus is within a 10‑minute radius) rather than continuous live tracking.
Board members and staff raised multiple operational concerns. They noted substitute‑driver practices and route stability reduce the practical benefit of tracking in Revere; one staff member said the district already sends ParentSquare alerts when buses run more than 10 minutes late. The board also discussed safety risks during severe weather or accidents, citing a recent windy day when routes were repeatedly changed and warning that an app outage in that scenario could add hundreds of parent calls and lead parents to the scene of an incident before emergency responders.
Cost, technical compatibility and vendor support were recurring questions. Board members asked whether hardware modifications would void vehicle warranties and how routing software would communicate locations in low‑cell‑coverage areas. Staff reported the district’s routing software currently costs about $5,000 a year; the incremental cost to add a parent‑facing tracking app was not known at the meeting.
Members also sought empirical comparisons. Several suggested staff contact neighboring districts that use tracking—one example cited was Brecksville–Broadview Heights—to learn how often systems go down, whether districts handle initial help‑desk volume in‑house, and whether pilots or short‑term trials were offered.
Outcome and next steps: the board asked staff to gather vendor cost estimates, technical details (including any required bus modifications), and peer‑district experience, and to return with that information before any purchase decision. No formal action or vote was taken.
