security guard incident report writing sample

Standard Operating Procedure: Security Incident Documentation

Document Control

• Document ID: SEC-OPS-004
• Version: 1.0.0
• Effective Date: [__________]
• Review Cycle: Annual

1. Purpose & Scope

This document defines the mandatory protocol for documenting security-related events at [Company Name]. The objective is to ensure objective, chronological, and legally defensible records that support internal investigations and potential litigation. This procedure applies to all security personnel, contractors, and site supervisors.

2. Prerequisites

• [Digital Reporting Platform/Physical Logbook]
• [Company-issued identification credentials]
• [Standardized Incident Report Template]
• [Access to digital evidence storage/camera system]
• [Black ink pen (if manual)]

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Immediate Documentation

• Record exact time and date of the observation: [__________]
• Identify location of incident: [__________]
• Note environmental conditions (lighting, weather, crowd density): [__________]

Phase 2: Fact Gathering (The Five Ws)

• Who: List all individuals involved. Use [Full Legal Name] or physical descriptors (height, clothing, distinguishing marks) if identity is unknown.
• What: Describe the incident chronologically. Use neutral, professional language.
• Where: Specify the exact area within [Company Name] facility.
• When: Establish a timeline of events using the 24-hour clock.
• Why/How: State observed causes or methods (e.g., "Subject forced entry via..."). Do not speculate on motives.

Phase 3: Narrative Construction

• Write the report in the first person ("I observed...").
• Ensure all statements are objective observations, not opinions.
• List all physical evidence collected (e.g., [Item Name], [Evidence Tag ID]).
• Document all notifications made (e.g., Law Enforcement, EMS, Management).

Phase 4: Finalization and Submission

• Proofread for clarity, grammar, and completeness.
• Attach digital files or sketches to the incident ID: [__________].
• Submit to supervisor for sign-off: [__________].

5. Quality Assurance & Best Practices

Pro-Tips

• The "Mirror" Test: If you were reading this in court, would you be able to verify every statement as a fact?
• Stick to the Facts: Avoid adjectives like "aggressive," "suspicious," or "angry." Instead, describe the behavior: "Subject raised voice, clenched fists, and paced back and forth."
• Timeliness: Complete the report before the end of the shift. Memory degrades significantly after 24 hours.

Common Pitfalls

• Subjectivity: Including personal feelings or assumptions about the subject's intent.
• Vague Timelines: Using terms like "a few minutes later" instead of specific timestamps.
• Missing Evidence: Failing to document the existence of CCTV footage or witness contact information.

6. FAQs

Q: Should I include hearsay in my report? A: No. If a witness provides information, use the format: "Witness [Full Legal Name] stated that [Quote]." Do not present witness statements as your own observations.

Q: What if I make a mistake while writing? A: If using a digital system, use the "Amendment" function. If using a physical logbook, draw a single line through the error, initial it, and write the correction next to it. Never use correction fluid or obscure the original text.