Establishing secure connection…Loading editor…Preparing document…

Incident Security Guard Report

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

INCIDENT SECURITY GUARD REPORT

Parties and Recitals

Client Name:     Security Company:

WHEREAS, Client engages Security Company to provide on-site security services at the location(s) indicated in this report; and

WHEREAS, an incident occurred requiring documentation of facts, actions taken, persons involved, and any evidence collected for the protection of persons and property; and

WHEREAS, Security Company and Client agree that the statements and entries in this report constitute a contemporaneous record prepared by authorized personnel and will be relied upon for incident resolution and any subsequent administrative or legal action.

Incident Details

Incident Date:     Time:

Guard Name:    Guard ID/Badge #:    Shift:

Theft    Assault    Medical Emergency    Alarm Activation    Suspicious Activity    Trespass    Vandalism    Other:

Witnesses

Evidence and Property

Evidence Collected: Photo    Video    Physical Item    Other

Actions Taken

Police Notified: Yes    Report/Case #:

EMS/Medical Notified: Yes    Transported to Hospital: Yes

Injuries and Damages

Supervisor Review

Scope of Work

The following Scope of Work describes the services to which this incident report relates and any additional services required as a result of the incident. Security Company shall perform the services in a professional manner consistent with industry standards.

Payment Terms

Amount Due for Incident Response: $

Late Payment Fee:

Term and Termination

Agreement Start Date:     End Date:

Either party may terminate this engagement for cause or convenience by providing written notice prior to termination. Client remains responsible for payment for services rendered up to termination date.

Confidentiality

All non-public information contained in this report, including witness statements, surveillance media, and chain-of-custody details, shall be treated as confidential by the parties. Neither party shall disclose confidential information except as required by law or necessary for investigation or legal proceedings.

Client acknowledges and agrees to maintain the confidentiality of sensitive materials provided by Security Company: Acknowledged

Governing Law and Entire Agreement

This report and any agreement arising from it shall be governed by the laws of the State of . This document, together with any referenced scopes of work or invoices, constitutes the entire agreement between the parties with respect to the incident and supersedes prior negotiations and understandings.

Certification and Attestation

I hereby certify under penalty of law that the foregoing statements are true and correct to the best of my knowledge and that this report was prepared contemporaneously by an authorized representative of Security Company. I understand that false statements may be subject to civil or criminal penalties.

Client Representative:

By:

Date:

Security Company Representative:

By:

Date:

Enter text✕

What an Incident Security Guard Report Is and When it's Used

An Incident Security Guard Report documents observed security incidents, injuries, property damage, suspicious activity, or policy violations observed by a security officer. It records factual details — who, what, when, where, and how — and supplements evidence such as photos or video. These reports are used for internal investigations, insurance claims, law enforcement referrals, and regulatory compliance. A clear, contemporaneous report preserves memory, supports corrective action, and creates an audit trail when multiple parties review the event.

Why a Clear Incident Report Matters

A well-prepared report preserves facts, protects staff and property, supports insurance and legal processes, and speeds corrective response. Accurate incident records reduce ambiguity and help supervisors, investigators, and external authorities act quickly.

Why a Clear Incident Report Matters

Who Completes and Uses the Incident Security Guard Report

Security officers, site supervisors, loss-prevention teams, HR investigators, and facility managers typically prepare or review these reports.

  • On-site Security Officers who witnessed or responded to the event and can record first-hand observations and actions taken.
  • Supervisors and Shift Managers who review reports, assign follow-up, and escalate to law enforcement or insurance as needed.
  • Loss Prevention and Risk Teams who analyze incidents for patterns and coordinate corrective measures across locations.

Reports serve internal review and external stakeholders; keep copies in site files and route appropriately to HR, legal, or claims teams.

Primary Roles That Sign and Authorize Reports

Site Supervisor

A supervisor reviews completed incident reports, confirms factual accuracy, adds supervisory notes, and authorizes escalation. Supervisors often attach corrective action plans or disciplinary recommendations when grounded in documented facts.

Security Officer

The officer completing the report provides the initial narrative, time-stamped actions, and witness statements. Their signed account is the primary source document used in investigations and insurance claims.

Essential Fields to Include in Every Report

Incident Date: Use MM/DD/YYYY format
Incident Time: Use 24- or 12-hour time with AM/PM
Location: Exact address and area description
Reporting Officer: Full name and badge/ID
Persons Involved: Names, DOB if available
Witnesses: Names and contact info

Step-by-Step: Completing the Incident Security Guard Report

Follow a consistent order to capture facts while details are fresh and to support any downstream review or legal process.

  • 01
    1. Secure scene: Ensure safety and preserve evidence first
  • 02
    2. Record basics: Enter date, time, exact location
  • 03
    3. Describe incident: Write a chronological, factual narrative
  • 04
    4. Attach evidence: Add photos, videos, and witness statements

Where to File and How the Report Moves Through Your Organization

Incident reports should follow a defined routing path so investigators, HR, legal, and insurance receive copies quickly.

  • Local File: Store original signed report in site incident log
  • Supervisor Review: Supervisor reviews and signs, then forwards
  • Risk/Claims: Send copy to risk management and insurance
  • Law Enforcement: Notify and provide report when required

How to Configure a Digital Incident Report Workflow

Define fields, signer roles, authentication, storage, and notifications before rolling out the form to staff.

Field Configuration
Template Lock required fields and make narrative mandatory
Signer Order Officer -> Supervisor -> Risk
Authentication Email + optional SMS code
Storage Secure cloud folder with versioning

Digital Delivery Options and File Formats

Choose a platform that supports eSigning, secure storage, and common formats so reports remain admissible and auditable.

  • File Types: PDF, DOCX, or image files
  • Integrations: CRM, Google Drive, Box, NetSuite
  • Authentication: Email, SMS, or SSO

Typical Timelines and Reporting Deadlines

Certain incidents require immediate action while others follow internal timelines; document-handling deadlines ensure compliance and preserve evidence.

Immediate Notification:

Call emergency services and secure scene immediately if required

Initial Report Filing:

Complete and submit report within 24 hours of the incident

Supervisor Review Deadline:

Supervisor should review within 48 hours of submission

Insurance Notification:

Notify risk management as required by policy, often within 72 hours

Law Enforcement Referral:

Refer to police immediately for criminal matters

Common Mistakes to Avoid When Preparing an Incident Report

  • Using speculative language or conclusions instead of factual, observable details undermines report credibility and can confuse investigations.
  • Failing to attach time-stamped photos, video, or witness contact details reduces the report's evidentiary value during claims or prosecutions.
  • Delaying report completion allows memory decay and may create inconsistencies between witness statements and recorded facts.
  • Editing the original narrative without a clear audit trail or change log raises questions about the report's integrity.

Risks and Consequences of Incomplete or Incorrect Reports

Evidence Loss: May lead to lost claims
Liability Exposure: Inaccurate reports increase legal risk
HIPAA Breach: Unauthorized PHI disclosure risk
Criminal Liability: False statements can trigger charges
Insurance Denial: Insurer may deny coverage
Operational Delay: Slows incident remediation

Practical Tips for Accurate, Efficient Reports

Adopt uniform templates, train officers on field formats, and keep evidence attached to the report to reduce follow-up and preserve records.

Use neutral language
Describe observed facts and direct quotes objectively. Avoid adjectives that imply motive or intent; stick to verifiable actions and times to maintain credibility.
Timestamp everything
Include exact times for arrival, actions taken, and evidence collection. Accurate timestamps help reconcile camera footage and electronic logs during reviews.
Attach media with metadata
Include file names and timestamps for photos and video. Preserving original metadata helps prove authenticity during claims or court proceedings.
Train regularly
Provide scenario-based training and sample reports so officers recognize required fields and the level of detail expected in incident narratives.

Two Typical Incident Report Scenarios

Below are concise, realistic examples showing how a factual narrative and evidence attachments support downstream action.

Late-Night Vandalism

Officer observed broken window and spray paint damage on the east facade at 02:10 AM

  • Officer secured scene and collected two witness statements
  • Photos with timestamps and witness contact details enabled a swift insurance claim and police follow-up, minimizing repair delays and supporting vendor invoicing.

Slip-and-Fall

Customer slipped in the main lobby near the entrance at 11:45 AM after rain tracked inside

  • Officer documented floor condition, obtained witness names, and recorded first aid actions
  • The neutral factual account, medical details, and security camera clips helped HR coordinate the incident review and the insurer assess liability.

eSignature Provider Comparison for Incident Reports

Common selection criteria include starting price, trial availability, bulk send, audit trail, HIPAA support, and envelope caps. Compare core facts below to match operational needs.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial, no credit card Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes (Business Premium) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions About Incident Security Guard Reports

Answers to common questions about form use, eSigning, evidence attachments, and legal considerations for incident reports.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users