incident report template for security guard

Security Operations Incident Documentation Protocol

Document Control

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

1. Purpose & Scope

This procedure establishes the standardized method for recording security-related events at [Company Name] facilities. It ensures that all data points required for legal, insurance, and internal auditing are captured accurately and consistently. This protocol applies to all security personnel, contractors, and site supervisors.

2. Prerequisites

• Access to [Digital Reporting System/Physical Logbook].
• Validated [Company Name] identification credentials.
• Standardized incident reporting forms (Form ID: [__________]).
• Access to high-resolution camera system (if applicable).
• [__________] (e.g., Body-worn camera/Radio/Flashlight).

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Immediate Response & Site Security

• Ensure personal safety and the safety of any victims.
• Render first aid if necessary and call [Emergency Number] if required.
• Secure the scene to prevent evidence tampering.
• Note the exact time of the event: [__________].

Phase 2: Information Gathering

• Obtain the full legal name of involved parties: [__________].
• Collect contact information for witnesses: [__________].
• Document the exact location of the incident: [__________].
• Note environmental conditions (lighting, weather, crowd status).

Phase 3: Formal Documentation

• Complete the "Incident Summary" section using objective, factual language.
• Attach digital evidence (photos/video) to the report ID: [__________].
• Verify that the report contains no opinions or speculation.
• Sign and date the document: [__________].

Phase 4: Submission & Escalation

• Submit the completed report to [Supervisor Name] within [Timeframe].
• Ensure the report is logged in the daily shift summary.
• Confirm receipt of the report by the shift supervisor.

5. Quality Assurance & Best Practices

• Pro-Tips: Use the "Who, What, Where, When, Why, How" framework. Write reports as if they will be read by a judge or insurance adjuster.
• Common Pitfalls:
  • Using subjective descriptors (e.g., "he looked suspicious"). Use objective observations (e.g., "he was pacing near the restricted entrance for 15 minutes").
  • Delaying the report submission, which leads to loss of detail.
  • Failing to include the exact time of notification.

6. FAQs

Q: What should I do if a witness refuses to provide their name? A: Record the individual's physical description, clothing, and any unique identifiers, then note "Witness refused to provide identification" in the report.

Q: How do I handle conflicting accounts of an incident? A: Document both accounts separately in the report, clearly labeling them as "Statement from [Name]" and "Statement from [Name]." Do not attempt to determine who is telling the truth.