how do i write an incident report for a security guard

Security Incident Documentation and Reporting Protocol

1. Purpose & Scope

This procedure establishes the standardized method for recording security-related events at [Company Name]. It ensures that all documentation is objective, legally defensible, and actionable for management and law enforcement review. This applies to all site security personnel, contractors, and designated facility staff.

2. Prerequisites

• Access to [Digital Incident Management System/Physical Logbook]
• [Company Name] Incident Report Template (Form ID: [__________])
• Reliable writing instrument (if physical) or secured terminal (if digital)
• Supporting evidence (e.g., CCTV timestamps, witness contact details, photos)

3. Roles & Responsibilities (RACI)

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

4. Step-by-Step Procedure

Phase 1: Immediate Documentation (The "Golden Hour")

• Record the exact time and date of the event: [__________]
• Identify the specific location of the incident: [__________]
• Log the names and titles of all parties involved: [__________]
• Note environmental conditions (e.g., lighting, weather) if relevant to the site: [__________]

Phase 2: Narrative Drafting

• Write a chronological account using the "Who, What, When, Where, Why, and How" framework.
• Use plain, objective language (e.g., "The individual shouted" instead of "The individual was aggressive").
• Quote statements directly using quotation marks: "[__________]"
• Avoid speculation, opinions, or emotional descriptors.

Phase 3: Evidence Integration

• List all attached evidence (e.g., "Attachment A: CCTV footage from Camera 04").
• Document the chain of custody for any physical items seized or recovered.
• Include contact information for all third-party witnesses: [__________]

Phase 4: Review and Submission

• Perform a final read-through to ensure the report is free of grammatical errors and omissions.
• Submit the report to the Shift Supervisor for validation: [__________]
• Confirm receipt of the report via [System/Email/Logbook]: [__________]

5. Quality Assurance & Pro-Tips

• The "Objective Test": If a person reading your report cannot visualize the event without your personal opinion, it is not objective enough.
• Pro-Tip: Always document what you did in response to the event. A report that describes a problem but not the security response is incomplete.
• Common Pitfall: Using "we" or "I" excessively. Focus on the actions taken and the events observed. Avoid jargon or acronyms unique to a specific shift.

6. FAQs

Q: Should I include my personal opinion on why the incident happened? A: No. Stick strictly to observable facts. If you must note a suspicion, preface it with "It appeared that..." or "Based on [evidence], it is possible that..."

Q: What if I make a mistake while writing the report? A: If using a digital system, follow the revision history protocol. If using a physical logbook, draw a single line through the error, initial it, and write the correction next to it. Never use correction fluid or obscure the original text.

Q: How soon after the incident should I file the report? A: Reports must be completed and submitted before the end of the shift in which the incident occurred to ensure the freshest memory.