The Incident Record That Protects Students, Staff and the University

An incident report serves several purposes at once: immediate continuity, resident support, statutory or regulatory reporting, internal review and later accountability. Trying to write it as a legal defence usually makes it worse. The writer should record the truth clearly and let authorised investigators assess it.

The report must also respect privacy. Collecting every rumour, screenshot or medical detail ‘just in case’ increases harm and creates a larger information-security risk.

The minimum reliable chronology

• Date, time and precise location.
• How the matter came to attention and who first reported it.
• Observable conditions and exact words where materially important.
• Immediate safety and medical action.
• People and authorities notified, including attempts without response.
• Handover, unresolved risks and next update time.

Separate fact, statement and assessment

‘The student was intoxicated’ is a conclusion. ‘The student was unsteady, speech was unclear and a bottle was present’ records observations. Attribute statements to the speaker and identify professional assessments by the qualified person who made them. Avoid moral labels, sarcasm and irrelevant character history.

Correct without concealing

If an honest error is found, preserve the original entry and add a dated correction explaining what changed and why. Never overwrite the chronology silently. A system audit trail should show creation, access, export and amendment where the sensitivity justifies it.

Evidence and personal devices

• Use an authorised upload or secure handover route.
• Do not keep copies on personal phones or personal cloud storage.
• Preserve the original file, source and available metadata.
• Limit access to people with a genuine role in response or review.
• Do not circulate distressing images in operational chat groups.

Closure is part of the record

Record who verified the corrective action, what support was offered, whether a mandatory report or committee referral was completed, and what system learning was assigned. Closing a ticket is not the same as resolving risk.

Conclusion

A strong record does not protect an institution by hiding weakness. It protects everyone by preserving a dependable account, enabling timely care and making unfinished responsibility visible.

Official references