security guard incident report writing sample pdf

Standard Operating Procedure: Security Incident Documentation

2. Purpose & Scope

This procedure establishes the standardized method for recording security incidents at [Company Name]. It ensures that all documentation is legally defensible, objective, and provides sufficient detail for administrative review, insurance claims, or law enforcement handover. This applies to all security personnel operating on [Site Location].

3. Prerequisites

• Access to the [Company Name] Digital Incident Reporting Portal OR hard-copy Incident Report Form (IRF-01).
• Standardized black-ink pen (for manual logs).
• Digital camera or mobile device with [Company Name] approved secure storage.
• Knowledge of site-specific [Emergency Protocol Code].

4. Roles & Responsibilities

5. Step-by-Step Procedure

Phase 1: Initial Containment and Data Collection

• Secure the scene and ensure the safety of all involved parties.
• Identify and record contact details of all witnesses: [Name], [Phone Number], [Statement].
• Capture timestamped photographic evidence of relevant conditions or damage.

Phase 2: Drafting the Narrative

• Log the incident start time: [__________].
• State the location: [__________].
• Compose the narrative using the "Five Ws" (Who, What, When, Where, Why).
• Ensure the narrative uses strictly objective language (e.g., "The individual appeared to be agitated" instead of "The individual was crazy").

Phase 3: Finalization and Submission

• Review the report for chronological consistency.
• Attach all supporting digital media files to the report ID: [__________].
• Submit the report to the [Shift Supervisor] for digital signature.

6. Quality Assurance, Pro-Tips, and Pitfalls

Quality Assurance:

• All reports must be filed within [__________] hours of the incident.
• Use the "Plain Language" standard; avoid jargon or radio codes.

Pro-Tips:

• If you made a mistake on a paper form, draw a single line through the error, initial it, and write the correction next to it. Never use correction fluid.
• Always include the weather conditions if the incident occurred outdoors.

Common Pitfalls:

• Subjectivity: Avoiding emotional descriptors or personal opinions.
• Omission: Failing to record the full legal names of involved parties.
• Inconsistency: Discrepancies between the incident log and the narrative.

7. FAQs

Q: Should I include my personal opinion on why the incident happened? A: No. Reports must be strictly factual. If you suspect a motive, phrase it as: "The individual stated [__________]."

Q: What if I forget a detail after I have already submitted the report? A: Do not alter the original report. File a "Supplemental Incident Report" referencing the original Document ID and provide the additional information.