The five pieces of the working stack
1. AI cameras at every exterior entry. Person-of-interest and weapon detection, where third-party platforms (ZeroEyes, Omnilert, Defendry) overlay on the feed. The camera classifies the threat at the door, not after it's inside.
2. Role-based access control on interior doors. Classroom locks that trigger on a single press from the office or a teacher's mobile credential. Modern platforms (Brivo, Avigilon Alta, Genetec Synergis, HID Origo) handle district-wide lockdown in under five seconds, turning a corridor into a series of safe rooms.
3. Visitor management at the lobby. Watchlist screening, per-visitor passes, photo capture, host notification. It catches the visit that shouldn't be happening before the visitor moves past the lobby.
4. Two-way audio at perimeter doors. An after-hours buzzer-in event isn't unlock-on-faith. The principal or resource officer talks to the person on camera, then unlocks if appropriate.
5. Integration with the local police CAD system. First responders see live feeds on the way in, locate the threat, and stage entry without losing time. This requires policy work between the district and police before procurement.
FERPA, retention, and access
Identifiable footage of students may qualify as an education record under FERPA (20 U.S. Code Section 1232g). The practical implications: retention scoped to the district's records policy (typically 30 to 90 days), role-based VMS access, audit logging on every clip retrieval, and a chain-of-custody workflow for any export to law enforcement or insurance. Every modern platform supports this; the policy paragraph is the gap.
For private and faith-based schools, FERPA doesn't strictly apply, but state student-privacy laws often do. Design for FERPA expectations from day one regardless of public versus private status.
Grant funding: SVPP, NSGP, state programs
SVPP funds up to 75 percent of project cost for cameras, access control, classroom locks, lighting, and emergency communication. Eligible recipients include public districts, charter networks, and county or state law-enforcement agencies acting for schools. Awards typically range from $50,000 to $500,000 per applicant, with project periods of 36 months. NSGP funds up to $200,000 per site for nonprofit private and faith-based schools facing documented threats. State programs (New York's SAVE Act funding, Texas's school safety allotment, California Prop 1, Florida's Guardian program) layer on top. For funding-cycle detail, see the NPSE grant overview and NSGP for nonprofits and schools.
What we'd do the same again on a school project
Run the tabletop exercise before procurement, not after. Time the alert-to-response chain with the resource officer and local police. The exercise tells you which piece of the stack is the actual bottleneck. Often it's not the cameras.
Write the policy paragraphs before installing the hardware: FERPA retention, role-based VMS access, chain-of-custody for exports, escort-required areas. Two pages. Without it, the install runs but the audit doesn't pass.
Stage the rollout around grant cycles. SVPP and NSGP awards have project-period deadlines the install schedule has to land inside. See the broader education security overview for the full vertical pitch.