Private by design. This report is built entirely in your browser and kept in memory only. Nothing is saved, sent, logged or tracked, and this page loads no chat or analytics scripts. Closing or refreshing the page clears an unsaved report, so copy or print it when you are done.
What makes a report usable
- Chronological and timed. One line per event, each with a time. If you did not note the time, say so rather than guessing.
- First-hand and attributed. What you saw and heard is your evidence. What someone else told you is theirs: name them and keep their words in quotes.
- Specific, not labelled. "He struck the counter twice with his right hand and shouted, 'Let me in'" can be tested against CCTV. "He was aggressive" cannot.
- Complete. Actions you took, who you notified and when, the outcome, and where any evidence is: camera numbers, photographs, body-worn video, incident numbers.
- Nothing invented. The builder only writes what you enter. An empty witnesses box produces no witnesses line, because "there were no witnesses" is itself a claim you would have to stand behind.
The witness statement unit of the Door Supervisor course and Security Guard course uses the same approach; our practical assessments guide explains what the assessor looks for.
FAQ
What should a security incident report include?
Date, time, location, who wrote it, a timed account of what the writer personally saw and did, anything reported by others with their names, people notified, witnesses and references, and the outcome. Keep opinion out.
Is this a UK incident report template?
Yes. The format follows what UK security companies, venues and the police expect from door supervisors, security officers and CCTV operators, and it matches the evidential statement taught on SIA courses.
Does the report leave my phone?
No. It is generated in your browser and held in memory until you copy, print or clear it. This page does not load chat, analytics or any other third-party script.
How do I record an event after midnight?
Set the entry's day to "Next day" and the report writes the following date next to the time, so 00:10 is not read as the start of the shift.