NEWRecognition module — recognise hard work and the people going above and beyond
SecureOptixSecurity workforce software
Operations8 September 2026 · 3 min read · Updated 27 September 2026

Recording conflict and use of force properly

Incidents involving physical intervention are the ones most likely to be examined afterwards — by a client, an insurer, a regulator, or in proceedings — and they are also the ones written up in the worst conditions: at the end of a long shift, by somebody with adrenaline still in their system, who would rather go home.

Observation and conclusion are different things

The most common weakness in these reports is recording judgements as facts. "He was aggressive" is a conclusion. "He moved towards me with a raised hand and shouted" is an observation, and it is what allows a reader years later to form their own view rather than being asked to accept somebody else's.

That distinction sounds academic and is the single thing most likely to determine whether a report supports a contractor's position or undermines it. Officers can be trained on it in an hour and very few are, because report writing is treated as administration rather than as a skill with consequences.

Timing and sequence carry the weight

What happened, in what order, at what times, and what the officer did at each point. Reports written as a narrative summary lose the sequence, and the sequence is what questions afterwards are about — when did you first ask him to leave, how long between that and the intervention, when did you call.

Contemporaneous notes, even rough ones with times against them, are what make a later report credible. A polished account written the following morning with no underlying notes is weaker than untidy notes written at the time, however much better it reads.

The training record is part of the evidence

Where an intervention is examined, one of the questions is what the officer was trained to do. A contractor that can produce dated training records showing what conflict management the officer had received, and when, is in a materially different position from one relying on the fact that training generally happens.

In practice: the report that read badly and described a reasonable act

An officer removes somebody from a site entirely properly. The report, written at shift end, says the person was "being aggressive and refusing to leave so I removed him". Fourteen words covering roughly four minutes.

The act was reasonable. The record supported almost nothing about it — no sequence, no times, no account of what was said or attempted first, and a conclusion where the observations should have been. Everything that would have helped was in the officer's memory and never written down.

Common mistakes

  • Recording conclusions about behaviour rather than observations
  • Writing up at shift end with no contemporaneous notes
  • No times against events, so the sequence cannot be reconstructed
  • Omitting what was attempted before the intervention
  • No record of who was notified and when
  • No dated training record to show what the officer was trained to do

One practical test: read one report for conclusions

Take a recent report involving physical intervention and underline every statement that is a conclusion rather than an observation — "aggressive", "threatening", "refused to comply".

Most reports are largely underlined, and each phrase is a judgement the reader is being asked to accept rather than reach. Replacing them with what was seen and heard is a skill officers can be taught in an hour, and almost nobody is, because report writing is treated as administration.

  • Record observations, not conclusions about behaviour
  • Put times against events so the sequence is reconstructable
  • Record what was attempted before the intervention
  • Keep contemporaneous notes, however rough
  • Hold dated training records showing what the officer was trained to do

Worth adding: debrief before anybody goes home

A five-minute conversation with a supervisor immediately after an intervention captures far more than a report written alone at shift end. It prompts the sequence, surfaces what was attempted first, and produces a second contemporaneous account from somebody who was not in the incident.

It also catches the officer who is more affected than they are letting on, which matters for reasons beyond the paperwork.

Key takeaways

  • Record what was observed, not what was concluded from it.
  • Times and sequence are what questions afterwards are actually about.
  • Rough contemporaneous notes beat a polished account written the next day.
  • Record what was attempted before the intervention, not just the intervention.
  • Dated training records are part of the evidence for any intervention.

The SecureOptix team

Written by people who work daily with security contractors on SIA licensing, screening and the records that hold up under an inspection.