Contract Insurance Clauses: Limits, Exclusions, Endorsements
Contract Insurance Clauses: Limits, Exclusions, Endorsements
A practical walkthrough for small construction businesses to compare a client's insurance request against what your policy actually covers before you sign.
Updated on: 2026-10-09
The contract says $2 million per occurrence and a $4 million aggregate, with a per-project aggregate endorsement. Your declarations page says $1 million per occurrence and $2 million aggregate. Somebody on the project is going to ask you to prove you meet the contract. And the gap between what the contract wants and what your policy carries is where a lot of small contractors get stuck, usually about three days before they're supposed to start work.
Here is the thing most people miss: a limit printed in a contract is not proof you carry that limit. A certificate showing the right numbers is not proof the coverage behaves the way the contract assumes. The only documents that tell you what you actually have are your declarations, your coverage forms, your exclusion endorsements, and the schedule of any umbrella or excess policies. Everything else is a summary of a summary.
This is a review workflow, not a licensing explainer and not a certificate-of-insurance tutorial. The goal is to help you read a client's insurance request, line it up against your real policy, and know exactly which questions to bring to your agent or broker before you commit.
Start by separating "requested" from "covered"
When a contract lands, there's usually an insurance section buried in it. It lists coverage types, limits, required endorsements, and sometimes a duration. Treat that section as a shopping list the client wrote. It describes what they want you to have. It says nothing about what you've got.
Public construction-insurance requirements make this obvious. The University of California's construction insurance guidelines describe their requirements as a framework rather than a one-size rule, and the University of Colorado's sample requirements change depending on the type of work and the contract form. Different buyers set different limits for different projects. So the number in front of you is one buyer's demand, not an industry minimum and not a benchmark you should assume applies everywhere.
My read: do this comparison on paper, side by side, before you call anyone. Half the panic calls to a broker could be a calm email if the contractor had first circled the specific mismatches instead of forwarding the whole contract and asking "am I covered?"
What to actually compare, clause by clause
Here's the comparison I'd run through. Left column is what the contract asks. Right column is what you verify in your own documents.
| Contract asks for | Where to confirm it in your policy | The pitfall that bites people |
|---|---|---|
| Limit per occurrence | Your each-occurrence limit on the applicable coverage form, plus any umbrella layer you're counting | An occurrence limit is not the annual aggregate. For covered bodily injury and property damage, the occurrence limit also applies to completed-operations losses |
| General aggregate | The aggregate amount and how it applies; whether a per-project or per-location aggregate is required | The general aggregate and the products/completed-operations aggregate are separate pools. Prior claims may have already drawn down what's left |
| Products/completed-operations | The separate completed-ops aggregate and how long the contract wants coverage to continue after the job ends | Damage can surface after you've finished. One university sample asks for completed-ops coverage to continue three years post-completion, longer for high-value buildings. That's their term, not a universal rule |
| Umbrella or excess limit | The schedule of underlying policies, the excess policy's own exclusions, and how each layer attaches | "Follow form" does not guarantee the excess matches the underlying. Excess policies carry their own exclusions and exceptions |
| Required coverage type | Whether you actually hold that line (GL, auto, workers' comp, builder's risk, professional, pollution) for this work | A big liability limit does not substitute for a different policy type the contract names |
| Exclusions and restrictions | The full exclusion endorsements and the work, materials, or hazards they touch | An exclusion can quietly remove the exact exposure the project depends on |
| Claims-made terms (where relevant) | Retroactive date, reporting requirements, extended reporting / tail provisions | A claims-made policy can hinge on both when the act happened and when the claim is reported. The retro date matters |
The occurrence-versus-aggregate distinction is the one I see tripped over most. Contractors read "$2 million" and feel covered, not noticing the contract wants $2 million per occurrence against a $4 million aggregate, with a per-project aggregate so one bad job doesn't eat the whole year's limit. The standard ACORD certificate language even warns that displayed limits may already be reduced by paid claims. A project-specific aggregate endorsement changes how the general aggregate applies, and you cannot assume it's attached just because the contract wants it.
Endorsements: read the wording, not the label
Endorsements are where "it says so on the certificate" falls apart. The name of an endorsement tells you its subject. It does not tell you its scope, its conditions, or whether it fits the relationship the contract describes.
Additional insured. If the contract asks to be named as an additional insured, I'd keep the review simple here and point you to the dedicated article on it, because the mechanics deserve their own space. The one point that belongs in a contract review: additional-insured status does not add limits, and the endorsement's scope has to match the requested relationship and the work. Some forms cover ongoing operations, others cover completed operations. A Sonoma County reference guide gives a case where the endorsement supplied as proof didn't actually fit the relationship between the parties.
Primary and non-contributory. If requested, confirm the real policy wording addresses both ideas. "Primary" on its own doesn't establish that your policy won't share costs with another primary policy.
Waiver of subrogation. This is its own requested term. It is not a byproduct of additional-insured status. Check the relevant policy and endorsement instead of assuming one supplies the other.
Everything else. Match the contract's exact language to the issued endorsements and their conditions. A certificate summary doesn't prove the wording is present.
Exclusions are where the real surprises live
Limits are the loud part of the comparison. Exclusions are the quiet part, and they're usually what actually determines whether a claim gets paid.
The University of California construction form specifically flags exclusions worth checking: damage to subcontractor or vendor work, insured-contract language, residential or multifamily work, EIFS, and subsidence or earth movement. Those are examples a careful buyer raises. They are not proof your policy carries any of them, and not every project needs the same wording. But they're a good prompt. If you're a roofer and your policy excludes a type of roofing the project involves, the limit on the page is irrelevant.
Read the actual exclusion endorsements. Ask one question per exclusion: does this remove or narrow something the contract or the project relies on? If the answer is yes or "I'm not sure," that's a line for your agent.
A concrete mismatch, and why the certificate won't fix it
Back to the opening example. Contract wants $2M per occurrence, $4M aggregate, per-project aggregate. Your declarations show $1M per occurrence, $2M aggregate.
That's an apparent mismatch, and it goes to your insurance professional, not to a certificate. You can't close this gap by producing a nicer-looking certificate, and you can't assume an umbrella quietly solves it. If an umbrella is in play, someone still has to confirm how it attaches, whether its terms and exclusions match the required coverage, and whether the aggregate structure the contract wants actually reaches this project. These numbers are illustrative. The point is the shape of the problem, not the figures.
This is also where the certificate caveat earns its one paragraph. The standard ACORD certificate states it's informational and does not amend, extend, or alter the policy, and that an additional insured must be endorsed, not merely listed. Georgia's insurance regulator makes a similar point under Georgia's certificate rules: a certificate can't expand coverage, and the underlying policy or endorsements can be requested to verify compliance. Those are Georgia-specific legal rules, so don't stretch them to every state. The general lesson holds regardless: the certificate is a receipt, not the coverage.
The review checklist I'd actually use
Before accepting a job, run through these six. Most take a minute each once you have the right documents open.
- Scope. Does your policy cover this trade, this operation, this location, and this phase of work?
- Limits. Do occurrence, aggregate, and completed-operations limits meet the contract, including how the aggregates apply?
- Restrictions. Does any exclusion or endorsement narrow coverage for this particular work?
- Required parties and terms. Are the requested endorsements actually attached, and do their wording and duration fit the contract?
- Timing. Will the needed policies and endorsements be in force before work starts, and for any required period after completion?
- Escalation. Send policy-compliance questions to your agent or broker. Send indemnity, defense, warranty, and other legal obligations to an attorney.
That last split matters. Insurance requirements do not necessarily cap your separate contractual obligations. The University of Colorado's sample is explicit that its insurance terms do not limit the indemnity covenants in the contract. So the indemnity clause can obligate you well beyond your insurance limits, and that's a lawyer's call, not your agent's.
Where a contractor-focused insurer fits
Doing this review well is easier when your coverage was built around construction work in the first place. 1 Insurance Solutions works specifically with contractors across trades, putting general liability, workers' compensation, builder's risk, and professional liability under one roof, which means the person reviewing a contract request against your policy already understands why a per-project aggregate or a completed-operations period shows up in the first place. Coverage should reflect your trade, your subcontractor exposure, your project values, and your contractual obligations, and the actual policy language, exclusions, limits, and endorsements are what decide whether a contract's requirements are met. A generic small-business policy rarely maps cleanly onto a construction contract's demands, which is exactly how coverage gaps go unnoticed until a claim.
I'd still bring the specific mismatches to a real person. The value of the checklist above isn't that it answers the questions. It's that it hands your agent a precise list instead of a forwarded PDF and a prayer.
FAQ
Does a certificate of insurance prove I meet the contract's requirements?
No. A certificate is informational and doesn't amend or extend the policy. It summarizes limits that may already be reduced by paid claims, and it can't make you an additional insured on its own. To prove compliance, someone has to look at the declarations, coverage forms, and endorsements behind it.
My limit is lower than the contract wants. Does an umbrella automatically cover the gap?
Not automatically. An umbrella or excess policy has its own schedule of underlying policies, its own exclusions, and its own attachment rules. "Follow form" doesn't guarantee it mirrors the coverage below it. You have to confirm how each layer applies and whether its terms match what the contract requires.
Isn't checking exclusions overkill for a small job?
That's the assumption I'd push back on. Exclusions decide whether a claim gets paid regardless of job size. A single exclusion for the exact type of work on a small project can wipe out coverage that your limits suggest you have. It takes a few minutes to scan the exclusion endorsements, and it's the cheapest part of the whole review.
Can my insurance agent interpret the indemnity clause?
Your agent can confirm whether your policy meets the insurance requirements. Indemnity, defense, and warranty language is a legal interpretation and belongs with an attorney. Insurance limits don't necessarily cap what you've agreed to contractually, so the two reviews are separate on purpose.
Further reading
- University of California construction insurance guidelines
- University of Colorado sample insurance requirements
- ACORD certificate sample and caveats
- Additional insured endorsements reference guide
A note for the editor: the strategy brief calls for internal links to the published general-liability guide, the coverage overview, and the dedicated additional-insured article. Those live URLs were not available in the research, so please confirm and insert the correct internal targets before publishing. The brand link above is a placeholder and should be verified against the live domain.
