GuardDesk

How to write a daily activity report clients actually read

What to put in it, what to leave out, and a structure that takes a guard ten minutes, not forty.

8 MIN READ · GUARDDESK TEAM

The report is the product your client sees

Your client pays for guards they rarely see working. Most nights, the daily activity report is the only evidence they get that the money was well spent. A vague report doesn’t just look lazy; it makes the client wonder what else isn’t happening.

A good report is short, factual and organized the same way every day, so the client can find what changed in under a minute.

Answer the five questions every client has

Before anything else, the report should answer the questions a property manager asks when they open it:

  • Was the post covered? Who was on site, from when to when, and any gap.
  • Were the patrols done? How many tours, how many checkpoints, and which ones were late or missed.
  • Did anything happen? Incidents, with what was done about them.
  • Is anything still open? Problems the next shift or the client needs to follow up.
  • Who came and went? Visitors and contractors, with times.

Use the same structure every night

Clients learn where to look. Keep the order fixed: a header (site, date, shift, guard), a four-number summary, patrols, incidents, log entries, visitors and handover. If a section is empty, say “none” instead of deleting it, so the client knows it wasn’t forgotten.

Writing rules for guards

Give guards a short list of rules and the reports improve within a week:

  • Facts, not opinions. Write what you saw and did, not what you think happened.
  • Times on everything. Use the 24-hour clock and note the time of every entry.
  • One event per entry. A leak and an unlocked door are two entries, not one sentence.
  • A photo for every issue. If it can be photographed, photograph it.
  • Never hide a miss. A late checkpoint with a reason is believable. A perfect night every night is not.

Before and after

The difference between a report that builds trust and one that doesn’t is usually specificity.

BeforeQuiet night. Did my rounds. Some people in the garage, asked them to leave. All good.
AfterTours at 22:30, 01:15 and 04:00; 23 of 24 checkpoints scanned, stairwell B 18 min late (02:14) while escorting two trespassers out of P2 via the north ramp at 01:20. Photos attached. Loading dock door found unlocked at 23:10, locked.

A template you can copy

Print it, paste it into your current system, or adapt it per client:

DAILY ACTIVITY REPORT
Site: ____________   Post: ________
Date: ____________   Shift: __:__ – __:__
Guard(s): __________   Supervisor: ________

SUMMARY
Coverage: __ h of __ h scheduled
Checkpoints: __ of __ verified (__ late, __ missed)
Incidents: __     Visitors: __

PATROLS
__:__–__:__  Tour 1  __/__ checkpoints  Notes: ______

INCIDENTS
__:__  Type · Location
What happened: ______
Action taken: ______
Photos: __   Reviewed by: ______

LOG ENTRIES
__:__  ______

VISITORS
Name / company · in __:__ · out __:__

HANDOVER TO NEXT SHIFT
- ______

How GuardDesk does it

GuardDesk builds this report automatically from the shift’s verified scans, incidents, logbook and visitor entries, and sends it to the client each morning after a supervisor has reviewed anything sensitive. Guards don’t retype anything; they just do the rounds.

Stop writing reports by hand. Try GuardDesk free for three months.

Apply for the pilot