Can the form be signed electronically?

Yes. Electronic signatures are legally binding under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws where adopted, provided the signature meets intent, consent, attribution, and retention requirements.

When must serious injuries be reported to OSHA?

OSHA requires reporting workplace fatalities within 8 hours and inpatient hospitalizations, amputations, or loss of an eye within 24 hours (29 CFR 1904.39); follow agency rules for notification method.

What if the incident involves protected health information?

If the report contains PHI, store and transmit under HIPAA controls and ensure a BAA with vendors; HIPAA retention is 6 years (45 CFR §164.530(j)).

Who should be notified after submitting a report?

Route to supervisors, safety/EHS, HR, compliance, and legal as appropriate; notify regulators or insurers when statutory or policy triggers are met.

How long should I retain incident records?

Retain active investigation files until closure plus at least 3 years; follow IRS, HIPAA, and industry-specific retention rules for longer periods.

What if a submitted report has inaccurate information?

Correct errors promptly with an addendum noting the correction date and author; preserve original and amended versions to maintain an auditable record.

Electronic Signature
Templates
Miscellaneous
Incident Reporting Document

Incident Reporting Document

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

Incident Reporting and Response Agreement

Parties

This Incident Reporting and Response Agreement (the Agreement) is entered into between: , Address: (hereinafter "Reporter" or "Party A"), and , Address: (hereinafter "Recipient" or "Party B").

WHEREAS

WHEREAS, Party A has observed or obtained information concerning an incident affecting the operations, personnel, property, or assets under Party B's control; and

WHEREAS, the parties desire to document the facts of the incident, to assign responsibilities for response and remediation, and to establish payment and confidentiality terms for any services rendered in connection with the incident; and

NOW, THEREFORE, in consideration of the mutual covenants contained herein, the parties agree as follows.

Incident Details

Incident Report Number

Incident Date: Time:

Location of Incident Incident Type (select all that apply)

Injury Property damage Near miss Security breach Other

Detailed Description of Incident

Witnesses and Statements

Witness 1 — Name and Contact Witness 2 — Name and Contact

Immediate Actions & Impact

Immediate Actions Taken

Were there injuries? Yes No

Injury Details (if any)

Property damage estimated amount:

Attachments Included

Photographs Related reports Video Other

Attachments description

Scope of Work

The parties agree that the Scope of Work for incident response, investigation, and remediation shall include, without limitation, the following. Party responsibilities and deliverables shall be documented below and are binding if executed by both parties.

Detailed Scope of Work

Payment Terms

If Party B engages Party A or any designated contractor for response or remediation services under this Agreement, the parties agree to the following payment provisions:

Contracted Amount Payment Schedule Late Fee

Payments not made within the agreed schedule shall accrue the late fee and may be subject to suspension of services until payment is made. The prevailing party shall be entitled to recover reasonable collection costs, including attorneys' fees, for enforcement of payment obligations.

Term and Termination

This Agreement shall commence on: and shall continue until: unless earlier terminated as provided below.

Notice Period for Termination

Either party may terminate this Agreement for material breach by the other if the breaching party fails to cure such breach within the notice period specified above. Termination shall not relieve a party of obligations accrued prior to termination, including payment for services performed or costs reasonably incurred.

Confidentiality

Each party acknowledges that in the course of reporting, investigating, and responding to the incident, it may receive Confidential Information of the other party. "Confidential Information" means non-public information disclosed in any form relating to the incident, personnel, technical data, or remediation activities. Each party agrees to: (a) hold Confidential Information in strict confidence; (b) use such information solely for performance of this Agreement; and (c) not disclose Confidential Information to third parties except as required by law or to perform the Scope of Work and subject to written confidentiality obligations. The obligations of confidentiality shall survive termination of this Agreement for a period of three (3) years unless a longer statutory period applies.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to conflict of law principles. Any dispute arising out of or relating to this Agreement shall be resolved in the courts located within that State, and the parties submit to the exclusive jurisdiction of those courts.

Representations and Certifications

The reporting person certifies that the information provided in this incident report is, to the best of their knowledge, true, accurate and complete. The parties further represent that they have authority to enter into this Agreement and to bind the entity they represent.

Entire Agreement

This Agreement, including all attachments, scopes of work, and any written amendments signed by both parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, representations, and understandings, whether written or oral. No amendment or modification shall be effective unless in writing and signed by both parties.

Reporting Person Information

Name Title / Role Contact Information

Acknowledgment

By signing below, each party acknowledges receipt of an executed copy of this Agreement, certifies the accuracy of the information provided, and agrees to perform its obligations hereunder in good faith.

Reporter (Party A) — Printed Name:

By:

Date:

Recipient (Party B) — Printed Name:

By:

Date:

What an Incident Reporting Document Is

An Incident Reporting Document is a standardized record used to capture the facts surrounding a workplace, safety, data, or security incident. It collects essential data such as date and time, location, parties involved, witness statements, immediate actions taken, and supporting evidence. Organizations use the document to initiate investigations, notify regulators or insurers when required, preserve chain of custody for evidence, and create a durable record for corrective actions. When executed electronically, the form can meet ESIGN (15 U.S.C. ch. 96) and UETA requirements for enforceability in the United States.

Why a Clear Incident Report Matters

A complete incident report creates a single authoritative account for investigations, regulatory compliance, insurance claims, and legal defense. Accurate forms reduce ambiguity, speed corrective action, and preserve evidence integrity.

Who Typically Prepares and Reviews These Reports

Many roles interact with incident reports depending on the incident type and organizational structure.

Human resources for employee incidents and disciplinary review.
Safety or EHS teams for occupational injuries and near misses.
IT or security teams for data breaches and system incidents.

Completed reports usually route to supervisors, compliance officers, and legal counsel for review and retention.

Core Sections to Include in a Professional Incident Report

A professional Incident Reporting Document groups information so investigators can follow the event timeline, verify identities, and assess impact without extra follow-up.

Incident Details

Record date, time, exact location, incident classification, and a concise factual narrative that avoids speculation and emotional language.

People Involved

List names, job titles, contact details, and roles (victim, reporter, witness) so investigators can reach and interview relevant parties promptly.

Timeline

Provide a step-by-step timeline of events with timestamps and who performed each action to support root-cause analysis and potential legal review.

Immediate Actions

Document first aid, containment, system shutdowns, notifications, or other mitigation steps taken at the scene and by whom.

Evidence & Attachments

Attach photos, logs, CCTV clips, screenshots, and exported forensic data; describe how and where physical evidence is stored.

Follow-up and Resolution

Note assigned investigators, corrective actions, deadlines, and closure criteria so the incident lifecycle is auditable and trackable.

Security and Compliance Elements to Protect Report Data

Encryption: TLS 1.2/1.3; AES-256 at rest

Access Controls: Role-based permissions only

Audit Trail: Timestamps, IP, and action log

HIPAA: BAA required for PHI

Retention Controls: Policy-based deletion schedules

Authentication: Multi-factor where required

Step-by-Step: Completing and Submitting the Report

Follow these steps to prepare a clear, auditable incident report that supports timely investigation and required notifications.

01

Prepare the Form: Gather IDs, witness contacts, and evidence.
02

Record Facts: Enter timestamps and objective observations.
03

Attach Evidence: Upload photos, logs, or screenshots.
04

Sign and Submit: Apply signature and route to stakeholders.

Configuring an Online Incident Reporting Workflow

Design fields, routing, and notifications to match your investigation and escalation requirements before publishing the form.

Field \| Configuration	Visible \| Required \| Conditional
Reporter Contact	Required \| Email + phone
Severity Level	Dropdown \| Triggers escalation
Attachment Upload	Accept PDFs, JPGs \| Max 50 MB
Escalation Rule	Automatic email \| Safety manager

Where a Completed Incident Report Typically Goes

Route completed reports to the right recipients automatically to ensure timely review and follow-up.

Internal Portal: Stored in secure incident management system.
Email Notification: Automatic alert sent to assigned reviewers.
Regulatory Agency: Forward when reportable by law or regulation.
Insurance Carrier: Send claims-related reports to insurer.

Technical Considerations for eSubmission and Distribution

Choose software that supports secure uploads, role-based access, and audit trails for signed forms.

Integrations: Salesforce, NetSuite, Microsoft 365
File Types: PDF, DOCX, JPG accepted
Authentication: Email, SMS code, or SSO

Typical Reporting Deadlines and Timing Expectations

Different incident types trigger different reporting windows. Plan for internal escalation immediately and external notifications where law requires them.

Immediate Internal Notice:

Report to supervisor or safety team within 24 hours.

OSHA Severe-Injury Reporting:

Fatality within 8 hours; inpatient hospitalization within 24 hours (29 CFR 1904.39).

Data Breach Notification:

State breach laws typically require prompt notice; timelines vary by state.

Insurance Claims:

Submit as soon as facts are known to preserve coverage.

Internal Investigation Start:

Begin fact-gathering within 24–72 hours of report.

Common Errors to Avoid When Preparing a Report

Omitting exact timestamps and locations, which complicates timeline reconstruction and can undermine root-cause analysis.
Using speculative or emotional language instead of factual descriptions, which weakens admissibility and clarity.
Failing to collect or label evidence properly, damaging the chain of custody and impairing investigations or insurance claims.
Not routing the completed report to required stakeholders, causing missed regulatory notifications or delayed corrective actions.

Consequences of Incomplete or Late Incident Reporting

Regulatory Fines: Civil penalties and citations

Insurance Denial: Claim rejection risk

Legal Exposure: Weaker defense in litigation

Operational Risk: Recurring hazards unaddressed

Reputational Harm: Public trust erosion

HIPAA Violations: Monetary penalties possible

eSignature Pricing Landscape for Incident Reporting Workflows

Platform pricing and feature limits affect total cost for high-volume incident reporting; signNow is listed first for vendor comparison as requested.

	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	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	Yes	Yes	No	No

Frequently Asked Questions About Incident Reporting Documents

Answers to common questions about form validity, electronic signatures, required timelines, and recordkeeping when using an Incident Reporting Document.

Need help? Contact support

Can the form be signed electronically?
Yes. Electronic signatures are legally binding under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws where adopted, provided the signature meets intent, consent, attribution, and retention requirements.
When must serious injuries be reported to OSHA?
OSHA requires reporting workplace fatalities within 8 hours and inpatient hospitalizations, amputations, or loss of an eye within 24 hours (29 CFR 1904.39); follow agency rules for notification method.
What if the incident involves protected health information?
If the report contains PHI, store and transmit under HIPAA controls and ensure a BAA with vendors; HIPAA retention is 6 years (45 CFR §164.530(j)).
Who should be notified after submitting a report?
Route to supervisors, safety/EHS, HR, compliance, and legal as appropriate; notify regulators or insurers when statutory or policy triggers are met.
How long should I retain incident records?
Retain active investigation files until closure plus at least 3 years; follow IRS, HIPAA, and industry-specific retention rules for longer periods.
What if a submitted report has inaccurate information?
Correct errors promptly with an addendum noting the correction date and author; preserve original and amended versions to maintain an auditable record.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now

Field \| Configuration	Visible \| Required \| Conditional
Reporter Contact	Required \| Email + phone
Severity Level	Dropdown \| Triggers escalation
Attachment Upload	Accept PDFs, JPGs \| Max 50 MB
Escalation Rule	Automatic email \| Safety manager