The Disconnect Between School Cameras and 911 Dispatch

Nearly every public school in the United States now has security cameras — the National Center for Education Statistics puts the share at 93 percent as of 2021, up from 61 percent a decade earlier. Yet in an active emergency, the 911 dispatchers coordinating the response cannot see what those cameras capture. The footage stays locked inside school systems, and responders arrive relying on fragmented, second-hand updates.

A new opinion piece published on eSchool News argues this gap is an access problem, not a technology problem. Written by Dean Drako, chairman and CEO of cloud security firm Brivo, it calls for secure camera-sharing links between schools and emergency communication centers (ECCs), so dispatchers can pull up live video the moment an incident is reported and relay concrete details — where a suspect is, who is in danger, which areas are unsecured — to officers en route.

The pitch comes with privacy guardrails: access would be triggered only by a 911 call, limited to the duration of the emergency, and extended voluntarily to nearby businesses that opt in. The author cites an unnamed survey finding 96 percent of parents support the idea, and notes that average response times exceed eight minutes nationwide and can stretch past 25 minutes in rural areas — minutes that live video could help responders use.

What Camera-Sharing Would Change — and Who Stands Behind It

The central observation is easy to verify: the hardware gap has largely closed, while the access gap remains open. The harder question is who should be trusted to bridge it.

Advertisement

Brivo's Stake in the Argument

This is not a neutral public-interest essay. Drako runs a company whose flagship products — cloud access control, video intelligence and AI-based gun detection — sit precisely at the intersection the article describes. The fix he proposes is, in effect, a blueprint for a product category his firm sells. That does not make the underlying problem less real, but it explains why the problem is framed as urgent and solvable today: advocacy of this kind doubles as demand creation for an emerging security market.

Why the Real Bottleneck Is Governance

With camera penetration at 93 percent, the obstacle is no longer infrastructure. It is rules: who may view a feed, for how long, under what authority, and how a safety tool avoids becoming a surveillance network. The article's answer — emergency-only access, temporary activation, cameras staying under owner control, opt-in participation from surrounding businesses — is essentially a governance model designed to make the technology politically and legally acceptable. As the author concedes, trust is the limiting factor: without it, schools and nearby property owners will not opt in, and the network never reaches scale.

What's Unproven in the Pitch

Two headline numbers need scrutiny. The 96 percent parent-support figure is attributed only to "a recent survey," with no source or methodology; the eight-minute and 25-minute response-time averages are cited with no underlying data. Districts evaluating the idea should treat those numbers as claims to verify, not verified benchmarks. The article also leaves practical questions unanswered — integration costs, technical capacity at local ECCs, and how smaller districts would implement and audit access.

What Districts Should Ask Before Linking Cameras to 911

For district safety administrators weighing camera-sharing, the conversation should start with specifics:

  • Integration, not replacement: with 93 percent of schools already wired for video, the question is whether existing systems can connect to the local emergency communication center — not whether to buy new cameras.
  • Get the access model in writing: the proposal limits viewing to the duration of a 911-triggered incident. Any agreement should spell out who can view feeds, for how long, and how that access is audited.
  • Test the numbers locally: the 96 percent parent-support figure comes from an unnamed survey, so gauge your own community's appetite and privacy concerns before committing.
  • Ask about capacity: confirm the ECC serving your district can actually receive and display live feeds, and clarify who covers the integration cost.