security guard incident report template

Security Operations Incident Documentation Protocol

Document Control

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

1. Purpose & Scope

This procedure establishes the standardized method for recording, documenting, and escalating security-related events occurring within [Company Name] facilities. This protocol applies to all on-site security personnel, contractors, and site managers responsible for incident reporting.

2. Prerequisites

• Tools: Access to [Reporting Software/Physical Logbook], digital camera/mobile device for evidence capture, and [Specific Pen/Ink Color].
• Materials: Blank [Incident Report Form ID], [Company Name] Site Map, and local emergency contact directory.
• Access: Authorized credentials for the [Security Management System].

3. Roles & Responsibilities

4. Procedure

Phase I: Immediate Response & Scene Preservation

• Ensure personal safety and the safety of others.
• Administer first aid or request emergency medical services if [__________].
• Secure the area to preserve evidence; restrict access to unauthorized personnel.
• Note the exact time of arrival at the scene: [__________].

Phase II: Data Collection & Documentation

• Identify all involved parties: [Full Legal Name(s)].
• Collect contact information for witnesses: [__________].
• Capture high-resolution photographs of the scene, damage, or relevant items.
• Record a factual, chronological account of events without personal opinion.
• Document specific property damage or missing items: [__________].

Phase III: Formal Report Completion

• Complete the Incident Summary: [Provide brief description of event].
• Attach all supporting digital evidence to the report file: [__________].
• Obtain signatures from involved parties if possible: [__________].
• Submit the completed document to [Supervisor Name/Title] by [Time].

5. Quality Assurance & Best Practices

• Pro-Tip: Use the "Five Ws" (Who, What, Where, When, Why) to ensure the report narrative is comprehensive.
• Common Pitfall: Including subjective language (e.g., "The suspect looked suspicious") instead of objective observations (e.g., "The suspect was wearing a dark hoodie and pacing near the entrance").
• QA Check: Ensure all timestamps match digital logs and surveillance footage.

6. Frequently Asked Questions

Q: Should I include my personal opinion on why the incident occurred? A: No. Reports must remain strictly objective. Only document facts, observations, and statements provided by witnesses or involved parties.

Q: What should I do if a witness refuses to provide their information? A: Document their refusal in the report, note their physical description, and notify your supervisor immediately for further instruction.

Q: How long must these records be retained? A: All documentation must be retained for a minimum of [Number] years in accordance with [Company Name] data retention policies.