Can the list be e‑signed?

Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted; ensure intent, consent, attribution, and retention capabilities are met before relying on e‑signatures for your jurisdiction.

Is notarization required?

Most emergency contact lists do not require notarization. If a jurisdiction or policy demands notarized attestations, use in‑person or Remote Online Notarization following state rules and record retention requirements.

How often must I update the list?

Update at least quarterly and anytime personnel or contact methods change; rapid updates after hires, departures, or drills reduce the risk of failed notifications during incidents.

Who should sign the list?

Typically the safety officer, facility manager, and an authorized executive sign to attest accuracy. For regulated entities, include any required role specified by policy or statute.

How should I distribute changes?

Distribute new signed versions to stakeholders via secure email, SMS alerts for critical updates, and by posting in a controlled document portal with version history and access logs.

How do I revoke or supersede a prior list?

Issue a new signed version that explicitly supersedes prior versions, annotate the master record with a revocation note, and notify stakeholders of the change to avoid confusion during incidents.

Electronic Signature
Templates
Miscellaneous
Emergency Response Call List

Emergency Response Call List

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

EMERGENCY RESPONSE CALL LIST

This Emergency Response Call List and Service Understanding (the "List") is entered into effective as of by and between Client Name: and Service Provider Name: .

WHEREAS

WHEREAS, the Client operates facilities and assets that require an organized emergency notification and response protocol and associated contact roster for timely notification and deployment of resources; and

WHEREAS, the Service Provider maintains and provides personnel, equipment, or consultancy capable of responding to emergency incidents identified by the Client, and the parties desire to document the primary contacts, escalation sequence, expected response objectives, and administrative terms governing such engagement.

WHEREAS, the parties agree that the following list, procedures, and administrative provisions will be used to effect notification, mobilization and billing for emergency responses.

SCOPE OF WORK

Detailed Scope of Services

EMERGENCY CALL LIST

The following primary and alternate contacts shall be notified according to the escalation procedure. For each listed contact, indicate primary telephone, mobile, pager (if applicable), email, typical availability, and any special instructions.

Primary Contact 1 — Name Organization / Role

Primary Contact 2 — Name Organization / Role

Primary Contact 3 — Name Organization / Role

For additional contacts, attach a supplemental sheet or list each contact in the same format and incorporate by reference into this List.

ACTIVATION & ESCALATION PROCEDURE

Activation and Escalation Protocol

SERVICE LEVELS & RESPONSE OBJECTIVES

Response objectives are target times from notification to arrival on site. These targets are operational objectives and will be used for prioritization and billing where applicable.

PAYMENT TERMS

The Client will compensate the Service Provider for responses and related services in accordance with the following terms.

Standard Response Fee (per activation) Payment Schedule Late Payment Fee

TERM AND TERMINATION

This List commences on Start Date: and continues through End Date: unless earlier terminated in accordance with this section.

Either party may terminate this List for convenience upon written notice delivered at least days prior to the intended termination date. Either party may terminate immediately for material breach if the breach remains uncured for a period of days following written notice.

CONFIDENTIALITY

Each party acknowledges that information shared in connection with emergency incidents, response plans, security details, and contact lists is Confidential Information. Confidential Information shall not be disclosed to third parties except as required to effect response, as required by law, or pursuant to a valid order of a government authority. Each party shall use at least the same degree of care to protect Confidential Information as it uses for its own similar information, but in no event less than reasonable care.

Confidentiality Acknowledgement I acknowledge and agree to the Confidentiality clause.

GOVERNING LAW

This List shall be governed by and construed in accordance with the laws of the State/Province of without regard to choice-of-law principles.

ENTIRE AGREEMENT

This List, including all attachments and incorporated schedules, constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior oral and written proposals, negotiations, and communications related to emergency notification and response covered herein.

AMENDMENTS

Amendments to this List, including updates to contact information or response objectives, must be made in writing and signed by authorized representatives of both parties. Emergency contact updates intended for operational use may be distributed administratively but must be incorporated into this List at the next formal revision.

ADMINISTRATIVE INFORMATION

Client Primary Administrative Contact Service Provider Primary Administrative Contact

Client — Printed Name

Party Label:

By:

Date:

Service Provider — Printed Name

Party Label:

By:

Date:

What the Emergency Response Call List Is

An Emergency Response Call List is a concise, organized roster of people, roles, and contact methods used to notify and coordinate responses during an incident. It typically lists primary and backup contacts, escalation order, role responsibilities, and preferred communication channels for on-site staff, contractors, and external first responders. The list is designed for rapid access and clear handoff during emergencies and is often integrated with incident response procedures, shift logs, and digital notification tools to reduce delay and confusion.

Why a Clear Call List Matters

A well‑maintained Emergency Response Call List shortens notification time, reduces coordination errors, and documents accountability for audits. When shared and retained correctly, it supports legal compliance for regulated sectors and can be executed electronically under ESIGN (15 U.S.C. §7001) or state UETA rules when permitted.

Who Maintains and Uses the Call List

Typical owners create and update the list proactively so response teams can act immediately.

Facility managers and safety officers responsible for site operations and incident coordination.
Human resources and security teams that handle employee notifications and off‑hours escalation.
Contractors, vendors, and incident commanders who must be reached during specific emergencies.

Core Elements to Include on a Professional Call List

A professional list balances speed and accuracy: include identification, escalation rules, access notes, and alternative contacts.

Primary Contacts

Name, role, direct mobile, and work phone for first‑line responders; include backup contacts and shift coverage times to avoid gaps.

Escalation Order

Clear ordered steps for who to contact next if prior contacts are unreachable, including time thresholds and required actions at each step.

Alternate Channels

Secondary notification methods such as SMS, voice, email, and push notifications; list vendor or system routing instructions when applicable.

Location Details

Exact site address, building/wing/floor information, assembly points, and any access restrictions emergency teams should know.

Role Responsibilities

Short task assignments tied to each contact (e.g., evacuations, first aid, media liaison) to prevent duplicate efforts during incidents.

Update Log

Date and author of the last revision plus a short change history so recipients can verify currency before acting.

Required Fields to Capture

Incident Contact: Full legal name

Role/Title: Job title or duty

Phone Numbers: Mobile and alternate numbers

Email Addresses: Primary and backup emails

Location Details: Site address and access notes

Notes/Instructions: Special instructions or limitations

How to Complete the Call List Step by Step

Follow a short, repeatable process to collect accurate contact and role information and confirm permission to share.

01

Gather Data: Collect names, phones, emails, roles, and shift hours from HR and site supervisors.
02

Define Escalation: Set ordered contact tiers and timeframes for escalation if a contact does not respond.
03

Verify Consent: Confirm contacts agree to be listed and can be reached by listed methods during incidents.
04

Publish & Train: Distribute the list to stakeholders and include it in tabletop exercises.

Customizing and Completing the List Online

Set up a template and routing rules in your document platform so the list can be updated, signed, and redistributed quickly.

Field	Configuration
Template Name	Emergency Response Call List template
Signers	Safety lead; facility manager; optional witness
Authentication	Email link or SMS code for signer identity
Notifications	Auto‑email on change and version updates

Where to Send and Store Completed Lists

Designate authoritative recipients and archival locations so responders and auditors can retrieve the current version.

Internal Teams: Distribute to safety, HR, facilities, and security teams for operational use.
Dispatch Center: Provide local fire, police, or emergency medical services a version where required.
Third-Party Vendors: Share with significant contractors or building managers under access agreements.
Document Archive: Store final signed copy in a centralized secure repository with versioning enabled.

Distribution Channels and eSubmission Options

Choose channels that match your incident workflow and security requirements.

Email: Simple distribution for routine updates
SMS/Phone: Faster for urgent alerts and two‑way confirmation
Secure Portal: Controlled access with audit logs and role permissions

Integrations with CRM, collaboration, and cloud storage systems help automate updates and preserve audit trails.

Recommended Timing and Update Cadence

Establish a regular schedule and triggers for updates so lists remain accurate through personnel changes and shifts.

Routine Review:

Quarterly review and confirmation of all primary and backup contacts

After Personnel Change:

Update within 48 hours of role or contact change

After Drills:

Revise list within seven days following a full incident drill

Regulatory Trigger:

Update on changes mandated by industry audits or compliance reviews

Ad hoc Reissue:

Redistribute whenever critical contact information is altered

Common Mistakes to Avoid

Using outdated numbers or shared home phones that are not monitored during shifts, causing missed alerts and delayed responses.
Failing to include backups or escalation timeframes, which leaves responders without clear next steps when contacts are unavailable.
Publishing the list without documented consent or data minimization, which can create privacy and regulatory exposures for personal contact data.
Storing a single, unchecked copy only in email draft folders instead of a versioned secure repository with access controls and audit logs.

Consequences of an Incorrect or Missing Call List

Delayed Response: Increased injury or property damage

Regulatory Exposure: Fines or corrective orders

Operational Downtime: Longer recovery and business loss

Liability Claims: Higher legal and insurance costs

Reputational Harm: Loss of stakeholder trust

Noncompliance: Failed audits and remediation

Example Use Cases

Two concise scenarios show how organizations structure and use the Emergency Response Call List during events.

Property Management

When a boiler failure required evacuation, the property manager used the list to notify tenants and contractors within 10 minutes

Escalation moved from onsite manager to regional facilities within 15 minutes
The recorded timestamps and signoffs supported an insurance claim and post‑incident review.

Healthcare Facility

A sudden utility outage triggered the facility's call list; nursing supervisors and engineering were alerted immediately

Backup power and critical patient transfers were coordinated
The signed, time‑stamped list later demonstrated compliance with emergency preparedness protocols.

Practical Tips for Accuracy and Speed

Adopt simple rules and routine checks to keep the list reliable when it matters most.

Single Authoritative Source

Maintain one canonical list in a secured, versioned repository; distribute read‑only copies for operational teams and update only from the master to prevent conflicting versions.

Verify Contacts Regularly

Institute scheduled confirmations (quarterly) and require confirmation after each personnel change; document verification timestamps to show due diligence.

Use Multiple Channels

List at least two independent contact methods per person (mobile, SMS, email); specify preferred channels and whether replies are required for confirmation.

Integrate with Drills

Exercise the list in drills and post‑action reviews; track response times and refine escalation thresholds based on measured performance.

eSignature Vendor Comparison for Executing Call Lists

Common vendor features and starting prices for electronic signing platforms; signNow is listed first per comparison standards.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
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 Call List

Answers to common operational and legal questions when creating, signing, and distributing an Emergency Response Call List.

Need help? Contact support

Can the list be e‑signed?
Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted; ensure intent, consent, attribution, and retention capabilities are met before relying on e‑signatures for your jurisdiction.
Is notarization required?
Most emergency contact lists do not require notarization. If a jurisdiction or policy demands notarized attestations, use in‑person or Remote Online Notarization following state rules and record retention requirements.
How often must I update the list?
Update at least quarterly and anytime personnel or contact methods change; rapid updates after hires, departures, or drills reduce the risk of failed notifications during incidents.
Who should sign the list?
Typically the safety officer, facility manager, and an authorized executive sign to attest accuracy. For regulated entities, include any required role specified by policy or statute.
How should I distribute changes?
Distribute new signed versions to stakeholders via secure email, SMS alerts for critical updates, and by posting in a controlled document portal with version history and access logs.
How do I revoke or supersede a prior list?
Issue a new signed version that explicitly supersedes prior versions, annotate the master record with a revocation note, and notify stakeholders of the change to avoid confusion during incidents.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now