Back to Guides
ConstructionInsurance Basics

Construction Contract Insurance Requirements: What to Include in Subcontracts

Bramble·March 23, 2026·5 min read

A $17 million data center project in Austin uses a standard subcontract form with a 12-page insurance exhibit. The project administrator reviewing the electrical subcontractor's COI is checking against a two-page internal checklist - one that hasn't been updated in four years and doesn't reflect the requirements in the current subcontract form. The internal checklist says $2M per-occurrence GL; the subcontract exhibit requires $5M. The checklist says AI required; the subcontract exhibit requires both CG 20 10 and CG 20 37, primary and noncontributory, with a specific notice of cancellation period.

The sub is marked compliant. The checklist says so. The subcontract says something different.

This disconnect - between what the contract requires and what the compliance review actually checks - is one of the most common sources of construction insurance coverage gaps. Closing it requires knowing how to read a construction contract insurance exhibit and how to translate that language into a specific verification checklist.

Anatomy of a Construction Contract Insurance Exhibit

Key Compliance Facts
70%
Sub COIs non-compliant at first receipt
$500K+
Average cost of one uncovered claim
41%
Sub COIs with at least one material gap

Most commercial subcontracts include a standalone insurance exhibit or rider that specifies subcontractor insurance requirements. These exhibits vary considerably in length and specificity - from a half-page matrix of limits to a 15-page detailed specification - but they share common structural elements.

Section 1: Required Coverage Lines Lists each line of coverage required: commercial general liability, workers' compensation and employers' liability, commercial auto, umbrella/excess liability, and any specialty lines (professional liability, pollution, builders risk, etc.).

Section 2: Minimum Limits Specifies minimum limits for each coverage line, often in a table format. Pay attention to whether aggregate limits are per-project or per-policy, and whether there are separate sublimits for specific claim types.

Section 3: Endorsement Requirements Specifies required endorsements by name and, in well-drafted exhibits, by ISO form number. This section typically addresses additional insured, waiver of subrogation, primary and noncontributory, and notice of cancellation requirements.

Section 4: Additional Insured Schedule Lists the entities that must be named as additional insureds - typically the GC, the owner, the lender, and sometimes the owner's lender. The GC entity name must be exact.

Section 5: Special Provisions Project-specific or scope-specific requirements that modify the standard exhibit for this particular subcontract or project type.

Extracting Requirements from Subcontract Language

Compliance Process
1
Subcontract Review
Extract all insurance and endorsement requirements
2
COI Collection
Require certificates before site mobilization
3
Clause Comparison
Verify limits, AI, WOS against subcontract
4
Completed Ops
Track post-completion coverage for claims protection

Insurance requirements are not always confined to the insurance exhibit. They can appear in:

  • The main subcontract body (Article 11 is common for insurance in AIA and ConsensusDocs forms)
  • Special conditions attached to the subcontract
  • The prime contract, which is often incorporated by reference
  • Rider documents or amendments
  • The project specifications (Division 01 in CSI format)

When reviewing a subcontract for insurance requirements, check all documents, not just the exhibit. Prime contract flow-down is particularly important: if the owner-GC contract requires higher limits than the GC-sub contract, the GC is carrying the gap on paper - and may be liable to the owner for failing to flow down those requirements.

Common Construction Insurance Contract Clauses

Additional Insured (AI)

Standard language: "The Subcontractor shall name the Contractor, Owner, and Owner's lender as additional insureds on the Subcontractor's commercial general liability policy, including coverage for completed operations, on ISO form CG 20 10 and CG 20 37 or equivalent."

What to verify: Both form numbers present on endorsement; all required entities named; "or equivalent" language investigated if a non-ISO form is used.

Waiver of Subrogation (WOS)

Standard language: "The Subcontractor waives all rights of recovery against the Contractor, Owner, and their respective agents, employees, and successors for any loss or damage covered by the Subcontractor's insurance policies, including workers' compensation."

What to verify: WOS endorsement on GL, WC, and auto; WOS applies to all entities listed; no carve-outs or exceptions that contradict the contract language.

Primary and Noncontributory (P&NC)

Standard language: "The Subcontractor's insurance shall be primary and noncontributory with respect to any other insurance maintained by the Contractor or Owner."

What to verify: P&NC endorsement (CG 20 01 or equivalent) on the GL policy; if only AI endorsement is issued, confirm the AI endorsement includes P&NC language.

This clause is critical. Without P&NC, if a claim triggers both the sub's GL policy and the GC's GL policy, both carriers can argue that the other policy is "primary" and contest defense obligations. P&NC resolves this: the sub's policy pays first, and the GC's policy is excess.

Notice of Cancellation

Standard language: "The Subcontractor shall provide thirty (30) days' prior written notice to the Contractor in the event of cancellation or non-renewal of any required insurance policy."

What to verify: The ACORD 25 has a field for notice of cancellation, but many policies limit notice to 10 days for non-payment of premium. If your contract requires 30 days, verify the actual endorsement provides that period.

Per-Project Aggregate

Standard language: "The limits of liability required herein shall apply as a separate limit for each project at which the Subcontractor performs work."

What to verify: Per-project aggregate endorsement on GL policy; not all carriers offer this, and it may require a premium adjustment.

Financial Strength Requirement

Standard language: "All insurance shall be maintained with insurers rated no less than A- (Excellent) by A.M. Best."

What to verify: Look up each insurer's A.M. Best rating; verify the rating class as well as the rating (A-/XII vs A-/VIII matters for large projects).

Translating Contract Language into a Verification Checklist

The goal is to convert the contract insurance exhibit into a specific, line-by-line checklist that the compliance reviewer uses when reviewing the COI. This checklist should:

  1. List every coverage line required and the specific minimum limit
  2. List every endorsement required with the specific form number where provided
  3. List every additional insured entity with the exact legal name
  4. List all special requirements (per-project aggregate, financial strength rating, etc.)
  5. Include the source document and section for each requirement (for audit purposes)

A checklist built from this contract-specific analysis will catch gaps that a generic template will miss - and will produce a documented compliance determination tied to the specific subcontract.

How Bramble Reads Contracts to Extract Requirements Automatically

Manual extraction of insurance requirements from a 15-page subcontract exhibit is time-consuming and prone to error. An experienced reviewer doing a careful job spends 30-45 minutes extracting requirements from a complex subcontract. A less-experienced reviewer may miss provisions in special conditions or prime contract flow-down language.

Bramble automates this extraction step. Upload the subcontract (including all attached exhibits, riders, and incorporated documents), and the system identifies all insurance requirements - limits, endorsements, additional insured entities, special provisions - and structures them into a verification checklist. The checklist is then used to compare against the sub's COI automatically.

The result: consistent, comprehensive requirement extraction that catches everything in the contract, not just what a reviewer happened to notice. For GCs who use multiple subcontract forms or who frequently incorporate project-specific riders, this consistency is the difference between genuine compliance and documented guesswork. See how Bramble reads construction contracts to extract insurance requirements.

See how Bramble reads the document that defines what the certificate should contain.

See It In Action