By Patrick Turcotte, COO, Docutrax. Last reviewed: 18 September 2026.

A certificate of insurance reports policy types, limits at issuance, effective dates, the named insured, and whether the producer understands certain endorsements to be in place. Seven conditions that decide whether coverage responds are not on the form, or appear on it only in part, because the form has no field for what actually settles them. That is the form's scope, not a defect in it.

The gaps that matter are scope questions, not accuracy questions

Most published guidance on this subject treats the problem as accuracy. Certificates can be wrong, so verify them. That is true and it is the smaller half of the problem.

The larger half is that a certificate can be entirely accurate, issued in good faith by a licensed producer against a real policy, and still leave every question below unanswered. The current ACORD 25 (2025/12) coverages grid carries eight columns: INSR LTR, TYPE OF INSURANCE, ADDL INSD, SUBR WVD, POLICY NUMBER, POLICY EFF, POLICY EXP and LIMITS. There is no field for a retroactive date. There is no schedule of underlying insurance. There is no endorsement schedule and no field for exclusions. Nothing reports how much of an aggregate remains.

So the useful question is not whether a certificate is right. It is which document answers the question you actually have, and whether this relationship warrants asking it.

The aggregate is shared, and the certificate shows it as written

The general aggregate is the most the insurer will pay during the policy period for Coverage A damages outside the products-completed operations hazard, plus Coverages B and C. Products-completed operations carries its own separate aggregate. As Craig Stanovich puts it, once an insurer pays as damages the full amount of an aggregate limit, payment being pursuant to a judgment or settlement, "the insurer has no further obligation to any insured for any claims or suits that fall within the exhausted aggregate limit." Payments on claims that have nothing to do with your relationship reduce what is left for one that does.

The form is candid about this. On the 2025/12 edition the asterisked note reads: "*LIMITS SHOWN MAY HAVE BEEN REDUCED BY PAID CLAIMS. LIMITS SHOWN ARE INCLUSIVE OF AMOUNTS REQUESTED BY THE CERTIFICATE HOLDER AND MAY NOT REFLECT POLICY LIMIT AMOUNTS IN EXCESS OF THOSE REQUESTED." The form marks that note as not applicable in Wyoming. A limit on a certificate is a limit as written, not a balance. The second half of that note is newer and cuts the other way: a certificate may show only the limit the holder asked for, not the higher limit the policy actually carries.

One thing the certificate does report is the basis the aggregate runs on. The GEN'L AGGREGATE LIMIT APPLIES PER field shows POLICY, PROJECT, LOC or OTHER, and that is worth reading rather than skipping. Where a designated construction project endorsement is in place, ISO CG 25 03 05 09 provides that "a separate Designated Construction Project General Aggregate Limit applies to each designated construction project, and that limit is equal to the amount of the General Aggregate Limit shown in the Declarations," and that payments against one project's limit "shall not reduce the General Aggregate Limit shown in the Declarations nor shall they reduce any other Designated Construction Project General Aggregate Limit." The endorsement reaches only sums attributable to ongoing operations at the designated project, and completed operations still run against the products-completed operations aggregate.

So the election is visible and the balance is not. Where a third party works across many relationships on one shared aggregate, that difference is the exposure.

Additional insured limits are capped by your own contract

This one surprises people who have read the certificate correctly.

The 2013 ISO revisions changed what an additional insured can reach. Mark Bell's summary of the change is direct: where coverage for the additional insured is required by contract, the insurance "is limited to the lesser of the amount (1) required by contract or agreement or (2) available under the limits of insurance listed in the declarations." The endorsement also provides that the insurance applies only as permitted by law and will "not be broader than that which you are required by the contract or agreement to provide."

The consequence runs the opposite way to intuition. Under a 2013 or later ISO additional insured endorsement, if your contract requires $1 million and the third party carries $2 million, the certificate reports $2 million and you can reach $1 million. Which edition is actually in place is not on the certificate either. The extra limit belongs to the named insured, not to you. Requiring more in the contract is what moves that line, not finding a third party who happens to carry more.

Which endorsement is in place, and whether it reaches completed operations, is a separate question that our guide to insurance endorsements works through form by form.

The excess layer does not automatically inherit the primary's grants

An additional insured endorsement on the primary general liability policy carries upward automatically only on the ISO umbrella and excess forms, and even there on narrower terms; on the many policies not written on those forms, nothing carries it up by itself.

Gregory Podolak's account of how follow-form excess actually behaves is the sentence to keep: these policies "almost always state that the excess policy follows the terms of the underlying policy except to the extent that the excess policy's terms differ." The differences are where the risk transfer quietly stops. An excess policy's own other insurance clause can undo primary and noncontributory status granted below it. Its own transfer of rights clause can override a waiver of subrogation on the underlying policy.

The certificate cannot help here, and not because it is poorly designed. It has no schedule of underlying insurance, which is the document that identifies what the excess layer actually attaches over. A certificate showing $1 million primary and $5 million excess reports two policies. It does not establish that the second sits above the first for your claim, for your entity, or on the same terms.

Where a large excess layer is doing real work in your requirements, the excess policy's insured provisions and its underlying schedule are the proportionate next request.

A retention can sit underneath, and the form has no field for one on the primary line

The certificate does carry a DED RETENTION field. It sits on the UMBRELLA LIAB and EXCESS LIAB line. There is no equivalent field on the commercial general liability line, which is where a retention most often changes the practical answer.

The distinction that matters is between a retention and a deductible, and they are not interchangeable. Under a self-insured retention, IRMI's definition is that "the insured (rather than the insurer) pays the defense and/or indemnity costs associated with a claim until the SIR limit is reached." Under a deductible, "the insurer pays the defense and indemnity costs associated with a claim on the insured's behalf and then seeks reimbursement of the deductible payment from the insured."

Read that from your side of the relationship. Where a third party carries a substantial SIR, the first tranche of defense and indemnity depends on that third party's ability and willingness to fund it, not on the carrier's. The certificate shows a limit. The declarations page shows whether anyone has to reach that limit before the insurer's obligations begin.

A claims-made policy carries a retroactive date the certificate never shows

The form does report the trigger. The general liability section carries CLAIMS-MADE and OCCUR checkboxes, and reading which one is ticked is not optional. Construction general liability is overwhelmingly occurrence based, but professional liability, pollution and several specialty lines commonly are not.

What the form does not carry is a retroactive date field. A retroactive date, in IRMI's definition, is a provision "found in many (although not all) claims-made policies that eliminates coverage for claims produced by wrongful acts that took place prior to a specified date, even if the claim is first made during the policy period."

The operational consequence is specific. A third party that changed carriers, let a policy lapse, or bought claims-made coverage for the first time partway through your relationship can hold a current, in-force, correctly-reported policy that will not respond to work it performed for you earlier. The certificate reports the policy period. The retroactive date is on the declarations page, and where a claims-made line is contractually required it belongs in the requirement and in the request.

Employers liability is a separate coverage, and in some jurisdictions it lives somewhere else

Workers compensation and employers liability are two coverages, not one. The form treats them as two, carrying E.L. EACH ACCIDENT, E.L. DISEASE EA EMPLOYEE and E.L. DISEASE POLICY LIMIT as their own fields. Employers liability is the half that responds when an injured employee's claim reaches beyond the compensation system, which is the half that interacts with an upstream party's risk transfer.

Jurisdiction changes where it lives. In a monopolistic fund jurisdiction, an employer "must obtain workers compensation insurance from a compulsory state fund or qualify as a self-insurer (as is allowed in two of the jurisdictions)." IRMI names North Dakota, Ohio, Washington and Wyoming, along with Puerto Rico and the US Virgin Islands. And, in IRMI's words, "fund workers compensation policies do not provide employers liability coverage."

So it comes from somewhere else. A stop gap endorsement supplies it: attached to the workers compensation policy where the employer also operates in non-monopolistic states, and attached to the general liability policy where the employer operates only in a monopolistic fund state.

The practical point for a compliance operation is that employers liability limits reported on a certificate for work in one of these jurisdictions warrant a look at where that coverage actually sits, because a requirement written for a standard workers compensation policy does not describe the document that would satisfy it there.

The exclusion that decides whether an indemnity clause is insured

This is the one most worth understanding, because it decides whether the risk transfer you negotiated has any coverage behind it. Whether the indemnity obligation itself is enforceable is a separate question that turns on state law. Most states restrict construction indemnity by statute, and in New York General Obligations Law 5-322.1 makes a construction contract clause purporting to indemnify an upstream party for its own negligence void and unenforceable, though a clause limited to the fullest extent permitted by law can still shift the share attributable to others.

The standard CGL employers liability exclusion bars bodily injury to "an employee of the insured arising out of and in the course of" employment, and it applies whether the insured "may be liable as an employer or in any other capacity." Read alone, that would appear to eliminate coverage every time an upstream party turns to a third party's policy after that third party's own employee is hurt.

It does not, because of one sentence. The exclusion "does not apply to liability assumed by the insured under an 'insured contract'." That carve-out is what leaves the third party's own liability policy responding to an indemnity obligation it agreed to, to the extent that obligation assumes the tort liability of another party. It is the mechanism that makes contractual indemnity insurable, and both halves of the picture are true at once: where the basis of the claim is the alleged tort liability of the employer itself, Craig Stanovich notes that "the employers liability exclusion of the CGL policy excludes such 'action over' claims," while the contractually assumed route survives on the exception.

Which is why what carriers do to the exception matters. Stanovich again: "Insurers may remove the 'insured contract' exception, eliminating coverage for the named insured for any obligation to hold harmless and indemnify another for bodily injury to that named insured's employees." Amended employee injury and action over exclusions do this, sometimes in a single endorsement line. Nothing on the certificate reports it.

New York is where this most often becomes decisive. Labor Law 240(1) reaches elevation-related hazards, and within that scope it makes project owners and general contractors, in Theresa Guertin's description, "absolutely liable for any violation that results in an injury, regardless of whether the project owner or GC supervised or controlled the work." Labor Law 241(6) works differently: it turns on violation of a concrete Industrial Code specification rather than a general safety standard, and such a violation is evidence of negligence rather than a basis for absolute liability. Both impose a nondelegable duty, which routes the injured worker's claim upstream and then routes the upstream party back to the third party's indemnity obligation. Guertin's observation about how these exclusions get missed is worth quoting exactly: "Subtle Action Over exclusions is easily and often overlooked by the upstream parties." Finding one requires the policy.

Which of these are worth chasing, and when

None of this is an argument against certificates. A certificate is the right level of review across a large share of relationships, where the approved requirements and the inherent exposure do not call for deeper analysis, and confirming one properly is real work with real value. The question is never whether certificates matter. It is whether the depth of review matches the requirements and the exposure.

Where scope, jurisdiction, completed-operations exposure or potential liability warrants closer scrutiny, the certificate may not reveal exclusions or endorsement language that matters at claim time. These seven are a way of deciding which scrutiny to apply rather than a list to run on everyone.

What this changes in a compliance operation

Four things follow, and none of them is "review every policy."

Requirements name the document, not the outcome. "Additional insured status" is not something anyone can send you, and neither is "adequate limits." A requirement that names the endorsement form, the limit, the trigger and, where it matters, the retroactive date and the aggregate basis is a requirement that can be satisfied and checked.

Depth is assigned before collection, not after a problem. The seven conditions above are decided by the relationship, so the decision about which of them to chase belongs at the point requirements are set for that third party, not at the point a claim is tendered.

The request goes out once. Where the exposure calls for the declarations page or the endorsement pages, asking for them alongside the certificate at first submission costs one message. Asking afterwards costs a remediation cycle through the third party's broker or agent.

And what was confirmed is retained. Completed operations claims arrive years after a file closed, and on an occurrence form the policy that responds is the one in force when the injury or damage occurs, not the one in force when the work was done. That is why completed operations coverage and additional insured status have to stay required after the work ends, and why the record of what was confirmed has to outlive the file.

That is the work Docutrax does on behalf of its clients. Licensed P&C insurance professionals review the documents at the depth the client's approved requirements call for, with CRIS-certified Account Managers on construction-risk work, and Docutrax works with third parties and their brokers and agents to resolve what the review surfaces and maintains the record, across more than 300,000 forensic policy reviews since 2017. Docutrax surfaces what the documents establish and what they do not. The client sets the requirements and makes the decisions.

Patrick Turcotte, COO, Docutrax