Citizen Portal
Sign In

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

Get email alerts on the School Safety topic

No spam. Unsubscribe anytime.

Coatesville board advances ShotSpotter proposal for senior high campus amid data‑retention and access concerns

Coatesville Area School District Board (committees) · March 10, 2026
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 operations committee advanced a draft agreement to expand SoundThinking’s ShotSpotter gunshot‑detection coverage to the senior high campus after lengthy discussion about audio snippets, who owns the recordings, data‑retention timelines and officer notification/access; the board asked administrators and the district solicitor to harden contract terms on retention, notification and reporting.

Coatesville Area School District’s operations committee on March 10 moved forward a draft agreement to expand ShotSpotter (SoundThinking) coverage to the senior high campus, but several board members pressed administration and legal counsel for stronger contract protections on privacy, access and data retention.

Administration said the system — already in use in the city of Coatesville after a grant obtained by the city police and district attorney — would provide event‑triggered audio snippets tied to percussive sounds consistent with gunfire and immediate alerts to law enforcement. The draft agreement describes audio data as limited to short, event‑triggered recordings and says data will be used “exclusively for public safety, criminal investigations, system performance validation.” The operations committee asked staff and counsel to seek clearer, written commitments.

Board concerns focused on three principal areas:

- Data ownership and retention: the draft indicates law‑enforcement partners may own the recordings. Several board members requested explicit retention and deletion timeframes for recordings that do not result in confirmed incidents and asked the vendor and police to commit to deleting non‑incident snippets within a short, stated window (the vendor’s usual practice was described in presentations as a short retention window such as 48–72 hours). Counsel said imposing an absolute short window could impair criminal investigations, and agreed to negotiate clearer language that balances investigatory needs with privacy protections.

- Access and notification: board members requested explicit language guaranteeing that school police and designated district staff will receive the same real‑time notifications available to city officers and that the district will be notified promptly when alerts implicate district property. The committee asked that such access be written into the agreement.

- Subpoenas, reporting and oversight: the solicitor said the draft holds each party harmless while preserving political‑subdivision immunities. The board sought a requirement that the police department or vendor bear the cost of responding to subpoenas for data they control, and asked for quarterly performance reporting (alert counts, confirmed incidents, false alerts) that the district can review.

Administration and counsel said they will return to the vendor and the police department to request contract edits and agreed performance reports. The committee voted to forward the draft agreement to the full board while staff negotiates clearer retention, notification and reporting language.

The discussion underscored competing objectives: speeding police response to potential campus gunfire while limiting routine audio capture and protecting students’ privacy. The district solicitor advised that the board may have the option to require notice or terminate the agreement with short notice if contractual performance does not meet the district’s expectations.