Schools face no shortage of security products, programs, and recommendations. Cameras, access-control systems, alert platforms, reinforced doors, training programs, and staffing options are all presented as ways to improve protection.
The difficult part is determining which solution addresses the school’s actual vulnerabilities—and whether it will perform as intended under realistic conditions.
One pattern repeatedly appears in safety planning: leaders begin comparing products before they have clearly defined the safety function the product needs to perform. That sequence makes it difficult to distinguish between a useful safeguard and a well-marketed feature.
| The Principled Safety® approach begins with the risk, the scenario, and the required performance. These five mistakes often prevent schools from making those connections. |
Mistake 1. Starting with the Product Instead of the Scenario
Evaluations often begin after a product or program has already attracted attention. A vendor offers a demonstration, another district recommends a system, or a recent incident creates pressure to adopt a particular measure. The discussion then centers on features, price, and implementation.
A more disciplined evaluation begins by defining the credible scenario the school needs to address. Leaders need to understand how an attacker could gain access, where students and staff could be exposed, how the threat might move through the campus, and which opportunities exist to interrupt that progression.
That analysis establishes the safety function a solution must perform. The requirement may be to detect unauthorized entry immediately, delay movement into occupied areas, communicate actionable information, or provide responders with rapid access. Once that function is clear, the school can evaluate whether a proposed solution is capable of achieving it.
| Start with the scenario. Define the safety function before comparing solutions. |
Mistake 2. Treating a Best Practice as a Universal Answer
Best practices offer useful reference points, but they cannot replace analysis. A safeguard that performs well in one setting may provide limited protection in another because school layouts, staffing models, schedules, and operating conditions differ.
This does not mean every school needs a completely different methodology. A consistent, principles-first process can be applied across different environments. What changes are the scenarios, vulnerabilities, and performance requirements identified through that process.
Before adopting a commonly recommended measure, leaders need to confirm that it addresses a vulnerability that actually exists on their campus. Otherwise, the school can invest in solving a visible or familiar problem while leaving a more consequential gap unresolved.
| Use best practices as reference points—not substitutes for campus-specific analysis. |
Mistake 3. Judging Solutions by Features Instead of Performance
Security products are often compared by the number of features they include. That information has value, but it does not establish whether the product will perform its intended safety function during an attack.
Consider a surveillance system. Recording quality, storage capacity, and camera count matter, but they do not answer the most important operational questions. Can the system detect unauthorized entry in real time? Can it maintain coverage as the person moves through the building? Will designated personnel receive useful information quickly enough to act? Will the system continue operating when smoke, dust, network congestion, or a power interruption affects normal conditions?
Performance expectations need to be defined before equipment is selected. Once the school knows what the safeguard must accomplish, vendor claims can be evaluated against measurable requirements rather than general descriptions.
A useful parallel comes from safety-critical engineering. A research laboratory installed an experimental unit with an enclosed glovebox and fume hood intended to protect technicians from toxic fumes. On paper, the system checked the expected boxes: the hood, ductwork, fan, and HEPA filtration system had been installed according to the design specifications, and a visual walk-down did not reveal an obvious defect.
The conclusion changed when the system was tested against the performance it actually had to deliver. During a smoke test at the required airflows, the hood failed to capture smoke completely under certain conditions, creating the potential for technician exposure. The problem was traced to small leaks at duct connections along the exhaust pathway.
The lesson is the same for school safety solutions: correct installation and impressive specifications are not proof of protection. A safeguard should not be considered effective until it demonstrates the required performance under realistic operating conditions.
| Features describe a product. Performance demonstrates whether it protects people. |
Mistake 4. Evaluating Each Measure in Isolation
A school safety measure rarely operates alone. Cameras depend on communications. Communications depend on reliable coverage and clear procedures. Access control affects both unauthorized entry and emergency responder access. Training depends on whether staff can realistically carry out the required actions under stress.
When these elements are evaluated separately, important conflicts and gaps can remain hidden. A door may provide effective lockdown protection while creating an access problem for responders. An alarm may communicate danger quickly while triggering an occupant response that increases exposure under another emergency scenario.
Principled Safety treats the school as an integrated safety system. The analysis therefore includes how a proposed solution interacts with existing equipment, procedures, staffing, and facility design in the given scenario. The relevant measure of success is whether the complete system performs better after the safeguard is introduced.
| Evaluate the whole safety system—not just the individual safeguard. |
Mistake 5. Assuming Installation Equals Effectiveness
Implementation does not complete the evaluation. A safeguard can be installed correctly and still fail to provide the intended protection because of maintenance problems, operational workarounds, inadequate training, or changes in campus conditions.
Critical safety functions need to be validated through inspections, drills, performance testing, and routine observation. If staff regularly bypass an access-control process because it interferes with daily operations, that behavior signals a system weakness. If communications do not work reliably throughout the campus, the gap needs to be identified before an emergency exposes it.
Mature safety organizations revisit assumptions even when no incident has occurred. Buildings change, equipment ages, staff members turn over, and procedures gradually drift from their original design. Continued evaluation confirms whether safeguards remain practical, reliable, and aligned with the scenarios they were selected to address.
| Installation is the beginning of validation—not proof of effectiveness. |
A Better Standard for School Safety Decisions
Schools do not need to reject new technologies or established best practices. They need a disciplined method for determining where those measures belong and what they are expected to accomplish.
Every proposed solution should connect to a credible threat scenario, a defined vulnerability, and a measurable safety function. It should be evaluated as part of the larger system and validated after implementation. That process gives leaders a defensible basis for prioritizing investments and identifying gaps that product comparisons alone will not reveal.
Schools will make different safety investments because their facilities, operations, and vulnerabilities differ. What should remain consistent is the process used to select, integrate, and validate those investments.
| Principled Safety® provides that structure, keeping the focus on measurable system performance and the prevention of harm. |
Source note: Adapted from “Five Common Mistakes Schools Make When Evaluating Safety Solutions,” based on Before the Next Tragedy: Preventing Harm in School Shooting Scenarios by John D. Menna, PhD.
If you’d like to explore more of the thinking behind the Principled Safety® approach, these related articles examine several challenges school leaders face when evaluating and improving safety:
Why School Safety Needs a Framework, Not Another Checklist
How the Principled Safety® Framework Would Analyze Parkland and Uvalde
Building Safer Schools Through Principled Thinking
Prevention by Design: Building School Safety Systems That Work
Explore these and other school safety articles.
Take the Free School Safety Assessment. It is designed to help school leaders begin examining that question—identifying potential gaps in existing safety plans and considering whether individual safeguards function together as an integrated system.
For readers who want to go deeper into the methodology, Before the Next Tragedy: Preventing Harm in School Shooting Scenarios provides a more comprehensive examination of applying principled, systems-based thinking to school safety—including the defense-in-depth concepts discussed in this article.
