When should I call 911?

Call 911 immediately whenever a threat is specific, mentions a location or time, or includes credible details. Local emergency services will advise on evacuation and search protocols.

Can I use an electronic checklist?

Yes; electronic checklists are valid under U.S. electronic signature laws when they show intent, consent, attribution, and are retained. Use secure platforms that preserve an audit trail.

Do I need a notary for the checklist?

Most incident checklists do not require notarization. Notarization is only needed if an organization or legal process specifically requests an authenticated copy for evidence.

How long must I keep recordings?

Retain call recordings and surveillance evidence for the duration of any investigation and typically 5–10 years depending on jurisdictional and internal retention policies.

Who should sign the completed checklist?

The person who completed the form and the incident commander or security lead should sign and date. Include role titles and contact information for accountability.

What if the caller hangs up?

Document as much as possible immediately — time, caller ID, partial statements, background noises — and notify law enforcement. Preserve phone records through the telecom provider if requested.

Electronic Signature
Templates
Other
Bomb Threat Checklist

Bomb Threat Checklist

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

What the Bomb Threat Checklist Is and When to Use It

The Bomb Threat Checklist is a structured incident form used to capture details when a bomb threat is received by phone, written message, or in person. It records caller identification, time and method of contact, verbatim threat language, device description and location, observed suspicious items or behavior, immediate actions taken, and names of staff or witnesses. Organizations use the checklist to standardize response, support evacuation decisions, preserve evidence, and provide a clear record for law enforcement and later review.

Why a Standard Checklist Improves Response Consistency

A consistent Bomb Threat Checklist reduces ambiguity during high-stress events by ensuring critical details are recorded and shared promptly with responders and law enforcement.

Typical Roles That Complete the Bomb Threat Checklist

The checklist is completed by staff who first receive the threat and by security or incident commanders who document actions taken and notifications made.

Front-desk or reception staff who answer incoming calls and first-contact reports.
On-site security personnel or designated incident commanders managing response and liaison with law enforcement.
Facility managers, campus safety officers, or operations leads who coordinate evacuations and post-incident reporting.

Step-by-step: Using the Checklist During an Incident

Follow a concise sequence: capture information, limit escalation, protect people, and preserve evidence while coordinating with authorities.

01

Receive Threat: Stay calm; keep the caller on the line and record verbatim language.
02

Document Details: Enter time, caller number, voice traits, and exact words used.
03

Notify Authorities: Call 911 immediately if a credible threat exists; inform security leadership.
04

Preserve Evidence: Save recordings, written messages, and physical items without altering them.

Core components to include in a professional Bomb Threat Checklist

A complete checklist combines caller data, event timeline, response actions, and evidence attachments so every incident is reproducible and reviewable.

Caller Information

Fields for originating phone, caller ID, extension, and received-from location are essential to trace and corroborate the event.

Threat Text

Dedicated area for verbatim transcriptions and any written message; avoid paraphrasing to preserve evidentiary value.

Device Location

Specify exact building, floor, room number, parking area, or exterior landmark to direct search and evacuation zones.

Witness Details

Capture names, contact info, roles, and short witness statements to support investigations and interviews.

Immediate Response

Record notifications (911, security, management), evacuation orders, search results, and medical response details.

Attachments & Evidence

Log and attach audio recordings, photos, SMS/email copies, surveillance clips, and chain-of-custody notes.

Technical and privacy controls to protect checklist records

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

Access Logs: Full audit trail for every view and edit.

User Authentication: Multi-factor or SSO for privileged accounts.

Retention Controls: Configurable retention and legal hold options.

HIPAA Support: BAA available where ePHI is present.

Compliance Certifications: SOC 2 Type II and ISO 27001 attestations.

Common mistakes to avoid when completing the checklist

Delaying documentation — waiting even minutes risks losing exact wording and timestamps that investigators need.
Paraphrasing verbatim speech — summaries reduce evidentiary value and complicate threat analysis.
Failing to preserve original artifacts — deleting messages, overwriting recordings, or altering items breaks chain of custody.
Incomplete notification logs — omitting who was told and when creates ambiguity during post-incident review.

Legal and operational risks tied to incomplete or incorrect checklists

Criminal Liability: False reporting may be prosecuted.

Civil Exposure: Negligent recordkeeping can increase liability.

Evidence Loss: Missing recordings weakens investigations.

Failed Compliance: Privacy violations risk regulatory action.

Operational Disruption: Poor records prolong downtime.

Reputational Harm: Mishandled incidents damage public trust.

Where completed checklists should be routed next

After capturing details, route the checklist and attachments to the appropriate internal and external recipients in parallel.

Local Police: Provide a copy to the responding law enforcement officer.
Security Team: Deliver to on-site security for incident command records.
Facilities Manager: Send to facilities for search and recovery coordination.
Records Retention: Store an authenticated copy in secure incident archives.

Suggested digital workflow settings for eSubmission and tracking

Configure automated routing, retention, and authentication so checklists flow to responders without manual delays.

Field Mapping	Map caller, timestamp, and evidence fields to data store for quick search.
Notification Rules	Trigger automatic emails/SMS to security and management on submission.
Authentication	Require SSO or MFA for users accessing sensitive incident records.
Evidence Attachments	Allow uploads of audio, photos, and video with size limits.
Retention Policy	Apply legal hold when law enforcement opens an investigation.

Digital platform capabilities to support checklist workflows

Choose a platform that securely stores records, supports attachments, and produces a tamper-evident audit trail.

File Formats: PDF, DOCX, JPEG, MP4 accepted for records.
Integrations: Works with SIEM, RMS, and communication tools.
Authentication: SSO, MFA, and role-based access control.

Time-sensitive steps and recommended deadlines

Certain steps must be performed immediately; others have defined preservation or reporting windows to meet investigative and regulatory needs.

Immediate Notification:

Call 911 immediately for any credible or specific threat.

Document Within 24 Hours:

Complete the full checklist and attach evidence within 24 hours of the event.

Preserve Recordings:

Retain call recordings and surveillance footage for 5–10 years when subject to RON or notarization requirements.

Internal After-Action:

Conduct review and update policies within 7 days after the incident.

Law Enforcement Requests:

Respond to lawful evidence requests promptly; maintain a chain-of-custody log.

Key milestones in the incident lifecycle

Track milestone progression from initial contact through final reporting to ensure a complete record for review and learning.

01

Threat Received

Call or report logged; initial details recorded immediately.

02

Assessment & Decision

Security evaluates credibility and decides evacuation/search actions.

03

Active Response

Evacuation, search, or shelter-in-place executed; first responders coordinate.

04

Debrief and Reporting

Compile final checklist, evidence packet, and incident report for stakeholders.

Sample eSignature vendor comparison for hosting and signing checklists

Compare common plan features relevant to Bomb Threat Checklist workflows; signNow is listed first per platform ordering rules.

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

Frequently asked questions about the Bomb Threat Checklist

Answers cover common procedural, legal, and technical questions staff ask while completing or storing a checklist.

Need help? Contact support

When should I call 911?
Call 911 immediately whenever a threat is specific, mentions a location or time, or includes credible details. Local emergency services will advise on evacuation and search protocols.
Can I use an electronic checklist?
Yes; electronic checklists are valid under U.S. electronic signature laws when they show intent, consent, attribution, and are retained. Use secure platforms that preserve an audit trail.
Do I need a notary for the checklist?
Most incident checklists do not require notarization. Notarization is only needed if an organization or legal process specifically requests an authenticated copy for evidence.
How long must I keep recordings?
Retain call recordings and surveillance evidence for the duration of any investigation and typically 5–10 years depending on jurisdictional and internal retention policies.
Who should sign the completed checklist?
The person who completed the form and the incident commander or security lead should sign and date. Include role titles and contact information for accountability.
What if the caller hangs up?
Document as much as possible immediately — time, caller ID, partial statements, background noises — and notify law enforcement. Preserve phone records through the telecom provider if requested.

Explore Templates

Notification of Sale Transfer or Assignment Arizona Assignment of Trade Name Application Palm Beach County School Reassignment Form Assignment of Interest in a Geothermal Lease NCIS 757 Form Key Assignment Form

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now