Incident Report Sample for Security Guard

SOP-SEC-004: Incident Reporting Standards for Security Personnel

1. Document Control & Revision History

---

2. Executive Summary & Scope

This Standard Operating Procedure (SOP) defines the mandatory protocol for the documentation of security-related incidents within facility boundaries. The objective is to ensure objective, admissible, and forensically sound reporting to support internal audits, legal defense, and operational risk mitigation. This policy applies to all contracted and in-house security personnel, third-party responders, and supervisors overseeing site operations. Compliance with this SOP is a condition of site clearance.

---

3. Prerequisites & Tool Requirements

• Hardware: Encrypted handheld reporting device (or authorized Site Security Logbook, watermarked).
• Software: Access to Integrated Security Management System (ISMS) portal via biometric authentication.
• PPE: Approved high-visibility vest, radio communication gear, body-worn camera (BWC).
• Certifications: Active site-specific security certification; mandatory completion of "Data Privacy & HIPAA/PII Handling" training module.
• Evidence Collection: Digital camera (if BWC is unavailable), chain-of-custody bags for physical artifacts.

---

4. Roles & Responsibilities (RACI Matrix)

---

5. Step-by-Step Operational Procedure

Phase I: Immediate Response & Containment

• Stabilize the scene and ensure personal safety and the safety of any bystanders.
• Administer first aid or request emergency medical services (EMS) if required.
• Secure the perimeter and preserve the integrity of the scene (no unauthorized entry).

Phase II: Data Collection & Documentation

• Record the precise UTC timestamp, GPS coordinates, and weather conditions.
• Capture objective observations only; avoid subjective assumptions or emotional interpretation.
• Obtain contact information from all witnesses and involved parties (verify via government-issued ID).
• Secure visual evidence (BWC footage, CCTV retrieval, photos) and log as an attachment in the ISMS.

Phase III: Report Drafting & Submission

• Complete the Incident Report Form using the "Who, What, Where, When, Why, How" (5W1H) framework.
• Cross-reference report against the shift log to ensure chronological continuity.
• Submit the drafted report to the Shift Supervisor for review within 60 minutes of incident clearance.

---

6. Quality Assurance & Verification Criteria

Verification: Reports failing the Quality Assurance audit will be returned to the primary guard for immediate remediation. Continued failure to meet these criteria warrants performance review.

---

7. Practical Troubleshooting Scenarios

Scenario A: Technology Failure (Mobile Device/ISMS Down)

• Symptom: Incident reporting software is inaccessible or handheld device battery failure.
• Corrective Action: Immediately pivot to the "Legacy Contingency Plan." Record the incident in the physical, serialized Site Security Logbook. Notify the Shift Supervisor via radio. Once the system is restored, transcribe the logbook entries into the ISMS within 2 hours, referencing the original logbook entry ID.

Scenario B: Witness Refusal to Provide PII

• Symptom: Involved party refuses to provide name/contact details.
• Corrective Action: Do not escalate the interaction. Document the refusal in the report, provide a detailed physical description of the individual, and include the time/location of the request. Immediately flag the report for the Site Security Manager and Legal/Compliance for further investigation via CCTV.

Scenario C: Uncontrolled/Violent Scene

• Symptom: The situation escalates, preventing safe collection of data.
• Corrective Action: Prioritize safety over data collection. Retreat to a secure area. Radio for backup and wait for the Shift Supervisor or external law enforcement. Document only what was observed from a position of safety. Do not attempt to re-enter the scene until declared "Code Clear" by the responding Supervisor.