Can this report be completed electronically?

Yes. Electronic completion is legally valid when it meets ESIGN Act standards (15 U.S.C. §7001) and applicable state UETA or ESRA rules. Ensure the platform captures a reliable audit trail and retention capability.

Are electronic signatures acceptable?

Most electronic signatures meet legal requirements under ESIGN and UETA when intent, consent, attribution, and reliable record retention are demonstrable. For certain sworn affidavits, notarization or RON may still be required.

When is notarization required?

Notarization is not typically required for an internal incident report, but supporting affidavits or sworn statements may need notarization or RON depending on state law and prosecutorial needs.

How do we protect PHI in reports?

Limit PHI to the minimum necessary, use encrypted transmission and access controls, and execute a Business Associate Agreement if a vendor will handle protected health information under HIPAA.

How should attachments be formatted?

Use native or PDF formats with preserved timestamps; label each file clearly with case number, uploader, and brief description to maintain evidentiary context.

What if information changes after filing?

Document amendments as supplemental reports with timestamps and author attribution rather than editing the original entry, preserving an immutable audit trail for legal review.

Electronic Signature
Templates
Miscellaneous
Terrorism Incident Report

Terrorism Incident Report

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

What the Terrorism Incident Report Is

A Terrorism Incident Report documents the factual details of suspected or confirmed terrorist activity, including time, location, actors, actions, and evidence. It is used by first responders, investigators, public safety officials, and counterterrorism units to create a formal record for operational response, intelligence sharing, prosecution, and interagency coordination while preserving chain-of-custody and privacy obligations.

Why a Clear Report Matters

A complete, contemporaneous report preserves evidence, supports criminal and administrative processes, and enables rapid information sharing with fusion centers and federal partners. Accurate reporting reduces investigative delay, helps protect public safety, and documents actions taken by responding agencies.

Who Typically Prepares and Uses These Reports

Multiple agencies may share and supplement the record; ensure roles for who completes, reviews, and retains the report are clear before final submission.

Local law enforcement agencies assembling an official investigative record for prosecution or referral to federal partners.
Hospital and EMS personnel documenting patient condition and chain-of-custody for evidence that may contain protected health information.
School or campus safety officers recording suspicious activity, threats, or attacks affecting students and staff.

Essential Sections to Include in a Professional Report

A standardized structure improves clarity, reduces follow-up, and supports legal and operational uses. Include consistent headings and discrete data fields for each element below.

Event Overview

A concise summary of what occurred, including date/time, location, type of incident, and immediate outcomes for situational awareness and record indexing.

Actors Involved

Clear descriptions of suspects, victims, witnesses, and responders with identifying information and roles observed during the event for investigative follow-up.

Chronology

A precise timeline of actions and communications with timestamps to reconstruct the sequence of events and identify response gaps.

Evidence and Chain-of-Custody

List collected items, their location, who collected them, and secure storage steps to preserve admissibility and integrity of physical and digital evidence.

Actions Taken

Document immediate tactics, medical care, evacuation, notifications, arrests, or detentions, and any interagency coordination performed at the scene.

Attachments

Reference photos, video, forensic reports, medical records, CAD logs, or other supporting files with clear file names and custody notes.

Required Information Fields at a Glance

Incident ID: Unique case number

Date/Time: MM/DD/YYYY HH:MM

Location: Street, city, state

Reporter: Name and agency

Victim/Suspect: Name or description

Attachments: List of files attached

Step-by-Step: Completing the Report

Follow a consistent sequence to ensure completeness and preserve evidence integrity; document contemporaneously when possible.

01

Identify: Record incident ID, date/time, and exact location.
02

Describe: Write a factual, chronological narrative of observed events.
03

Collect: List evidence and note chain-of-custody actions and storage locations.
04

Attach: Add photos, videos, CAD logs, and medical records as referenced.

How to Configure an Online Report Workflow

Set up digital fields and routing rules so the right parties receive and complete only the sections they must provide or approve.

Field	Configuration
Incident ID Field	Auto-generate unique case number
Date/Time Field	Timestamp on save; editable for correction
Attachments Field	Allow multiple file types (PDF, JPG, MP4)
Routing Rule	Send to supervisor then to fusion center

Where Reports Typically Flow After Completion

After finalization, route the report to internal and external stakeholders according to policy to enable investigation and information sharing.

Internal Records: Local records management system stores official copy for the department.
Supervisor Review: Supervisor verifies factual completeness and approves routing.
Fusion Center: Share with state fusion center for cross-jurisdictional intelligence.
Federal Referral: If terrorism nexus exists, transmit to FBI or designated federal partner.

Technical Options for Digital Completion and Submission

Ensure the platform meets agency policy and applicable privacy law before accepting electronic submissions from third parties or the public.

File Formats: PDF, DOCX, JPG, MP4 supported
Integrations: Connect to RMS, GIS, or evidence management
Security: TLS and AES encryption required

Key Timelines and Processing Expectations

Timely reporting and retention affect investigative utility and legal compliance; record expected processing windows for each step.

Immediate Entry:

Enter initial incident report as soon as scene is secure.

Supervisor Review Window:

Review and approve within 24 hours of submission.

Fusion Center Referral:

Transmit priority incidents within 24 hours when required.

Evidence Transfer:

Transfer physical evidence within 72 hours when feasible.

Public Records Requests:

Anticipate disclosure review timelines as agency policy dictates.

Common Preparation Errors to Avoid

Delayed entry leading to lost detail: waiting to write the narrative reduces accuracy and weakens later testimony.
Incomplete chain-of-custody notes: failing to record who handled evidence or where it was stored undermines admissibility.
Mixing opinion with fact: including conjecture or unverified motives can confuse investigators and complicate prosecutions.
Poor attachment labeling: ambiguous file names or missing timestamps make it hard to match supporting files to report sections.

Legal Risks and Consequences

False Reporting: Criminal liability possible

Evidence Loss: Case dismissal risk

Privacy Violations: HIPAA civil penalties

Delayed Referral: Operational harm

Obstruction: Obstruction charges possible

Civil Exposure: Civil suits for negligence

Practical Examples of Typical Use

Two concise scenarios illustrate how an incident report supports operations and investigation.

Case Study 1

A campus threat was reported at 02:15 with a suspicious device observed near a dorm

Responders secured the scene and documented evacuation procedures
The completed report, photos, and CAD logs enabled rapid referral to state fusion center and supported evidence preservation for prosecution.

Case Study 2

An unattended vehicle with incendiary indicators triggered an officer response at a transit hub

First responders collected witness statements and video evidence on-scene
The structured report and clear chain-of-custody allowed federal partners to correlate similar incidents and coordinate resource deployment.

Frequently Asked Questions

Answers to common questions about electronic completion, signatures, privacy, and evidence handling for terrorism incident reports.

Need help? Contact support

Can this report be completed electronically?
Yes. Electronic completion is legally valid when it meets ESIGN Act standards (15 U.S.C. §7001) and applicable state UETA or ESRA rules. Ensure the platform captures a reliable audit trail and retention capability.
Are electronic signatures acceptable?
Most electronic signatures meet legal requirements under ESIGN and UETA when intent, consent, attribution, and reliable record retention are demonstrable. For certain sworn affidavits, notarization or RON may still be required.
When is notarization required?
Notarization is not typically required for an internal incident report, but supporting affidavits or sworn statements may need notarization or RON depending on state law and prosecutorial needs.
How do we protect PHI in reports?
Limit PHI to the minimum necessary, use encrypted transmission and access controls, and execute a Business Associate Agreement if a vendor will handle protected health information under HIPAA.
How should attachments be formatted?
Use native or PDF formats with preserved timestamps; label each file clearly with case number, uploader, and brief description to maintain evidentiary context.
What if information changes after filing?
Document amendments as supplemental reports with timestamps and author attribution rather than editing the original entry, preserving an immutable audit trail for legal review.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now

Terrorism Incident Report