Clery Act Emergency Notifications: What Colleges Send
The Clery Act is the federal law that requires colleges and universities participating in federal student aid programs to disclose campus crime information and, critically for communication teams, to warn their campus communities about threats. Two distinct obligations do that warning work: the timely warning, for Clery-reportable crimes that represent an ongoing threat, and the emergency notification, for significant emergencies or dangerous situations involving an immediate threat to health or safety. Institutions that blur the two, or that treat alerting as a technology purchase rather than a policy obligation, discover the difference during federal program reviews. This guide explains both requirements in plain language, where they come from, and how campuses operationalize them. It is general information, not legal advice.
Key takeaways:
- The Clery Act is codified at 20 USC 1092(f), with implementing regulations at 34 CFR 668.46, and is administered by the U.S. Department of Education.
- Timely warnings cover Clery-reportable crimes posing a serious or continuing threat; emergency notifications cover immediate threats to health or safety, including non-crime events like fires, chemical spills, and severe weather.
- Emergency notifications must be issued immediately upon confirmation of a dangerous situation, with content and delivery decided without delay, subject only to a narrow exception where notification would compound the emergency.
- Institutions must publish their notification procedures in the Annual Security Report and test them at least annually.
- The law requires effective reach, which in practice means layered channels with SMS at the core, since text is the channel students actually see in minutes.
Where the obligations come from
The Jeanne Clery Disclosure of Campus Security Policy and Campus Crime Statistics Act, enacted in 1990 and amended repeatedly since, conditions participation in federal student aid under Title IV of the Higher Education Act on a set of campus safety duties. The statute lives at 20 USC 1092(f); the operative regulations at 34 CFR 668.46 spell out the requirements institutions actually implement. The Department of Education enforces the law through program reviews and civil fines, with per-violation fine amounts adjusted over time by inflation rules, and its Clery handbook guidance shapes day-to-day compliance practice.
Three communication-related duties matter most:
- Timely warnings under 34 CFR 668.46(e).
- Emergency notification under 34 CFR 668.46(g).
- Publication and testing of these policies in the Annual Security Report, including annual tests of emergency response and notification procedures.
Timely warning vs. emergency notification: the distinction that decides everything
The two alerts answer different questions, and institutions need operational fluency in both:
| Dimension | Timely warning | Emergency notification |
|---|---|---|
| Trigger | Clery-reportable crime (e.g., certain offenses in Clery geography) considered a serious or continuing threat | Significant emergency or dangerous situation involving an immediate threat to health or safety |
| Scope of events | Crimes only | Crimes and non-crimes: fire, gas leak, disease outbreak, severe weather, active threat |
| Timing standard | As soon as pertinent information is available | Immediately upon confirmation |
| Audience | Campus community | The segment(s) of campus affected, which may be everyone |
| Purpose | Enable people to protect themselves from a continuing crime threat | Enable immediate protective action |
A useful compression: timely warnings look backward at a crime that may continue; emergency notifications look at a danger happening now. The regulation also provides that when an emergency notification is issued, a separate timely warning for the same circumstances is not required.
The emergency notification duty carries the sharpest operational language: institutions must, without delay and taking into account the safety of the community, determine the content of the notification and initiate the system, unless issuing it would compromise efforts to assist a victim or to contain, respond to, or otherwise mitigate the emergency. That narrow exception is the only sanctioned reason to hold an alert.
What the regulation requires your procedures to include
Under 34 CFR 668.46(g), an institution's emergency notification procedures must include:
- Confirmation process: how the institution confirms a significant emergency exists, and who does it.
- Audience determination: who decides which segments of the campus receive the notification.
- Content determination: who drafts and approves what the alert says.
- Initiation: who has authority to trigger the system, at any hour.
- Larger-community dissemination: procedures for informing the surrounding community where appropriate.
- Annual testing: at least one test per calendar year, which may be announced or unannounced, with documentation of each test including date, time, and whether it was announced.
Every element names a decision and a decision-maker, which is the regulation's quiet insight: alerting failures are usually authority failures, not technology failures. The institution that needs three phone calls to approve a message has a compliance gap no software fixes.
Why SMS anchors the channel stack
The regulation does not mandate a specific technology; it mandates a system that actually notifies. In practice, campuses layer channels, sirens, email, apps, digital signage, social media, web banners, and SMS, and text messaging carries the core load for a simple reason: it is the only channel on this list that most students, faculty, and staff see within minutes without having opted into an app or being near a speaker.
The operational requirements for the SMS layer:
- Enrollment coverage. Registration-time capture of mobile numbers, with policies favoring automatic enrollment and clear opt-out records, because an alert list missing half the campus is a paper system.
- Speed at scale. Delivery infrastructure that can push to an entire campus population quickly, with registered high-throughput sending.
- Segmentation. The regulation contemplates notifying affected segments; the platform must target a building, a campus, or everyone.
- Templates and authority. Pre-approved message templates for foreseeable scenarios, mapped to the initiation authority the policy names, so confirmation-to-send is minutes.
- Testing and logs. Annual tests are mandatory; delivery logs and timestamps are the evidence of a working system, for both program reviews and after-action improvement.
These are the same architectural requirements covered in our guides to campus emergency alert systems and mass notification for schools.
Beyond the siren: two-way and follow-through
The regulation defines the floor: get the warning out. Well-run programs build past it, because real emergencies are conversations, not announcements:
- Follow-up and all-clear messages keep the community oriented as situations evolve.
- Inbound handling matters more than planners expect: an alert triggers a wave of replies and questions. An AI Powered Helper can field the routine ones, where do I go, is the library affected, when is the next update, from approved emergency content, while anything indicating danger or a person in distress escalates to safety staff immediately.
- Routine use builds emergency reach. A number students already text about ordinary campus life is one they trust in a crisis, which argues for running emergency and everyday campus messaging on one governed platform, the model described on our higher education solutions page.
FRANSiS supports this layered model: campus-scale alerting, segmentation, template governance, delivery logging, and two-way handling with escalation, alongside the daily communication that keeps enrollment data fresh.
Frequently asked questions
What does the Clery Act require for emergency notifications?
Under 34 CFR 668.46(g), institutions must immediately notify the campus community upon confirmation of a significant emergency or dangerous situation involving an immediate threat to health or safety, with documented procedures covering confirmation, audience, content, initiation authority, community dissemination, and at least annual testing.
What is the difference between a timely warning and an emergency notification?
Timely warnings respond to Clery-reportable crimes that pose a serious or continuing threat and must go out as soon as pertinent information is available. Emergency notifications respond to immediate threats, including non-crime emergencies, and must be initiated immediately upon confirmation. An emergency notification about a situation removes the need for a duplicate timely warning.
Can a college delay an emergency notification?
Only under the regulation's narrow exception: when issuing it would compromise efforts to assist a victim or to contain, respond to, or mitigate the emergency. Administrative convenience, reputational worry, and approval bottlenecks are not sanctioned reasons, which is why initiation authority must be settled in advance.
Does the Clery Act require text message alerts specifically?
No specific technology is mandated; the duty is an effective notification system with documented, tested procedures. In practice, SMS anchors compliant systems because it reaches the campus population fastest without requiring app installation, supplemented by email, sirens, signage, and other layers.
How often must emergency notification systems be tested?
At least annually, through tests that may be announced or unannounced, with documentation of each test's date, time, and nature, and with procedures publicized in connection with at least one test per year. Delivery logs from real platforms turn this obligation into ordinary recordkeeping.
Conclusion
The Clery Act's notification rules reward institutions that decide everything decidable in advance: who confirms, who targets, who drafts, who sends, and through what channels, leaving only the emergency itself to be new. Build the authority map, anchor the stack on SMS with layered redundancy, test on the calendar and log the evidence, and the regulation becomes what it was meant to be: a floor under a campus that already communicates well.
Reviewing your campus notification readiness? Contact the FRANSiS team to see campus-scale emergency texting with segmentation, delivery logs, template governance, and an AI Powered Helper that handles the inbound surge when it matters most.
