How to Write a Security Guard Daily Activity Report (DAR)

The daily activity report is the most-read document your security company produces. Clients use it to judge whether they're getting what they pay for. Supervisors use it to catch problems early. And when an incident turns into an insurance claim or a lawsuit, the DAR is often the first piece of evidence anyone asks for. A vague or incomplete report doesn't just look unprofessional — it can cost the contract or lose the case.

This guide covers what belongs in a DAR, how to write entries that hold up under scrutiny, and the habits that separate a defensible report from a useless one. There's a copy-paste template at the end.

What a daily activity report is (and isn't)

A DAR is a chronological log of everything a guard does and observes during a shift: patrols completed, checkpoints scanned, visitors processed, deliveries accepted, hazards spotted, and anything out of the ordinary. It is not an incident report — when something serious happens, the DAR should reference a separate, more detailed incident report rather than try to contain it.

The test of a good DAR is simple: could someone who wasn't there reconstruct the shift from it? If a client calls Monday morning asking what happened at their property on Saturday night, the DAR should answer the question without a single phone call to the guard.

What every DAR entry needs

• Time — exact, not approximate. "2147" beats "around 10pm" every time.
• Location — specific enough to act on: "northeast stairwell, level 2," not "the back."
• What happened — observed facts, in plain language.
• Action taken — what the guard did about it, even if the answer is "monitored, no action required."
• Evidence — photos of damage, hazards, or violations, attached at the time of the entry.

Write facts, not conclusions

The fastest way to ruin a DAR's credibility is to editorialize. "Suspicious male loitering with intent" is a conclusion — and a lawyer will take it apart. "Male, approx. 6′0″, dark hoodie, observed standing at the loading dock gate for 15 minutes, did not respond when greeted, left on foot heading north at 0214" is a fact pattern. Write what you saw, heard, and did. Let the reader draw conclusions.

Log as you go — never reconstruct at end of shift

Reports written in the last ten minutes of a shift read like it: identical timestamps, copy-paste patrol entries, and gaps where the interesting things happened. Memory degrades fast on a twelve-hour overnight. Entries made in the moment are more accurate, more detailed, and far more credible as evidence — a contemporaneous record carries real weight in disputes; a reconstruction doesn't.

This is the single strongest argument for mobile reporting over paper: a guard with a phone logs the entry in thirty seconds at the spot where it happened, with a photo, while a paper DAR waits for the end of the shift and gets whatever the guard still remembers.

The entries supervisors actually want to see

A defensible DAR includes the routine, not just the exceptional. Patrol start and end times. Checkpoint scans. Interval checks confirming the site is quiet. Visitor and delivery logs with names and times. Equipment or maintenance issues — the broken light, the propped door, the leaking pipe — flagged for follow-up. These "nothing happened" entries are what prove service was delivered, and they're exactly what clients are paying to know.

Copy-paste DAR template

Example entries — weak vs. strong

Weak: "10pm — did patrol, all ok."

Strong: "2204 — Completed exterior patrol route B (8/8 checkpoints scanned). East parking structure: vehicle with broken window in stall 214, photographed, plate noted. No occupants. Reported to dispatch, owner notification requested. Resumed post 2231."

Weak: "Visitor came by in the afternoon."

Strong: "1438 — HVAC contractor (J. Alvarez, TechServ, ID verified) signed in for rooftop unit service, escorted to roof access, badge V-12 issued. Signed out 1602, badge returned."

Where software changes the math

Everything above can be done on paper — security companies did it for decades. What software changes is verification and speed. With a platform like ShiftsGo, each log entry is automatically time-stamped and GPS-stamped, checkpoint scans flow into the report on their own, photos attach in the moment, and the supervisor sees entries live instead of collecting binders on Friday. Edits keep a version history, so the record stays trustworthy even when a typo gets fixed. The guard writes less; the client gets more.