security guard incident report template word pdf

Security Incident Documentation and Reporting Protocol

Document Control

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

1. Purpose & Scope

This procedure establishes a standardized methodology for documenting security-related occurrences within [Company Name] facilities. It ensures that all data collected is legally defensible, chronologically accurate, and actionable for management and law enforcement review. This protocol applies to all security personnel, contractors, and third-party vendors operating on-site.

2. Prerequisites

• Access: Secure digital repository or physical logbook access.
• Tools: [Company Name] approved incident reporting software, or standardized document template (Word/PDF).
• Materials: Camera/mobile device for evidence, witness contact information forms, and site-specific incident classification codes.

3. Roles & Responsibilities (RACI)

4. Procedure

Phase I: Immediate Response and Data Collection

• Secure the scene and ensure the safety of all individuals present.
• Identify all witnesses and record their contact details: [__________].
• Capture photographic or video evidence of the scene and any damaged property.
• Note the exact time and location of the incident: [__________].

Phase II: Drafting the Formal Report

• Open the standardized report template and enter the Incident ID: [__________].
• Provide a factual, objective narrative. Use the "5 Ws" (Who, What, Where, When, Why).
• Avoid personal opinions or subjective interpretations; stick strictly to observable facts.
• List all items collected as evidence in the custody log.

Phase III: Review and Submission

• Perform a final proofread to ensure dates, times, and names are accurate.
• Submit the report to [Supervisor Name/Title] for final verification.
• Export the final document as a PDF to ensure data integrity and prevent unauthorized editing.
• File the report in the [__________] database and notify the appropriate department heads.

5. Quality Assurance and Pro-Tips

• Pro-Tip: Write reports in the present tense or immediate past tense to maintain a sense of urgency and accuracy.
• Pro-Tip: If an error is made, strike through the text with a single line, initial it, and write the correction next to it (if using physical logs). Never use correction fluid.
• Common Pitfall: Using vague language like "the suspect seemed angry." Instead, use descriptive language: "the suspect raised their voice and clenched their fists."
• QA Check: Ensure the report is submitted within [__________] hours of the incident occurring.

6. FAQs

Q: Should I include my personal opinion on why the incident happened? A: No. Reports must be strictly factual. Your role is to document what occurred, not to provide psychological analysis or personal theories.

Q: What if I don't have all the information at the time of the initial filing? A: File a preliminary report with the information available and submit a supplemental report as soon as further details are confirmed.

Q: How long should these reports be retained? A: Reports must be retained for [__________] years, or in accordance with your local regulatory and legal requirements.