Independent guide
Classify the incident, meet the reporting duty, keep the evidence
The Incident Ledger is an independent guide to campus safety compliance in higher education, written for the people who keep the ledger: compliance officers, campus safety teams, CSA coordinators, housing staff and administrators. It follows one backbone through every guide: incident, location, category, reporting obligation, warning, investigation, annual disclosure, evidence.
That is deliberately different from a general campus safety blog, which tells readers how to stay safe. This site explains the compliance job: what must be classified, reported, warned about, disclosed and filed, and how an auditor checks it afterwards. Start with the Clery Act, explained for colleges, or open a ledger below. Every guide opens with an incident ledger card: the subject, the decision it supports, the evidence level and the first move.
This site is not a reporting channel and not an emergency service. If someone is in danger now, contact campus security or local emergency services immediately, and report an incident through your institution's own channels, not through this site.
Walk the ledgers
From the notice board
Where to start, and where to check the record
- Start with the Clery Act, explained for colleges, the ledger guide for the whole site.
- Browse all 302 guides A-Z when you know the duty you need to check.
- Read the corrections page for what has changed and why, and the sources page for the statute, regulation and official guidance behind the guides.
How this desk works
How an incident becomes a statistic
Three rules. First, no invented figures and no determination for a specific incident: this site publishes no case studies of its own and never says how a particular incident must be classified, because a guide cannot examine a report it has never seen. Where a number appears, it comes from an official source, is attributed, and carries the date it was checked; worked examples use round numbers and are labelled illustrations. Second, the backbone is kept in order throughout, because skipping geography to reach a warning, or skipping classification to reach a statistic, is how ledgers go wrong. Third, corrections are published, not buried: the corrections page records what changed and why. The desk's position throughout: a statistic is trustworthy only when the incident was classified by definition, placed by geography, warned about by threat, and filed so the whole chain can be checked.

Browse the whole site in the 20 ledgers, or search the full list in all guides A-Z.