Security guard report writing is the practice of recording what an officer saw, did and handed over in plain, factual, time-stamped language that another person can rely on months later. The examples below show the same event written badly and then written well, so the difference is visible rather than theoretical.
The best security guard report writing examples are not the longest ones. Most report writing goes wrong in the same small way. The officer was there, the officer dealt with it, and then the officer wrote “checked area, all ok.” Nothing in that line is untrue. It is also worth nothing when a client asks what happened at 03:40 on the fourteenth, or when a manager is trying to work out why a door was unlocked for six hours.
Report writing is not about longer reports. It is about writing entries that still answer questions after everyone has forgotten the shift. This guide gives security guard report writing examples – weak entries rewritten into strong ones – the six rules behind each rewrite, and the mistakes that make an otherwise diligent officer look careless on paper.
Why report writing quality matters more than report volume
Before the security guard report writing examples themselves, it is worth being clear who a report is actually for. A shift report has three audiences and the officer writing it is none of them.
The first is the incoming officer, who needs to know what is still open. The second is the supervisor or client, who reads a week of entries looking for patterns. The third is whoever reads it under pressure – an insurer, a lawyer, an investigator – usually long after the event, with no way to ask a follow-up question.
That third audience is why vague entries are expensive. “Dealt with intruder” cannot be defended, explained or built on.
Compare it with this. “23:14 – observed male, approx 30s, dark jacket, attempting rear fire door. Challenged from 5m. Male left north towards car park. Door checked and secure at 23:19. Photographed door. Control informed 23:20.” can be. Same event, same officer, same amount of time to write. One holds up and one does not.
The six rules behind every good entry
Every rewrite in the security guard report writing examples below applies the same six rules.
- Time everything. Every observation and every action gets a clock time, not “later” or “during the shift.”
- Write what you observed, not what you concluded. “Male appeared intoxicated” is a conclusion. “Male unsteady on feet, slurred speech, smell of alcohol” is an observation. Record the observation and let the conclusion follow from it.
- Be specific about people, places and things. A location name, a door number, a vehicle colour and partial plate, a description. “Rear car park, bay 14” beats “outside.”
- Record the action you took, not just the event. What you did, when you did it, who you told.
- Close the loop or say it is open. Either the matter was resolved and how, or it was handed over and to whom.
- Keep it plain. Short sentences, no jargon, no attempt at formal register. “I proceeded to the aforementioned location” is not more professional than “I went to the loading bay.”
Security guard report writing examples
Each of the security guard report writing examples below shows the same event twice: the entry an officer typically writes at the end of a long shift, and the entry that still answers questions a year later. Read the weak line first and note what a reader would have to guess.
Example 1: a routine patrol entry
Weak: Patrolled building, all clear.
Strong: 02:00 to 02:26 – patrol of levels 1 to 3 completed, all nine checkpoints scanned. Level 2 east stairwell light out, reported as a defect. All other doors and windows secure. No persons encountered.
What changed: a time span, what was actually covered, a checkpoint count, one specific defect with a follow-up, and a clear statement that nothing else was found. The weak version cannot prove the patrol happened. The strong version can. This is the failure most security guard report writing examples are meant to cure: an entry that reads fine and proves nothing.
Example 2: an unsecured door
Weak: Found door open, secured it.
Strong: 04:12 – loading bay door 3 found unlocked and closed, not forced. No signs of entry, stock area checked and appears undisturbed. Door locked at 04:15. Photographed. Control informed 04:17. Handed to day supervisor for check against yesterday’s delivery sign-out.
What changed: which door, its exact state, what was checked as a result, the time of the fix, who was told, and what remains open for the next shift.
Example 3: an aggressive visitor
Weak: Man became aggressive at reception, was asked to leave.
Strong: 16:40 – male visitor, approx 40s, 1.8m, grey coat, refused to sign in at reception and raised his voice at the receptionist. No physical contact. Asked to leave at 16:42, left through main entrance at 16:44 on foot towards High Street. Description circulated to shift. Receptionist declined first aid, statement taken. Incident report raised 16:55.
What changed: a description, what was actually said and done, the explicit absence of physical contact, exact times for the request and the departure, and the record that followed.
Example 4: a slip on a wet floor
Weak: Someone slipped near the entrance, they were ok.
Strong: 11:05 – cleaner reported water on main lobby floor near entrance mat. 11:08 – member of public, female, approx 60s, slipped and fell on the same area. Assisted to a seat, no visible injury, declined first aid and declined ambulance. Details taken. Area coned at 11:12, cleaned and dry at 11:25. Photographs taken before and after. Medical report raised 11:30.
What changed: the hazard is recorded before the fall, the refusal of treatment is explicit, and the correction is timed and photographed. “They were ok” is exactly the sentence that causes trouble a year later.
Example 5: a handover note
Weak: Nothing much to report, see you tomorrow.
Strong: Handover 07:00 to incoming officer. Open items: level 2 stairwell light still out, defect logged, contractor due today. Loading bay door 3 under review by day supervisor. Radio 4 intermittent, swapped for spare, fault logged. All keys returned except server room key, signed out to facilities at 06:30, due back 09:00.
What changed: a handover that lists what is open, what is already logged, and what is outstanding with a name and a due time.
Where these entries actually live
Good security guard report writing examples are only half the job. The rules above are the same whether the entry goes in a paper book or an app. What changes is whether the entry can be trusted afterwards.
AVES holds the free-text half in a pocket book – a timestamped running log an officer writes through the shift, exactly where entries like examples 1 and 2 belong. Structured events go into their own forms: an incident form for example 3, with the 6-sided photo capture plus video and audio, the findings and the actions taken.
Patrol records carry the checkpoint scans, the GPS location and time of each scan, the waypoint start and end times and the distance covered, so an entry like example 1 is backed by scan data rather than by the officer’s word alone.
The daily briefing carries the shift’s officers and attendance, the discussion topics and a follow-up list where each item has a status and a remark – which is where the open items in example 5 belong so they survive the handover.
The practical effect is that a well-written entry is no longer just well written. It is timestamped, attributed to a named user, attached to photographs, and impossible to quietly rewrite three weeks later.
One honest note on sign-off: AVES has no signature image field. A report is signed off by an accept, decline or submit action tied to a named user with a date and time, which is an audit trail rather than a scrawl.
Common report writing mistakes
These are the errors supervisors find most often when they read a month of entries against good security guard report writing examples.
Copying last night’s entry. Duplicated wording across shifts is the fastest way to destroy the credibility of an entire logbook. If two nights genuinely looked identical, the times and checkpoint counts will still differ.
Writing opinions as facts. “He was clearly lying” is unusable. What he said and what you observed are usable.
Leaving out what you did not find. “No signs of forced entry” is information. Silence is not.
Writing up at the end of the shift. Detail decays fast. Entries written six hours later lose the times, and times are the part that matters most.
Using vague quantities. “Several people,” “a while later,” “near the back.” Replace each one with a number, a time or a place name.
Never re-reading. One pass to check that every entry has a time, an action and either a resolution or a handover catches most of the above.
Frequently asked questions
What should a security guard report include?
The time of each observation and action, the location, factual descriptions of any people or vehicles involved, what the officer did, who was informed, and whether the matter was resolved or handed over. Conclusions should follow from recorded observations rather than replace them.
How do you write a good security guard report?
Write in plain language, time-stamp everything, describe what you observed rather than what you assumed, be specific about places and descriptions, record the action you took, and state clearly whether the matter is closed or still open. Working from security guard report writing examples like the five above is the quickest way to calibrate.
Where can I find good security guard report writing examples?
The five security guard report writing examples above cover a patrol, an unsecured door, an aggressive visitor, a slip and a handover. A short one: “04:12 – loading bay door 3 found unlocked and closed, not forced. Stock area checked and appears undisturbed. Door locked at 04:15. Photographed. Control informed 04:17. Handed to day supervisor.” It gives a time, a specific location, an observed state, an action, a notification and a handover.
How long should a security guard report be?
Long enough to answer who, what, where, when and what was done. A routine patrol entry may be two lines. An incident may take a paragraph plus a separate incident form. Length is not the measure – answerability is.
Should reports record things that did not happen?
Yes, where it matters. “No signs of forced entry,” “no persons encountered,” “declined first aid” are all meaningful records. Absence noted at the time is evidence. Absence left unwritten is a gap.
See how a pocket-book entry, a patrol scan and an incident report link together on the real screens. Book a 30-minute AVES demo and we will walk you through the actual guard-app and admin screens, not a mock-up. Book a demo or start a free trial.
Internal links: Security Reporting Software (hub) · Security Daily Activity Report · Pocket Book · Daily Briefing · Incident Reporting Software (related hub) · Security Guard Logbook. External: AVES on Instagram (DoFollow).