Establishing secure connection…Loading editor…Preparing document…

Emergency Response Earthquake Form

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

EMERGENCY RESPONSE EARTHQUAKE FORM

Client Name:     Response Provider:

RECITALS

WHEREAS, Client requires emergency response services and post-event incident documentation in the event of an earthquake affecting Client's operations or facilities; and

WHEREAS, Response Provider represents that it has the personnel, equipment, training, and qualifications necessary to perform emergency response, search and rescue, damage assessment, and stabilization services consistent with applicable safety standards; and

WHEREAS, the parties desire that this document serve as both a binding agreement governing emergency-response services and a contemporaneous incident report that documents actions, conditions, and resource deployment.

SCOPE OF WORK

The Response Provider shall perform the following services when activated for earthquake response. Describe anticipated scope, deliverables, and constraints in detail below.

PAYMENT TERMS

Client will pay Response Provider for services and reasonable, documented expenses in accordance with the amounts and schedule set forth below. Payment is due in accordance with the invoice terms described. Late payments accrue the late fee described.

TERM AND TERMINATION

This Agreement becomes effective on the Start Date and shall remain in force until the End Date or until earlier termination as set forth below.

Start Date:    End Date:

Either party may terminate for cause upon material breach that remains uncured for the period specified in the notice requirement above. Termination shall not relieve Client of payment obligations for services already performed.

CONFIDENTIALITY

Each party shall maintain as confidential all non-public information obtained in connection with emergency response operations, including security plans, structural assessments, personal medical information, and proprietary procedures ("Confidential Information"). Recipient may disclose Confidential Information only to its employees, subcontractors, and authorities with a need to know, and only to the extent reasonably necessary. Confidential Information does not include information that: (a) is or becomes public through no breach of this Agreement; (b) was rightfully received from a third party without restriction; or (c) is required to be disclosed by law or competent authority, provided the disclosing party gives prompt notice to the other party when lawful and practicable.

I acknowledge my obligation to protect Confidential Information under this Agreement.

GOVERNING LAW

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

ENTIRE AGREEMENT

This document, together with any attached incident documentation and appendices signed by the parties, constitutes the entire agreement between the parties with respect to emergency earthquake response services and supersedes all prior agreements, representations, and understandings, whether written or oral, relating to the subject matter hereof. Any amendment must be in writing and signed by both parties.

INCIDENT REPORT — EVENT DETAILS

Use this section to record observed conditions, resource deployment, and actions taken at the incident scene.

Incident Date:    Incident Time:

Magnitude/Intensity:    Epicenter / Reference:

Number Injured:

Number Deceased:

Estimated Property Damage ($):

Yes     Partial     No
Shelter(s) activated

CERTIFICATION

The undersigned certify that the information provided in this form is true and correct to the best of their knowledge, that actions recorded above were performed consistent with applicable safety procedures, and that incident documentation will be retained for a period consistent with lawful record retention requirements or as otherwise agreed.

I certify under penalty of perjury or similar sanction that the foregoing is accurate and complete.

Client Name:

By:

Date:

Response Provider:

By:

Date:

Enter text✕

What the Emergency Response Earthquake Form Is

The Emergency Response Earthquake Form is a standardized incident report used by public safety agencies, facilities, and response teams to record immediate event details, damage assessments, injuries, and actions taken after an earthquake. It captures the who, what, when, where, and initial resource needs, producing a single record used for coordination, resource requests, insurance intake, and after-action reviews. When completed promptly and accurately the form supports faster response, clearer handoffs between agencies, and a documented record for reimbursement and recovery planning.

Why a Consistent Earthquake Report Matters

A consistent Emergency Response Earthquake Form reduces ambiguity during chaotic events, enables faster interagency coordination, and creates an auditable record for recovery funding and liability review.

Why a Consistent Earthquake Report Matters

Typical Users and Signers

Agencies and organizations complete this form to document initial response and to support subsequent claims, repairs, or reviews.

  • Local emergency management offices and county EMA coordinators responsible for event logging and mutual aid requests.
  • Campus, hospital, or facility safety officers who document building damage, occupant status, and immediate needs.
  • First responders and field teams who record on-scene actions, casualty counts, and hazardous conditions.

Use this list to identify who on your team should complete, review, and approve the form after an earthquake.

Step-by-step: Completing the Form Quickly

Follow this concise workflow to gather accurate information on scene and submit a usable incident record without delay.

  • 01
    Notify: Record notification time and reporting party contact details.
  • 02
    Document: Enter incident date/time, exact location, and GPS if available.
  • 03
    Assess: Summarize injuries, structural damage, and hazardous conditions.
  • 04
    Submit: Attach photos and send to the designated agency or archive.

Essential Sections of a Professional Earthquake Report

A well-constructed Emergency Response Earthquake Form balances structured data for systems with free-text fields for narrative observations and action steps.

Header

Form ID and version, incident name, and initial reporter details so records remain traceable across systems and revisions.

Event Details

Date/time, exact location, coordinates, magnitude if known, and whether the event is ongoing — critical for prioritizing response.

Damage Assessment

Structured damage categories (infrastructure, buildings, utilities) plus estimated severity to support resource allocation and insurance metrics.

Casualty Report

Counts for fatalities, serious injuries, minor injuries, and displaced persons with age or special-needs annotations as needed.

Actions Taken

Immediate response actions, agencies involved, resources deployed, sheltering locations, and outstanding needs to support continuity of operations.

Attachments

Photos, video, maps, and inspector checklists attached in native formats to preserve evidence and contextual detail for reviewers.

Required Data Elements and Security Notes

Reporter Name: Full name required
Agency Identifier: Agency or unit code
Timestamp: MM/DD/YYYY HH:MM
Location Data: Address plus GPS
Photo Attachments: JPEG/PNG preferred
Authentication: Record signer method

From Field Entry to Central Repository

This shows the typical routing: capture on scene, verify, and send to the responsible archive or operations center.

  • Capture: Complete form on mobile or paper on scene.
  • Verify: Supervisor reviews for completeness before submission.
  • Route: Send to EMA, facility leadership, or archive.
  • Archive: Store in records with audit trail and attachments.

Configuring an Online Submission Workflow

Map form fields to your digital workflow and set authentication, attachments, and retention to match agency rules.

Field Configuration
Authentication Email + optional SMS code or agency SSO
Conditional Fields Show detailed damage fields when 'major' is selected
Attachments Allow photos, video, and PDF up to set size
Retention Setting Set archival period per agency policy

Technical Compatibility and Integration Needs

Confirm supported file formats, authentication options, and integrations before deploying digital forms.

  • File Formats: PDF, DOCX, JPEG supported
  • Integrations: Salesforce, NetSuite, Microsoft 365
  • Auth Options: Email, SMS, SSO

Time-sensitive Submission Deadlines

Certain follow-up reports and retention milestones are time-sensitive; meet these windows to preserve funding eligibility and legal protections.

Immediate Notification:

Report to dispatch and EMA within 24–72 hours of incident

After-Action Report:

Submit detailed assessment within 30 days of initial report

Insurance Intake:

Provide supporting materials within insurer window, typically 30–60 days

Public Records Requests:

Preserve originals until Freedom of Information requests resolved

Retention Start:

Retention clock runs from form creation date

Key Milestones from Event to Closeout

Track these core milestones so teams know what to expect from incident reporting through final archiving.

01

Incident Occurs

On-scene event and initial observations recorded immediately.

02

Initial Report Filed

Representative files the Emergency Response Earthquake Form with basic data.

03

Assessment & Response

Field teams verify damage, report resource needs, and update the record.

04

Final Report Closed

After-action summary and attachments archived; case closed for administrative tracking.

Common Errors to Avoid

  • Incomplete location details (missing street or GPS) cause delays in resource dispatch and damage verification.
  • Using vague damage descriptions rather than standardized severity codes leads to inconsistent triage and funding disputes.
  • Failure to attach timestamps or photos reduces evidentiary value for insurance and grant reimbursement.
  • Missing signer identity or weak authentication can render a report non‑actionable in interagency workflows.

Risks and Consequences of Incorrect Reporting

Delayed Response: Slower resource allocation
Funding Loss: Denied reimbursement claims
Liability Exposure: Increased legal risk
Regulatory Noncompliance: Breach of agency rules
Evidence Gaps: Weakened insurance claims
Data Integrity: Unreliable audit trail

Example Use Cases

These archetypal examples show how the Emergency Response Earthquake Form is used in practice by different organizations.

County Emergency Management

A county EMA files an initial report immediately after local shaking

  • the report triggers mutual aid checks and shelter activation
  • the completed form, with photos and resource requests, becomes the basis for state reimbursement and after-action planning.

Hospital Incident Reporting

A hospital documents structural assessment and patient impacts on the form

  • clinical and facilities leads review and sign to confirm triage status
  • the record supports continuity plans and insurance documentation while preserving HIPAA-required protections.

Who Can Legally Sign the Report

Incident Commander

Typically the on-scene officer or designated incident commander who has authority to certify the accuracy of operational facts and request resources. Their signature confirms the report was prepared under official direction and is relied upon for response actions.

Facility Manager

Facility or site manager signs to confirm property condition, occupant welfare, and actions taken to secure the site. Their signature supports insurance claims and administrative follow-up.

Notarization and Witnessing Workflow

When notarization or witnesses are required, follow these authentication steps to preserve legal validity.

01

Prepare Document

Ensure form is fully completed before signing to avoid re-notarization.

02

Signer Identity

Present government ID for notary or use agency SSO for digital authentication.

03

Witness Presence

If state requires witnesses, have them sign and provide contact details.

04

Notary Acknowledgement

Notary completes journal entry and stamps the form.

05

Remote Notarization

Use RON where permitted; follow identity-proofing and recording rules.

06

Retain Recording

Keep RON audio-video per state retention rules when applicable.

07

Attach Proof

Attach notary certificate or witness affidavits to the form.

08

Archive

Store notarized copy in secure records system.

Export Formats and Supporting Attachments

Maintain native attachments and export signed records in standard formats to support downstream review and evidence preservation.

Export Formats

Save signed copies as PDF/A for long-term preservation; maintain original JPEG/MP4 attachments

Supporting Docs

Include inspection checklists, permits, or structural engineer notes as separate attachments

Timestamping

Ensure exports include timestamps and an audit trail for legal admissibility

Compression

Compress attachments thoughtfully to retain evidentiary quality

How to Update or Amend a Submitted Form

Follow a controlled amendment process to preserve the original record while applying corrections or supplements.

01

Identify:

Note original form ID and amendment reason
02

Annotate:

Record changes with date, author, and rationale
03

Supplement:

Attach new photos or supporting files
04

Review:

Supervisor verifies and signs the amendment
05

Link:

Link amendment to original record in archive
06

Resubmit:

Notify recipients of the updated record

Practical Tips for Accurate and Efficient Reporting

Adopt consistent practices that reduce rework and improve the legal utility of each report.

Use Standard Codes
Adopt agency-approved severity and damage codes to improve triage and later data analysis.
Capture Evidence
Attach clear, timestamped photos and short video clips to corroborate written descriptions.
Authenticate
Record signer identity and consent method; prefer two-factor or SSO for sensitive reports.
Train Staff
Conduct periodic drills on form completion and digital submission to reduce errors under stress.

How This Form Differs from a General Incident Report

Compare common characteristics to determine whether the earthquake-specific form or a general incident report fits your workflow.

Criteria Emergency Response Earthquake Form General Incident Report
Purpose damage and resource needs broad operational log
Timeframe immediate and short-term any incident period
Signatures Required operational leads typical varies widely
Typical Attachments photos, structural notes logs, witness statements

eSignature Vendor Comparison for Earthquake Response Workflows

Compare basic pricing and key capabilities for eSignature providers commonly used to digitize incident reporting and approvals.

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

Frequently Asked Questions

Answers to common operational and legal questions about completing and validating the Emergency Response Earthquake Form.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users