Do I need to notarize an Emergency E911 Form?

In most cases, notarization is not required for E911 submissions; carriers accept signed records with a verifiable audit trail. However, state-specific rules or provider contracts may require notarization or additional verification—check carrier policies and, for RON, state notary commission rules.

Can I submit the form electronically to my carrier?

Yes where carriers accept electronic submissions. Ensure your platform meets ESIGN/UETA criteria: signer intent, consent, attribution, and record retention. For consumer-facing or PHI-containing forms, provide required ESIGN consumer disclosures and obtain consent to electronic records.

How should phone numbers be formatted?

Use E.164 format for all telephone entries (U.S. numbers use +1 followed by ten digits). Consistent formatting reduces provisioning errors; include DID ranges and trunk details where multiple numbers map to one location.

What happens if a location changes?

Update the Emergency E911 Form immediately and notify your carrier. Carriers typically verify changes within 7–14 business days; failure to update can result in misrouting, regulatory exposure, or service suspension. Document the change and retain version history for audits.

Are there privacy concerns with E911 data?

Yes, if the form includes protected health information or other sensitive data, HIPAA and state privacy laws apply. Limit PHI in the form, secure transmissions with TLS/AES encryption, and execute a BAA with vendors when handling patient information.

How long must I retain signed E911 forms?

Retention varies: keep active records for the service term, retain copies at least three years for tax/business records (IRC §6501(a)), and six years for HIPAA-related records (45 CFR §164.530(j)). Check state rules for longer periods.

Emergency E911 Form

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

EMERGENCY E911 SERVICE AGREEMENT

This Emergency E911 Service Agreement (the "Agreement") is entered into between Client Name: and Service Provider Name: on this date:

WHEREAS

WHEREAS, Service Provider maintains and operates E911 routing, location validation and emergency call-handling services necessary to provide dispatchable location information to public safety answering points for the Client's telephony endpoints; and

WHEREAS, Client requires Service Provider to provision, maintain, and verify E911 information for the Client's sites and endpoints in accordance with applicable technical and operational requirements to enable appropriate emergency response; and

WHEREAS, the parties wish to set forth the scope, payment, confidentiality, term and termination, and governing law for the E911 services to be provided.

SCOPE OF WORK

Scope of services and deliverables

EMERGENCY SITE INFORMATION

Site 1 — Primary Location

Site Name Physical Address Dispatchable Location Description

Primary Phone:

DID / Extension:

Endpoint Type(s)

Analog line VoIP endpoint Enterprise PBX Hosted/Cloud PBX Mobile device

Site Emergency Contact

Site 2 — Additional Location (if applicable)

Site Name Physical Address

Primary Phone:

DID / Extension:

PAYMENT TERMS

Client agrees to pay Service Provider the fees set forth below for the services performed under this Agreement. Fees cover provisioning, verification, testing, and support unless otherwise stated.

Total Fee Payment Schedule Late Fee / Interest

TERM AND TERMINATION

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

Either party may terminate this Agreement for material breach if the breaching party fails to cure the breach within Notice Period: days after receiving written notice. Termination for convenience by either party requires advance written notice of: days and payment of fees for services rendered through the effective termination date.

CONFIDENTIALITY

Each party shall keep confidential and shall not disclose to any third party any non-public information labeled or reasonably understood to be confidential, including but not limited to dispatchable location data, network configuration details, call-routing information, and security credentials ("Confidential Information"). Confidential Information shall be used solely for the performance of this Agreement. Confidentiality obligations shall survive termination for a period of three (3) years, except that obligations with respect to personally identifiable information and dispatchable location data shall survive for the longer period required by law.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of , without regard to principles of conflict of laws.

ENTIRE AGREEMENT

This Agreement, together with any exhibits or attachments executed by the parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals and communications, whether written or oral. No amendment shall be effective unless in writing and signed by authorized representatives of both parties.

ACCURACY AND CLIENT CERTIFICATION

Client certifies that the information provided in this form, including physical addresses, dispatchable location descriptions, and emergency contact information, is accurate to the best of Client's knowledge. Client acknowledges that inaccurate or incomplete information may result in delayed or improper emergency response and may require additional fees for remediation.

Name of person certifying information Title

Client Name:

Printed Name:

By:

Date:

Service Provider:

Printed Name:

By:

Date:

What the Emergency E911 Form Is and when it's used

The Emergency E911 Form is a standardized record used to collect and verify caller location and contact details for emergency response systems, particularly for VoIP, multi-line telephone systems, and hosted telephony services. It captures the physical service address, billing and administrative contacts, and any secondary locations or access notes that 911 operators require. Providers use the form to map telephone numbers to geographic coordinates and to furnish accurate dispatch information to public safety answering points (PSAPs). Accurate completion reduces misrouted calls and speeds emergency response.

Why a complete Emergency E911 Form matters

Using an Emergency E911 Form helps ensure emergency services receive precise location and contact data, improves PSAP accuracy, supports regulatory compliance for service providers, and reduces response delays caused by incomplete or outdated caller information.

Who typically completes and maintains E911 records

Typical users include telecommunications carriers, IT administrators at enterprises, VoIP providers, and government public safety coordinators responsible for provisioning emergency service data.

Telecommunications carriers: collect and submit location data to PSAPs and regulatory bodies.
Enterprise IT: maintain accurate site-of-record addresses for multi-line phone systems and hosted services.
Managed service providers: update E911 records during deployments, migrations, and number reassignments.

Smaller businesses may complete the form when ordering VoIP service; municipalities and emergency coordinators review submissions for accuracy.

Step-by-step: complete and submit the Emergency E911 Form

Follow these steps to complete and submit an Emergency E911 Form for VoIP or hosted telephony services.

01

Collect Details: Gather name, address, phone, and access instructions.
02

Verify Address: Confirm physical dispatch location via map and facilities.
03

Populate Form: Enter fields exactly, include E.164 phone format.
04

Submit to Carrier: Send completed form and supporting documents to provider.

Configure digital workflows for eSubmission

Configuration tips for completing and eSubmitting the Emergency E911 Form using an eSignature platform and provider portals.

Field	Configuration
Signature Auth	Use email link or SMS code; enable 2FA for admin signers.
Conditional Fields	Show suite and access notes when 'multi-unit' selected.
Automatic Fields	Auto-fill signer name and date with Magic fields.
Document Retention	Store signed PDF with embedded audit trail and timestamps.

Delivery channels, formats, and authentication options

Platform and delivery options affect how you collect signatures and store the completed Emergency E911 Form securely.

Supported Formats: PDF, DOCX, and HTML accepted.
Integrations: Connectors for Salesforce, Microsoft 365, NetSuite.
Authentication: Email, SMS, or KBA; enable stronger admin checks.

How an eSubmitted Emergency E911 Form flows to PSAPs

This flow shows how the Emergency E911 Form is routed from completion to PSAP provisioning by carriers and portals.

Prepare: Complete form fields and attach supporting ID or floor plans.
Authenticate: Signer confirms identity via email OTP or account login.
Submit: Send to carrier provisioning team or upload to provider portal.
PSAP Update: Carrier maps number to location and forwards data to PSAP.

Essential elements to include on a professional E911 form

Core elements of a professional Emergency E911 Form focus on location precision, contact verification, access details, and supplier or carrier routing metadata.

Service Location

Exact physical address including street, suite or unit, floor, building name, and internal location descriptors. This is the primary dispatch address PSAPs will use when routing emergency responders.

Routing Number

Telephone number in E.164 format that maps to the service location. Carriers use this identifier to link calls to PSAP records during emergency dialing. Include DID or main trunk identifiers if multiple numbers serve the site.

Administrative Contact

Name and role of the person who can verify or amend the E911 record, and their daytime phone and email. This contact handles carrier queries and emergency coordination.

Access Details

Instructions for responders including building entrance, gate codes, elevator locations, internal directions, restricted access hours, and any hazards. Accurate access notes reduce on-scene response time.

Verification Method

Document the method used to verify address and identity—carrier lookup, utility bill, government ID, or facilities confirmation. Record date, verifier name, and evidence source for auditability.

Retention & Version

Include form effective date, version number, and retention instructions. Retain signed records with audit trail for the period required by HIPAA, IRS, or state regulations as applicable.

Saving, exporting, and attaching supporting documents

Download, save, and attach supporting files in common formats while preserving audit trails and metadata for compliance and PSAP ingestion.

Formats Available

Export signed Emergency E911 Forms as PDF/A for archival, as standard PDF for sharing, or DOCX for editable copies. Ensure embedded timestamps and signer certificate details are preserved.

Audit Trail

Store a certificate of completion with each signed file containing signer IP, timestamps, authentication method, and field-level activity to support legal admissibility. Keep this alongside the PDF for compliance.

Attachments

Include floor plans, utility bills, or facility authorizations as separate attachments. Label files clearly and reference them in the form to avoid processing delays promptly.

Storage Security

Use encrypted storage (AES-256), access controls, and retention policies. Ensure backups and role-based access protect sensitive location data. Maintain incident response procedures and periodic access reviews.

Security and compliance considerations

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

Audit Trail: Detailed timestamps, IPs, and signer activity

HIPAA Compliance: BAA required when PHI included

Legal Frameworks: ESIGN and UETA legal acceptance

21 CFR Support: Controls for FDA-regulated records available

Access Controls: Role-based permissions and SSO support

Common preparation pitfalls to avoid

Using P.O. boxes or billing addresses instead of the physical dispatch location leads to misrouted emergency calls and delays in public safety response.
Mismatched or misspelled names between carrier records and government IDs can cause verification failures and require manual reconciliation before PSAP updates proceed.
Failing to include suite, floor, or unit numbers in multi-tenant buildings makes it hard for responders to locate the caller within a complex structure.
Not updating E911 records after moves, renovations, or numbering changes risks noncompliance with carrier obligations and possible regulatory penalties.

Potential penalties and operational risks

Tax Penalties: 1099 late penalties $60–$330 per form (IRC §6721)

I-9 Violations: $281–$2,789 per violation (8 CFR §274a.2)

Noncompliant E911: Possible service suspension or fines by regulator

Emergency Delay: Increased risk of harm or property loss

Data Breach: HIPAA exposure if health data included (45 CFR §164.502)

Civil Liability: Potential negligence claims if misrouting causes injury

Timing expectations for submissions and updates

Key deadlines and expectations for submitting and updating Emergency E911 Forms with carriers and public safety agencies.

Initial Submission:

Submit before service activation to avoid provisioning delays.

Address Changes:

Update within 30 days of a physical move or renovation.

Number Reassignment:

Notify carrier immediately when numbers are reassigned.

Verification Window:

Carriers may require 7–14 business days for verification.

Audit Responses:

Respond to carrier audits within the stated timeframe to maintain compliance.

Submission milestones from completion to maintenance

Sequential milestones from form completion through PSAP provisioning and ongoing maintenance for a typical Emergency E911 submission lifecycle.

01

Form Completion

Gather and enter verified location and contact information.

02

Provider Verification

Carrier verifies address and may request additional documentation.

03

PSAP Mapping

Number is mapped and PSAP records updated.

04

Ongoing Maintenance

Periodic audits and updates for relocations or facility changes.

Practical examples of electronic E911 form use

Real-world examples show how electronic E911 forms reduce turnaround and keep PSAP records current across property management and enterprise IT deployments.

Martin Properties — Tim Martin

Tim Martin used electronic E911 forms to collect precise unit-level locations across his rental portfolio without site visits.

This cut dispatch confusion on multi-unit properties.
By integrating form submissions into the property management workflow and storing signed PDFs with audit trails, Martin reduced manual follow-ups, accelerated carrier provisioning, and maintained a verifiable history for compliance and incident response.

Xerox — Kodi-Marie Evans

Xerox's NetSuite integration allowed automatic population of E911 fields during device provisioning, reducing manual data entry and errors.

Signatures and audit trails were attached to each record.
That integration ensured accurate routing data reached carriers promptly, simplified compliance reporting, and enabled internal teams to trace changes when addresses or phone mappings changed due to relocations or renumbering.

Practical tips for accurate and efficient completion

Practical recommendations to ensure Emergency E911 Forms are accurate, accepted by carriers, and maintain compliance with recordkeeping rules.

Confirm Physical Dispatch Address Exactly

Verify the site on a map, confirm suite and floor identifiers with facilities, and cross-check against utility or lease documents. Accurate physical descriptors reduce PSAP ambiguity and speed first responder arrival while minimizing carrier follow-up requests.

Use Standard E.164 Phone Formatting

Enter telephone numbers in E.164 format (for US: +1NNNNNNNNNN). Include DID ranges where applicable and note trunking arrangements to ensure carriers correctly map numbers to physical locations. This prevents formatting-related rejections during provisioning.

Document Clear Access and Hazard Instructions

Provide gate codes, hours of restricted access, elevator locations, and any hazardous materials. Use plain language and standard abbreviations; responders rely on concise, actionable directions rather than narrative descriptions during an emergency.

Keep Records Current and Auditable

Retain signed PDFs with embedded audit trails, note version changes and dates, and run periodic audits to confirm carrier and PSAP records match internal data. Quick corrections avoid service interruptions and regulatory exposure.

eSignature vendor pricing and feature comparison for E911 workflows

Compare common pricing and feature dimensions for eSignature plans that are relevant when submitting and storing Emergency E911 Forms.

	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	Verify vendor	Verify vendor	Verify vendor	Verify vendor
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Electronic signature vs digital (PKI) signature: quick comparison

Key distinctions between electronic signatures and cryptographic digital signatures for users of the Emergency E911 Form and compliant systems.

Criteria	Electronic Signature	Digital Signature
Definition	any electronic mark	pki-based cryptographic signature
Technology	image/metadata/click	public-key infrastructure
Legal Status	esign/ueta accepted	esign/ueta accepted
Non-repudiation	audit trail evidence	cryptographic non-repudiation

Frequently asked questions about the Emergency E911 Form

Answers to common questions about completing, submitting, and managing Emergency E911 Forms, including eSignature, notarization, and retention concerns.

Need help? Contact support

Do I need to notarize an Emergency E911 Form?
In most cases, notarization is not required for E911 submissions; carriers accept signed records with a verifiable audit trail. However, state-specific rules or provider contracts may require notarization or additional verification—check carrier policies and, for RON, state notary commission rules.
Can I submit the form electronically to my carrier?
Yes where carriers accept electronic submissions. Ensure your platform meets ESIGN/UETA criteria: signer intent, consent, attribution, and record retention. For consumer-facing or PHI-containing forms, provide required ESIGN consumer disclosures and obtain consent to electronic records.
How should phone numbers be formatted?
Use E.164 format for all telephone entries (U.S. numbers use +1 followed by ten digits). Consistent formatting reduces provisioning errors; include DID ranges and trunk details where multiple numbers map to one location.
What happens if a location changes?
Update the Emergency E911 Form immediately and notify your carrier. Carriers typically verify changes within 7–14 business days; failure to update can result in misrouting, regulatory exposure, or service suspension. Document the change and retain version history for audits.
Are there privacy concerns with E911 data?
Yes, if the form includes protected health information or other sensitive data, HIPAA and state privacy laws apply. Limit PHI in the form, secure transmissions with TLS/AES encryption, and execute a BAA with vendors when handling patient information.
How long must I retain signed E911 forms?
Retention varies: keep active records for the service term, retain copies at least three years for tax/business records (IRC §6501(a)), and six years for HIPAA-related records (45 CFR §164.530(j)). Check state rules for longer periods.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now