security guard incident report sample word

Standard Operating Procedure: Security Incident Reporting Protocol

Document Control

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

1. Purpose & Scope

This procedure establishes the standardized method for documenting security breaches, safety hazards, or policy violations within [Company Name]. This protocol applies to all security personnel, contractors, and third-party vendors operating on-site.

2. Prerequisites

• Access to the [Company Name] Digital Security Portal or physical logbook.
• Standardized Incident Report Form (Template provided below).
• Camera/Mobile device for evidentiary photography.
• Access to [Emergency Contact/Supervisor Number].

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Immediate Response & Stabilization

• Ensure personal safety and the safety of all individuals involved.
• Administer first aid if necessary and contact emergency services.
• Secure the scene to prevent tampering with evidence.
• Identify and isolate witnesses.

Phase 2: Documentation (The Incident Report)

• Open the official report template and input the [Incident Date] and [Incident Time].
• Record the [Exact Location of Incident].
• List all [Involved Parties/Full Legal Names].
• Draft a chronological narrative of the event, focusing on objective facts rather than opinions.
• Attach digital logs, photos, or video timestamps to the report.

Phase 3: Reporting & Submission

• Review the report for clarity, accuracy, and completeness.
• Submit the report to [Supervisor Name] via [Submission Method].
• Receive a confirmation receipt or tracking number.

Security Incident Report Template (Fill-in-the-Blank)

Incident ID: [] Reporting Officer: []

Summary of Event: On [Date] at [Time], I, [Officer Name], responded to [Location]. Upon arrival, I observed [Detailed Description of Observations].

Involved Parties:

Actions Taken: [Describe steps taken to mitigate the situation]

Sign-off: Officer Signature: __________ Date: [__________]

5. Quality Assurance, Pro-Tips, and Pitfalls

• Pro-Tip: Always document the weather conditions and lighting status if the incident occurred outdoors.
• Quality Assurance: Ensure all reports are written in the third person and use active voice (e.g., "The individual exited the vehicle" instead of "The vehicle was exited by the individual").
• Common Pitfall: Including subjective opinions (e.g., "The suspect looked suspicious"). Replace with objective observations (e.g., "The suspect was observed peering into parked vehicles").

6. FAQs

Q: How quickly must a report be submitted after an incident? A: All incident reports must be completed and submitted within the same shift the event occurred, or within [Number] hours, whichever is sooner.

Q: Can I use abbreviations in the report? A: Avoid abbreviations unless they are standard industry terms explicitly defined in the [Company Name] glossary. Always spell out full names and titles on first mention.