Skip to content

Insights , 5 min read

How to write a security incident report

How to write a security incident report that is clear, factual and useful: what to include, what to leave out, and why the record matters after the shift.

Kingpin Security
A person writing in a small spiral notebook at a desk, with a laptop and phone alongside

Knowing how to write a security incident report is part of the job, not an afterthought. A good report is a clear, contemporaneous record of what you saw, what you did, and what happened next. It may be read by a duty manager, a client, an insurer, a licensing officer or the police. It may also be the only reliable account of a night that several people remember differently a week later. This is practical guidance for officers and supervisors in the UK. It is not legal advice. Follow your employer's reporting procedure and current official guidance.

We provide manned and door services from Holmes Chapel across the North West. Our officers are SIA licensed and screened to BS 7858. We expect reports to be written in the same calm, factual voice we use on a door or a gatehouse.

Write it while it is still clear

The best report is written as soon as you can do so safely, using notes taken at the time. Memory fades, conversations blur, and times slip. A pocket notebook, a radio log and CCTV timestamps are more useful than a long write-up completed from memory the next afternoon. If you were involved in a refusal, an ejection, first aid, a theft, a use of force, or a welfare concern, do not leave the site without a record.

Official SIA training on physical intervention and ejections treats reporting as part of the professional process, not as paperwork you can skip because the night went quietly after the incident. If force was used, the record should be particularly careful, and should sit alongside any review your employer requires.

How to write a security incident report that holds up

Use the form your employer provides if there is one. If you are writing in a notebook or a blank report, the following headings keep the account usable:

  • Date, start and end times of the incident, and the exact location.
  • Your name, licence number if required, and the names of other officers or staff who were present.
  • Who else was involved, described carefully: a name if you have it, or a factual description if you do not.
  • What you saw and heard, in order, without speculation.
  • What you said and did, including any warning, request to leave, first aid, or call to the police.
  • The outcome: left voluntarily, ejected, arrested, treated, or declined help.
  • Any injuries, damage or property, and what happened to them.
  • CCTV, body-worn video, or other records, and where they can be found.
  • Witnesses, and whether a statement was taken.

Write in the first person for your own actions, and keep sentences short. "I asked him to leave at 23:16. He walked to the exit with Officer B" is better than "the subject was then removed from the premises in the usual way". Give times. If you do not know an exact time, say so, and use the radio or CCTV to check.

What to leave out

Leave out opinions dressed as fact, jokes, slang, and guesses about what someone intended. Do not diagnose someone as "on drugs" if what you can actually report is slurred speech, a smell of alcohol, or a statement they made. Do not copy a colleague's wording if it is not what you saw. Do not include personal data you do not need, and follow your employer's rules on how reports are stored. If you inspected ID, record that you did so, and remember that official SIA guidance says there is no power to seize an identification document.

For an illustrative example, imagine a warehouse officer who finds a fire exit wedged open at 02:40. The report notes the time, the exact door, that a small wooden wedge was in place, that the area was searched, that the wedge was removed, and that the duty manager was told at 02:47. It does not claim a theft that was not observed. That is an illustrative example, not a real incident. The value of the report is the precision.

After you have written it

Read the report once, correct spelling that would confuse a reader, and do not tidy the facts to make the night look neater. Sign and date it, or submit it in the system your employer uses. If the police attended, make sure your account can be given clearly at the time and in writing afterwards. If CCTV is relevant, say which camera and roughly which time, so someone else can find the footage before it is overwritten.

If you would like a security team that treats reports as part of the service, request a quote or contact us. Officers who are new to the door may also find our notes on refusals and first shifts useful, alongside official SIA training material.

Frequently asked questions

When do I need to write a security incident report?

Follow your employer's procedure. As a rule, write a report for refusals that may be disputed, ejections, first aid, crime, welfare concerns, property damage, and any use of force. Write it as soon as you can do so safely.

Should I write in the first person?

Yes, for your own actions. It is clearer, and it stops the report sliding into vague language about what "we" or "staff" did.

Can I include my opinion about what happened?

Stick to what you saw, heard and did. If you need to record a concern, label it as a concern, not as a fact. Opinions about character or motive usually weaken a report.

How long should the report be?

Long enough to let a reader who was not there understand the sequence, the times and the outcome, and no longer. A short, complete report is more useful than a dramatic one.

Free, no-obligation quote

Protection, priced in minutes.

Tell us what you need protecting. You will see an indicative price instantly and a specialist will confirm a tailored proposal, usually the same day.

SIA-licensed officers Free site survey 24/7 operations desk
Or call 0800 099 6449
Call 24/7 Instant quote