Insurance compliance
9 min readAll explainers

Subcontractor insurance certificate compliance 101.

What a Certificate of Insurance must list for a GC to accept it — additional-insured endorsements, primary-and-non-contributory wording, waiver of subrogation, and per-occurrence and aggregate limits that match the subcontract — the most common ACORD 25 mistakes that bounce a submittal, when a separate builders-risk policy or commercial umbrella rider is required, and how admin support keeps the COI master log current against policy renewals — written and run by Johnston Admin Management Services at $45/hour, billed to the exact minute through Clockify.

Written by Johnston Admin Management Services LLC · Virginia HQ, U.S. nationwide.
Section 1

What a COI must list for the GC to accept it

A Certificate of Insurance — issued on the ACORD 25 form — is the document a subcontractor provides before setting foot on the jobsite. It is also the most commonly mis-filed compliance document in construction: a COI that looks right on its face but lacks the right endorsement citations is unenforceable, and a bounced COI stalls the sub's start date while the GC waits on the corrected version.

For a GC to accept a COI without sending it back, four things must be present and verifiable: the GC must be named as an additional insured on the sub's Commercial General Liability and Commercial Auto policies via a policy endorsement (not just a certificate notation); per-occurrence and aggregate limits must meet or exceed the subcontract minimums; the Description of Operations box must confirm primary-and-non-contributory status and a waiver of subrogation; and the policy dates must bracket the full project period. Every one of these can be present in summary form on the certificate face and absent in the actual policy — which is why the endorsement citation, not the certificate checkbox, is what the compliance desk verifies.

The four COI acceptance requirements

A GC compliance desk verifies these four items — all four must be present before the sub is cleared to work.

  • Additional-insured endorsement — GC (and owner, if the prime contract requires) named on CGL and auto via CG 20 10 / CG 20 37 or a blanket AI endorsement, with the endorsement number cited in the Description of Operations box.
  • Limits meeting the subcontract floor — commonly $1M per occurrence / $2M aggregate for CGL, $1M CSL for auto, plus any umbrella or excess layer the contract specifies.
  • Primary-and-non-contributory language — confirmed in the Description of Operations, backed by an ISO CG 20 01 or equivalent endorsement so the notation is enforceable.
  • Waiver of subrogation— the carrier's right of recovery against the GC is waived in favor of the GC and owner, stated in the Description of Operations and backed by an endorsement.
  • Policy dates bracketing the project period— effective date before the sub's start date; expiration date after the project's substantial completion plus any warranty tail the subcontract names.

The ACORD 25 itself is not the policy — it is a broker-issued snapshot that is expressly non-binding and non-amendatory. Checking the boxes on the certificate face without confirming the endorsement behind each box is the single most common compliance gap that GC risk managers find on audit. A COI that says “additional insured — if required by contract” with no endorsement number is not a compliant COI; it is a placeholder.

Section 2

Common ACORD 25 mistakes that bounce a submittal

Six mistakes account for the vast majority of bounced COIs. Most are broker errors, not carrier errors — the endorsement exists and is in force, but the broker issued the certificate without citing it. The fix is typically a reissued certificate, not a new endorsement, but the reissue still takes time the sub doesn't have if the GC has a start-date deadline.

Mistake #1

Endorsement not cited

Additional-insured status shown on the certificate face but no endorsement number in the Description of Operations. The AI endorsement exists; the broker just omitted the citation. Fix: reissued COI with the CG 20 10 / CG 20 37 form number in the Description of Operations box.

Mistake #2

Missing PNC language

The certificate shows "additional insured" but does not confirm that the GC's own policy is excess. Without primary-and-non-contributory language, both carriers share the loss pro-rata and the GC's own policy erodes.

Mistake #3

No waiver of subrogation

The carrier's right of recovery against the GC is not waived. If the sub's carrier later pursues the GC for a loss the sub caused, the GC has no contractual bar to that recovery claim.

Mistake #4

Wrong project address

The Description of Operations cites a prior project or leaves the address blank. The GC's compliance desk cannot confirm that the coverage described applies to this jobsite.

Mistake #5

Policy expires mid-project

The policy expiration date falls before the project's substantial completion — sometimes before the sub even finishes its scope. A mid-project gap means the sub is uninsured on the jobsite the day the policy lapses.

Mistake #6

Umbrella not scheduled

The subcontract requires $5 million total limits; the underlying CGL shows $1 million; no follow-form umbrella is listed. The certificate appears to show adequate limits until the GC adds the columns.

The pattern behind all six: the policy is in place but the certificate does not accurately describe it. The fix is almost always a reissued ACORD 25, not a new policy. Keeping a standard COI checklist — reviewed on intake for every new sub — is the GC's defense against bouncing the same sub twice on the same mistake.

Section 3

When a builders-risk or umbrella rider is required

Standard CGL covers third-party bodily injury and property damage arising from the sub's operations. It does not automatically cover damage to the structure under construction, and it does not close the gap when the sub's underlying limits fall below the contract floor. Builders-risk and umbrella/excess policies fill those two gaps — but whether the sub is required to carry them depends on the subcontract insurance exhibit, not the ACORD form.

When each policy type is triggered
  • Builders-risk (Course of Construction) — required when the subcontract makes the sub responsible for damage to the structure — common on mechanical, electrical, and roofing subs. The GC may carry the master policy and require the sub to be named, or may require a separate sub limit.
  • Commercial umbrella / excess— required when the sub's underlying CGL and auto limits are below the contract minimum. Example: contract floor $5M aggregate, sub CGL shows $2M — a $3M follow-form umbrella closes the gap.
  • Professional liability (E&O) — required for design-assist subs whose scope includes engineering or design deliverables. Stand-alone policy; not covered by CGL.
  • Pollution liability — required for subs working with hazardous materials (abatement, underground storage, chemical handling). Stand-alone policy; standard CGL excludes pollution.

The controlling document is the subcontract's insurance exhibit, not the ACORD form. Every requirement listed there needs a corresponding policy line on the COI — builders-risk, umbrella, E&O, and pollution each has its own line with its own carrier, policy number, and limit. A COI that lists only CGL, auto, and workers' comp is not a complete submittal if the exhibit requires additional policy types.

Section 4

Primary-and-non-contributory wording explained

Primary-and-non-contributory is not a coverage type — it is a loss-sharing rule that determines which carrier pays first when a claim triggers both the sub's CGL and the GC's own liability policy. Without it, both carriers treat themselves as co-primary and share the loss pro-rata, which erodes the GC's policy on a claim that is the sub's fault and drives up the GC's renewal premium accordingly.

Without PNC

Both carriers share the loss pro-rata

Both the sub's CGL and the GC's own policy contribute to the claim at their respective coverage ratios. The GC's policy erodes on the sub's fault — raising the GC's loss-run and renewal premium.

With PNC endorsement

Sub's policy responds first, GC's is excess

The sub's CGL pays up to its limits before the GC's policy contributes anything. The GC's loss-run is protected on sub-caused claims, and the GC's renewal premium is not eroded by the sub's work.

Most GC subcontracts require PNC by endorsement — ISO CG 20 01 or equivalent — not by certificate notation. A Description of Operations box that says “primary and non-contributory” without an endorsement form number cited is unenforceable: the carrier can reject the notation as a certificate modification that alters the policy terms. The compliance check: endorsement form number cited in the Description of Operations box, or endorsement page attached to the COI transmittal.

Section 5

How admin support keeps the COI master log current against policy renewals

The COI master log is a per-sub register of every policy line — CGL, auto, umbrella, workers' comp, builders-risk, professional liability — with carrier, policy number, effective and expiration dates, per-occurrence and aggregate limits, and endorsement status for each. On a mid-size project with 15-40 active subs, the log is not a document you update once and file: it is a live compliance register with daily intake on new submittals and weekly sweeps on near-expiry policies.

The COI log maintenance cadence

Four operational habits keep the log from becoming a compliance liability.

  • 45-day renewal chase— every policy within 45 days of expiration gets a renewal request to the sub's broker. Enough lead time for the broker to issue the renewal certificate before the old one lapses.
  • Incoming COI cross-check — each renewal COI is verified against the subcontract insurance exhibit: limits, endorsements, and policy dates all confirmed before the log is updated.
  • Gap flag to the PM— any sub whose policy expired and no renewal COI has been received is flagged to the GC's project manager before the next scheduled site visit, not after.
  • Superseded certificate archive — every prior COI is retained against the policy period it covered, so the GC has a complete paper trail if a completed-operations claim arrives years after the project closes.

A mid-size project with 20 active subs, each with 4-5 policy lines, generates 80-100 policy lines that need monitoring — and on a 12-month project, most of those policies will renew at least once. Running that intake and renewal cadence ad-hoc, alongside a PM's full schedule, is how gaps appear. A dedicated admin running the COI queue at $45/hour — daily intake, weekly renewal sweep, gap flags before the site visit — keeps the log current and the project's risk manager off the defensive.

FAQ

Frequently asked questions.

What must a Certificate of Insurance list for a GC to accept it?

The COI (typically an ACORD 25) must name the GC as an additional insured on the subcontractor's Commercial General Liability and Commercial Auto policies — not just on the certificate itself but via a policy endorsement (CG 20 10 / CG 20 37 or equivalent). The certificate must show per-occurrence and aggregate limits equal to or greater than the amounts the subcontract specifies — commonly $1 million per occurrence / $2 million aggregate for CGL, and $1 million CSL for auto — and it must show the same limits on any Umbrella or Excess policy the contract requires. The ACORD 25 Description of Operations box must include language confirming that the additional-insured status is on a primary-and-non-contributory basis and that a waiver of subrogation applies in favor of the GC and owner. The policy effective and expiration dates must bracket the entire project period, including any warranty tail the subcontract specifies. A certificate that shows correct limits but omits the endorsement citation, or that uses "if required by contract" language without a signed endorsement attached, is routinely bounced.

What are the most common ACORD 25 mistakes that bounce a submittal?

Six mistakes account for the majority of bounced COIs at the GC's desk. (1) Additional-insured status shown only on the certificate face — not backed by an endorsement number in the Description of Operations box; insurers issue the endorsement at no cost but brokers sometimes omit the citation. (2) Missing primary-and-non-contributory language — the certificate says "additional insured" but does not confirm that the GC's own policy is excess. (3) No waiver of subrogation — the carrier's right of recovery against the GC is not waived in writing, which exposes the GC if the sub's carrier later seeks to recover. (4) Wrong project address — the Description of Operations cites a prior project or leaves the address blank, and the GC's compliance desk cannot confirm coverage. (5) Expiration date before project substantial completion — a policy that expires mid-project creates a coverage gap the GC's risk manager must flag before the next draw. (6) Umbrella or Excess policy not scheduled — the subcontract requires $5 million total limits, the underlying CGL shows $1 million, but no follow-form umbrella is listed to close the gap.

What is additional-insured status and why does the endorsement matter more than the certificate?

An additional insured is a party — here the GC and often the owner — who gains the right to be defended and indemnified under the subcontractor's policy for claims arising from the sub's work. The ACORD 25 certificate is a snapshot issued by the broker; it is expressly non-binding and non-amendatory — the certificate itself creates no coverage. The policy endorsement is the binding document. A GC that accepts a COI without confirming the endorsement (CG 20 10 for ongoing operations, CG 20 37 for completed operations, or a blanket AI endorsement with project-specific language) has no enforceable coverage if the sub's carrier disputes the certificate. Best practice: require the sub's broker to attach the endorsement pages to the COI transmittal, or confirm the endorsement number in the Description of Operations field. An endorsement obtained after a loss is rarely effective retroactively.

When is a separate builders-risk policy or commercial umbrella rider required?

A builders-risk policy (also called Course of Construction insurance) is required any time the subcontract or the prime contract includes language making the sub responsible for damage to the structure under construction — common on specialty subs (mechanical, electrical, roofing) who work on partially complete buildings and whose scope could cause fire, water, or structural loss. The GC may carry the master builders-risk and require the sub only to be named, or may require the sub to carry its own limit if the sub's scope is a standalone contract. A commercial umbrella or excess liability rider is required when the sub's underlying CGL and auto limits are below the contract floor — e.g., a subcontract requiring $5 million aggregate means a sub with $2 million CGL must show a $3 million follow-form umbrella. Some contracts also require professional liability (E&O) for design-assist subs and pollution liability for subs working with hazardous materials; both are stand-alone policies not covered by standard CGL. Check the subcontract's insurance exhibit — it is the controlling document, not the ACORD form.

What is primary-and-non-contributory wording and why do GCs require it?

Primary-and-non-contributory (PNC) language means that when a claim triggers both the sub's CGL and the GC's own liability policy, the sub's policy responds first and pays up to its limits before the GC's policy contributes anything. Without PNC, both insurers share the loss pro-rata, which means the GC's own policy is eroded by the sub's claim — raising the GC's loss experience and potentially its renewal premium. Most GC subcontracts require PNC by endorsement (ISO CG 20 01 or equivalent), not just by certificate notation. A certificate that says "primary and non-contributory" in the Description of Operations box without a corresponding endorsement is unenforceable — the carrier can reject the language as a certificate modification. Verify the endorsement form number is cited, or ask the sub's broker to attach the page.

How does admin support keep the COI master log current against policy renewals?

The COI master log is a per-sub register that tracks every policy line (CGL, auto, umbrella, workers' comp, builders-risk, professional liability) with its carrier, policy number, effective date, expiration date, per-occurrence limit, aggregate limit, and endorsement status. Admin support keeps it current by (1) setting a 45-day renewal chase on every expiring policy — enough lead time for the broker to issue a renewal certificate before the old one lapses; (2) cross-checking each incoming renewal COI against the subcontract insurance exhibit to confirm limits and endorsements still meet the requirement; (3) flagging any gap (a sub whose policy expired yesterday is uninsured on the jobsite today) to the GC's project manager before the next scheduled site visit; and (4) archiving the superseded certificates against the policy period they covered, so the GC has a complete paper trail if a completed-operations claim arrives years after the project closes. Most active GC offices have 15-40 active subs on a mid-size project; the log update cadence is a weekly sweep on near-expiry policies and a daily intake on new COI submittals — exactly the kind of volume that justifies a dedicated admin running the queue at $45/hour rather than the PM handling it ad-hoc.

TL;DR

The 30-second version.

  • A COI is not the policy — it is a broker-issued snapshot. The endorsement behind each certificate checkbox (additional insured, primary-and-non-contributory, waiver of subrogation) is what creates enforceable coverage.
  • For a GC to accept a COI: additional-insured endorsement cited (CG 20 10 / CG 20 37), limits meeting the subcontract floor, PNC and waiver of subrogation confirmed by endorsement, and policy dates bracketing the full project period.
  • Six mistakes bounce most COIs: endorsement not cited, missing PNC language, no waiver of subrogation, wrong project address, policy expires mid-project, and umbrella not scheduled. Most are broker errors — a reissued certificate fixes them, but it still takes time.
  • Builders-risk is required when the sub is responsible for damage to the structure under construction. Umbrella is required when underlying limits are below the contract floor. The controlling document is the subcontract's insurance exhibit.
  • Primary-and-non-contributory means the sub's policy pays first; the GC's policy is excess. Without a PNC endorsement cited on the COI, "primary and non-contributory" in the Description of Operations box is unenforceable.
  • The COI master log is a live register — daily intake on new submittals, weekly sweep on near-expiry policies (45-day renewal chase), gap flags to the PM before the site visit, and a superseded-certificate archive for completed-operations claims.
Who this helps

For general contractors.

Keep subcontractor insurance certificates current, searchable, and ready for the next compliance check without chasing the inbox.

Explore support for general contractors
Send the subcontracts, we'll run the COI log

From first COI submittal to a current master log.

Drop the subcontract insurance exhibits and the current COI submittals — we'll build the per-sub master log, run the intake checklist on every new COI, set the 45-day renewal chase, and flag gaps before the site visit. At $45/hour, billed to the exact minute, every minute visible on the invoice before the line amount is ever printed.

$45/hour · Clockify-tracked · billed to the exact minute
Read next
General contractors

Admin support behind every GC's subcontractor roster.

COI compliance, pay-app intake, lien waiver tracking — the admin work behind a GC's subcontractor roster, run at $45/hour, billed to the exact minute.

Pay applications

G702/G703 payment applications explained — for subcontractors.

What G702 and G703 actually are, when subs file them, where lien waivers fit in the monthly billing cycle, and the six mistakes that stall pay apps on the GC's desk.