Board hears proposal to replace local servers with cloud-based Verkada cameras; members ask about access, retention and bond transparency

District IT staff presented a procurement proposal to replace the district's on-site Milestone camera servers with a cloud-hosted Verkada system. Presenters described expected benefits: browser-based access from phones and tablets, longer cloud retention, simplified footage search and the ability to trace an individual across cameras.

"If you're looking for an individual with the yellow shirt and red hat, you type that in a search field and it's gonna pull up all the camera footage in the district of someone with yellow shirt, a red hat," the presenter said, noting the system's search features and broader coverage.

Board members asked how account access would be handled when staff or SROs leave, whether non-district contractors or law enforcement would retain access, how long footage would be kept on the cloud, and whether public-facing procurement materials would show pricing tied to bond funds. Presenters said in-house IT would administer accounts, that camera storage on devices holds 30'60 days locally before cloud upload and that the cloud retains data longer, and that removing school floorplans from public documents could be done before wider publication.

Why it matters: The proposal shifts video storage and administration from local servers and an external vendor to a cloud platform with broader access. That raises privacy and operational questions about who can view footage, how quickly access can be revoked, how retention policies are set, and whether the public can see procurement pricing for bond-funded purchases.

Board next steps: The presenter said the district could supply public-facing pricing and that technical documentation can be redacted to remove floorplans. No formal procurement vote occurred during the meeting; board members asked for public-facing pricing information tied to bond funds if the board considers a near-term decision.