Establishing secure connection…Loading editor…Preparing document…

Legal Incident Statement

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

LEGAL INCIDENT STATEMENT

This Legal Incident Statement is executed by Declarant Name: of Address: and provided to Receiving Party Name: at Address: . The incident occurred on Date of Incident: .

RECITALS

WHEREAS, Declarant has personal knowledge of the facts set forth in this statement and is competent to testify to the matters herein; and

WHEREAS, Receiving Party requests a written, sworn description of the events, witnesses, and physical evidence relating to the incident described below for the purpose of investigation, risk assessment, and potential legal proceedings; and

WHEREAS, the parties agree that this statement will be used in accordance with the terms and limitations set forth in this document.

NOW THEREFORE, for good and valuable consideration, the receipt and sufficiency of which are acknowledged, Declarant hereby states the following under penalty of perjury.

1. DEFINITIONS

For purposes of this Statement: "Declarant" means the individual identified above who furnishes this statement; "Receiving Party" means the individual or organization identified above that receives this statement; "Incident" means the event or occurrence described in Section 2 below.

2. INCIDENT SUMMARY

3. INJURY, DAMAGE, AND EMERGENCY RESPONSE

Injuries sustained: No Yes — If yes, describe:

Property damage: No Yes — If yes, describe:

Emergency services notified: Police EMS/Medical Fire Incident report number (if any):

4. WITNESSES

5. EVIDENCE AND DOCUMENTATION

Evidence collected or available (check all that apply): Photographs Video Documents/Records Physical items

6. COOPERATION AND ACCESS

Declarant agrees to cooperate with reasonable requests by Receiving Party, law enforcement, or other authorized investigatory bodies for statements, documents, and access to information relevant to the Incident. Declarant shall not destroy, conceal, or alter evidence relevant to the Incident.

7. CONFIDENTIALITY AND LIMITATIONS ON DISCLOSURE

Unless otherwise required by law or court order, Receiving Party shall treat this statement as confidential investigative material. Receiving Party may disclose this statement to legal counsel, insurers, and governmental authorities when necessary for investigation or legal compliance. Any other disclosure requires prior written consent of Declarant, which shall not be unreasonably withheld.

8. USE OF STATEMENT

This statement may be used as evidence in internal investigations, administrative hearings, insurance claims, and civil or criminal proceedings. Declarant acknowledges that the statement may be relied upon by Receiving Party and may be provided to tribunals or insurers as necessary.

9. CERTIFICATION AND OATH

I, the undersigned Declarant, certify under penalty of perjury under the laws of the applicable jurisdiction that the foregoing is true and correct to the best of my knowledge, information, and belief. I understand that knowingly making a false statement in this document may subject me to civil or criminal penalties.

Do you affirm that the above statement is true and accurate? Yes No

10. REPRESENTATIONS AND WARRANTIES

Declarant represents that the statements herein are given voluntarily, without coercion, and that Declarant has the authority to provide the information described. Receiving Party represents that it will treat the statement in accordance with Section 7 and will use the statement only for legitimate investigatory or legal purposes.

11. NOTICES

Any notices required or permitted under this Statement shall be in writing and delivered to the addresses set forth at the beginning of this document or to such other address as a party may specify in writing.

12. AMENDMENT, WAIVER, COUNTERPARTS

This Statement may be amended only by a written instrument signed by both parties. No failure or delay in exercising any right shall operate as a waiver. This Statement may be executed in counterparts, each of which shall be deemed an original and all of which together shall constitute one instrument.

13. GOVERNING LAW; SEVERABILITY; ENTIRE AGREEMENT

This Statement shall be governed by and construed in accordance with the laws of the jurisdiction in which the Receiving Party is located, without regard to conflict of law principles. If any provision of this Statement is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect. This Statement constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior oral or written statements relating to the same.

14. MISCELLANEOUS

The parties acknowledge that they have read and understood this Statement, that they have had an opportunity to seek independent advice, and that the signatures below constitute a binding affirmation of the facts contained herein to the extent set forth above.

Declarant (Print Name):

By (Signature):

Date:

Receiving Party (Print Name):

By (Authorized Signature):

Date:

Enter text✕

What a Legal Incident Statement Is and When It’s Used

A Legal Incident Statement is a formal, written account describing an event that has legal, safety, regulatory, or employment implications. It records who was involved, what happened, where and when the incident occurred, and any immediate actions taken. Organizations use these statements for internal investigations, insurance claims, disciplinary processes, regulatory reporting, and evidence preservation. The statement is intended to be factual, dated, and signed by the reporting party; accuracy and prompt completion improve evidentiary value and reduce legal exposure in later proceedings.

Why a Clear Incident Statement Matters for Legal and Operational Outcomes

A complete Legal Incident Statement preserves contemporaneous facts, helps meet regulatory reporting obligations, and supports defensible personnel or claims decisions. Under ESIGN (15 U.S.C. ch. 96) and UETA, electronically signed statements are admissible when intent, consent, attribution, and retention are established.

Why a Clear Incident Statement Matters for Legal and Operational Outcomes

Who Typically Prepares and Reviews Incident Statements

Organizations rely on a mix of employees and officials to prepare or review Legal Incident Statements based on role and responsibility.

  • Employees and witnesses complete firsthand accounts promptly after an event to preserve memory and evidence.
  • Supervisors review statements to confirm facts, note corrective steps, and escalate to HR or legal as required.
  • Legal, compliance, or risk teams evaluate statements for regulatory obligations and potential litigation exposure.

Routing usually goes to HR, risk, legal, or the appropriate regulator depending on the incident type and internal policy.

Primary Signatories and Document Owners

Reporting Party

An employee, contractor, or witness who observed or participated in the event. The Reporting Party provides a first-person, contemporaneous narrative, signs and dates the statement, and may be asked to provide follow-up details or clarifications for investigators.

Authorized Reviewer

A supervisor, HR representative, or legal counsel who verifies completeness, records any immediate corrective actions, assigns internal tracking numbers, and directs submission to insurers or regulators when required by policy or law.

Core Elements to Include in a Professional Legal Incident Statement

A thorough statement follows a consistent structure to ensure clarity, traceability, and legal utility across internal and external processes.

Incident Header

Unique identifier, incident date/time, and exact location. Use precise timestamps and physical addresses to tie the statement to other records and surveillance footage if available.

Parties Involved

Full legal names, roles, employer or affiliation, contact information, and badge or employee ID numbers where applicable to avoid identity confusion.

Chronological Narrative

A factual, step-by-step description of events in chronological order, avoiding opinion language and speculation; include objective observations such as injuries, property damage, or policy breaches.

Witness Information

Names and contact details for witnesses, plus brief summaries of their observations and notes about whether written witness statements were collected.

Evidence & Attachments

List photographs, video timestamps, documents, or physical evidence attached; reference file names and preserve originals in secure storage for chain of custody.

Signatures & Dates

Reporting Party signature, printed name, role, and date; reviewer signature and date; include electronic audit trail data if signed digitally.

Required Fields and Key Data Points

Incident Date: MM/DD/YYYY
Incident Time: 24-hour or AM/PM
Location: Street, city
Persons Involved: Full names
Immediate Action: First response
Attachments: Photos, files

Step-by-Step: Completing a Legal Incident Statement

Follow these sequential steps to prepare, verify, and distribute an incident statement that meets legal and internal standards.

  • 01
    1. Record: Document facts immediately while fresh and factual.
  • 02
    2. Attach: Include photos, video timestamps, and supporting files.
  • 03
    3. Sign: Sign and date; capture electronic audit data if used.
  • 04
    4. Route: Send to supervisor, HR, legal, or insurer as policy requires.

Where to File, Send, or Submit the Statement

Destination depends on incident severity, internal escalation procedures, and any legal or regulatory reporting obligations.

  • Internal Records: Store in HR or risk database with restricted access.
  • Employer Reporting: Provide copies to immediate supervisor and HR.
  • Law Enforcement: Forward when the incident involves criminal conduct.
  • Regulator or Insurer: Submit to agency or carrier if required by law or policy.

Configuring an Online Incident Statement Workflow

Set up a repeatable digital workflow to capture statements consistently and preserve audit logs for legal compliance.

Field Configuration Required, conditional, or optional
Authentication Email, SMS code, or stronger
Conditional Logic Show fields based on incident type
Bulk Routing Automate distribution to stakeholders
Audit Trail Retain timestamps and signer details

Digital Signing and Submission: Platform Considerations

Choose a platform that supports secure storage, auditable signatures, and integration with your record systems.

  • Integrations: Salesforce, NetSuite, Microsoft 365
  • Formats Supported: PDF, DOCX, HTML
  • Authentication Options: Email, SMS, KBA, SSO

Typical Deadlines and Timing Expectations

Timely preparation and routing preserve evidence and meet internal and external obligations; these timelines are common organizational standards.

Immediate Preservation:

Preserve physical and digital evidence immediately after the incident.

Initial Report:

Create initial statement within 24–72 hours of discovery.

Supervisor Notification:

Notify supervisor or safety officer within one business day.

HR Submission:

Submit to HR within five business days for personnel issues.

Regulatory Filing:

File with regulators or insurers per their required deadlines.

Common Mistakes When Preparing an Incident Statement

  • Delaying documentation allows memory degradation and reduces evidentiary value; complete statements as soon as safely possible after the event.
  • Including opinions or accusations instead of observable facts can complicate investigations and introduce bias; stick to who, what, when, and where.
  • Failing to attach supporting evidence or to note its preservation location creates gaps in the record and may invalidate conclusions.
  • Using inconsistent names, dates, or identifiers across related records increases risk of misidentification and administrative rejection by insurers or regulators.

Consequences of Inaccurate or Incomplete Statements

Perjury Risk: Criminal liability possible
Civil Liability: Damages or lawsuits
Regulatory Fines: Agency penalties may apply
Employment Action: Discipline or termination
Evidence Spoliation: Loss of admissibility
I-9 Penalties: $281–$2,789 per violation

Real-World Examples of Legal Incident Statements in Use

These brief case summaries show how statements support investigations, claims, and compliance workflows.

Property Damage Claim

A tenant documents a water leak with timestamps and photos

  • Policy: attach receipts and vendor reports
  • Outcome: insurer accepted claim after audit trail verification and supporting evidence preserved, speeding remediation and payment.

Workplace Safety Report

An employee records a slip-and-fall with witness names and ladder inspection details

  • Point: attach safety logs and photos
  • Outcome: internal safety team used the statement to correct procedures, and legal counsel relied on contemporaneous facts during a claims review.

Supporting Documents and Export Options to Attach

Attach standardized supporting documents and choose export formats that preserve audit information and are accepted by regulators and insurers.

Supporting Documents

Photographs, video files, medical reports, and witness statements should be attached and named consistently to maintain chain of custody and support verifiable timelines.

Export Formats

Use PDF/A or PDF with embedded audit trail for long-term preservation; also retain original media files and transcripts separately when available.

Access Logs

Keep detailed access and modification logs to show who viewed or edited the statement and when for audit and evidentiary purposes.

Version Control

Record version history and avoid overwriting original statements; preserve an unalterable master copy when possible.

eSignature Platform Pricing and Capability Snapshot

Compare basic pricing and capability points for common eSignature providers. Confirm current plan details directly with each vendor when finalizing procurement.

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 vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA) Yes (BAA) Yes (BAA) No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Frequently Asked Questions About Legal Incident Statements

Answers to common procedural and legal questions about preparing, signing, and storing incident statements in the United States.


Need help? Contact support

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