Priority Conflict Between Fire Alarm and Mass Notification

Priority comes from the risk analysis and the emergency response plan, not from habit. The district's own hazard analysis ranks tornado as the top event, and a tornado warning can arrive with minutes of lead time while a fire alarm is already sounding. If the fire alarm is permanently top priority, the district cannot deliver the message that the analysis says matters most.

Proposed hierarchy:

1. Imminent-threat mass notification (tornado warning, active threat, shelter-in-place, evacuation of the whole campus) - per the risk analysis.
2. Fire alarm and evacuation signaling from any building.
3. Lower-priority mass notification (weather watches, utility notices, scheduled announcements).
4. Administrative paging, athletics, and public address.

The conditions that make overriding the fire alarm defensible:

• The override is time-limited and the fire alarm message resumes automatically when it ends, without an operator action.
• The override is logged as an event with the originating device and the authorizing user.
• Only designated roles can invoke a priority-1 message, and the designation is written in the emergency response plan.
• The specific precedence is documented and accepted by the AHJ, not invented by the integrator.

Where the district's instinct is right: a coach with a handset must never outrank a fire evacuation. The failure in the drill was not that the hierarchy allowed an override - it was that a low-priority paging source had no priority class assigned at all and simply keyed over whatever was playing.

Priority must live in the system, not in the operator's reflexes. Every audio source - every handset, every pre-recorded message, every remote initiator - must be assigned a priority class in the system programming, and the system must arbitrate automatically: a higher-priority message preempts lower-priority audio on the same speakers, the preempted message either queues and resumes or is terminated per the plan, and the preemption is recorded. Anything a human keys manually without a priority class is a latent defect; the drill exposed one, it did not create one.

Practical consequences:

• Locker room and coaching handsets get the lowest class, or are removed from the system and given a separate intercom.
• Paging zones at the stadium are restricted so a page cannot blanket the stadium during an event without a priority decision.
• Audio routing, not just message selection, has to honor the hierarchy - a priority-1 message must reach speakers currently in use by a priority-4 page.

The missing log entry is the more serious finding. An activation from a laptop that does not appear in the event log almost certainly terminated in a separate network appliance or notification gateway rather than in the listed control unit. That means the activation was never a fire alarm or emergency communication system event at all - it was a software instruction with no annunciation, no supervision, and no record. Remediation: all emergency initiations, including remote ones, must terminate in the listed control unit and appear in a time-stamped, protected event log with the originating device and user identity. Review who holds credentials for the remote initiation path and revoke those that are not on the district's authorized list.

Intelligibility is a measured acceptance criterion, and 0.38 does not meet it. Do not average it away against passing locations elsewhere in the building - the concourse fails, and the concourse is where students congregate.

Diagnose before adding speakers:

• Check tap settings and loudspeaker spacing against the design; a concourse with high hard ceilings and glass frequently needs more, lower-level, or differently aimed loudspeakers rather than more power.
• Measure background noise at the survey positions; a cafeteria during lunch may be 75 dBA or higher, and a system designed for an empty room will fail when occupied.
• Check delay and equalization settings in the distributed system, and look for reverberation time problems that need acoustic treatment, which is an architectural fix rather than an audio one.
• Re-test at the same twelve or more positions with a calibrated meter, both empty and occupied, and report the method and instrument.

On the all-call button: a single unsupervised button that can launch any message in any building, from a press box, is an accidental-activation and misconfiguration risk - and the outdoor array is loud enough to be a hazard on its own. Offer instead: a supervised activation device with a confirmation step, message selection restricted to pre-approved scenarios rather than arbitrary selection, role-based credentials, and full logging of who activated what, when, and from where. If the district wants speed at the press box during an event, the right design is one button for one pre-defined stadium evacuation message, not one button for everything.