ISO Insurance Endorsement Codes: A Contractor’s Reference

What do ISO insurance endorsement form numbers mean?

ISO stands for Insurance Services Office. Verisk describes its ISO standardized policy forms and endorsements as policy wording that is revised over time. Insurance endorsement form numbers identify those documents, including the commercial general liability series marked CG. An endorsement changes a policy; a certificate of insurance summarizes information about policies.

Asking a subcontractor to put a form number on a COI does not replace asking for the endorsement itself. The New York Department of Financial Services guidance on certificates explains that certificates should not alter policy terms. Our additional insured versus certificate holder guide explains why being listed as the holder does not establish additional insured status.

Treat the code as a filing reference. It helps your coordinator request the right page and a later reviewer understand what was accepted. Start with the signed requirement, then connect each supporting document to the subcontractor, job and applicable insurance-exhibit item.

Which CG endorsement codes do contractors need to check?

This table covers commercial general liability forms that can arise in contractor and vendor files. Purposes are abbreviated, not full coverage descriptions. Read the issued edition and policy before deciding whether it meets a requirement. The linked specimens are references, not documents to complete yourself or attach to a vendor's policy.

Keep separate requirements separate. Our primary and non-contributory versus waiver of subrogation comparison explains why those two requests need different evidence. Cancellation notice needs its own review too; use the ACORD 25 notice-of-cancellation guide for that question.

How do you read an endorsement edition date?

A full identifier such as CG 20 01 12 19 includes the base form number and an endorsement edition date. Here, 12 19 means December 2019. It is not the date the subcontractor bought the policy, the date an agent issued the certificate, or the date coverage expires. Those belong in separate fields in your review record.

You can see that identifier on the CG 20 01 specimen published by the City of Ventura. Its primary and non-contributory treatment depends on conditions, including an agreement in writing. Finding the expected heading is therefore only the start of the check.

Copy the full identifier into your log exactly as printed. If your contract asks for an older edition and the carrier supplies a newer one, flag the difference for review. Do not approve it merely because the base form number matches, or reject it merely because the year differs. Ask which wording the contract requires and whether the issued form meets that requirement. Save the reviewer's explanation so the next person does not have to repeat the comparison at renewal.

Can CG 20 10 replace CG 20 37 for completed operations?

Do not carry an old edition's coverage assumptions into a newer form. Contemporary CG 20 10 editions address ongoing operations; CG 20 37 addresses completed operations. If the contract requests both, a packet containing only CG 20 10 leaves a completed-operations question open. A renewal certificate also does not prove last year's endorsements continued unchanged. Compare the current issued forms each time.

For the wording and edition differences between the scheduled ongoing- and completed-operations forms, use our CG 20 10 versus CG 20 37 guide. Keep this reference for identifying the document you need next.

How do you spot endorsement mismatches in a contractor file?

A clean specimen can demonstrate what a form looks like. Your file needs evidence of what the insurer issued for this insured. Request the complete endorsement, referenced declarations or schedules, and enough policy information to connect the pages. An isolated blank form downloaded from the internet leaves that connection unanswered.

• Policy connection: compare the named insured and policy number across the COI, declarations and endorsement. A page from the prior carrier needs an explanation.
• Protected party: compare the scheduled legal entity with the contract. A parent name may leave a subsidiary unaddressed. For automatic status, check the written-contract trigger.
• Work or location: match the project address and operations. Follow “see schedule” references; a missing schedule leaves the check open.
• Timing: distinguish the edition date from the endorsement effective date. Confirm the applicable policy period and any written-contract conditions.
• Coverage purpose: distinguish ongoing work, completed work, primary wording and waivers. One matching code cannot close all four requirements.

The distinction matters for aggregates as well. The CG 25 04 and CG 25 03 specimens in this carrier packet designate locations and construction projects respectively. Neither is a shortcut for assuming every limit resets for every job. Check the applicable schedule and the limits the endorsement actually changes. See our per-project aggregate endorsement guide for a worked comparison.

When should a broker review the endorsement wording?

Stop at the point where the question becomes whether wording is equivalent, a condition is satisfied, or an exclusion defeats the intended protection. A carrier-specific code is a reason to request the wording, not evidence that the document is wrong. Send your broker the contract requirement, certificate, endorsement and schedule together, with the exact question you need answered.

For example, the CG 24 04 05 09 specimen names liability coverage parts and a scheduled beneficiary. A request for a workers' compensation waiver needs evidence from that policy, not an assumption based on this GL form. Likewise, a wrap-up project needs review beyond the additional insured pages. Our OCIP and CCIP wrap-exclusion guide addresses that separate issue.

Are CG 20 11 and CG 20 12 substitutes for construction endorsements?

Match the relationship before comparing numbers. CG 20 11 concerns leased premises; CG 20 12 concerns governmental permits or authorizations. A landlord, a permit issuer and a project owner have different roles. When either code appears in a construction packet, ask which contract obligation it answers and what evidence supports the remaining work-related requirements.

Worked example: does this endorsement packet match the subcontract?

In this hypothetical example, Cedar Electric LLC works for Oak Construction LLC at 18 Market Street. The subcontract requires ongoing and completed-operations additional insured coverage, primary and non-contributory treatment, and a GL waiver. The agent sends a COI for policy GL-4821 and CG 20 10 04 13 naming Oak Construction Inc. at 81 Market Street. No completed-operations page is included.

Log the full identifier, then flag two schedule mismatches: the protected entity and the project address. Ask the producer to confirm the intended entity and location and supply corrected issued evidence if needed. Separately request completed-operations evidence, the provision supporting primary treatment, and the GL waiver with its schedule. Reconcile each page to GL-4821.

Send one clear deficiency list: the missing evidence, the requirement it relates to, and where the agent should send the response. Our COI request email templates provide a starting point. Keep the status as awaiting review until the reviewer resolves the questions. Record the decision separately from the date the email arrived.

If revised pages name Oak Construction LLC at 18 Market Street and the reviewer confirms the remaining requirements, close those items with the reviewer's name, date and document references. A corrected COI alone leaves the missing endorsement evidence unresolved.

What belongs on a contractor endorsement checklist?

Turn the requirements in your subcontractor insurance clause into a short review register beside the PDFs so a coordinator can tell what was requested, received and accepted. One row per requirement works better than one blanket note saying all insurance is approved. For each row, keep:

1. Requirement: the contract clause or insurance-exhibit item, with the required party and work.
2. Evidence: file name, relevant page, full form identifier, policy number and any referenced schedule.
3. Open question: the missing document or wording issue, the person handling it and the requested response date.
4. Decision: reviewer, review date, outcome and any approved exception or broker explanation.
5. Next review: policy expiration and any project milestone that requires another check.

At renewal, use the old register as your comparison list rather than copying its approval forward. Ask for the current evidence, note any carrier or form changes, and close each requirement again. Preserve the prior documents and decision record so a question about last year's work can be answered from last year's file. Your retention schedule should follow your contracts and professional advice, not the space left in an inbox.

Give someone responsibility for unresolved items. A note that says broker reviewing is useful only if a person owns the next action. The same applies when a project manager requests an exception: record who authorized it, which requirement it covers and when it must be reconsidered.

How can SubDoc support insurance endorsement review?

SubDoc helps organize vendor insurance records and the information extracted from certificates. Its endorsement signals can help a reviewer see what needs attention. They do not establish which exact ISO edition was issued or whether a contract trigger has been satisfied.

Choose the workflow around the person doing the review. Check current plan details for feature availability, and agree with your broker how questions about policy wording will be handled.

Frequently Asked Questions