security guard report writing examples

Standard Operating Procedure: Incident and Daily Activity Documentation

Document Control

• Document ID: SOP-SEC-DOC-001
• Version: 1.0.0
• Effective Date: [__________]
• Review Cycle: Annual

1. Purpose & Scope

This document establishes the standardized requirements for documenting security observations, incidents, and daily operations at [Company Name]. This procedure applies to all security personnel tasked with maintaining the integrity of the site log and incident narrative records.

2. Prerequisites

• Access to [System Name/Physical Logbook].
• Valid [Company Name] issued identification credentials.
• Knowledge of the [Site/Facility Name] Post Orders.
• Access to [Digital Reporting Platform/Software].
• Standardized incident classification matrix.

3. Roles & Responsibilities (RACI)

4. Procedure

Phase 1: Data Collection & Observation

• Record the precise time [HH:MM] of the event or observation.
• Identify all individuals involved using [Full Legal Name] or physical descriptors if unknown.
• Document specific locations using site-standardized terminology (e.g., [Zone/Sector Name]).
• Collect visual evidence, including [Photo/Video/CCTV Reference Number].

Phase 2: Report Drafting (The 5 Ws)

• Who: List all parties involved, including witnesses and [Company Name] staff.
• What: Provide a concise, objective summary of the event.
• Where: Specify the exact location of the incident.
• When: State the date and duration of the event.
• Why/How: Describe the sequence of events without speculation or personal opinion.

Phase 3: Review and Submission

• Review the narrative for clarity, grammar, and adherence to objective language.
• Ensure all [Required Attachments] are linked or attached to the record.
• Submit the report to [Supervisor Name/System] for final review.
• Confirm receipt of the digital signature or [Supervisor Approval Stamp].

5. Quality Assurance & Best Practices

• Objectivity: Report only facts. Avoid subjective adjectives like "suspicious," "angry," or "aggressive." Instead, describe the behavior (e.g., "Subject raised voice and clenched fists").
• Pro-Tip: Use the "Chronological Method." List events in the exact order they occurred to prevent confusion.
• Common Pitfalls: Do not use police jargon or acronyms not defined in the [Site Training Manual]. Avoid "I think" or "I feel"; use "I observed."

6. FAQs

Q: Should I include my personal opinion on why an incident happened? A: No. Reports must remain strictly factual. If you have a theory, submit it in a separate supplemental memo marked "For Internal Review Only."

Q: What do I do if I make a mistake in a written logbook? A: Do not use correction fluid or scribble out the entry. Draw a single line through the error, write "Error" next to it, initial the correction, and rewrite the correct information immediately following.