Establishing secure connection…Loading editor…Preparing document…

Incident Statement of Facts

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

Incident Statement of Facts

Identification

Reporting Party Name:

Incident Details

Incident Reference Number:

Date: Time:

Persons Involved and Witnesses

Total persons involved:

Witnesses present:

Sequence of Events (Statement of Facts)

Provide a chronological, factual description of what occurred. Include actions, statements, and observable facts. Refrain from speculation.

Damage, Injury, and Evidence

Property damage observed:

Estimated monetary amount (if known): $

Injuries reported:

Evidence collected (check all that apply):

Notifications and Actions Taken

Law enforcement notified:

Use, Confidentiality and Legal Notice

Use and Disclosure: This statement of facts is provided for the purpose of documenting the incident and may be used by the reporting organization, investigators, insurance carriers, and law enforcement. Disclosure may be required in legal or administrative proceedings. The reporting party should not expect absolute confidentiality.

Legal Notice: I understand that false statements in this document may subject me to civil or criminal liability under applicable law. I make this statement voluntarily and based on my personal knowledge, observation, or reasonable inquiry.

Attachments and Supporting Documents

Certification and Signature

Certification: By signing below, I certify under penalty of perjury that the information contained herein is true, accurate, and complete to the best of my knowledge and recollection. I understand that this statement may be relied upon in investigations and proceedings.

Reporting Party:

Signature:

Date:

Receiving Official:

Signature:

Date:

Enter text✕

What an Incident Statement of Facts Is and When It’s Used

An Incident Statement of Facts is a written record that documents the who, what, where, when, and how of a specific incident. It organizes observed facts, witness details, and immediate actions taken so the account can be used for internal review, insurance claims, disciplinary processes, or legal proceedings. The statement should be factual, chronological, and limited to direct observations or first-hand knowledge; avoid speculation, opinion, or admissions that extend beyond what the recorder actually saw or heard.

Why a Clear Statement of Facts Matters

A concise, well-structured statement preserves evidence, clarifies timelines, supports claims or investigations, and reduces disputes. Accurate statements improve internal investigations and make insurance or legal reviews more efficient while protecting the rights of all parties involved.

Why a Clear Statement of Facts Matters

Who Typically Prepares and Receives These Statements

Organizations and individuals prepare incident statements whenever a factual account is needed for review, claim, or recordkeeping.

  • Supervisors and managers who document workplace accidents and safety incidents for internal investigation and OSHA reporting.
  • Employees or witnesses asked to record their first-hand observations for HR, insurance, or legal purposes.
  • Claims adjusters, risk managers, and legal teams who rely on signed factual statements during evidence collection and adjudication.

Keep copies with the incident file and distribute only to authorized recipients to preserve confidentiality and chain-of-custody.

Typical Signatories

Witness

A witness is a person with first-hand observations who signs to attest to their direct observations. Their narrative should be limited to what they personally saw, heard, or did; include contact information for follow-up.

Investigator

An investigator or supervisor attests that the statement was collected as part of an inquiry. Their signature confirms the record’s capture date, any attachments, and whether the signer was informed of the purpose and how the record will be used.

Essential Security and Legal Attributes

Preserve Original: Keep original signed copy
Tamper Evidence: Use audit trail or tamper log
Authentication: Confirm signer identity
Confidentiality: Limit access to authorized parties
HIPAA Awareness: Protect PHI when applicable
Retention Policy: Store per record retention

Key Risks of Inaccurate or Incomplete Statements

Evidentiary Weakness: Incomplete facts reduce admissibility
Insurance Denial: Missing details can trigger claim disputes
Disciplinary Errors: Faulty statements may lead to unfair outcomes
Perjury Risk: Intentional falsehoods can carry legal penalties
Loss of Trust: Contradictions damage credibility
Data Exposure: Improper sharing may breach privacy rules

Common Preparation Errors to Avoid

  • Including opinion or conjecture rather than strictly observable facts leads to disputes and weakens the statement's reliability.
  • Failing to record exact dates and times undermines timelines and can make cause-and-effect analysis inconclusive during investigations.
  • Omitting witness contact details prevents follow-up verification and increases the likelihood that a claim will be challenged.
  • Using inconsistent names or misspelled identifiers (e.g., legal names vs. nicknames) complicates cross-referencing with other records.

Real-World Examples of How Statements Are Used

Sample scenarios illustrate practical uses: workplace safety, property damage, and customer incidents where a factual account is required.

Workplace Injury

An employee documents a slip and fall in the breakroom, noting exact time and surface conditions.

  • The investigator records witness names and immediate first aid rendered.
  • The completed statement enabled timely OSHA reporting and an insurance claim review without conflicting accounts, reducing administrative delay and preserving medical timelines for claims processing.

Property Damage

A delivery driver records vehicle damage after a loading dock impact, including photos and measurements.

  • The driver names two witnesses and notes weather conditions.
  • The signed statement and photo attachments supported the carrier’s claim submission and clarified fault during a quick liability determination, avoiding prolonged dispute.

How to Complete an Incident Statement of Facts

Follow a clear, chronological approach: record fixed facts, attach evidence, and obtain signatures to create a reliable record.

  • 01
    Identify Parties: List full legal names and contact details.
  • 02
    Record Date/Time: Use MM/DD/YYYY and 24-hour or AM/PM format.
  • 03
    Describe Events: State observations chronologically and objectively.
  • 04
    Collect Signatures: Signer initials, printed name, signature, and date.

Typical Document Flow and Handling

A standard flow ensures accountability: capture, verify, route, and store securely with access controls and audit trails.

  • Capture: Create statement and collect attachments immediately.
  • Verify: Confirm identities and gather witness contacts.
  • Route: Send to HR, safety, or claims teams with timestamps.
  • Store: Archive signed record with restricted access.

What a Professional Incident Statement Includes

A complete statement balances brevity and completeness: clear header, factual narrative, corroborating details, and authenticated sign-off to support review or legal use.

Header

Document title, unique ID, preparer name, department, and capture date so reviewers can track the record.

Incident Details

Exact date, time, and precise location including building, room, or GPS coordinates where relevant for verification.

People Involved

Legal names, roles, contact information, and relationship to the incident for follow-up and witness interviews.

Chronology

Step-by-step factual sequence of events, written in plain language and limited to observed actions and direct quotes where applicable.

Evidence

List and attach photos, video, repair orders, medical reports, or IDs; label each attachment and reference them in the narrative.

Sign-off

Signature block with printed name, date/time, title, and authentication method (wet signature, notarization, or eSignature with audit trail).

Suggested Digital Workflow Settings

Configure the digital form to capture key fields, require attachments, and record an audit trail for each signer.

Field Configuration
Incident Date/Time Required field; MM/DD/YYYY HH:MM format
Witness Contact Phone and email required for follow-up
Photo Attachment Allow multiple images, label each file
Signature Require signer authentication and timestamp

Technical and Integration Considerations

Choose a platform that supports secure eSignatures, an audit trail, attachments, and common integrations for routing and storage.

  • File Formats: PDF, DOCX, and image files
  • Integrations: Connectors to cloud storage and case management
  • Authentication: Email, SMS, or stronger verification

Ensure the platform supports legal requirements (ESIGN/UETA) and organizational retention and access-control policies when routing and archiving records.

Time-Sensitive Actions After an Incident

Timely reporting preserves rights and evidence. Different recipients (employer, insurer, regulator) have their own windows for notification and documentation.

Immediate Response:

Provide first aid and secure scene as soon as safe

Internal Report:

Submit statement within 24–72 hours to preserve memory

Insurance Notice:

Notify insurer per policy timelines, often within days

Regulatory Filings:

File required reports (e.g., OSHA) within statutory deadlines

Evidence Preservation:

Retain physical evidence and digital files immediately

eSignature Vendor Comparison Relevant to Incident Statements

Compare baseline pricing and feature availability for common eSignature providers. signNow appears first for clarity; consult vendor pages for plan details and enterprise options.

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 Limited trial Limited trial
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions About Incident Statements

Answers to common questions about validity, eSigning, notarization, and edits help avoid procedural errors and preserve evidentiary value.


Need help? Contact support

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