Direct answer. A commercial emergency services agreement (ESA) is a pre-loss contract that gives a restoration company first-response rights on a facility and pre-decides scope, response time, rates, insurance, indemnity, term, data handling, and dispute path before water hits the floor. It is not a work authorization, not an assignment of benefits, and not a readiness brochure. The agreement is the product. Software is only where the signed terms live.
Most “priority response” one-pagers fail the night of the loss. They create no rate clarity, no risk transfer, and no authority path. The phone still rings into a negotiation while production is down. A real ESA does the opposite: it answers every commercial variable in daylight so the night questions stay operational — where is the water, what is at risk, who can open the door, when do we start.
This is the Restoration Intel standard for those eight provisions. For each: what it says, why it decides outcomes when a loss hits, and what to check in any agreement — including one that lives inside a paid platform. Structure and risk logic only. Exact clause language belongs with counsel in the state where the work will run. Sample indemnity, additional-insured, and assignment wording that works in one jurisdiction can fail in another.
Provision 1: Scope of services — and what the ESA is not
What it says. The ESA covers emergency stabilization: extraction, temporary dry-out, source containment, initial equipment protection, specialty stabilization coordination, and site documentation in the first hours to days. It does not cover reconstruction, full contents restoration, or permanent repair. Those need a separate work authorization or construction contract after the emergency phase and a developed scope of loss. If specialty categories are part of the offer — documents, electronics, fine art, medical equipment — name them, and state that specialists work under the contractor’s coordination while owning technical execution.
Why it decides outcomes. Mixing emergency and rebuild in one instrument forces either reconstruction pricing without a scope or locks the facility into a contractor for work the carrier may require them to bid. Clear separation keeps the night fast and the rebuild honest.
What to check. Can you list, from the document alone, what you may start at 2 a.m. and what still needs a second signature? If specialty work is promised, is the coordination model named? A platform portal that stores a vague “emergency services” line is not a scope provision.
Provision 2: Response time, staging, and on-call structure
What it says. Define response three ways: initial acknowledgment (minutes, twenty-four-seven, from someone who can deploy); arrival on site (honest window by geography and staging); and CAT-event modification (how priority sequences when every account is wet at once, plus staging or mutual-aid that makes the promise credible). Put the call tree, escalation path, backup contacts, and the facility’s duty to keep access contacts current in the same place.
Why it decides outcomes. The facility experiences acknowledgment first. On-site time decides whether the relationship feels real. Silence on CAT events is how preferred status collapses the week the city floods.
What to check. Are all three clocks written, or only a single “one hour on site” slogan? Is there a contact list that an after-hours answering service can use without hunting? If the agreement lives in software, open the live record and confirm the call tree matches the signed exhibit — not a stale CRM field.
Provision 3: Pricing framework and rate schedule
What it says. Attach a rate schedule complete enough to price an emergency without further negotiation: labor by role and shift; equipment by category with daily or weekly rates; consumables at cost plus a defined markup; specialist coordination or subcontractor handling; travel and mobilization; any CAT surcharge structure if used. State how the schedule reconciles with common insurance estimating databases — contractor rates as default, database pricing as default, or a hybrid that splits emergency phase from post-emergency scope work. Name how specialist pricing flows (direct to carrier with a coordination fee, through the contractor, or embedded in the schedule).
Why it decides outcomes. Price silence is a fight with the adjuster and a surprise for the FM. The exhibit is what makes the invoice defensible.
What to check. Can you price a midnight extraction from the exhibit alone? Is the estimating-database relationship stated? Is the specialist billing path named? A rate table buried in a platform that nobody can export for the claim file is not operational.
Provision 4: Insurance requirements and certificates
What it says. Require, at minimum, general liability, workers compensation, commercial auto, and — when specialty work touches data, medical devices, or art — appropriate professional or specialty coverage. Specify minimum limits, additional-insured status for the facility and named parent or property manager, waiver of subrogation, and notice of cancellation. Certificates on execution and renewal; right to request forms and endorsements. When specialists are used, state whether they are covered as subcontractors under the contractor’s policy, must name the facility (and usually the contractor) as additional insured on their own policies, or both. Healthcare, pharmaceutical, biotech, data center, and fine-art accounts often need higher limits than general commercial defaults — either specify them or commit to meeting the risk manager’s approval requirements.
Why it decides outcomes. The certificate on file is what lets work start without a risk hold. Specialty losses without subcontractor coverage clarity become three-party fights after damage.
What to check. Limits, additional insured, waiver, cancellation notice, certificate currency, specialty flow-down. In a platform, verify the uploaded COI matches the signed requirements and is not expired.
Provision 5: Indemnification and hold harmless
What it says. Structural intent: the contractor indemnifies, defends, and holds harmless the facility for claims arising from the contractor’s own negligence or breach; the facility retains liability for its own pre-existing conditions and its own negligence. That mutual floor is the usual commercial landing zone when bargaining power is balanced.
Why it decides outcomes. Anti-indemnity statutes in multiple states restrict or void clauses that force a contractor to cover the owner’s own negligence. Broad-form indemnity may also sit outside what the contractor’s general liability actually covers. The night of the loss is the wrong time to discover the clause is void or uninsured.
What to check. Is indemnity mutual for each party’s own negligence, or one-sided broad form? Has state counsel reviewed it against local anti-indemnity rules and against the contractor’s policy forms? Do not treat a platform’s default legal boilerplate as reviewed.
Provision 6: Term, renewal, and termination
What it says. Fixed term with automatic renewal unless notice is given. Allow termination for convenience with reasonable notice and for cause without notice, with cause defined tightly (breach, loss of insurance, insolvency, loss of licensure, failure to meet response commitments on a defined pattern). Address work in progress: an active stabilization continues under ESA terms; termination takes effect after that loss closes.
Why it decides outcomes. A lapsed ESA at the moment of loss is worse than no ESA — everyone thought coverage existed. Missing in-progress language lets someone try to walk mid-extraction.
What to check. Auto-renewal, notice windows, cause definitions, and the active-loss carve-out. In software, confirm renewal dates and alerts match the signed term — calendar fields are not the contract unless the exhibit says so.
Provision 7: Data, confidentiality, and regulatory compliance
What it says. Where work can touch protected information — PHI, cardholder data, student records, employee records, trade secrets — commit to the applicable standard and workforce awareness. Healthcare needs a business associate agreement under HIPAA referenced as a condition of performance; education, financial, and cardholder environments bring their own regimes. Confidentiality should be mutual and survive termination, with operational disclosures to carriers, adjusters, and conservators permitted. Put chain-of-custody and data-handling for off-site records, data-bearing electronics, and PHI-bearing equipment in this provision or a scope exhibit.
Why it decides outcomes. These are operational requirements on every regulated loss, not abstract compliance. Pre-decide transport, tracking, storage, and return — or invent them wet.
What to check. BAA or equivalent where required; mutual confidentiality; specialty chain-of-custody. If the platform stores photos and documents, confirm retention and access rules match the ESA, not only the vendor’s SaaS terms.
Provision 8: Dispute resolution, governing law, and venue
What it says. Name governing law (usually the facility’s state) and venue. Require meet-and-confer, executive escalation, and mediation before litigation. If arbitration is used, name rules, location, arbitrator count, and discovery. Prevailing-party fees are common; limitation of liability and consequential-damage exclusions are negotiated. For specialty work, acknowledge that technical disputes may need subject-matter expertise, not only a general commercial panel.
Why it decides outcomes. On a large loss with a carrier in the middle, this provision decides where and how the fight runs — or whether it becomes a fight at all.
What to check. Law, venue, escalation ladder, mediation/arbitration detail, fee shifting, liability caps. Platform terms of service do not replace this section unless the ESA expressly incorporates them — and usually they should not.
How the eight provisions work as one system
Scope defines what the work is. Response time defines when it happens. Pricing defines what it costs. Insurance protects both parties financially. Indemnity allocates legal risk. Term provides stability without captivity. Data and compliance keep both parties clean on regulated sites. Dispute resolution is the exit if the other seven break down.
An ESA with all eight, written for the state and the facility’s risk stack, is something legal, risk, and operations can sign without holding their breath. Four of eight — or eight written badly — either never gets signed or fails when water is on the floor. An emergency readiness plan maps the building. A master service agreement wraps a portfolio. A work authorization triggers a specific loss. The ESA is the operating framework those documents plug into. Keep them distinct.
Have a commercial attorney draft the words. Have the insurance agent review indemnity and additional-insured assumptions against actual coverage. Structure is teachable. Templates without review are not a strategy.
Questions
Is an ESA the same as an assignment of benefits? No. An ESA is a pre-loss operating agreement. An AOB is a post-loss claims instrument. Treat them as separate documents and follow state rules on assignments.
How does the ESA relate to the work authorization signed at the loss? The ESA is the framework. The work authorization is the short trigger that identifies the loss and confirms emergency scope; rates, indemnity, insurance, and compliance flow through from the ESA.
Can one master agreement cover a whole portfolio? Yes, with facility-specific exhibits for access, equipment, and operational needs. Single-site owners usually use a standalone ESA. Specificity in the exhibits matters more than the wrapper label.
What if the facility hands us their vendor template? Read it with counsel. Push back on one-sided indemnity, impossible insurance, and termination that only protects the facility. Most serious accounts will negotiate once you raise balanced points.
Does storing the ESA in software change what must be in it? No. The platform is a filing cabinet with login credentials. The eight provisions still have to be in the signed agreement, current, exportable for the claim file, and consistent with what operations will actually run.