Clery Act Requirements in 2026: The October 1 Deadline and the Confirmation Gap Nobody Documents

Ask a campus security director what the Clery Act is and you will usually hear some version of the same answer: it is a reporting statute, the compliance office owns it, and it turns into a PDF every autumn. That answer is half right, and the half it gets wrong is the half with operational teeth.

Two of the Clery Act requirements have nothing to do with writing a report. They are live decisions, made under time pressure, by whoever is watching when something happens. The timely warning rule and the emergency notification rule both hinge on a judgment call that federal regulation demands but never explains how to make. And this year, the report those decisions feed carries something no Annual Security Report has ever carried before.

Featured image: a real IntelliSee detection frame showing unauthorized access on a covered exterior walkway at an institutional building after hours. The confidence score has been removed and the class label re-rendered for publication. IntelliSee does not use facial recognition and does not identify who a person is.

What the Clery Act requires in 2026

The Clery Act requirements fall into four buckets: an annual report, ongoing crime statistics, real-time warnings to the community, and a daily crime log. All four are tied to federal student aid eligibility, which is what gives them force. The statute sits at 20 U.S.C. 1092(f), and the operative detail lives in the Department of Education regulations at 34 CFR 668.46.

The reporting side is well understood on most campuses. An institution must prepare an Annual Security Report reflecting current policies, publish three years of statistics for a defined list of offenses, and distribute the whole thing by October 1. The list covers criminal homicide, sex offenses, robbery, aggravated assault, burglary, motor vehicle theft, and arson, plus arrests and disciplinary referrals for liquor, drug, and illegal weapons possession violations, plus hate crimes and the dating violence, domestic violence, and stalking categories added by the Violence Against Women Act.

What gets less attention is that two of these requirements are not annual at all. They fire in the moment.

Clery geography decides what counts

Clery geography is the rule that determines whether an incident belongs in your statistics, and it is the single most common source of underreporting. The regulation defines it in three parts for statistical purposes, and adds a fourth boundary for the crime log specifically. Institutions that map their camera coverage to their property deed rather than to Clery geography routinely miss the third category entirely.

A practical consequence: the pedestrian areas between buildings, the lots, the loading zones, and the covered walkways are almost always inside Clery geography, and they are almost always the areas with the thinnest live coverage. That gap is the same one described in our look at why higher education can no longer rely on passive surveillance.

Timely warning and emergency notification are not the same requirement

These are two separate obligations with two different triggers, and mixing them up is a documented compliance failure. A timely warning under 34 CFR 668.46(e) applies to Clery-reportable crimes that were reported to a campus security authority or local police and that the institution considers to represent a threat to students and employees. It is about patterns and continuing danger, and it must withhold victim identifying information.

An emergency notification under 34 CFR 668.46(g) applies to a significant emergency or dangerous situation involving an immediate threat to health or safety occurring on the campus. It covers more than crime. A gas leak, a fire, and a severe weather event all qualify.

The regulation resolves the overlap directly. If there is an immediate threat and the institution follows its emergency notification procedures, it is not separately required to issue a timely warning on the same circumstances, though it must provide adequate follow-up information to the community. The distinction between a detection event and the alert that follows it is the same problem we examined in the trigger gap between detection and mass notification.

The confirmation gap the regulation does not fill

The emergency notification rule turns on a single word, and that word is where campus security operations either work or fail. The regulation requires an institution to immediately notify the campus community "upon the confirmation of a significant emergency or dangerous situation." It further requires the institution to describe the process it will use to confirm that emergency, and to state that it will act without delay once confirmed.

Read that carefully. Federal regulation imposes the duty to confirm, requires you to document how you confirm, and then says nothing at all about how confirmation should actually happen. That is left to the institution.

In practice, confirmation usually means a person is dispatched to look. A call comes in, an officer drives or walks to the location, and the notification clock does not start until that officer reports back. On a large campus, that trip is the delay. It is also why so many after-action reviews find that the cameras were online, recording, and pointed at the right place the entire time, with nobody watching them.

IntelliSee layers onto the cameras an institution already owns, with no hardware replacement, and flags risks in real time: weapons, unauthorized access, loitering, crowd formation, vehicles in restricted areas, falls, slip risk, rooftop intrusion, and smoke or fire.

It does not use facial recognition and does not store or retain video, which matters on a campus where privacy expectations are high and where state law may add its own limits, as covered in our guide to video surveillance laws by state. The same video verification logic applies to false emergency calls, a problem we detailed in our analysis of how video verification closes the swatting detection gap.

What hazing statistics change about the October 1, 2026 report

The 2026 Annual Security Report is the first one that must include hazing statistics. The Stop Campus Hazing Act, signed into law on December 23, 2024, amended the Clery Act to add hazing as a reportable category. Institutions were expected to begin collecting hazing statistics on January 1, 2025, which means the report due October 1, 2026 carries calendar year 2025 hazing data.

Two related deadlines have already passed. Institutions needed a process for documenting hazing violations by July 1, 2025, and the first Campus Hazing Transparency Report, listing findings against student organizations, was due to be publicly available by December 23, 2025. The Clery Center summary of the Act lays out the sequence.

Worth noting for anyone checking the regulation itself: as of August 2026, the text of 34 CFR 668.46 has not yet been amended to reflect the hazing category. The statutory obligation exists regardless. Institutions should work from the Act and Department guidance rather than waiting for the regulation to catch up.

Clery Act compliance milestones leading to the October 1, 2026 Annual Security Report deadline. Built by IntelliSee from 34 CFR 668.41(e), 34 CFR 668.46, and the Department of Education civil penalty rule effective January 21, 2025.

What noncompliance costs

The maximum civil penalty for a Clery Act violation is $71,545 per violation as of August 2026. That figure took effect on January 21, 2025 under the Department of Education annual inflation adjustment, and it did not rise for 2026 because the government-wide penalty inflation adjustment for that year was cancelled.

Per violation is the phrase that matters. Department reviews typically identify multiple separate findings across multiple years, which is how Clery penalties reach seven figures. Fines are also not the whole exposure. The Department can impose heightened cash monitoring, provisional certification, or limitation and termination proceedings against Title IV participation, and a documented reporting failure becomes discoverable material in civil litigation over the same incident.

A compliance checklist to run before October 1

Most Clery findings trace to process gaps rather than bad faith. Run these seven checks while there is still time to correct them.

1. Re-map your Clery geography. Walk the current property list, including newly leased space and any recognized student organization housing, and confirm the public property boundary was drawn from the regulation rather than the deed.
2. Request local police statistics in writing. The regulation requires a reasonable, good-faith effort. If the agency does not respond, your written request is the record that protects you.
3. Verify hazing data for calendar year 2025. This is the first year it appears. Confirm who collected it, from which sources, and whether student conduct records were included.
4. Audit the daily crime log. Entries are due within two business days of the report. The most recent 60 days must be open to public inspection during normal business hours, and older portions produced within two business days of a request.
5. Test the emergency notification system and document it. The regulation requires at least one annual test, announced or unannounced, publicized in conjunction with the test.
6. Write down how you actually confirm an emergency. Name the roles, the tools, and the sequence. If the answer is that someone drives over to look, say so, then decide whether that is acceptable at your response distances.
7. Reconcile your campus security authority list. Advisors to student organizations, athletics staff, and residence life staff are frequently campus security authorities and frequently never told.

Frequently asked questions about Clery Act requirements

The report is the record. The response is the point.

The Annual Security Report is a backward-looking document. It tells your community what happened last year and what your policies say you will do. The part of the Clery Act requirements that determines whether next year’s report describes an incident or a near miss is the part that runs in real time: whether anyone confirms a developing situation fast enough for the notification to matter.

That is the gap IntelliSee was built to close. Turning passive cameras into proactive protectors does not change what you have to file. It changes what there is to file about.

Campus safety technology is often eligible for federal and state funding. Start with our guide to security grant funding to see which programs fit your institution, then talk with our team about layering real-time detection onto the cameras your campus already has.