security guard incident report examples

Standard Operating Procedure: Security Occurrence Documentation

Document Control

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

1. Purpose & Scope

This procedure establishes the standardized method for recording, documenting, and filing security-related events occurring within [Company Name] premises. The scope includes all physical security personnel, contractors, and designated facility management staff responsible for documenting breaches, accidents, or policy violations.

2. Prerequisites

• Tools: [Company Name] Digital Incident Logging Portal or physical bound logbook.
• Materials: Camera (for evidence photography), [Company Name] Incident Report Form (IRF-01).
• Access: Validated security credentials and authorization to access the [System Name] database.

3. Roles & Responsibilities (RACI)

R: Responsible, A: Accountable, C: Consulted, I: Informed

4. Step-by-Step Procedure

Phase 1: Immediate Response and Scene Preservation

• Ensure personal safety and the safety of all [Company Name] personnel.
• Secure the area to prevent contamination of evidence.
• Identify and isolate witnesses or involved parties.
• Document the exact time the event was identified: [__________] (HH:MM).

Phase 2: Data Collection and Fact-Finding

• Record the full legal names and contact details of all involved parties: [__________].
• Capture high-resolution photographs of the scene, damages, or relevant equipment.
• Collect statements from witnesses using the standard [Company Name] Witness Statement Form.
• Verify CCTV footage timestamps corresponding to the event duration.

Phase 3: Formal Documentation

• Complete the Incident Report Form using objective, non-emotive language.
• Describe the event chronologically, starting from [] to [].
• List all physical evidence collected and its current storage location: [__________].
• Ensure all entries are signed, dated, and verified by a supervisor.

Phase 4: Reporting and Archiving

• Upload all digital files to the [Company Name] secure server.
• Submit the finalized report to the [Department Name] for review.
• Update the Master Security Log with the unique report reference ID: [__________].

5. Quality Assurance, Pro-Tips, and Pitfalls

• Quality Assurance: All reports must be reviewed for "The 5 Ws": Who, What, Where, When, and Why (if known).
• Pro-Tip: Always record what you did (e.g., "Called emergency services at 10:05") rather than what you felt (e.g., "I was scared").
• Common Pitfall: Using vague timelines. Always use specific clock times rather than "a while later" or "shortly after."
• Common Pitfall: Including personal opinions or character judgments. Stick strictly to observable facts.

6. Frequently Asked Questions

Q: What should I do if a witness refuses to provide a statement? A: Record the individual's full name, note that they were asked to provide a statement, and document their refusal in the "Notes" section of the report. Do not attempt to coerce a statement.

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

Q: Should I include my personal opinion on who is at fault? A: No. Reports must remain neutral and factual. Your role is to document the events as they occurred, not to adjudicate liability.