UA
Emergency Notification Procedure
The University of Arizona's Emergency Notification Procedure is the operational layer under its Emergency Notification and Timely Warning Policy: it restricts UAlert sending to a named roster of Authorized Users designated by the Chief Safety Officer, audits that roster at least twice a year, and defines campus-location segments for Greater Phoenix and Sierra Vista.
Read the official policy~53,000 studentsUAlert
In the policy’s own words
What the policy says
Closed roster of Authorized Usersverbatim
To ensure the integrity of the Emergency Notification System (ENS), a limited number of individuals, known as Authorized Users, are permitted to send Emergency Notifications.
- States system integrity, not convenience, as the reason for the closed operator roster.
Campus-location segmentsverbatim
Authorized Users may send Emergency Notifications to all Campus Community members registered to receive Emergency Notifications or to the segment affiliated with a specific campus location: Greater Phoenix and/or Sierra Vista.
- Defines geographic segmentation inside the procedure, so a Sierra Vista incident need not alert Tucson.
Roster audit cadenceverbatim
The Authorized Users list is audited and updated at least twice annually.
- A maintenance commitment for the operator roster itself, distinct from testing the notification system.
At a glance
How this policy works
- When it activates
- An Emergency Notification is sent when an authorized official confirms significant evidence of an emergency or dangerous situation that could jeopardize the health or safety of students or employees; confirmation does not require near certainty that an emergency exists.
- Who decides
- Only Authorized Users designated by the Chief Safety Officer may send: UAPD Chief of Police, Deputy Chief, Lieutenant, Dispatch Supervisor, and Communications Unit for all campuses, plus local senders for Greater Phoenix (Associate Vice President of Planning and Operations, Emergency Preparedness Planner) and Sierra Vista (Senior Campus Administrator); UAPD 911 dispatchers may initiate UAlert messages upon confirming an immediate threat.
- Timeliness standard
- Activation follows confirmation of an immediate threat; the 2024 dispatcher authorization moves initiation to the 911 desk so a confirmed threat can be alerted without escalation delay.
- Emergency notification vs. timely warning
- The procedure is the operational implementation of the university's Emergency Notification and Timely Warning Policy, covering the emergency-notification half; timely warnings run through the policy and the Annual Security Report process documented separately in this archive.
- Scope & limits
- Notifications can go to all registered Campus Community members or to the segment affiliated with a specific campus location, with Greater Phoenix and Sierra Vista defined as separate segments; the Authorized Users list is audited and updated at least twice annually.
ChannelsSmsEmailPhone Call
Analysis
Reading the policy
The University of Arizona separates its alerting rules into a policy and a procedure, and publishes both: the Emergency Notification and Timely Warning Policy states the institutional commitments, while the Emergency Notification Procedure, maintained by the Office of Public Safety, governs how UAlert activations actually happen. This archive already holds the university's Annual-Security-Report-level policy statement as a separate entry; this entry documents the procedure itself.
The procedure's core mechanism is a closed operator roster. To protect the integrity of the Emergency Notification System, only a limited set of Authorized Users, employees designated by the Chief Safety Officer, may send Emergency Notifications. For all campuses those users sit inside the police department: the UAPD Chief of Police, Deputy Chief, Lieutenant, Dispatch Supervisor, and Communications Unit. Two distant-campus segments get local senders: the Associate Vice President of Planning and Operations and the Emergency Preparedness Planner for Greater Phoenix, and the Senior Campus Administrator for Sierra Vista, who can send localized notifications to their segment without involving Tucson. The roster is audited and updated at least twice annually, a maintenance discipline most published procedures leave unstated.
The procedure's confirmation standard is deliberately practical: confirmation means an authorized official has verified significant evidence of an emergency or dangerous situation, not near certainty that an emergency exists. In a 2024 enhancement announced by UAPD, 911 dispatchers themselves were authorized to initiate UAlert messages upon confirming an immediate threat to the health or safety of the campus community, collapsing the gap between call-taking and activation that has produced delayed first alerts elsewhere in this archive.
Because arizona.edu hosts are not reachable from this research environment (automated fetches are blocked), the passages quoted below are reconstructed from search-engine-indexed extracts of the procedure page and the university's announcements rather than a firsthand line-by-line read, so every excerpt is marked isVerbatimConfirmed: false and confidence is held at medium even though the extracts present as close quotations.
Takeaways
Key findings
UAlert sending is restricted to a named roster of Authorized Users designated by the Chief Safety Officer, concentrated in UAPD roles, and the roster is audited at least twice a year.
Greater Phoenix and Sierra Vista are defined notification segments with their own local authorized senders.
The confirmation standard requires verified significant evidence, explicitly not near certainty, before an Emergency Notification is sent.
Since 2024, UAPD 911 dispatchers may themselves initiate UAlert messages upon confirming an immediate threat, removing an escalation step between call-taking and activation.
Policy, meet practice
When this system actually fired
44 documented times UA’s alert system was used, from the case archive.
Provenance
Sources
- Official
- Official
- Statement
- Student Paper
Tags
policysopemergency-notificationens-activationauthorized-usersarizonapublic-r1ualertdispatcher-authorization
Added 2026-08-23Updated 2026-09-14Via ingestion