security guard incident report sample pdf

Standard Operating Procedure: Security Incident Documentation and Reporting

Document Control

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

1. Purpose & Scope

This procedure establishes the standardized framework for documenting security-related occurrences within [Company Name]. It ensures that all incidents are captured with legal and operational integrity, facilitating accurate investigations, risk mitigation, and compliance reporting. This applies to all security personnel operating under [Department Name].

2. Prerequisites

• Tools: Standardized Incident Report Form (Digital or Physical), [Camera/Phone for evidence], [Flashlight], [Radio/Communication device].
• Access: Active credentials for [Incident Management System], access to [Specific Site Area], and authorization to document [Sensitive Data/Personnel].

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Immediate Response & Scene Preservation

• Ensure personal safety and the safety of [Staff/Visitors/Assets].
• Secure the scene to prevent tampering or contamination of evidence.
• Administer first aid or request emergency medical services if required.
• Identify and isolate witnesses or involved parties.

Phase 2: Data Gathering & Fact Recording

• Record the precise time of the occurrence: [__________].
• Record the exact location: [__________].
• Collect identification details of involved parties: [__________].
• Capture photographic evidence or video footage of the scene.
• Note environmental conditions (lighting, weather, etc.).

Phase 3: Formal Documentation

• Complete the Incident Report header with [Reporting Officer Name] and [Badge Number].
• Write a chronological narrative of the event using the "Who, What, Where, When, Why, How" framework.
• Use objective language; avoid assumptions or personal opinions.
• Attach all gathered evidence logs to the report: [__________].

Phase 4: Submission & Review

• Submit the completed report to the [Shift Supervisor] for initial review.
• Ensure all required signatures are present: [__________].
• Upload the final report into the [Central Database/Registry].
• Notify [Department Head] if the incident involves [Critical Assets/High-Risk Personnel].

5. Quality Assurance, Pro-Tips, and Pitfalls

• Pro-Tip: Always document the names of individuals who arrived on the scene after the incident, as they may be critical witnesses.
• Pro-Tip: If a mistake is made on a physical report, draw a single line through the error, initial it, and write the correction next to it—never use correction fluid.
• Common Pitfall: Using vague timeframes (e.g., "around 2:00 PM"). Use precise timestamps (e.g., "14:03:12").
• Quality Assurance: Reports must be reviewed for factual consistency and grammatical clarity before final archival.

6. FAQs

Q: How long should I keep the draft notes once the final report is typed? A: All original notes must be retained according to [Company Retention Policy] or until the statute of limitations for potential litigation expires.

Q: Can I use personal opinions to describe the behavior of a suspect? A: No. Describe observed actions only (e.g., "Subject was shouting and pacing") rather than subjective interpretations (e.g., "Subject was angry").