Direct answer: A commercial emergency services agreement is a pre-loss contract that gives a restoration company the right of first response to a facility’s property emergencies and defines scope, pricing, response time, indemnification, insurance, and termination before a loss ever happens. It is not an assignment of benefits, it is not a work authorization, and it is not a scope contract — it is the operating framework those other documents plug into when a loss occurs. The structural content is consistent across the industry. The exact language varies by state, carrier requirements, and facility type, which is why every serious ESA should be drafted or reviewed by an attorney and vetted by the facility’s risk manager before signature.
Most restoration companies treat the emergency services agreement as a sales artifact — a one-page “priority response guarantee” that gets signed at a vendor fair and filed in a binder nobody opens. That version of the ESA is nearly worthless. It creates no rights, no duties, no pricing clarity, and no risk transfer. When the loss hits, the contractor still has to negotiate scope, rates, indemnity, and insurance on the night of the event, while water is running and a facility director is trying to get production back online.
A real ESA does the opposite. It pre-decides every negotiable variable so that when the phone rings at 2 a.m., the only remaining questions are operational: where is the water coming from, what equipment is at risk, who is on site, and when can we start. The rate sheet is settled. The indemnity is settled. The certificate of insurance is on file. The scope framework is defined. The facility’s legal and risk functions have already signed off. That pre-decision is what converts an ESA from a marketing document into a commercial wedge.
This article walks through the eight structural provisions that belong in every commercial ESA, what each one actually protects, and how the specialty-services posture from the rest of this cluster fits into the agreement. It does not contain sample clause language. It does not tell you what to write in your indemnity paragraph. That restraint is deliberate, and the next section explains why.
Why this article stays structural and sends you to counsel for the words
There are a few categories of content in the restoration industry where the specificity of the advice is inversely related to its usefulness. Contract drafting is the clearest example. A sample indemnity clause pulled from a template site will get you sued in some states and held unenforceable in others. A sample additional-insured endorsement that looks reasonable on its face may fail to match the carrier’s underlying policy form. A sample assignment paragraph that worked in one jurisdiction five years ago may be void under a statute that passed last session.
A few specific reasons the clause-level language belongs with a lawyer, not a generic template:
State law on restoration contracts is genuinely inconsistent. Florida’s §627.7152, for example, imposes tight procedural requirements on any instrument that assigns post-loss insurance benefits — including a fourteen-day cancellation window, a written itemized estimate, and specific cost limits on emergency assignments. Other states have no statutory framework at all. A clause that satisfies Florida may be overbuilt elsewhere. A clause that works in a state with no statute may violate a Florida consumer-protection provision the moment you cross the border. An ESA is not an AOB, but some of the same drafting traps apply to both, and only a lawyer who practices in the state where the work will occur can tell you which ones.
Commercial insurance requirements are carrier-specific and property-specific. The additional-insured language that satisfies the facility’s general liability carrier will not necessarily satisfy the carrier underwriting a pharmaceutical plant’s product-liability tower, a hospital’s professional-liability layer, or a data center’s cyber-liability program. The insurance provisions in the ESA need to be negotiated against the facility’s actual policy stack, not against a generic standard. Facility risk managers have strong opinions about this, and the ESA is the document that either satisfies them on day one or triggers a six-week redline cycle.
Indemnification law is jurisdictionally fractured. Anti-indemnity statutes in California, Texas, Oregon, and several other states limit how far a contractor can transfer liability for its own negligence. A hold-harmless clause that reads naturally may be partially or fully void under statute, which means the indemnity you think you negotiated does not exist. The only way to get this right is to have counsel in the relevant state write the language.
The Restoration Industry Association publishes a contract sample package for members that is widely used in the industry as a starting point, and it is appropriately marked as informational only. Even the RIA explicitly notes that the package does not warrant compliance with any given state or local jurisdiction. If the trade association that wrote the templates will not warrant the language, a restoration company should not rely on it without review.
So the rule this article follows is simple. Structure, intent, and risk logic are safe to write about because they are consistent across the industry. Exact clause language is not safe to write about because it is not consistent. When you are ready to execute an ESA, take this structural framework to a commercial attorney who has drafted facility contracts in your state, hand them the facility’s standard vendor requirements, hand them your certificate of insurance and policy forms, and let them write the words. Budget for the review. It is cheaper than a deficient contract.
With that preface, here are the eight provisions.
Provision 1: Scope of services and what the ESA is not
The first provision defines what the agreement covers and, equally important, what it does not. This is the provision that most ESA templates get backwards — they either promise far too much (every possible restoration service the company offers) or far too little (a one-sentence “emergency response services” reference that creates no enforceable scope at all).
The structural answer is that the ESA covers emergency stabilization services: the water extraction, temporary dry-out, source containment, initial equipment protection, specialty stabilization subcontractor coordination, and site documentation that occur in the first hours to days after a loss event. It does not cover the reconstruction scope, the full contents restoration, or the permanent repair work. Those are separate agreements — typically a work authorization or a standard construction contract — that get executed after the emergency phase is stabilized and a full scope of loss has been developed.
Why separate them? Because emergency services have to move faster than any negotiated scope can support, and reconstruction services have to be priced against a known scope, which does not exist during the emergency. Mixing them in one agreement forces the contractor to either pre-commit to reconstruction pricing without a scope, or makes the facility pre-commit to a contractor for work that their insurance carrier may require them to competitively bid. Neither of those outcomes is good for either party.
For the specialty-services version of an ESA — the version this cluster has been building toward — the scope provision should explicitly name the specialty categories covered (documents, electronics, fine art, medical equipment, or whatever subset the contractor’s specialist bench supports) and should reference that specialty work will be performed by named or vetted subcontractors under the contractor’s coordination and supervision. The facility needs to understand from day one that the restoration company is the responsible party on coordination and the specialist is the responsible party on technical execution. Building that clarity into the scope provision prevents a dispute later when a specialist invoices directly and the facility wants to know why the restoration company’s name is on the ESA but not the bill.
Provision 2: Response time, staging, and on-call structure
Every ESA should define response time in three ways, not one. Most templates define it once — “one hour on-site response” is the cliché — and then say nothing about what one hour means or what happens when the weather, traffic, or a regional catastrophe makes one hour impossible.
The three definitions that belong in a real ESA:
Initial acknowledgment. The time from the facility’s first call to a confirmed response from someone at the restoration company who has authority to deploy. This should be measured in minutes and should be twenty-four-seven. It is the most important response-time commitment in the agreement because it is the one the facility experiences first and the one that determines whether the contract feels like a real service.
Arrival on site. The time from call to boots-on-the-ground at the loss location. This varies by geography, by staging strategy, and by type of event. A contractor with a local crew and a truck that lives in the facility’s metro can honestly commit to one to two hours under normal conditions. A contractor serving a multi-state region may commit to four hours for a single-site event and acknowledge longer windows during CAT events when every truck is already deployed.
CAT-event modification. What happens when a hurricane, winter storm, wildfire, or regional flood creates simultaneous demand across every account the contractor serves. Honest ESAs acknowledge that pre-loss priority status gets harder to honor during a CAT event, define how priority is sequenced among covered accounts, and explain the staging approach — crew positioning, equipment staging, mutual-aid agreements with out-of-region affiliates — that makes priority response credible under stress. A facility with a real risk function will ask this question explicitly. A facility without a real risk function should still have it answered in the document.
The on-call structure provision also belongs here: the call tree, the escalation path, the backup contacts, and the requirement that the facility maintain current contact information on its side so the restoration company does not lose fifteen minutes finding someone authorized to allow access.
Provision 3: Pricing framework and rate schedule
This is the provision that separates serious ESAs from sales artifacts. The ESA should reference a rate schedule attached as an exhibit, and that rate schedule should be complete enough to price an actual emergency without further negotiation.
Structural components of a real rate schedule: labor rates by role (technician, lead technician, supervisor, project manager) and by shift (straight time, overtime, holiday, after-hours callout); equipment rental by category (air movers, dehumidifiers, HEPA filtration, desiccant systems, generators, extraction trucks) with clear daily or weekly rates and minimum-days commitments; consumables and materials at cost plus a defined markup; subcontractor handling fee or specialist coordination fee for specialty services; travel and mobilization charges and how they apply; and any CAT-event surcharge structure if the contractor uses one.
The rate schedule should also state how it reconciles with insurance industry pricing databases. Most commercial losses end up being scoped and priced in Xactimate, and the ESA rate sheet should either (a) commit to Xactimate pricing as the default with contractor rates as a fallback, (b) commit to contractor rates with Xactimate as a reconciliation benchmark, or (c) use a hybrid where emergency labor and equipment use contractor rates and scope work after the emergency phase uses Xactimate. All three are defensible. Silence is not.
The specialty-services layer adds one more requirement: the ESA should define how specialist pricing flows through. Some specialists bill direct to the carrier and the restoration company takes a coordination fee. Some specialists bill the restoration company and the restoration company bills the carrier with a markup. Some specialists are embedded in the restoration company’s rate schedule directly. All three models are fine. The ESA should name which one applies so the facility and the adjuster know what to expect when the invoice arrives.
Provision 4: Insurance requirements and certificates
The ESA should require, at minimum, four categories of insurance from the restoration company: general liability, workers compensation, commercial auto, and — for any specialty work that touches data, medical devices, or art — appropriate professional or specialty-services coverage.
For each, the ESA should specify minimum limits (per occurrence and aggregate), additional-insured status for the facility and for any parent entity or property manager the facility names, waiver of subrogation in favor of the facility, and a thirty-day notice of cancellation provision. The restoration company should be required to provide certificates of insurance on execution and on renewal, and the ESA should give the facility the right to request policy forms and endorsements on reasonable notice.
The specialty-services layer matters here. When a restoration company is coordinating a document-recovery specialist, an electronics restoration vendor, or an art conservator, the specialists carry their own insurance and the facility needs to know whether they are covered as subcontractors under the restoration company’s policy, whether they are required to name the facility as additional insured on their own policies, or both. The cleanest structure is usually both — the specialist names the facility and the restoration company as additional insureds on their own policy, and the restoration company’s policy extends to cover the specialist’s work as a subcontractor. Building that into the insurance provision up front avoids a fight after a claim.
For healthcare, pharmaceutical, biotech, data center, and fine-art accounts, the minimum limits should be higher than the commercial-general defaults. A small restoration company with a one-million-dollar general-liability limit is not adequately insured to work inside a hospital, a data center, or a facility holding seven-figure art. Those accounts will require higher limits as a condition of vendor approval, and the ESA should either specify the higher limits or explicitly commit to meeting whatever the facility’s risk manager requires at the time of approval.
Provision 5: Indemnification and hold harmless
This is the provision where state law matters most and where a generic template is most dangerous. The structural intent is straightforward: the restoration company agrees to indemnify, defend, and hold harmless the facility for claims, damages, and expenses arising from the contractor’s own negligence or breach, and the facility retains its own liability for its own pre-existing conditions and for claims arising from its own negligence. That is the defensible mutual structure that most commercial contracts land on when the parties have balanced bargaining power.
What makes this provision jurisdictionally fragile is that states regulate how far one party can indemnify another for the other party’s negligence. California Civil Code §2782 and similar anti-indemnity statutes in several other states restrict or void clauses that require a contractor to indemnify a property owner for the owner’s own negligence. The permissible scope ranges from “contractor’s negligence only” to “comparative indemnity for proportional fault” to “broad-form indemnity including the indemnitee’s own negligence” — and which of those is enforceable depends entirely on the state.
The operator’s takeaway is that mutual indemnity for each party’s own negligence is nearly always enforceable and is a reasonable floor. Broader indemnity may or may not be enforceable and should never be signed without state-specific counsel review. If a facility’s vendor form asks the contractor to broad-form indemnify the facility, the contractor should not sign it without a lawyer explaining whether the clause is enforceable in that state and whether it is covered by the contractor’s insurance. Some insurers exclude broad-form contractual indemnity from general liability coverage, which means a contractor who signs a broad-form clause may be uninsured for the liability they just assumed.
Provision 6: Term, renewal, and termination
The ESA should be a fixed-term agreement with automatic renewal unless either party provides notice. Three years is a common term. One-year terms with annual renewal work as well. The automatic renewal is the important feature — a contract that expires and has to be re-negotiated annually is a contract that lapses accidentally, and a lapsed ESA at the moment of a loss is worse than no ESA at all.
Termination provisions should allow either party to terminate for convenience with reasonable notice (thirty to ninety days is standard) and for cause without notice. Cause should be defined tightly: breach of the agreement, loss of required insurance, insolvency, loss of licensure, or failure to meet response time commitments on a defined number of events. A facility should not be able to terminate on a whim, because the contractor has been investing in relationship-specific knowledge of the facility; a contractor should not be able to hold the facility hostage, because the facility has emergency needs that require the flexibility to replace the contractor if performance degrades.
The ESA should also address what happens to work in progress at termination. If a loss is active and stabilization is mid-stream when termination notice is given, the termination does not apply to the active loss — the contractor continues to completion under the ESA terms and the termination takes effect afterward. Missing that clause can create a situation where one party tries to walk away from an active loss, which serves no one.
Provision 7: Data, confidentiality, and regulatory compliance
This provision is where commercial ESAs have evolved significantly over the last decade, and where most template documents are still underbuilt.
For any account where the work touches protected information — patient health information in healthcare, cardholder data in retail, student records in education, employee records generally, trade secrets in manufacturing — the ESA needs to specify how the restoration company handles that information. For healthcare specifically, the ESA needs to be accompanied by a business associate agreement under HIPAA, and the ESA should reference the BAA as a required condition of performance. For education, FERPA creates similar obligations. For financial services, GLBA. For retail handling cardholder data, PCI-DSS. The ESA does not need to recite every provision of every regulation, but it does need to commit the contractor to meeting the applicable standard and to making the workforce aware.
Confidentiality should be mutual — the contractor agrees to protect facility information, and the facility agrees not to disclose contractor pricing, methods, or proprietary approaches. Confidentiality survives termination. Disclosures to carriers, adjusters, and conservators for the purpose of executing a loss are permitted as operational necessity.
Chain-of-custody and data-handling obligations for specialty work belong in this provision or in the scope exhibit. Document restoration that involves moving records off-site must define how the records are tracked, transported, stored, and returned. Electronics restoration that involves systems carrying data must define whether data is preserved, destroyed, or extracted and returned. Medical equipment restoration must define how PHI-bearing equipment is handled during triage and transport. These are not abstract compliance questions — they are operational requirements that come up on every loss and need to be pre-decided in the contract.
Provision 8: Dispute resolution, governing law, and venue
The last provision is the one most people skip reading. It is also the one that determines what happens if things go sideways on a seven-figure loss with an insurance carrier in the middle.
Governing law should be specified explicitly — usually the state where the facility is located. Venue for any litigation should be specified — usually the county where the facility is located or a nearby federal district. Dispute resolution should include a mandatory meet-and-confer step before any formal action, an escalation path to executive-level representatives on both sides, and a commitment to mediation before litigation. Arbitration can be used, but should be specified clearly — including the rules that apply (AAA, JAMS, or another recognized body), the location, the number of arbitrators, and whether discovery is permitted.
Attorney’s fees and costs should follow the prevailing party — both as a deterrent against frivolous claims and as a protection for whichever party is forced to litigate a legitimate position. Limitation of liability caps are common in commercial contracts, and the ESA may or may not include one depending on negotiation. Consequential and punitive damage exclusions are also common and negotiated.
For specialty work, the dispute resolution provision should acknowledge that technical disputes over conservation methods, recertification requirements, or data-restoration outcomes may need subject-matter-expert arbitrators rather than generalists. A dispute over whether a painting was properly stabilized is not a dispute a commercial litigator is equipped to decide; it needs a conservator. The agreement can name the tribunal or defer to mutual selection, but should acknowledge the issue.
How the eight provisions fit together
The eight provisions are not a checklist — they are a system. The scope defines what the work is. The response time defines when the work happens. The pricing defines what the work costs. The insurance protects both parties financially. The indemnity transfers legal risk rationally. The term provides stability without captivity. The data and compliance obligations keep both parties regulatorily clean. The dispute resolution provides an exit path if the other seven provisions break down.
A well-drafted ESA with all eight provisions is a document that a facility’s legal team, risk manager, and operations leader can sign without holding their breath. An ESA that has four of the eight, or that has all eight written badly, is a document that either never gets signed or that gets signed but does not actually protect either party when a loss hits.
The specialty-services layer — the wedge this entire cluster has been building toward — fits naturally inside a well-drafted ESA. The specialty services are named in the scope. The specialist coordination model is named in the pricing. The specialist insurance structure is named in the insurance provision. The specialist data-handling obligations are named in the compliance provision. The facility signs one document, gets priority response for property losses, and inherits a specialist bench they did not have to vet themselves. That is the door-opener. The eight provisions are the hinges.
What to do before you sign anything
If you are a restoration company using this article to prepare for ESA conversations with commercial accounts, the honest sequence is:
Engage a commercial attorney in your state. Give them your existing contract templates, your insurance declarations, your standard rate schedule, and the categories of facilities you are targeting. Ask them to build a master ESA that addresses all eight provisions with state-appropriate language, and a set of modifications for regulated verticals (healthcare, data, education, fine art). Budget two to four thousand dollars for the initial work and a few hundred dollars annually for review and updates. That number is trivial compared to the cost of a deficient contract on a seven-figure loss.
Review the RIA contract sample package if you are a Restoration Industry Association member. It is a useful starting point and a useful cross-check against your attorney’s draft, but it is not a substitute for counsel-drafted documents. The RIA itself does not warrant the language.
Have your insurance agent review the indemnity, additional-insured, and limit-of-liability provisions before you circulate the draft to accounts. Your general liability carrier may exclude certain contractual assumptions of liability from coverage, and you need to know that before you sign something that strips you of your insurance protection.
Run the final document past a facility risk manager or two — a peer in the property management or corporate real estate space — and get their candid reaction. Risk managers see dozens of vendor contracts a year and can tell you within five minutes whether your document looks professional or amateur.
None of that is glamorous. All of it is what separates a restoration company that gets written into facility vendor files from a restoration company that shows up with a one-page “priority response guarantee” and gets treated like the last call the facility director makes instead of the first.
Frequently asked questions
Is an ESA the same as an assignment of benefits?
No, and conflating them is a serious error. An assignment of benefits is a post-loss instrument in which the policyholder transfers some or all of their insurance claim rights to the contractor. An ESA is a pre-loss operating agreement that defines how emergency services will be performed if a loss occurs. An ESA may reference how assignments or direct-pay arrangements will be handled, but it is not itself an assignment. States like Florida have enacted strict rules on AOBs — §627.7152 — that do not apply to ESAs in the same way. Treat them as distinct documents and let your attorney advise on whether, when, and how you use AOBs inside your state.
How long should the ESA be?
A properly drafted commercial ESA with all eight provisions and a rate schedule exhibit usually runs fifteen to thirty pages. If it is shorter than that, something is missing. If it is substantially longer, something is probably over-engineered. The structural content can be expressed concisely; length comes from exhibits (rate schedule, insurance requirements, specialty subcontractor list, compliance addenda) that the main contract references.
Can a facility sign our ESA as-is, or will they always want to redline?
Most serious commercial accounts will redline. Expect it, plan for it, and do not treat it as a rejection. The facility’s legal and risk functions are doing their job. The redlines usually concentrate in insurance limits, indemnity scope, termination rights, and data compliance — the provisions where the facility’s exposure is real. A well-drafted starting document narrows the redlines to reasonable negotiation rather than a fundamental rewrite.
What if the facility has their own ESA template they want us to sign?
Read it carefully, have your attorney read it carefully, and push back where the document is unbalanced. Facility templates frequently contain one-sided indemnity provisions, insurance requirements that exceed what a mid-size restoration company can reasonably carry, and termination rights that give the facility everything and the contractor nothing. Most facilities will negotiate those points once you raise them — because most facilities would rather have a qualified contractor with reasonable protections than an unqualified contractor who signs whatever is in front of them.
How often should we update our ESAs once they are in place?
Annually at minimum. Insurance limits may need to rise. State law may have changed. Your own rate schedule almost certainly has. The compliance landscape around HIPAA, data protection, and specialty handling continues to evolve. An ESA from three years ago is probably not the ESA you want defending you today.
Do we need a separate ESA for each facility, or can we use a master agreement across a portfolio?
Both structures work. For multi-site accounts with a single corporate owner — a hospital system, a data center operator, a property manager — a master services agreement with facility-specific exhibits is cleaner. For single-site owners, a standalone ESA is simpler. What matters is that the scope and pricing exhibits are specific to each facility’s actual equipment, access requirements, and operational needs, rather than generic.
How does the ESA interact with the work authorization signed at the time of a loss?
The ESA is the operating framework. The work authorization is the post-loss trigger. When a loss occurs, the facility signs a short work authorization that references the ESA, identifies the specific loss, and confirms the scope of the emergency services being authorized. The ESA provisions (rates, indemnity, insurance, compliance) flow through automatically. This structure is why the ESA pre-decides everything — so the work authorization at 2 a.m. is a one-page document, not a contract negotiation.
What happens if a subcontractor specialist damages the facility during specialty work?
The answer depends on how the ESA is drafted. In the cleanest structure, the restoration company carries general liability that extends to the work of its subcontractors, the specialist carries their own liability that names the facility and the restoration company as additional insureds, and the indemnity provision allocates responsibility based on whose negligence caused the damage. A well-drafted ESA and subcontract between the restoration company and the specialist will define the flow so that a covered loss is paid by an insurer rather than argued over between the parties.
Is the ESA a confidential document, or can we reference it in marketing?
The ESA itself is usually confidential — both the pricing and the legal terms. The fact of the relationship is often not. Many facilities are comfortable being referenced as emergency-services accounts with pre-loss agreements in place, as long as the contents remain private. Ask before you reference anyone, get the answer in writing, and respect the answer.
How do we actually get a facility to sign one of these?
That is the subject of the next article in this cluster. The short answer is that you do not walk in and ask for a signature. You work the account through vendor qualification, risk-manager education, and a staged demonstration of capability that makes signing the ESA feel like the natural outcome of a longer conversation rather than the thing you asked for in the first meeting. The specialty-services wedge this entire cluster has been building makes that conversation easier because the door opens around specialty recovery, not around general restoration.
