Can the Act be signed electronically?

Yes. Electronic signatures meeting the ESIGN Act (15 U.S.C. ch. 96) and state UETA standards are generally valid. Confirm exceptions such as certain court filings or testamentary documents that remain ineligible for e-signature.

Is notarization required for the Act?

Not always. Notarization needs vary by state and by the type of authorization recorded; check local notary statutes and whether the document will serve as a record requiring acknowledgment.

Who should sign the Act for it to be effective?

Authorized governing officials (e.g., city manager, county commission chair) or their delegated designees should sign. Where required, obtain signatures from multiple officials per local ordinance.

What supporting documents should I attach?

Attach member rosters, training matrices, equipment inventories, and indemnity or mutual-aid agreements to ensure the Act functions as an operational instrument.

How do I update or amend the Act?

Amendments should follow the original adoption process—legal review, formal approval by the governing body, and updated records with revised effective dates.

How long must records be kept?

Retention varies: follow federal guidance (e.g., IRS 3-year rule, IRC §6501(a)) and industry-specific rules such as HIPAA six-year retention (45 CFR §164.530(j)). Consult counsel for state-specific requirements.

Electronic Signature
Templates
Miscellaneous
Emergency Response Brigade Act

Emergency Response Brigade Act

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

EMERGENCY RESPONSE BRIGADE ACT

This Emergency Response Brigade Act (the Act) is entered into by and between:

Authority Name: Authority Address for Notices:

Authority Contact Name:

Contact Phone:

Operator Name (Brigade Provider): Operator Address for Notices:

Operator Contact Name:

Contact Phone:

WHEREAS

WHEREAS, the Authority requires trained personnel, equipment, and coordinated operational procedures to provide emergency response services for incidents affecting public safety, property, and critical infrastructure within the Authority's jurisdiction; and

WHEREAS, the Operator maintains a qualified Emergency Response Brigade with trained staff, supervisory personnel, and specified equipment capable of responding to natural disasters, industrial incidents, and other declared emergencies; and

WHEREAS, the parties desire to set forth the duties, activation procedures, compensation, and legal terms governing the Operator's provision of emergency response services to the Authority as set forth in this Act.

SCOPE OF WORK

The Operator shall provide a brigade capable of tactical emergency response, including but not limited to search and rescue, hazardous materials containment, emergency medical support, site stabilization, and incident command support. Specific deliverables, staffing levels, equipment lists, activation thresholds, and reporting requirements are described below and shall be provided in practical execution consistent with the Authority's operational directives.

Detailed Scope of Work (describe responsibilities, staffing, equipment, and reporting):

PAYMENT TERMS

The Authority shall compensate the Operator for services rendered in accordance with the schedule and amounts set forth below. Invoices shall be submitted in the form required by the Authority and subject to verification.

Total Compensation (per term or event): Payment Schedule:

Late Fee (percent per month):

Grace Period (days):

TERM AND TERMINATION

This Act shall commence on and continue until , unless earlier terminated under the provisions below.

Either party may terminate this Act without cause upon providing days' prior written notice to the other party. Termination for cause may be effected immediately upon written notice where the non‑breaching party demonstrates a material breach that is not cured within the cure period specified in this Act.

Termination for Cause — Cure Period and Conditions:

CONFIDENTIALITY

Each party shall keep confidential all non-public information disclosed by the other in connection with this Act, including operational plans, vulnerability assessments, personnel rosters, and technical specifications. Confidential information shall not be disclosed except to agents or subcontractors with a need to know, who are bound by confidentiality obligations no less protective than those herein. Confidentiality obligations shall survive termination of this Act for years.

INSURANCE, INDEMNITY, AND COMPLIANCE

The Operator shall maintain insurance coverages customary for emergency response service providers, including workers' compensation, commercial general liability, and professional liability as applicable. The Operator agrees to indemnify and hold harmless the Authority from claims, liabilities, losses, and expenses arising from the Operator's negligence or willful misconduct in performing services under this Act. The parties shall comply with applicable laws, regulations, and safety standards in the performance of obligations.

ACTIVATION AND COMMAND

Activation of the Brigade shall occur upon written or recorded verbal authorization by the Authority's designated incident commander. Within 24 hours of activation, the Operator shall provide a written incident action plan and staffing manifest. The Authority retains operational control consistent with incident command protocols; the Operator shall comply with on‑scene direction and applicable mutual aid agreements.

GOVERNING LAW

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

ENTIRE AGREEMENT

This Act, including any appendices, schedules, and written modifications executed by both parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior proposals, negotiations, and agreements, whether written or oral.

NOTICES

Notices under this Act shall be sent to the addresses set forth below and shall be deemed given when delivered in accordance with the notice provisions specified in this Act.

Authority Notice Attention / Department: Operator Notice Attention / Department:

ADDITIONAL PROVISIONS

Subcontracting. The Operator shall not subcontract material elements of the Scope of Work without the prior written consent of the Authority. Any approved subcontractor shall be bound to the Operator's obligations under this Act.

Records and Audit. The Operator shall maintain records of personnel deployment, equipment usage, and costs incurred and shall permit the Authority to audit such records upon reasonable prior notice.

Amendment. No amendment, modification, or waiver of any provision of this Act shall be effective unless in writing and executed by authorized representatives of both parties.

Authority — Printed Name:

Party Label:

By:

Date:

Operator — Printed Name:

Party Label:

By:

Date:

What the Emergency Response Brigade Act establishes

The Emergency Response Brigade Act is a statutory template that creates a formal framework for establishing, organizing, and authorizing volunteer or paid emergency response brigades at the municipal or regional level. It defines brigade purpose, membership categories, command structure, training and certification expectations, equipment custody, and limited liability or indemnification provisions to support coordinated response during declared emergencies.

Why adopting this Act matters for coordinated emergency response

Adopting a clear Emergency Response Brigade Act clarifies authority, reduces operational confusion during incidents, and documents legal protections for responders. It also creates a record that helps align local practice with state public safety statutes and federal guidance, while preserving eligibility for certain grants and mutual aid arrangements.

Who typically adopts and implements the Emergency Response Brigade Act

Local governments, special districts, and nonprofit emergency organizations most commonly adopt a brigade act to formalize roles and responsibilities.

Municipal governments and counties responsible for public safety and emergency management
Healthcare facilities and hospitals that maintain internal rapid-response teams
Nonprofit search-and-rescue groups, volunteer fire associations, and campus safety units

The Act also supports schools, hospitals, and private property managers that maintain on-site response teams and need a documented governance and liability framework.

Core components to include in a professional Act

A complete Emergency Response Brigade Act addresses legal authority, membership and training requirements, command and control, resource management, indemnification and liability, and recordkeeping. Each component should be drafted to work within state law and local ordinances while supporting interoperable mutual aid.

Authority

Clear statutory or ordinance basis naming the brigade, its scope, and invoking emergency powers where authorized.

Membership

Eligibility criteria, background checks, medical clearance, and role classifications for brigade personnel.

Training

Minimum certification standards, continuing education, and documentation of completed competencies.

Command Structure

Lines of command, incident responsibilities, and how brigade leadership integrates with emergency management.

Liability & Indemnity

Statements on sovereign immunity, indemnification, workers' compensation, and volunteer protections where allowed by law.

Records

Requirements for incident logs, personnel rosters, equipment inventories, and retention periods for audit and legal purposes.

Step-by-step: adopting and executing the Emergency Response Brigade Act

Follow a predictable sequence to adopt and operationalize the Act so legal and operational checks are completed before activation.

01

Draft review: Compare the Act to applicable state statutes and local ordinances.
02

Legal approval: Obtain review from municipal or agency counsel for liability and authority language.
03

Formal adoption: Pass the ordinance or resolution and record the effective date.
04

Operationalize: Register members, schedule training, and publish activation procedures.

Typical workflow for activating and using the Act

Activation and execution follow a short operational chain to move from authority to action with clear documentation at each step.

Initiation: Authorized official declares activation per Act provisions.
Notification: Alert brigade members and partner agencies using predefined channels.
Deployment: Assign personnel and equipment according to role and training.
After-action: Document incident, collect logs, and update training records.

Setting up the digital workflow for the Act

Design a reproducible e-workflow that captures signatures, approvals, and attachments while preserving an auditable trail for legal and grant purposes.

Field	Configuration
Signer authentication	Email + SMS code or organization SSO for officials
Conditional fields	Show role-specific waivers when 'Volunteer' selected
Attachment rules	Require member ID and certifications as PDFs
Storage location	Encrypted cloud archive with access controls

Technical needs for secure eSubmission and storage

Choose a platform that supports authenticated e-signatures, tamper-evident PDFs, and a detailed audit trail for official records.

Authentication: Multi-factor options and SSO support
File formats: PDF and DOCX accepted; PDF/A recommended for archival
Integrations: Connectors for cloud storage and ERP systems

Common mistakes to avoid when preparing the Act

Using informal or inconsistent names for the brigade, causing confusion in mutual aid or grant applications.
Failing to record delegation of authority clearly, which delays decisions during incident activation.
Omitting equipment custody provisions, which creates disputes over maintenance and replacement responsibilities.
Not aligning indemnity or volunteer protections with state law, increasing legal exposure for the governing entity.

Key legal risks and consequences of errors

Invalid authority: Potential nullification of activation orders

Civil liability: Lawsuits for negligence or wrongful acts

Loss of funding: Grant disallowance for noncompliance

Operational delay: Slower response due to unclear roles

Regulatory fines: Penalties under specific statute

Reputational harm: Public trust erosion after failures

Distribution and document-format considerations

Choose distribution channels and file formats that preserve evidentiary integrity and meet partner-system requirements.

Formats: PDF, DOCX, and Excel supported
Integrations: Salesforce, Microsoft 365, NetSuite, Box, Procore
Auditability: Tamper-evident PDF and detailed audit logs

Representative eSignature pricing and capabilities (vendor overview)

Comparison of common plan characteristics and starting prices for major eSignature vendors. Confirm feature availability per vendor plan before procurement.

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

How organizations apply the Act in practice

Real-world examples show how the Act supports preparedness, liability clarity, and interoperable response across agencies.

Municipal activation

A county incorporated the Act to unify volunteer teams and clarify resource sharing

Activation authority centralized with the EMA director
After adoption the county reported clearer mutual-aid requests and a documented chain of custody for donated equipment, improving reimbursement eligibility.

Healthcare on-site brigade

A hospital defined a medical rapid-response brigade under the Act to coordinate campus incidents

Members required NIMS training
The hospital preserved credentialing records and reduced confusion during joint exercises with local EMS and fire agencies.

Practical drafting and implementation recommendations

Adopt clear, simple language, align the Act with existing emergency plans, and test activation procedures through regular exercises.

Use plain legal language

Avoid ambiguous terms and define key concepts such as 'activation', 'member', and 'incident commander' to reduce interpretation disputes.

Align with mutual aid

Reference existing mutual-aid compacts and interstate agreements to ensure brigade actions are supported during multi-jurisdiction responses.

Document training

Require and record minimum training and certification for each role; attach training matrix as an exhibit.

Review periodically

Schedule formal legal and operational review every 2–3 years or after significant incident activations.

Frequently asked questions about using the Emergency Response Brigade Act

Answers to common questions about execution, electronic signatures, notarization, and post-adoption updates for the Act.

Need help? Contact support

Can the Act be signed electronically?
Yes. Electronic signatures meeting the ESIGN Act (15 U.S.C. ch. 96) and state UETA standards are generally valid. Confirm exceptions such as certain court filings or testamentary documents that remain ineligible for e-signature.
Is notarization required for the Act?
Not always. Notarization needs vary by state and by the type of authorization recorded; check local notary statutes and whether the document will serve as a record requiring acknowledgment.
Who should sign the Act for it to be effective?
Authorized governing officials (e.g., city manager, county commission chair) or their delegated designees should sign. Where required, obtain signatures from multiple officials per local ordinance.
What supporting documents should I attach?
Attach member rosters, training matrices, equipment inventories, and indemnity or mutual-aid agreements to ensure the Act functions as an operational instrument.
How do I update or amend the Act?
Amendments should follow the original adoption process—legal review, formal approval by the governing body, and updated records with revised effective dates.
How long must records be kept?
Retention varies: follow federal guidance (e.g., IRS 3-year rule, IRC §6501(a)) and industry-specific rules such as HIPAA six-year retention (45 CFR §164.530(j)). Consult counsel for state-specific requirements.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now