WHO WE SERVE · EDUCATION · CAMPUS SAFETY & EMERGENCY RESPONSE
Independent technology governance for the systems that have to work the first time and every time. Emergency notification, classroom alerting, threat assessment, lockdown, and the integration layer that connects campus systems to municipal PSAP and CAD environments.
THE CAMPUS SAFETY REALITY
Campus safety technology is the rare category where partial system performance is operational failure. The notification system either reaches every recipient on every channel or it does not. The classroom alerting hardware either triggers cleanly or it does not. The integration with municipal PSAP either works or it does not. Sentinel governs the campus safety stack because the cascade of integrations either holds or fails, and the failure mode is not an inconvenience.
50
states with post-Parkland school safety statutes mandating threat assessment teams, lockdown drills, or emergency operations plans
3
primary integration boundaries the campus safety stack has to span: campus systems, municipal PSAP / CAD, and parent / community notification channels
$3-4B
annual US market for campus safety technology across K-12 and higher-ed
2018
the year (Parkland) that fundamentally reshaped the regulatory and procurement environment, with sustained growth since
CHALLENGE
Campus safety is not a single technology category. It is a cascade of systems that have to talk to each other. Emergency notification, classroom alerting hardware, access control, video surveillance, weapons detection, threat assessment workflow, and the campus dispatch or municipal PSAP that handles the actual incident. Most consultancies advising on this work specialize in one layer and treat the integration boundaries as someone else’s problem. Sentinel governs the integration layer because that is where campus safety either holds or fails.
THE PRESSURES
These are the structural pressures we hear from district safety directors, campus police chiefs, threat assessment team leads, emergency managers, and the IT staff who keep the integration layer running. Sentinel’s role is to help your institution navigate them with documentation that survives post-incident review, board scrutiny, and potential litigation.
Evolv Express, ZeroEyes, and others are now standard procurement evaluation items. The 2024-2025 FTC scrutiny of vendor performance claims (Evolv settlement) reshaped the discipline overnight. Districts and campuses are caught between political pressure to act and uncertainty about which technology actually performs in their deployment context.
Districts that bought standalone notification systems are retrofitting integration. The “every system talks to every other system” expectation is moving from aspiration to baseline. Most architectures evolved organically without the integration layer as the design priority.
Florida SB 7026, Texas HB 3, Tennessee threat assessment requirements, Colorado school safety statutes, and parallel statutes in most states. The Bipartisan Safer Communities Act (2022) added significant federal resources. The patchwork is more variable than student data privacy and changes faster.
Video analytics, behavioral threat assessment AI, social media monitoring tools. Vendor claims often outpace evidence. Civil liberties pushback is meaningful and material. Institutions need governance frameworks that distinguish legitimate analytics from theater.
Cyber insurance underwriters increasingly require evidence of MFA on safety platforms, EDR, segmented backup, and tabletop exercises. The insurance posture has become an effective enforcement layer that federal and state policy have not driven directly.
Threat assessment teams need access to student records to do their work. FERPA and state student data privacy laws constrain that access. The reconciliation is governed at the operational level by every district and institution that has a threat assessment team. Most are operating without explicit guidance.
OUR APPROACH
Sentinel's campus safety approach is built on integration discipline. Each principle reflects the operational reality that university public safety technology programs span dispatch, mass notification, access control, residence-life systems, and emergency operations. They must function as a single coordinated layer the moment an alert triggers.
Most campus safety consultancies advise on platform selection and treat the integration with municipal PSAP, with classroom alerting hardware, with access control, and with parent communication channels as someone else’s problem. Sentinel governs the integration boundary because that is where the cascade holds or fails.
Campus safety incidents become municipal public-safety incidents at a defined trigger point. The technology has to support that handoff cleanly. Sentinel’s public-safety dispatch pedigree is exactly what this discipline requires.
Sentinel does not resell emergency notification platforms, classroom alerting hardware, threat assessment tools, weapons detection systems, or access control. We do not partner with them. The recommendation you get is the recommendation we would make if it were our own campus.
Our governance work documents what we find and surfaces evidence. It does not become a party to disputes between institutions and vendors, between institutions and municipal PSAP, between institutions and post-incident litigation. Sentinel documents, never litigates.
CORE CAPABILITIES
Every engagement is anchored in six disciplines that protect the institution from broken integrations, weak documentation, and the post-incident accountability gap that follows a real or simulated event.
Independent oversight of multi-channel emergency notification system selection, deployment, and operation. Multi-channel delivery (SMS, push, voice, digital signage, sirens), integration with municipal PSAP and NG911, integration with classroom alerting hardware.
Governance of the institution’s threat assessment team workflow and supporting technology. Tool selection, data handling discipline, FERPA mapping, parent notification protocols, integration with district SIS for student record access.
Configuration authority for the integration between campus safety systems and municipal PSAP / NG911 environments. The most technically demanding work in the discipline; the work no other consultancy in this market can credibly govern.
Vendor-neutral oversight of access control modernization, video surveillance, and the integration into the broader safety cascade. Includes weapons-detection technology evaluation against actual performance evidence.
Body-of-evidence preparation for post-incident review, board scrutiny, parent inquiry, or potential litigation. Documentation that survives every audience.
Documenting whether the technology stack performed as designed during a real or simulated incident. Findings advisory and non-binding. Critical for the institution’s defensive posture and for ongoing program improvement.
Most campus safety consultancies organize around a single layer. Notification, threat assessment, access control. Sentinel positions around the cascade as a whole, with the four practices as the load-bearing structure that holds across integration boundaries, vendor handoffs, and the post-incident review nobody plans for.
Every layer has to hold. Every time.
Each addresses a specific pressure point in the campus safety cascade. All are governed by the SVA standard: findings advisory, non-binding, structured for documentation that survives post-incident review and potential litigation.
Targeted engagement evaluating district or campus emergency notification system options against operational requirements: multi-channel delivery, integration with municipal PSAP / NG911, integration with classroom alerting hardware, parent and staff communication patterns. Includes vendor procurement support and post-deployment integration audit. Cross-domain credibility on the PSAP integration question.
Multi-quarter engagement governing the institution’s threat assessment team workflow and the supporting technology. Covers tool selection, data handling, FERPA mapping, parent notification protocols, integration with SIS / LMS, and post-incident review readiness. Bridges threat assessment as an operational discipline with the technology and documentation discipline that survives review.
Post-event engagement reviewing whether the campus safety technology stack performed as designed during a real or simulated incident. Independent and findings-advisory. Includes notification timing analysis, system availability review, integration performance review, and recommendations for remediation. Independent of all vendors involved; structured to survive litigation discovery.
OUR PRACTICES
Every Sentinel engagement draws on the practices that match the program’s stage. We bring them in proportionally; we never sell the whole stack when only part of it earns its keep.
PROGRAM MANAGEMENT
How we govern your program.
Program execution discipline for campus safety technology modernization across multi-year capital cycles. Phase gates that survive Chief of Public Safety transitions, Vice President for Student Affairs reorganizations, and capital-campaign budget shifts. Decision logs that survive Clery audits, Title IX inquiries, and post-incident reviews.
CHANGE MANAGEMENT
How we prepare your operators.
Operator readiness for new campus safety technology fielding across departments. Dispatch console transition training, mass-notification cutover drills, residence-hall access-control rollouts, and threat-assessment platform onboarding. The change rhythms that determine whether the new system actually works the night the alarm comes in.
CONFIGURATION AUTHORITY
How we own the configuration.
Configuration authority for the campus safety technology stack. Translating institution-specific operational realities into platform configuration. The team that owns “is this how the dispatch console should escalate when a residence-hall alarm aligns with a stadium-event blue-phone activation?” decisions across CAD, NG911, mass notification, access control, and BWV systems.
VALUE ASSURANCE
How we prove the mission outcome.
Independent governance documenting whether the institution’s campus safety technology investments are delivering operational outcomes: incident response times, mass-notification reach during drills, mutual-aid interop performance, and Clery and VAWA compliance posture. Findings advisory and non-binding. Critical for trustee briefings, accreditation reviews, and post-incident transparency.
After engagement closes, Sentinel Sustain keeps the practice active across the life of the investment. Three tiers: Core, Active, and Strategic.
Learn more →DEEP EXPERTISE
Sentinel’s campus safety bench combines public-safety dispatch pedigree, integration boundary governance experience, and audit-grade documentation discipline. The campus-safety-specific advisor bench is in flight; the firm-level governance discipline is operational today.
WE KNOW THE TRICKS
The campus safety vendor playbook has matured rapidly since 2018, with consistent patterns across emergency notification, classroom alerting, threat assessment, access control, and weapons detection. Here is what we look for, before the contract is signed.
01
Vendor markets weapons detection technology with performance claims that exceed what published evidence supports. The Evolv Express FTC scrutiny and 2024-2025 settlement reshaped the discipline. We require independent performance evidence, deployment-context-specific testing, and false-positive rate documentation before any procurement decision.
02
Vendor claims 99-percent or higher delivery rates across all channels. The actual reach varies sharply by channel, by recipient, by time of day, and by the institution’s database hygiene. We test channel-specific reach with the institution’s actual contact data before the contract is signed.
03
Vendor commits to integrations with the institution’s SIS, the municipal PSAP, the access control system, and the classroom alerting hardware by some future date. The roadmap slips and the institution staff manually bridges the gaps. We require working integration demonstrations before contract signature, not roadmap promises.
04
Vendor offers tabletop exercises as a substitute for actual integration testing. Tabletop exercises are valuable, but they do not surface integration failures that only manifest under real-system load. We require both tabletop and live integration testing.
05
Vendor pitches campus safety technology with cybersecurity tools bundled in (or vice versa). The bundle creates contractual lock-in that the institution did not need. We unbundle the procurement decisions and evaluate each on its own merits.
WHO YOU ARE WORKING WITH
The people on the other side of every Sentinel campus safety engagement combine public-safety dispatch pedigree with the cross-jurisdictional documentation discipline that the campus-to-PSAP boundary requires. Where the discipline-specific advisor bench has gaps, we name them, and we name what is in flight.
Justin co-founded Sentinel after a career in state-government technology governance and emergency-response coordination, including direct work with public-safety dispatch and PSAP environments. The cross-jurisdictional pedigree and the campus-to-PSAP integration boundary are exactly where this discipline lives.
Jason co-founded Sentinel after sitting on every side of the technology-program table. Vendor, integrator, program office, operator. His practitioner-grade perspective on multi-system program governance is what shaped Sentinel’s vendor-neutral standard. Campus safety is a cascade of integrations; Jason’s pedigree maps directly.
24+ years in public education administration with 15 years as Grants Manager for Bridgeport Public Schools, where she has secured more than $20M in federal, state, and private funding. Currently serves as elected Mayor of Bridgeport, Nebraska. Brings deep institutional, civic-coordination, and post-incident communication experience to every Sentinel campus safety engagement.
Also Supporting Your Program
The right engagement depends on where your institution is in the campus safety program lifecycle, what your existing safety bench looks like, and which cascade pressure is creating the most friction. Each subscription has a clear scope, deliverable structure, and exit point. Subscriptions stack.
Managed Technology Subscription
End-to-end managed operations for the campus safety platforms Sentinel helped your institution stand up. Sustainment, vendor coordination, integration discipline across emergency notification, CCTV, access control, and threat assessment workflows, plus round-the-clock readiness coverage. The campus is still ready for the next incident, because someone is still accountable for the systems behind it.
The institution needs ongoing operations of a Sentinel-deployed safety platform; safety posture depends on continuous integration health across multiple vendors; or the program runs across multiple chiefs, deans of students, or board cycles.
We govern the operation. We never sell the platforms.
Read more about Sustain →Retained Governance & Advisory
Ongoing retainer with quarterly governance reviews, pre-decision advisory, and an open line for board briefings, parent-community response, regulatory inquiry response, and vendor escalations. The institution has independent counsel on the safety technology side of the table, every cycle.
The institution has a multi-year safety program; the cost of a misstep is post-incident scrutiny, Clery finding, or board-level escalation; or campus safety governance cycles are continuously in motion.
Sentinel documents. We do not litigate.
Read more about Guardian →Anchored to a Signature Practice or Defined Deliverable
Anchored to one of SDF, SRM, SDB, or SVA, or to a single defined deliverable: Campus Emergency Notification System Selection and Integration Audit, Threat Assessment Workflow Governance, or Campus Safety Post-Incident Technology Review. Fixed scope, named practice or deliverable, defined timeline.
The institution knows the discipline or deliverable needed and wants a contained, scope-bounded engagement that produces a defensible institutional record before the next safety governance review.
Independent. Practitioner-led. Vendor-neutral.
See how the practices apply →Specialized Services + Practice + Sentinel Institute
A specialized service plus a signature practice plus Sentinel Institute training combined into a tailored program. Best when the safety and IT teams need to learn the discipline as the discipline is being applied, particularly after an incident or during major safety platform rebuild.
The institution is rebuilding the campus safety technology stack from scratch and wants the institutional capacity to operate it across multiple administrations.
Cutting-edge. Never bleeding-edge.
See the Institute deep-dive →READY WHEN YOU ARE
Tell us where your institution is. Pre-event planning, post-event review, mid-modernization of the safety stack, or evaluating a new technology category. We will tell you honestly whether Sentinel is the right fit. The conversation costs nothing. The integration either holds or fails. We help make sure it holds.
