Incident documentation for Clery reporting

In short, incident documentation combines a legal definition, an institutional procedure, and a public record, and all three must agree.

For incident documentation, the definition is the starting point and the finishing point: start with it, decide with it, and file the note that shows it was used. For incident documentation, the duty extends to places and people the institution might prefer to forget, and the ledger must include them anyway.

The history of incident documentation matters because guidance has been revised over the years, and a practice that was acceptable a decade ago may no longer match the current regulation. The best time to fix a weakness in incident documentation is before the annual report is assembled, when a correction is a note, rather than after publication, when it is a public correction. Institutions that do incident documentation well tend to talk about it in ordinary language, while institutions that struggle tend to hide behind jargon.

For incident documentation, senior leadership needs a summary, not the raw file, but the summary must be reconcilable to the file, or it is a story rather than a report. The registrar's data can affect incident documentation in unexpected ways, for example through enrolment records that establish who counts as a student. The parents and families of students read the published outcome of incident documentation with particular attention, and the file behind it should be able to withstand that attention.

For incident documentation, the most important training may be for the people who never expected to be involved, because reports find them anyway. The human side of incident documentation is easy to lose behind the ledger, and a good file remembers that every entry began as a person reporting something that mattered to them.

Finally, for incident documentation, the method is only as good as its last use, so review the method itself once a year against the cases it handled and the findings it produced. A method for incident documentation that depends on one person's memory will fail on their first holiday, so write the method down and train a deputy to follow it. For incident documentation, the order of operations matters: intake, definition, decision, warning or disclosure, filing, and only then publication, in that order.

For incident documentation, the warning decision and the classification decision are separate decisions, and the file should show each one with its own reason, even when they are made by the same person. When incident documentation is decided under time pressure, the steps do not shorten, but the note can: a short note written now beats a perfect note promised for later.

Another mistake in incident documentation is to treat a branch campus, a study abroad site, or a clinical placement as if it shared the main campus geography, when each needs its own analysis. In incident documentation, the error of the vague policy is common: a statement so general that staff cannot tell what to do in a specific case. For incident documentation, a frequent mistake is to treat a branch campus as an extension of the main campus in the tables, when the regulation treats it separately.

In incident documentation, the error of the overlong note is real: a note so long that the decision hides inside it, and a reviewer cannot find the reason. Another recurring mistake in incident documentation is to ignore the fire side of the ledger entirely, as if crime statistics were the whole report, when fire statistics have their own log and tables.

The index for incident documentation should be kept current, because an index that lags the files by months is an index that misleads. For incident documentation, redaction should be recorded as well: what was redacted, why, and who authorised it, so that a redacted file is still an auditable file. For incident documentation, the evidence file for the annual report should be built through the year, so that publication is an assembly task, not a reconstruction.

When incident documentation is handled at a branch campus, the file should live where the branch campus reviewer will look for it, and a copy or a clear pointer should exist centrally. For incident documentation, the institution's retention schedule should be published internally where the people who file can actually consult it, not held only by one office.

The next move on incident documentation is to test the notification system, if it has not been tested in the current cycle, and to file the test. The next move on incident documentation is to note the checking date on this guide and to set a reminder to re-read it when the regulation changes. The next move on incident documentation is to review the last warning or notification decision and to test its reasoning against a review.

The next move on incident documentation is to check that the file for the last case is findable by someone other than the person who filed it, by asking them to find it. Finally, the next move on incident documentation is to remember the boundary: this site explains duties in general terms, decides no specific incident, and never replaces the institution's own channels in an emergency.