The pressure to improve school security today can create an understandable temptation for leaders in the education sector to move toward quick, visible solutions—things like new cameras, access control systems, alarms, duress devices, or other technologies.

But the harsh reality facing school administrators and facility staff is that technology—while incredibly helpful (and sometimes even life-saving)—can’t make a school safer on its own.

That was one of the central messages of “From Concept to Completion of a School Security Project,” a July 22 webinar presented as part of the Partner Alliance for Safer Schools’ School Safety and Security Summer Camp Webinar Series. The session brought together school security and project-management professionals to talk about what happens in between that gap after identifying a security need and actually creating a system, policy, or program that works.

The larger lesson for school facilities and operations leaders was pretty straightforward: Security improvements should be managed as comprehensive organizational projects, not isolated purchases.

Panelist Les Nichols, president of R.L. Nichols & Associates, an independent school safety and security consultant and former school architect, said districts often underestimate what’s involved.

“They do not appreciate at the front end of this the complexity involved in improving school security,” Nichols explained.

Physical improvements and technology are only part of the equation, she noted. Security projects also may require training, policies, organizational buy-in, and plans for maintaining improvements long after installation—considerations that belong at the front end of the process, Nichols said.

That’s an important distinction for districts balancing school safety against limited capital dollars, aging facilities, staffing pressures, and competing operational priorities.

Begin with the “why”

The presenters organized the security planning process around a very simple framework that’s familiar to just about everyone (especially journalists, like yours truly): the five W’s and H—why, what, who, where, when, and how.

Rather than beginning with a product or system, school leaders should start simple and first establish why an improvement is necessary in the first place, and how it supports broader district safety objectives.

“You are trying to increase your school’s capacity to protect people,” Nichols said.

Construction, technology, training, and policy are all effective ways of building that capacity, he explained, and each should align with a district’s goals, applicable requirements, and accepted security practices.

For Scott Clark, director of Health and Safety for Kansas-based Geary County Schools USD 475, the “why” behind a major security-management initiative could be expressed in a question as simple (yet important) as: “How do we make our schools safe and secure without making them feel like prisons?”

That question helped guide his district as it assessed existing conditions, explored the PASS School Safety and Security Guidelines, and developed its security program. It’s also one that every school must address in order to protect students and staff without allowing security measures to overwhelm the qualities that make a school feel welcoming and conducive to learning.

It also underscores why districts should define desired outcomes before selecting solutions. PASS organizes recommendations into security tiers, but webinar moderator Jim Crumbley, president and CEO of Risk Response Team, Inc., stressed that a higher tier does not automatically equate to better security. Measures should correspond to risks identified through assessment, he observed.

Administrators across the country are frequently being told to “do something,” Crumbley said—and that something is often technology. However, allowing pressure for visible action to drive investment isn’t a sound or financially responsible security strategy.

“If we don’t really understand what we’re trying to accomplish, we’re just throwing money at the problem,” he said.

The objective, he added, is to define the intended result, the deliverables, the metrics for success, and the timeline before determining what type of solution should be purchased.

Turn goals into measurable outcomes

Defining what a project should accomplish proposes another challenging question: How does a district measure whether a security investment is working?

Unlike energy savings, maintenance costs, or other facilities metrics that are fairly easily trackable—especially with IoT connected devices that collect and now analyze data using AI—security effectiveness often involves events that simply don’t occur. The presenters encouraged school districts to develop operational indicators that can demonstrate whether systems and procedures are performing as intended.

Nichols offered the example of a school struggling with doors being propped open—a common challenge in nearly any and every facility. The district considered several types of alarms and electronic security measures, but after considering the problem at length, it turns out the more useful question was how to define a “safe” door.

Rather than setting the unrealistic expectation that a door would never be left unsecured (as ideal as that goal might be), the district developed a measurable standard based on how quickly an open or unlatched door would be detected and corrected.

Because installing a camera, door alarm, access-control system, or duress device is not a measure of success in and of itself. Districts also need to know what the system should accomplish and how they will determine whether it continues to operate as intended.

Get the right people involved

Security projects rarely fit neatly within a single department because school safety isn’t just one person’s or group’s responsibility. It’s a complex, moving target that requires input and buy-in from multiple stakeholders.

Facilities, security, information technology, purchasing, communications, administrators, first responders, vendors, human resources, and maintenance personnel may all have roles to play, and Nichols cautioned districts against limiting participation too early because complex projects inevitably reveal issues one department may not anticipate.

Panelist Desire Bayne, security systems network specialist for Fairfax County Public Schools in Virginia, recommended using a RACI matrix—a responsibility assignment tool used in project management—to help identify who is responsible, accountable, consulted, and informed for individual tasks.

“When everyone is responsible for something, no one is truly accountable,” Bayne said.

Defining those roles using this type of matrix can help reduce duplicated work, accelerate decisions, and make it clear who has authority when problems arise. It also helps avoid a familiar project-management problem: a stakeholder learning too late that a decision affects a system or responsibility that falls under his or her purview.

That can carry significant consequences when it comes to connected security technology. Bayne noted that IT evaluations and cybersecurity issues can stall projects, while security systems may intersect with visitor management, mass notification, video surveillance, emergency communications, and first-responder access.

Given all these variables, communication itself starts to become part of a successful execution strategy.

“Even if you don’t have an update and you’re telling the customer or a manager, ‘Hey, I don’t have any update today,’ that’s an update,” Crumbley said. “Communication is critical.”

Plan around the realities of operating schools

Scheduling is another area where school security projects differ from many conventional installations. Construction, procurement, bidding, testing, training, policy approvals, and commissioning may all need to fit around the academic calendar. Clark said the overriding consideration in his district is how the work affects teaching and learning.

Projects may be scheduled for summer or outside instructional hours to minimize disruption, but districts also have to leave sufficient time for training, testing, and retesting before systems are placed into service.

Bayne recommended testing assumptions under actual building conditions rather than relying solely on estimates. “Go out and do something yourself,” she advised.

A device expected to take two minutes to install, for example, may actually take 10 minutes or more, so installation work that’s assumed to be possible during school hours may prove too disruptive. Further, contractors may require staff escorts or special building access, complicating matters even further.

Those discoveries can change labor requirements and project schedules substantially when you multiply them across dozens of schools or hundreds of devices. The lesson here is particularly relevant for facilities departments that are accustomed to compressed summer construction schedules: A security system has to leave enough time not just for installation, but also for commissioning, employee preparation, troubleshooting, and operational integration.

Let assessment drive investment

The webinar condensed the broader project-management process into four phases:

1. Visioning
2. Assessment
3. Execution
4. Handoff

During visioning, districts should create a project charter connecting the initiative to institutional goals, establishing its scope, and documenting why it’s necessary. Assessment then provides the evidence that’s needed to prioritize improvements.

Nichols urged districts to consider state requirements alongside industry guidelines, community standards, and what he described as “leading practices.” Clark similarly emphasized grounding security assessments in established laws, standards, and guidelines.

The panel also addressed a concern some administrators may have about documenting security vulnerabilities in writing. Nichols argued that districts shouldn’t view an assessment as an admission that every risk has been eliminated. Rather, documentation can demonstrate that leaders recognized a vulnerability, developed a response, and committed available resources toward addressing it.

“The goal is reasonableness, not perfection,” Nichols said.

That mindset gives facilities leaders a useful way to think about the difficult and unfortunate reality that no security plan can eliminate every possible risk. But a thorough planning process does help demonstrate that a district has systematically evaluated its facilities and is making rational decisions about where limited resources can have the greatest effect.

The presenters also cautioned that public-record and disclosure requirements concerning security information vary by jurisdiction. Districts should understand applicable state and local requirements governing the storage and distribution of assessments and related records.

Installation is not the finish line

The final phase—handoff—may be the one most closely aligned with the day-to-day responsibilities of school administrators and facility and IT staff. Security projects need operating procedures, training programs, maintenance responsibilities, and processes for bringing new employees up to speed. Staff members maintaining physical systems need to know what requires inspection or service, and administrators need a way to verify that required training remains current.

Systems also have to be reevaluated as buildings, staffing, technology, and procedures change, Crumbley noted: “The handoff has to continue,” he said. “It’s not a one-play handoff. It’s live, it’s ongoing.”

The panelists explained that security measures sometimes fail years after installation not because the original idea was necessarily flawed, but because maintenance, evaluation, training, or operational ownership faded over time.

The lesson? Effective school security isn’t created simply by accumulating products—it comes from connecting risk assessment, facility design, technology, operations, people, policies, training, and maintenance into a larger, coordinated strategy.

For administrators under pressure to “do something,” disciplined planning may be less visible than a new camera, electronic lock, or emergency notification system. But it may ultimately determine whether that investment becomes part of a safer school or simply another piece of technology that never delivers what the district expected.