Certificates of Insurance (COIs): what they prove
A Certificate of Insurance (COI) is one of the most common documents requested in business. Landlords, general contractors, vendors, property managers, and clients ask for them to confirm that insurance exists and to document basic policy details. Used correctly, a COI prevents delays and keeps contracts moving.
Used incorrectly, a COI creates false confidence. Many “compliance surprises” happen when someone assumes the certificate changes coverage, guarantees payment, or adds protections that only exist with specific endorsements. This guide explains what a COI proves, what it does not do, and how to keep requests simple, accurate, and fast.
What a COI is (and why it exists)
A COI is a standardized summary of a policy. It’s meant to communicate key facts quickly—not to rewrite the insurance contract.
- Proof of insurance: shows that certain coverages are currently in force on a specific date.
- Snapshot of key terms: carrier, policy number, effective dates, and major limits.
- Evidence for compliance: supports contract requirements like GL limits, auto liability, workers’ comp, or umbrella.
A COI is a receipt-like summary—useful for verification, but not a substitute for the policy itself.
What a COI does prove
A COI can confirm the existence of coverage and document the high-level structure your client or vendor needs to see.
- Coverage exists today: the listed policies are active on the issue date, for the named insured shown.
- Effective dates: confirms the policy term (and whether it aligns with a contract start date).
- Limits at a glance: general liability, auto liability, umbrella/excess, and other major limits shown on the form.
- Certificate holder identity: documents who requested the certificate and where it should be sent.
A COI is often “good enough” for basic compliance—especially when requirements are limited to standard coverages and standard limits.
If the requirement is simple, the COI is usually simple. Complexity starts when someone needs the policy changed.
What a COI does NOT do (common compliance surprises)
Most COI problems come from assuming the certificate creates coverage. It does not.
-
It does not add coverage:
If the policy doesn’t include a required endorsement, the certificate cannot “promise” it into existence.
This includes additional insured status, waiver of subrogation, primary & noncontributory wording, and special project endorsements.
-
It does not guarantee payment:
Claims are paid according to the policy language, exclusions, conditions, and claim facts—not based on a certificate.
A COI is informational. It is not a claim approval or a guarantee of indemnity.
- It does not override exclusions: If a loss is excluded (contractual liability limits, professional services, residential work, certain hazards), a COI won’t change that.
- It does not guarantee notice of cancellation: Many certificates reference cancellation notice language, but carriers and policy terms control what notice is actually required.
A certificate can confirm coverage exists—it cannot expand what the coverage does.
When a COI request actually requires policy changes
Some requirements are not “certificate items.” They require endorsements or underwriting approval.
- Additional insured (AI): usually requires a specific endorsement; wording varies by contract and carrier.
- Primary & noncontributory: often requires a separate endorsement or built-in form language.
- Waiver of subrogation: common on WC/GL/auto; typically endorsement-based and sometimes priced.
- Per project / per location endorsements: frequent in construction and property management.
- Higher limits or umbrella requirements: may require re-rating, updated applications, or carrier approval.
If your contract includes any of the items above, send the requirement language to your agent early. “We just need a certificate” often becomes “we need an endorsement.”
The fastest COI is the one that matches reality—endorsements requested upfront, not after rejection.
How to request a COI the right way
Clear requests prevent back-and-forth and reduce the risk of your certificate being rejected by compliance.
- Use the exact legal name: your business name should match the policy; the certificate holder should match the contract.
- Provide the requirement text: send the insurance section of the contract—especially endorsement wording.
- List limits and coverages: GL, auto, WC, umbrella; include required minimum limits and any special conditions.
- Confirm the job scope: location, type of work, and whether subs are involved can affect eligibility and endorsements.
- Allow lead time: certificates are quick; endorsements can require underwriting review.
The goal is not “a certificate.” The goal is acceptance by compliance without surprises.
How to read a COI (what matters most)
You don’t need to memorize the form. Focus on the sections that cause rejections and delays.
- Named insured: confirms the policy is actually yours (or your subcontractor’s).
- Policy effective dates: confirm they cover the project dates; watch for renewals mid-project.
- Limits: verify the numbers match the contract (per occurrence vs aggregate matters).
- Description / remarks: where AI status, project naming, and special wording often appears.
- Certificate holder: ensure the entity and address are correct to avoid compliance rejection.
If a contract requires an endorsement, the “remarks” section may reference it—but the actual endorsement is the proof. When in doubt, request copies of the endorsements.
The COI is the summary. The endorsement is the evidence.
Common reasons a COI gets rejected (and how to prevent it)
Rejections are usually fixable—if you know what compliance is actually checking.
-
Mismatch in names:
certificate holder name doesn’t match the contract, or insured name doesn’t match the entity doing the work.
Tip: if you operate under a DBA, confirm how it’s shown on the policy.
- Missing endorsements: additional insured / waiver / primary & noncontributory required but not actually endorsed.
- Limits don’t match: contract requires higher limits or a specific structure (e.g., $1M per occurrence + $2M aggregate + umbrella).
- Wrong coverage type: hired/non-owned auto may be required when you don’t own vehicles; or WC is required but you only have a waiver/exemption.
- Dates don’t align: policy renews mid-project and the updated certificate wasn’t issued; compliance flags it as expired.
Most “certificate problems” aren’t document problems—they’re policy structure problems.
Common questions
Does a COI make someone an additional insured?
Not by itself. Additional insured status is created by an endorsement (or policy form language). A COI can reference that status, but it does not create it.
Can you add special wording in the description box?
Sometimes, but wording in the description does not override the policy. If compliance requires specific language, the correct approach is the proper endorsement.
How fast can I get a COI?
Basic certificates are usually quick. Requests involving endorsements, project-specific wording, or underwriting approval can take longer—especially if submitted right before a deadline.
Use COIs for proof—not promises
A COI verifies coverage exists and summarizes the basics. It does not modify the policy, guarantee claim payment, or replace endorsements. If a contract requires special status or wording, handle it early and request the endorsement—then the certificate becomes a formality, not a scramble.