A maintenance contractor wraps up work on a commercial property. The landlord collected the contractor's Certificate of Insurance before work started, confirmed the coverage limits looked right, and filed the certificate. The contractor's COI listed the landlord as an additional insured. A claim arises. The insurer denies coverage. The reason: the underlying policy contained an exclusion the certificate never mentioned.
The landlord had the paper. The landlord had a signed contract requiring insurance. What the landlord did not have was coverage.
This is not an unusual outcome. It is the standard one.
A Certificate of Insurance is administrative evidence that a policy exists. It is not the policy. Courts across jurisdictions have held that when a COI conflicts with the underlying policy, the policy controls. Exclusions left off the certificate are not waived. Coverage listed on a certificate that the policy does not actually provide does not become real coverage because the certificate said so.
What the Certificate Actually Is — and What Courts Say It Isn't?
ACORD certificates, the standard form used across the industry, carry an explicit disclaimer on their face: "This certificate is issued as a matter of information only and confers no rights upon the certificate holder. This certificate does not affirmatively or negatively amend, extend, or alter the coverage afforded by the policies below."
That language is not boilerplate filler. It is the legal architecture of the document.
In Mountain Fuel Supply Co. v. Reliance Insurance Co. (10th Cir. 1991), the court applied this logic directly. A COI that expressly states it does not alter policy terms cannot amend the insurance contract. The policy language governs. Courts cite this case repeatedly for what they call the majority rule: when the certificate and the policy conflict, the policy wins.
Taylor v. Kinsella (2d Cir. 1984) reinforced the same point. The certificate is expressly subject to the policy's terms and conditions. Exclusions in the policy remain enforceable even where the COI implies otherwise.
Bradley Real Estate Trust v. Plummer and Rowe Insurance Agency (NH, 609 A.2d 1233, 1992) put it plainly: a COI is merely evidence that insurance exists. It is not the insurance contract.
Landlords and property managers who collect COIs and treat them as proof of coverage are treating evidence of a contract as the contract itself. Those are different things.
Does a Certificate of Insurance Create Coverage the Policy Does Not Provide?
No. The question is worth examining precisely because so many real estate operators act as if the answer might be yes.
A COI typically does not enumerate policy exclusions. A contractor's certificate may show $2M in general liability coverage without disclosing that the policy excludes the specific type of work being performed on the property. The certificate holder sees the coverage amount. The exclusion is invisible.
Courts have been consistent on this point. Omission of an exclusion from a certificate does not waive that exclusion. Certificate holders are expected to understand that the COI is a summary, not the definitive source of coverage terms. Erie Insurance Exchange v. Gosnell (Md., 230 A.2d 467, 1967) stated this directly: when the certificate conflicts with the policy, the policy controls. That case is still cited when insurers enforce exclusions that COIs failed to mention.
The operational implication for real estate is specific. A property team that requires a vendor to carry completed operations coverage, professional liability, or additional insured status must verify those terms in the actual policy and its endorsements, not in the certificate. If those provisions are not in the policy, the COI cannot put them there.
When Can a COI Actually Bind the Insurer?
There are exceptions. They are narrow, jurisdiction-dependent, and turn on specific facts. Treating them as reliable protection is a mistake.
Equitable Estoppel is the doctrine most often raised when a misleading COI causes harm. The argument: the insurer (or its authorized representative) issued a certificate that misrepresented coverage, the certificate holder reasonably relied on it, and that reliance caused prejudice. If those elements are present, a court may stop the insurer from denying the representations in the certificate. The catch is that courts are reluctant to use estoppel to create coverage that never existed in the policy. Quincy Mutual Fire Insurance Co. v. Imperium Insurance Co. (3d Cir. 2016) held that reliance on a COI containing standard ACORD disclaimer language is not reasonable reliance, which defeats the estoppel argument outright.
Agency Authority is where the more consequential exceptions live. T-Mobile USA, Inc. v. Selective Insurance Co. of America (Wash. 2019) held that an insurer was bound by its authorized agent's representation in a COI identifying an additional insured, even though the underlying policy listed a different entity. The court's reasoning turned on the agent's actual authority. When a broker or agent has actual or apparent authority to bind the insurer, the insurer can be held responsible for what that agent represented in the certificate.
The distinction matters in ways that most COI compliance programs miss entirely. If the broker acts solely on behalf of the insured and lacks authority from the insurer, liability for an inaccurate COI may fall on the broker for negligent misrepresentation, not on the insurer. The certificate holder still has a claim. The claim is against a different party, and that difference affects recovery, timing, and litigation strategy significantly.
Why COI-Only Reliance Keeps Showing Up in Real Estate?
The COI has become a compliance checkbox rather than a compliance mechanism. Property teams collect them, file them, and treat collection as confirmation of coverage. The underlying policy rarely gets reviewed. The endorsements almost never get verified.
The pressure is volume. A portfolio with 50 vendors has 50 annual renewals, some with mid-term changes. Teams covering larger portfolios collect hundreds. Reviewing every endorsement page is not realistic without systems built for it. So teams rely on the summary document, which is precisely what the courts say they should not do.
What Property Teams Should Do Differently?
Treat the COI as the starting point, not the finish line. The certificate tells you a policy exists and gives you the policy number. Actual confirmation of coverage requires looking at the declarations page, relevant endorsements, and the specific provisions that matter for your property and your relationship with that vendor or tenant. A number on a certificate is not a guarantee.
When specific endorsements matter, request the endorsement documents directly. Additional insured status, waiver of subrogation, and completed operations coverage each require a specific endorsement to the policy. A COI that lists any of these does not make them present. Courts have declined to create that coverage from the certificate alone. Request and retain the actual endorsement documents for any provision your lease or vendor contract specifically requires.
Build verification into the workflow, not just the checklist. QTREN manages COI collection and expiration tracking across vendor and tenant relationships, with automated compliance flagging that closes the gap between "collected" and "verified" before a claim forces the issue.
The Broader Lesson
A COI that lists your property as an additional insured is an assertion, made by a broker, on a summary document, that a policy meeting certain parameters exists. The policy itself is the guarantee. Or it is not.
The question every property team should ask after their next COI collection: if a claim arose tomorrow against this vendor's policy, do we actually know what coverage exists, or do we only know what the certificate said?
Disclaimer: This article is provided for informational and educational purposes only and does not constitute legal, financial, or compliance advice. Real estate professionals should consult qualified counsel regarding insurance requirements, certificate of insurance standards, and jurisdiction-specific coverage obligations.