School doors today are expected to perform two very different functions in an emergency: to allow occupants to evacuate safely during a fire and help secure the building during a lockdown. Both are essential to student and staff safety, but the codes and standards governing these systems don’t always address how they should work together when emergencies overlap. So, it’s vital for facilities teams to understand how these systems interact well before emergency situations arise.

Where fire safety and lockdown requirements intersect

NFPA 101, the Life Safety Code, requires electronically locked doors to unlock on fire alarm activation. It’s one of the most consistent rules in the code. Whether a door uses an access-controlled egress release, a delayed egress lock, or a magnetic lock tied to the fire panel, the fire alarm has to win. That’s the whole point of the rule. It keeps occupants from being trapped behind a locked door during a fire.

Alyssa’s Law, named for Alyssa Alhadeff, a student killed in the 2018 shooting at Marjory Stoneman Douglas High School, and its state-level equivalents pull in the other direction. The law requires public schools to install a silent panic alert that reaches law enforcement directly, and in a growing number of states, that alert is required or expected to integrate with the building’s lockdown system to secure doors and restrict movement the moment it’s triggered.

Neither code addresses what happens when both signals hit the same door within seconds of each other. That’s not a hypothetical edge case. Fire alarms get pulled during lockdowns, sometimes as a diversion and sometimes by accident, and lockdown protocols get triggered during unrelated fire events often enough that fire marshals bring it up unprompted.

Why separate system tests can miss critical conflicts

Here’s what typically happens on a K-12 capital project. The fire alarm contractor tests horns, strobes, and pull stations against NFPA 72 and signs an acceptance report. The access control integrator tests card readers, door position switches, and the lockdown trigger against its own commissioning checklist. The door hardware supplier confirms the electrified locks release on power loss and meet the required opening force. Every one of those tests passes.

What those tests don’t confirm is what the door does when the fire alarm and the lockdown signal are both active on it at the same time.

NFPA 4, Standard for Integrated Fire Protection and Life Safety System Testing, exists for exactly this kind of interaction. It requires end-to-end testing of the sequence between two or more interconnected systems, not just each system tested on its own, and it’s been picked up into the International Building Code since the 2018 edition for buildings with interconnected fire protection and life safety systems. The complication is that access control and lockdown systems are typically treated as security systems rather than life safety systems for the purpose of triggering that code section, so plenty of K-12 renovation and capital projects fall outside where NFPA 4 gets automatically enforced. Whether or not the authority having jurisdiction (AHJ) applies it, a district can still hold a project to that same standard by contract.

Making integrated testing a contractual requirement

This is why the problem surfaces at commissioning instead of getting caught earlier. Separate bid packages mean separate scopes, separate acceptance criteria, and contractors with no obligation to coordinate with each other. If integrated testing isn’t named as a deliverable somewhere in the RFP or capital project scope, responsibility for it doesn’t sit with anyone on the project. It only gets caught if someone on the project decides, on their own initiative, to check for it, and that’s not a safeguard a capital project should depend on. On a project with a fixed commissioning budget and several trades racing to close out, that’s too much to leave to chance.

Six requirements to include in a school safety RFP

A handful of additions to a bid package or capital project scope close most of this breakdown.

1. Name integrated testing as its own line item, separate from individual system acceptance. Reference the NFPA 4 framework even where the jurisdiction hasn’t formally adopted it for security systems. Holding a project to that discipline by contract works whether or not the code requires it.
2. Require a written sequence-of-operations matrix before construction starts. It should show, door by door and zone by zone, what happens under a fire alarm alone, a lockdown alone, and both together. If the design team can’t produce that matrix, the doors and their triggers haven’t been mapped out yet, and that won’t get worked out on-site during commissioning either.
3. Require simultaneous-activation testing as a condition of final acceptance. That means physically triggering a fire alarm and a lockdown signal together, watching what every affected door does, and documenting the result, not testing each system on its own separate schedule. Tie sign-off to substantial completion or final payment so it can’t get skipped when the schedule tightens.
4. Assign one party as the integrated testing authority. NFPA 3 and NFPA 4 both use this model, with someone independent of the individual trade contractors owning the cross-system test plan and signing off on the results. On most K-12 projects, that’s a commissioning agent or a third-party life safety consultant, not the fire alarm contractor or the access control integrator, since neither has full visibility into the other’s system by default.
5. Build in retesting triggers. Any future retrofit to door hardware, access control panels, or the fire alarm system should trigger a retest of the interaction, not just a retest of whatever component was touched. Systems installed years apart, by different contractors, on different budget cycles, are exactly where this kind of seam reopens quietly.
6. Fund it as its own line item. Integrated testing gets value-engineered out more often than almost anything else in a safety budget, mostly because it doesn’t map cleanly to one trade’s scope. Pricing it separately in the RFP keeps it from disappearing during budget cuts.