A useful incident report is not just a record that something happened. It is a professional account that helps other people understand what happened, what action was taken, and what may need to happen next.
For healthcare security officers, that matters because incidents often sit at the point where safety, care, risk, and accountability meet. A good report can support patients, staff, supervisors, and wider site learning.
Keep the report factual
Start with what you saw, heard, did, and were told. Avoid adding motive, emotion, or assumptions unless they are clearly attributed.
For example, instead of writing that someone was “aggressive for no reason”, describe the observable behaviour: raised voice, clenched fists, threats made, refusal to leave, or movement towards staff.
Record actions and outcomes
A report should make it clear what security did in response. Include reasonable details such as who attended, what was said, what instructions were given, whether clinical staff were updated, and how the incident ended.
Write for the next reader
The next person reading the report may not know the ward, the people involved, or the pressure of the moment. Clear structure helps them follow the event without guessing.
