Guard OperationsAction checklist

Security Guard Daily Activity Report Quality Checklist

A security guard daily activity report should tell an authorized reader what happened during the shift, when and where it happened, what the guard directly observed, what action was taken and who was notified. This checklist helps guards and supervisors review completeness, chronology, objectivity, follow-through and confidentiality. It is not an incident-report substitute when site policy requires a separate report, and it does not authorize investigation or enforcement activity. Write promptly in plain language, distinguish firsthand observations from information supplied by others, correct errors transparently and follow the employer's approved form, retention and escalation rules.

Why it matters

Use a system view, not a single-control view

Daily reports support continuity across shifts and allow supervisors and clients to identify unresolved conditions. Vague phrases such as 'all secure' provide little evidence of what was actually checked or what an exception required.

FEMA's ICS 214 model records notable activities by date and time and can support after-action review. Department of Justice report-writing resources likewise emphasize relevant facts, accuracy, objectivity, clarity and review before submission.

Before you begin

How to use this checklist

  1. Write entries during or soon after the activity, using the site's approved time format and report system.
  2. Before submitting, review each applicable item and open the required separate incident, maintenance or safety report when policy calls for one.
  3. Use this quality example as a pattern, not copy: '21:14 — North lobby door alarm sounded. I observed the door ajar approximately two inches. I closed and checked the latch. Notified the on-duty supervisor at 21:18 per post orders; maintenance ticket 4821 opened.'
  4. Avoid weak entries such as 'Checked doors, all good' or 'Suspicious guy hanging around,' which omit evidence and substitute a conclusion for observable facts.
Interactive checklist

Mark each task from current evidence

Use Not applicable only when the item genuinely does not apply, and follow the site’s approved escalation process for any urgent condition.

Section 1 of 4

Report identification and chronology

Make the record attributable to the correct assignment and easy to follow.

01The report identifies the correct site, post, date, shift or reporting period and author. Priority review item

Evidence to look for: Use the approved identifiers; keep employee numbers or other protected data only in the authorized system.

02Entries use specific, consistent dates and times in chronological order.

Evidence to look for: Include the date when a shift crosses midnight and use the employer's approved 12- or 24-hour format.

03The report accounts for required duties and meaningful exceptions across the reporting period.

Evidence to look for: Record the duty, result and exception at the level required by post orders without exposing predictable patrol patterns to unauthorized readers.

04Late entries or corrections are transparent and do not overwrite the original record improperly. Priority review item

Evidence to look for: Follow the approved amendment process, showing who corrected what and when while preserving the original where required.

Section 2 of 4

Objective observations

Describe behavior and conditions before drawing or repeating conclusions.

05Each exception states the specific location and observable condition or behavior.

Evidence to look for: Write what was seen, heard or detected, such as a door visibly ajar or an alarm-panel message, rather than only 'unsafe' or 'suspicious.'

06The report distinguishes the guard's observations from statements made by another person. Priority review item

Evidence to look for: Attribute information, for example 'Tenant reported...' and avoid presenting it as personally verified fact.

07Descriptions avoid guesses about intent, guilt, diagnosis or protected characteristics. Priority review item

Evidence to look for: Record relevant actions, words, direction of travel and context; race, religion, disability and other protected traits are not suspicious by themselves.

08Names, quotations, measurements and identifiers are used only when relevant and supported.

Evidence to look for: Verify spelling or label uncertainty; include exact quotations only when important and accurately recalled or recorded under policy.

Section 3 of 4

Actions, notifications and outcomes

Show what followed the observation and what remains open.

09Each notable exception records the safe action taken within post orders and training. Priority review item

Evidence to look for: Examples include observing from a safe location, securing an assigned door, creating a work request or contacting a supervisor.

10Required notifications identify the role or authorized recipient and the time made. Priority review item

Evidence to look for: Record acknowledgment or instructions received when relevant; avoid placing private contact details in the narrative.

11Emergency-service contacts and reference numbers are recorded when applicable. Priority review item

Evidence to look for: Use the agency, call time, arrival or disposition known to the guard and an official reference number if provided.

12Unresolved items state the current status, responsible next role and handoff.

Evidence to look for: An authorized reader should be able to see what remains, who received it and whether follow-up documentation exists.

Section 4 of 4

Clarity, confidentiality and review

Finish with a record that is readable, appropriately shared and preserved.

13The narrative uses plain, professional language and defined abbreviations.

Evidence to look for: Prefer short active sentences and site-approved terms; avoid slang, sarcasm, filler and unexplained codes.

14The daily report points to required separate reports rather than burying a serious incident in the log. Priority review item

Evidence to look for: Follow site rules for incident, injury, use-of-force, maintenance or emergency documentation and cross-reference approved identifiers.

15Sensitive details are limited to the approved record and authorized audience. Priority review item

Evidence to look for: Do not include access codes, unnecessary medical details, complete identification numbers, camera blind spots or confidential investigative information.

16The author proofread the report and completed required supervisor review before finalization.

Evidence to look for: Check factual consistency, missing fields, attachments, spelling of relevant names and required signatures or acknowledgments.

Current result

Complete the checklist to see a summary

Results are informational and do not certify compliance or eliminate risk.

Common mistakes

What can weaken the review

  • Writing 'all clear' or 'all secure' without identifying what was observed or checked.
  • Copying the same entry repeatedly when conditions or task results differ.
  • Calling a person suspicious based on appearance instead of describing relevant behavior and context.
  • Mixing secondhand statements with firsthand observations without attribution.
  • Leaving the reader to guess what action was taken, who was notified or what remains open.
  • Deleting or silently changing a finalized record instead of using the approved correction process.
Practical questions

Frequently asked questions

What should a security guard daily activity report include?

Include the correct assignment and reporting period, chronological times, required duties, notable observations, actions, notifications and unresolved handoffs. Use the employer's approved form and create separate incident reports when required.

What is an example of an objective security report entry?

A useful entry states time, place, direct observation, action and notification: '21:14 — North lobby door alarm sounded. I observed the door ajar approximately two inches. I closed and checked the latch. Supervisor notified at 21:18; maintenance ticket opened.'

Should a daily activity report include routine patrols?

Include them at the level required by post orders and the report system. Avoid vague repetition, but also avoid distributing predictable routes or timing beyond authorized recipients.

Can a guard correct a report after submitting it?

Follow the employer's approved amendment procedure. A correction should remain attributable and transparent and should not improperly erase the original entry.

Is a daily activity report the same as an incident report?

No. A daily log summarizes shift activity, while an incident report usually provides the dedicated detail and routing required for a specific event. Site policy determines when both are required.

Sources and evidence baseline

These references support the general planning baseline. Site-specific decisions still require the responsible organization and appropriate qualified professionals.

  1. ICS Form 214, Activity LogFederal Emergency Management Agency

    An incident-command activity log used as an analogy for chronological documentation of notable activities and communications; it is not a controlling private-guard reporting standard.

  2. Unarmed Security Guard 8-Hour Training Syllabus, Rev. 11/2025Arizona Department of Public Safety

    Arizona's required training topics include report writing, note taking, steps in writing a report, grammar, spelling and report forms.

  3. Recognize Suspicious ActivityU.S. Department of Homeland Security

    Behavior-based observation and civil-rights guardrails.

Source links checked: July 19, 2026