Can this form be signed electronically?

Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided the four-part validity test is met: intent, consent, attribution, and retention.

When is notarization required?

Notarization depends on jurisdiction and whether the document must serve as an affidavit or contain a legally acknowledged signature; check state notary rules and agency requirements before relying on notarization status.

What if the requester lacks authority?

If the signer is not authorized, responders may refuse nonconsensual transport or require additional verification; document the attempted authorization and contact the responsible legal representative.

How do I correct mistakes after submission?

Do not alter the original record. Submit an amended request or add an addendum that references the original submission and explains the correction, preserving the audit trail.

Are there privacy or HIPAA concerns?

Yes. When health information is included, apply HIPAA safeguards and, if required, a Business Associate Agreement (BAA) with the eSignature vendor to lawfully transmit protected health information.

How long until a response is expected?

Response time varies by priority level and local dispatch capability; the request should capture triage level and expected ETA, and responders should provide an acknowledgment with estimated arrival.

Electronic Signature
Templates
Miscellaneous
Emergency Rescue Request

Emergency Rescue Request

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

EMERGENCY RESCUE REQUEST AND SERVICE AGREEMENT

This Emergency Rescue Request and Service Agreement (the Agreement) is entered into by and between:

Requester Name:

Service Provider Name:

WHEREAS

WHEREAS, Requester requires immediate emergency rescue services in connection with an incident described below; and

WHEREAS, Service Provider is duly qualified, equipped, and willing to provide emergency rescue services (including but not limited to technical rescue, extraction, stabilization, and emergency medical evacuation) on the terms and conditions set forth in this Agreement; and

WHEREAS, the parties intend to document the scope, payment terms, and legal responsibilities applicable to the requested rescue operation.

REQUEST DETAILS

Primary Contact Name Primary Contact Phone Primary Contact Email Requester Address Incident Location (if different)

Incident Date: Incident Time:

Type of Emergency (select all that apply)

Technical Rescue Medical Evacuation Fire-Related Other:

Number of Persons Involved Known Hazards or Special Conditions

SCOPE OF WORK

Service Provider shall perform emergency rescue services as requested and reasonably required to mitigate immediate life-safety threats, stabilize affected persons and property, and arrange transport or transfer as appropriate. Specific tasks to be performed are described below and will be executed in accordance with recognized rescue standards and Provider's operational protocols:

Detailed Scope of Work

PAYMENT TERMS

Requester agrees to pay Service Provider for services rendered and for reasonable equipment, personnel, and transportation costs as set forth below. Requester acknowledges that emergency operations may require immediate mobilization and that charges may be incurred even if the rescue is unsuccessful or aborted for safety reasons.

Estimated Total Amount Deposit or Mobilization Fee Payment Schedule / Terms

Late Fee: If payment is not received when due, Requester shall be responsible for late fees and all collection costs, including reasonable attorney fees.

TERM AND TERMINATION

This Agreement becomes effective upon the first mobilization by Service Provider in response to a Request and continues until completion of the specific rescue operation, unless otherwise terminated in accordance with this section.

Anticipated Operation Start Date: Anticipated Operation End Date:

Either party may terminate this Agreement for material breach if the breach remains uncured after days' written notice. Service Provider may suspend operations immediately where safety concerns exist or where Requester fails to remit required deposits or cooperate with rescue operations.

CONFIDENTIALITY

The parties acknowledge that certain information exchanged in connection with rescue operations may be sensitive. Except as required by law or to effect rescue, emergency medical care, or to comply with mandatory reporting obligations, each party shall maintain as confidential any non-public information received and shall not disclose such information without the other party's prior written consent.

ACKNOWLEDGMENT OF RISK, LIABILITY, AND INDEMNIFICATION

Requester acknowledges that emergency rescue operations involve inherent risks, including personal injury and property damage. Requester accepts such risks to the extent permitted by law and agrees to indemnify, defend, and hold harmless Service Provider, its officers, employees, contractors, and volunteers from any claims, liabilities, losses, damages, costs, and expenses (including reasonable attorney fees) arising from Requester's acts or omissions, except to the extent caused by the gross negligence or willful misconduct of Service Provider.

I acknowledge and agree to the foregoing indemnification and assumption of risk:

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the state indicated below, without regard to conflict of law principles. The parties submit to the exclusive jurisdiction of the federal and state courts located in that state for resolution of disputes.

Governing State

ENTIRE AGREEMENT

This Agreement 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 oral or written. Any amendment or modification of this Agreement must be in writing and signed by authorized representatives of both parties.

NOTICES

All notices required or permitted under this Agreement shall be in writing and delivered to the addresses set forth in this form or to such other address as a party may specify in writing. Notices are effective upon receipt.

Requester Emergency Contact (Name & Phone) Special Access or Entry Instructions

Requester Printed Name:

By:

Date:

Service Provider Printed Name:

By:

Date:

What an Emergency Rescue Request Is and when it’s used

An Emergency Rescue Request is a formal document used to request urgent rescue, extraction, or emergency assistance from a responding agency, private rescue provider, or coordinated incident command. It records the requester, location, nature of the emergency, priority level, and any immediate medical or safety needs. The form establishes facts and authorizations needed for responders, triage, transport, billing, and legal records. Where permitted, the request can be executed electronically and retained as a legal record under U.S. e-signature law (ESIGN/UETA) if the four-part validity conditions are met.

Why a clear Emergency Rescue Request matters

A complete, well-structured request speeds response, clarifies scope of assistance, and documents consent, location, and hazards for liability and billing. Accurate forms reduce confusion at handoff and support post-incident reporting and claims.

Which people and organizations commonly prepare these requests

Common preparers include on-scene incident commanders, attending medical staff, property managers, and authorized family or authorized representatives acting on behalf of an incapacitated individual.

Proper role identification on the form ensures the requester has authority to consent, which is critical for legal and billing purposes.

Stepwise process to complete and submit a request

Follow these chronological steps to ensure the request is actionable and accepted by responders.

01

1. Identify Scene: Confirm exact location and hazards for responders.
02

2. Gather Patient Data: Collect name, status, and immediate medical needs.
03

3. Set Priority: Assign triage level and special equipment needs.
04

4. Authorize and Submit: Signer provides consent and transmits the form to dispatch.

Parallel tasks to prepare while waiting for response

These concurrent actions improve safety and readiness during responder travel time.

01

Secure Area:

Clear bystanders and mark hazards to protect responders and victims.

02

Stabilize Patient:

Provide first aid within your scope while awaiting rescue.

03

Document Injuries:

Note visible injuries, vitals, and medications administered.

04

Confirm Access:

Ensure gates unlocked or designate entry point for crews.

05

Prepare ID:

Have patient ID and insurance info ready for handoff.

06

Record Witnesses:

List names and contact numbers of witnesses present.

How an electronic submission typically flows

This summarizes the information flow from requester to receiving agency when submitting electronically.

Create Request: Complete form and attach images or location coordinates.
Authenticate Signer: Confirm identity via phone, SMS code, or on-site badge.
Transmit to Dispatcher: Send via secure portal, email, or integrated dispatch system.
Receive Confirmation: Dispatcher acknowledges receipt and provides ETA.

Typical digital workflow settings for online completion

Configure these fields in your e-submission tool to ensure consistent intake and routing.

Field	Configuration
Authentication	SMS code or email OTP
Required Attachments	Photos, GPS coordinates
Routing	Dispatch queue or agency inbox
Notifications	ACK to requester and on-call supervisor

Technical considerations for eSubmission and integration

Ensure the platform you use supports secure transmission, audit logging, and required integrations for dispatch systems.

File Formats: PDF, DOCX, JPG accepted for attachments
Integrations: Supports CRM, dispatch, and cloud storage systems
Authentication: Phone/SMS, knowledge-based, or SSO options

These features help preserve the record for liability, auditing, and downstream billing while maintaining chain-of-custody for evidence.

Core elements to include on a professional request

A standard Emergency Rescue Request should collect the minimal data needed to dispatch, treat, and document the incident.

Requester Identity

Full name and organizational role for authorization and follow-up.

Accurate Location

Street address plus GPS or detailed landmark description.

Incident Description

Concise description of the emergency and immediate hazards.

Triage Code

Clear priority or severity level for resource allocation.

Attachments

Photos, diagrams, and medical information pertinent to rescue.

Signatures

Authorized signature and date, with signer role noted.

Security and compliance items to capture

Encryption: TLS 1.2/1.3 required

Storage: AES-256 at rest

Audit Trail: Timestamps and IP logs

Access Control: Role-based permissions

BAA Option: HIPAA BAA available

Retention: Immutable export options

Key penalties and operational risks of incorrect requests

Delayed Response: Longer arrival time

Misrouting: Wrong agency dispatched

Legal Exposure: Liability for inadequate consent

Billing Errors: Incorrect payer on record

Evidence Loss: Incomplete audit trail

Regulatory Violation: Privacy noncompliance

Common mistakes to avoid when preparing the request

Providing a partial or ambiguous location which forces responders to spend time locating the scene and can delay rescue.
Entering an incorrect or missing contact number that prevents dispatch from clarifying hazards or obtaining consent.
Failing to document special access instructions (gates, codes, or hazardous materials) that impede safe entry by responders.
Attaching low-quality photos or no GPS data, reducing situational awareness and increasing risk during approach.

Representative eSignature vendor pricing and capability snapshot

Compare common plan starting prices and basic capabilities for eSignature providers; signNow is listed first per benchmarking guidance.

	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 (no credit card)	Varies	Varies	Yes, limited	Yes, limited
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies

Common questions and practical answers

These frequently asked questions address legality, signatures, notarization, and common processing issues for Emergency Rescue Requests.

Need help? Contact support

Can this form be signed electronically?
Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided the four-part validity test is met: intent, consent, attribution, and retention.
When is notarization required?
Notarization depends on jurisdiction and whether the document must serve as an affidavit or contain a legally acknowledged signature; check state notary rules and agency requirements before relying on notarization status.
What if the requester lacks authority?
If the signer is not authorized, responders may refuse nonconsensual transport or require additional verification; document the attempted authorization and contact the responsible legal representative.
How do I correct mistakes after submission?
Do not alter the original record. Submit an amended request or add an addendum that references the original submission and explains the correction, preserving the audit trail.
Are there privacy or HIPAA concerns?
Yes. When health information is included, apply HIPAA safeguards and, if required, a Business Associate Agreement (BAA) with the eSignature vendor to lawfully transmit protected health information.
How long until a response is expected?
Response time varies by priority level and local dispatch capability; the request should capture triage level and expected ETA, and responders should provide an acknowledgment with estimated arrival.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now