security guard incident report writing sample philippines

Standard Operating Procedure: Security Incident Documentation and Reporting

Document Control

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

1. Purpose & Scope

This procedure establishes the professional standard for documenting security-related occurrences within [Company Name] facilities. It ensures all reports are legally defensible, objective, and compliant with local regulatory requirements for security personnel in the Philippines. This applies to all security guards, supervisors, and administrative personnel tasked with reporting breaches, accidents, or suspicious activities.

2. Prerequisites

• Official Security Occurrence Logbook (Hardbound)
• Black/Blue ballpoint pen (non-erasable)
• Digital camera or mobile device (for evidence photos)
• Incident Report Form Template (Form ID: [__________])
• Access to [Department/Security Office] filing cabinet

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Immediate Response and Documentation

• Secure the scene and provide assistance to injured parties if applicable.
• Note the exact time and location of the incident.
• Identify all witnesses and involved parties by [Full Legal Name].
• Record the initial entry in the Security Logbook (Time, Nature of Incident, Action Taken).

Phase 2: Drafting the Formal Report

• Gather facts using the "5 Ws" (Who, What, Where, When, Why/How).
• Write the report using objective, non-emotive language (e.g., "The subject shouted" instead of "The subject was aggressive").
• Use the following structure for the narrative:
  • Incident Details: Date, Time, Location.
  • Involved Parties: List [Full Legal Name] and contact details.
  • Chronological Narrative: Detailed account of events.
  • Evidence: List photographs, CCTV timestamps, or physical items recovered.
• Ensure all entries are signed and dated by the reporting officer.

Phase 3: Review and Submission

• Submit the draft to the [Shift Supervisor] for grammatical and factual review.
• Ensure the report is cross-referenced with the logbook entry.
• Submit the finalized, signed copy to [Department Name] for archiving.

5. Quality Assurance, Pro-Tips, and Pitfalls

Quality Assurance:

• Reports must be typed or written in clear, legible script.
• Ensure the report includes the specific [License Number] of the security personnel involved.
• Verify that all attachments (photos, statements) are clearly labeled with the Incident ID.

Pro-Tips:

• Use the "Active Voice" (e.g., "I observed the subject" instead of "The subject was observed").
• Include specific details such as clothing description, vehicle plate numbers, and direction of travel.

Common Pitfalls:

• Subjectivity: Avoid personal opinions or assumptions about the subject's intent.
• Vagueness: Avoid terms like "around 5 minutes" or "a large group." Use specific estimates or counts.
• Erasures: Never use correction fluid (Tipp-Ex). If a mistake is made, draw a single line through the text, initial it, and write the correction next to it.

6. FAQs

Q: Should I include my personal opinion on why the incident happened? A: No. A security report must be a factual record of events. Stick strictly to what you saw, heard, and did.

Q: What if I am unable to identify a person involved? A: Provide a detailed physical description (height, build, clothing, distinguishing marks) and note their last known direction or vehicle details if applicable.

Q: How long must these reports be kept on file? A: Reports must be archived for a minimum of [__________] years or as mandated by the [Local Regulatory Authority] and [Company Name] document retention policy.