Insurance Requirements in Service Agreements: COIs, Additional Insured Clauses, and What Happens When Your Vendor Isn't Covered

Picture this: your office renovation contractor drops a power tool through your client's glass display case on day three of a four-week project. The client is furious. The contractor shrugs and says, "My policy lapsed last month." You are now holding a service agreement that says absolutely nothing about insurance. Congratulations — you just became the responsible party.

Insurance requirement clauses are one of those contract provisions that feel like paperwork until the exact moment they save your business. Getting them right means understanding four distinct things: which policies to demand, what coverage amounts are realistic, how to make yourself an additional insured, and what a certificate of insurance actually proves. This article covers all four, with sample clause language drawn from real drafting practice. If you want to explore the full range of document types this problem touches, the template library is a good starting point.

The Contractor Shows Up Without Coverage — Now What?

Without an insurance clause in your contract, your options after an uninsured contractor causes a loss are grim: (1) sue the contractor personally, which works well if they have assets and terribly if they don't; (2) file on your own general liability policy and absorb the premium increase; or (3) eat the loss. None of those is "the vendor pays and everyone moves on."

Courts have been clear that the obligation to carry insurance doesn't arise automatically from a service relationship. In Travelers Casualty & Surety Co. v. U.S. Filter Corp., 895 N.E.2d 1172 (Ind. Ct. App. 2008), the court underscored that insurance requirements — including which party must be named as additional insured — must appear explicitly in the contract. If your agreement is silent, courts won't read one in.

The takeaway is simple: if you care about being covered when something goes wrong, you have to draft the requirement yourself. The law won't do it for you, and neither will good intentions.

What the Law Actually Requires (Hint: Not Much)

Federal law doesn't require private-sector vendors to carry any particular insurance unless they're working on a federal contract, where the Federal Acquisition Regulation, 48 C.F.R. Part 28, sets out coverage minimums. State law is similarly hands-off for commercial services. Workers' compensation is the main exception — most states require it for businesses with employees — but sole proprietors often opt out legally. That opt-out is valid, and it leaves their workers unprotected and potentially your business exposed.

What this means is that a freelancer operating as a sole proprietor can legally walk into your office to write software, redesign your showroom, or consult on HR policy with zero professional liability coverage, zero general liability, and no workers' comp. All of that is entirely permissible unless your contract says otherwise.

This is why risk-aware small businesses treat insurance as a contract requirement, not a legal given. You create the obligation; the contract enforces it.

The Four Insurance Types Worth Including in Your Contract

Not every vendor needs every type of coverage. But knowing what each policy does lets you ask for the right ones. Here is the standard lineup:

• Commercial General Liability (CGL) — Covers third-party bodily injury and property damage caused by contractor operations. A plumber who floods your server room, a caterer whose employee trips a client — this is the policy that pays. Typical minimums for small business contracts: $1 million per occurrence, $2 million aggregate.
• Professional Liability (Errors & Omissions / E&O) — Covers the contractor's mistakes in professional services. An accountant who miscalculates your tax position, a consultant whose advice triggers a regulatory fine, a designer whose deliverable infringes a third-party copyright — CGL won't touch those. E&O will. Especially important for consultants, IT vendors, attorneys, and designers.
• Workers' Compensation — If the contractor has employees (not just the owner), most states require this. If their worker injures themselves on your property and the contractor has no workers' comp, you may face direct liability under some state statutes. Require a certificate showing active coverage — and verify it.
• Commercial Auto — Relevant when the contractor drives to your site or client locations. Personal auto policies universally exclude business use. "My guy drives his own truck" is not coverage.

For most service contracts between legal entities — your LLC hiring a consulting firm, for instance — CGL and professional liability are the baseline. Add workers' comp if the vendor has employees, auto if driving is part of the engagement.

How to Draft an Insurance Requirement Clause That Has Teeth

A vague clause like "Contractor shall maintain appropriate insurance" is worse than useless. It hands the contractor the right to decide what "appropriate" means, which they will interpret as "whatever I already happen to carry." Your clause needs to name the policies, specify minimum amounts, require you be named as additional insured, and explain what happens if coverage lapses.

Here is sample language from a well-drafted consulting agreement that covers the essentials:

"During the term of this Agreement and for twenty-four (24) months thereafter, Contractor shall maintain at its own expense: (a) Commercial General Liability insurance with limits of not less than $1,000,000 per occurrence and $2,000,000 in the aggregate; (b) Professional Liability / Errors & Omissions insurance with limits of not less than $1,000,000 per claim; (c) Workers' Compensation insurance as required by applicable state law; and (d) Commercial Automobile Liability insurance, if Contractor operates any vehicle in connection with this Agreement, with limits of not less than $1,000,000 per accident. All policies shall name Client as an Additional Insured by endorsement to the underlying policy. Contractor shall provide certificates of insurance within five (5) business days of the Effective Date and upon each subsequent request. Failure to maintain required insurance constitutes a material breach of this Agreement and entitles Client to immediate termination."

The trailing 24-month coverage period matters specifically for professional liability claims that surface after the project ends. E&O policies are almost always written on a "claims-made" basis, meaning the policy in force when the claim is filed — not when the error occurred — is the one that responds. Without that tail requirement, a consultant can let the policy lapse after delivering the work, and you'll have no coverage when the mistake surfaces a year later. This is a common gap even in template agreements that otherwise look thorough.

The "Additional Insured" Designation — Don't Skip This

Being named as an additional insured on a contractor's policy is different from being a contract party who benefits from an insurance requirement. Without the additional insured endorsement, if the contractor's policy pays out for something that harmed you, the insurer pays the contractor — and the contractor may or may not pass that money along. Or they'll have spent it on their own legal fees by the time you see it.

As an additional insured, you can generally: (1) trigger the contractor's policy directly without going through the contractor, (2) be defended by the contractor's insurer in a lawsuit where both of you are named, and (3) benefit from the policy limits independently. That's a meaningfully different position than "the contract says they have insurance."

The critical detail: additional insured status requires an endorsement to the actual policy — not just a line on a certificate of insurance. This is the single most expensive mixup in small business contracting involving vendor insurance. Some certificates list you as an additional insured right on the face of the document, and if the underlying policy has no endorsement, those words are legally meaningless. Ask for a copy of the endorsement itself, separate from the ACORD 25 form.

When you draft your consulting agreement or use an existing framework as a starting point, make the endorsement a condition of the contract's effectiveness — not just a promise to obtain one later. "Contractor shall provide evidence of additional insured endorsement prior to commencing work" is better than "Contractor shall use commercially reasonable efforts to obtain."

Certificates of Insurance: What They Prove and What They Don't

A Certificate of Insurance — usually ACORD Form 25 — is a snapshot of a policy at the moment it was issued. It shows the insurer's name, the policy number, coverage type, limits, and policy period. That's genuinely useful information.

Here is what a COI does not tell you:

• Whether the policy has been cancelled since the certificate was printed
• Whether prior claims have eaten into the aggregate limits — leaving, say, $400,000 rather than $2 million available
• Whether the additional insured endorsement actually exists in the policy document itself
• Whether any exclusion in the policy applies to your particular project or work type
• Whether the contractor has paid their latest premium

Courts have consistently held that a COI is not a policy and creates no coverage obligations on the insurer. In Regency Realty Group, Inc. v. Lanton, an Illinois appellate decision, the court found that the standard COI language stating it "confers no rights upon the certificate holder" was controlling, and a named additional insured had no direct claim against the insurer when the underlying endorsement was missing from the policy.

The practical fix: require the contractor to instruct their insurer to send you 30 days' advance notice if the policy is cancelled or materially changed. Most insurers include this endorsement at no extra cost. Without it, you won't know the policy lapsed until after the loss — which is particulary unhelpful at that point.

Waiver of Subrogation: The Clause Nobody Reads Until There's a Loss

Subrogation is the right of an insurance company that paid a claim to step into the insured's shoes and sue whoever caused the loss. If your property insurer covers damage your contractor caused, your insurer can then sue that contractor to recover what it paid. That sounds fine — until the contractor's insurer points out that the loss was partly your fault too, and now there are two insurers, two sets of lawyers, and a comparative fault argument that buries the project relationship.

A mutual waiver of subrogation cuts this off. Each party waives, and requires their insurer to waive, any right of recovery against the other. Claims are resolved within each party's own coverage, the insurers don't go after each other, and the business relationship stays alive.

"Each party shall obtain from its respective insurer a waiver of all rights of subrogation against the other party. Each party hereby waives any and all rights of recovery against the other party for loss or damage to property covered by insurance required under this Agreement, to the extent that such loss or damage is covered by such insurance."

One wrinkle worth noting: if you don't carry property insurance — or if the specific loss isn't covered by your policy — the waiver doesn't help you. You've waived the right to subrogate through a policy that never paid the claim. The waiver works best when both sides are actually insured and both policies would respond to the same loss.

What to Do When a Contractor's Policy Lapses Mid-Project

Policies lapse. A premium payment gets missed, the insurer mails notices the contractor ignores, and three months into a six-month engagement you're holding a certificate for a policy that no longer exists. Your options depend entirely on what your contract says.

If your agreement includes a cancellation-notice clause, you should have received a heads-up from the insurer directly. If that didn't happen, contact the contractor's insurer — as a named additional insured, you generally have standing to inquire about the policy status without going through the contractor.

Look at your termination clause. A well-drafted freelance contract or service agreement treats failure to maintain insurance as a material breach, allowing immediate termination for cause without paying a termination fee. Without that explicit language, you'll be litigating whether a lapsed policy is "material" — an argument that costs money and time when you'd rather be finishing the project.

A cleaner alternative to outright termination when the relationship is otherwise solid is a work-stoppage provision:

"If Contractor's insurance coverage lapses or is cancelled during the term, Contractor shall immediately notify Client in writing and shall not resume performance until evidence of reinstated coverage has been provided to and accepted by Client in writing. Client may, at its election, treat such lapse as a material breach and terminate this Agreement immediately upon written notice."

One thing not to do: proceed with a contractor you know is uninsured and say nothing. If something then goes wrong, you'll have difficulty arguing later that the uninsured status was an unforeseen breach — because you knew and continued anyway. Document the lapse, demand reinstatement, and hold the work order until you see a new certificate and endorsement.

Insurance Requirements Between Legal Entities vs. Sole Proprietors

The risk profile shifts depending on who you're contracting with. Contracts between legal entities — your LLC engaging a corporation or another LLC — carry different practical exposure than hiring an individual operating under their own name.

When contracting between legal entities, both parties typically have some business infrastructure: dedicated accounts, potential employees, and possibly existing insurance. The entity has real assets at stake, which creates a baseline incentive to stay insured. In practice, if you require insurance and a vendor entity declines to carry any, that's a red flag worth addressing before the ink dries, not after.

Sole proprietors — freelancers, independent contractors working under their own name — are a different matter entirely. A sole proprietor's business liability is their personal liability; there's no separate entity absorbing the risk. They may carry no professional coverage at all, particularly in knowledge-work or creative fields. Some buy professional liability policies that exclude bodily injury entirely, creating a gap for anything physical that happens on-site.

For solo contractors, consider these adjustments:

• Require general liability at a minimum if they'll work on-site physically
• Require E&O if their work involves professional judgment, code, financial advice, or design
• Consider accepting lower limits ($500,000 rather than $1 million) for very small, low-risk engagements where the realistic exposure is proportionally limited
• Request the actual declarations page of the policy, not just a COI, if you have any doubt about what's actually covered
• Check whether your own CGL covers losses from vendor work performed on your premises — many do, partially

An online search for a standard independent contractor agreement will turn up dozens of template options. Most say nothing about insurance. That's the gap this clause fills, and filling it costs nothing beyond a few extra paragraphs.

Common Drafting Mistakes That Gut Your Protection

These are the mistakes that come up repeatedly when businesses try to create their own insurance provisions without reviewing what the clause actually needs to do:

• Setting limits that haven't been updated since 2010. "$500,000 per occurrence" sounded reasonable fifteen years ago. Today, a single slip-and-fall can generate medical bills, litigation costs, and a judgment that exceeds that figure. Check what your own umbrella policy requires as an underlying minimum and match it.
• Forgetting the tail requirement for claims-made policies. Almost all professional liability and E&O policies are claims-made. A contractor who lets their policy lapse the day after delivering a project leaves you exposed to claims that surface months or years later, when the coverage period has ended.
• Using "or equivalent" as a hedge. "Commercial general liability or equivalent coverage" hands the contractor the right to define "equivalent." Drop this hedge entirely. Name the policy type explicitly.
• Relying on the COI alone without requiring the endorsement. Already covered above, but it bears repeating — a COI is not a policy, and additional insured status listed only on a certificate is not enforceable additional insured status.
• Failing to update limits when the project scope grows. If a project doubles in value, the risk exposure often doubles too. Consider a clause that requires updated limits if the aggregate contract value exceeds an agreed threshold.

Subcontractor Flow-Down: Making Sure Their Subs Are Covered

Your prime contractor may subcontract parts of the work. Their subcontractor — who you've never met and didn't vet — may be the person who actually causes the loss. Your contract with the prime almost certainly doesn't reach that sub.

Flow-down clauses solve this by requiring your prime to impose the same insurance obligations on their subcontractors. Include language like this in your subcontractor agreement or directly in your prime service agreement:

"Contractor shall require all subcontractors engaged in performance of this Agreement to maintain insurance coverage at least equivalent to the coverage required of Contractor under this Agreement, and shall provide Client with evidence of such coverage upon request."

This doesn't automatically give you a direct claim against the subcontractor's insurer — for that, you'd need to be named as an additional insured on the sub's policy too, which is harder to enforce at that tier. But it does create a contractual obligation on your prime to ensure coverage exists down the chain, and it gives you a breach claim if they didn't bother. For higher-risk engagements — construction, on-site labor, anything involving physical work — ask for proof of sub-tier coverage before work starts.

For engagements where you're engaging multiple vendors with overlapping scopes, separate agreements for each layer of the work are almost always worth the drafting time. A single omnibus "everyone is covered somehow" arrangement tends to unravel exactly when it's most needed.

State Law Wrinkles You Should Not Ignore

Several state-specific rules affect how insurance clauses operate in practice. The most significant:

Anti-indemnity statutes. Texas, Louisiana, North Dakota, and several other states limit or prohibit contractual provisions that require a party to indemnify another for that party's own negligence. Because insurance requirements and indemnification are often paired — and sometimes the insurance clause is worded to cover losses attributable to the client — a clause in those states that forces a contractor to insure the client's own negligence may be unenforceable. Review the pairing carefully before finalizing.

Statutory employer rules. Florida, Texas, and a handful of other states impose workers' compensation liability on a hiring business that engages an uninsured subcontractor, treating it as the "statutory employer" of those workers. If your contractor doesn't carry workers' comp and their employee is injured at your location, you may be on the hook for benefits under state law regardless of your contract terms. This is one of the stronger arguments for requiring workers' comp coverage rather than treating it as optional.

Additional insured requirements by state. A few states require specific endorsement language to create valid additional insured status. A generic COI notation may not satisfy those requirements. When contracting across state lines, specify that coverage requirements apply "under policies issued in compliance with the laws of the state where work is performed" — or list each relevant state explicitly if you operate in multiple jurisdictions.

Pre-Signing Checklist: Insurance Clauses Done Right

Before you sign — or hand a draft to the other side — run through this list. It's shorter than it looks, and each item has a reason behind it:

• CGL, E&O, workers' comp, and (if applicable) commercial auto are named with specific dollar minimums — no "appropriate" or "equivalent" placeholders
• You are named as additional insured by endorsement to the underlying policy, with a copy of that endorsement required before work starts
• Claims-made policies (E&O, professional liability) carry a tail-coverage period of at least 24 months after the project ends
• A mutual waiver of subrogation is included
• The contractor must deliver a COI within 5 business days of signing and notify you of cancellation 30 days in advance
• Failure to maintain insurance is expressly a material breach, and the contractor cannot resume work after a lapse without your written acceptance of reinstated coverage
• Flow-down clause requires subcontractors to carry equivalent coverage, with proof available on request
• State-specific anti-indemnity and statutory employer rules have been reviewed for states where work will be performed

None of this needs to be written from scratch every time. A solid service agreement or consulting agreement template already has slots for most of these provisions. Your job is to make sure the blanks are filled with real numbers and not left as placeholders like "[amount]" or "[coverage type]." Those placeholders, by the way, are more common in final signed contracts than anyone wants to admit.

One more practical note: store every COI, every endorsement, and every renewal certificate somewhere you can actually find it when a claim happens. Not buried in an email thread with the subject line "Re: Re: Re: Fwd: Project kickoff." One folder, one naming convention, maintained throughout the engagement. That's not a legal requirement. It's just common sense with a filing cabinet — and the kind of thing that makes the difference between a resolved claim and a prolonged one.

Article reviewed by: Sylvia M. (Attorney)