security guard incident report sample philippines

Standard Operating Procedure: Security Incident Documentation and Reporting

Document Control

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

1. Purpose & Scope

This procedure establishes the standardized method for recording, documenting, and filing security-related events within [Company Name] facilities. This protocol ensures compliance with local regulatory requirements and provides a defensible audit trail for internal investigations and legal proceedings.

2. Prerequisites

• Official Security Logbook (Hardbound, numbered pages)
• [Company Name] Incident Report Form (IRF)
• Blue or Black ballpoint pen (non-erasable)
• Digital camera or mobile device (for evidence preservation)
• Access to [Security Supervisor Name/Department]

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Immediate Response & Fact Gathering

• Secure the area and provide assistance to injured parties.
• Identify all witnesses and request [Full Legal Name] and contact details.
• Preserve the scene; do not move physical evidence unless necessary for safety.
• Take timestamped photographs of the scene and any damages.

Phase 2: Initial Logbook Entry

• Record the precise time of the event (e.g., 00:00).
• Write a concise summary in the official logbook.
• Ensure no white-out or erasures are used; cross out errors with a single line and initial.
• Have the entry countersigned by the Shift Supervisor.

Phase 3: Formal Incident Report Drafting

• Complete the [Company Name] Incident Report Form using the 5 Ws: Who, What, Where, When, and Why.
• Use objective language; describe facts observed, not personal opinions or assumptions.
• Attach witness statements and inventory photos to the report.
• Submit the final document to [Department/Office Name] within [Number] hours of the incident.

5. Quality Assurance, Pro-Tips, and Pitfalls

Quality Assurance:

• All reports must be reviewed for grammatical clarity and completeness by the Shift Supervisor before final submission.
• Ensure the report matches the timestamp recorded in the master logbook.

Pro-Tips:

• Always use the "Active Voice" (e.g., "I observed the suspect," rather than "The suspect was observed by me").
• If a detail is unknown, write "Unknown at time of report" rather than guessing.

Common Pitfalls:

• Erasures: Using correction tape invalidates the document for legal purposes.
• Delay: Reporting an incident more than 24 hours after the event reduces the reliability of the testimony.
• Subjectivity: Including biased language can create liability for [Company Name].

6. FAQs

Q: Should I include my personal opinion on who is at fault? A: No. Focus strictly on objective facts, actions taken, and observations. Let management or legal counsel determine culpability.

Q: What if a witness refuses to give their name? A: Note the refusal in your report, provide a physical description of the individual, and notify your supervisor immediately for further action.

Q: Is digital photography acceptable as evidence? A: Yes, provided the images are clear, timestamped, and uploaded to the [Company Name] secure server immediately after the incident.