Does Adding Language to a COI Constitute Fraud? – IA Magazine

Certificates of insurance (COIs) are the most misunderstood one-page documents in commercial insurance. Everyone wants them. Everyone emails them at 4:58 p.m. on a Friday. And everyone seems to think they can do magic. Need broader coverage? “Just add a sentence to the COI.” Need to guarantee contract compliance? “Just write it in the description box.” Need peace of mind? “Maybe add three more all-caps lines.”

Here’s the problem: a COI is not a magic wand, and it is definitely not a policy endorsement. So when someone asks an agent or broker to add wording that goes beyond what the policy actually says, the issue is not just awkwardit can become a compliance, licensing, and errors & omissions (E&O) risk very quickly.

The short answer to the question in the IA Magazine title is this: adding language to a COI is not automatically “fraud” in every situation, but it can absolutely be a material misrepresentation, an unfair trade practice, or a violation of state certificate-of-insurance laws if the wording implies coverage the policy does not provide. And if there is intent to deceive, some jurisdictions could treat the conduct as fraud or insurance fraud under broader statutes.

In other words: calling it “fraud” may be legally imprecise in some states, but calling it “harmless” is even more dangerous.

What IA Magazine Gets Right About the COI Problem

The IA Magazine scenario is classic real-world insurance chaos: a school system asks the agent to add broad wording to the COI saying the policy will automatically cover all phases of work and people “whether specifically written therein or not.” That language sounds reassuring to the certificate holderbut from the producer’s point of view, it sounds like someone is trying to use the COI to rewrite the policy after the fact.

The IA Magazine responses are refreshingly blunt (and honestly, the insurance industry needs blunt sometimes): producers should not add broad wording like that to a COI unless the policy itself supports it, and if the requested language is truly required, the proper route is a carrier-issued endorsementnot freestyle certificate drafting. IA’s experts also point out an important nuance: while they push back on using the term “insurance fraud” casually, they still frame unsupported COI wording as material misrepresentation.

That distinction matters. It keeps the discussion legally grounded while still making clear that the request is not a paperwork quirk. It is a coverage representation problem.

Why a COI Cannot Change Coverage

1) The COI is evidence, not the contract

Across industry guidance and state law, the same principle shows up again and again: a certificate of insurance is evidence that a policy exists, not the policy itself. It summarizes coverage at a point in time. It does not create new rights. It does not expand exclusions. It does not sneak an extra insured onto the policy just because someone typed a name into a box.

That is why the standard certificate language and many state statutes emphasize that a COI does not amend, extend, or alter coverage. If a contract party wants different coverage, the legal tool is a policy endorsement, rider, or amendment issued by the insurernot a sentence in the COI description field.

2) State laws now specifically prohibit “creative COI writing”

Many states adopted certificate-of-insurance statutes modeled on the NCOIL approach. The theme is consistent: no one should prepare, issue, request, or require a COI that contains false or misleading information or that purports to alter the policy. These laws were designed to stop exactly the kind of pressure producers face from owners, GCs, landlords, and public entities demanding “special wording” that the actual policy doesn’t support.

For example, New York law prohibits requiring unsupported language in a COI and explicitly says a certificate cannot amend, extend, or alter coverage. Delaware’s statute says the same and also allows enforcement and fines. Texas likewise bars false or misleading COI content and states plainly that a certificate is not a policy and does not amend, extend, or alter coverage.

Translation: if someone says, “Everybody adds this wording,” the legal answer may still be, “Cool story, still not allowed.”

So… Is It Fraud, Misrepresentation, or Just Bad Practice?

This is where people talk past each other. The word fraud is emotionally satisfying because it sounds serious (and it is serious), but it also has legal baggage: fraud often requires elements like intentional misrepresentation, reliance, and damages. Not every bad COI sentence checks every box.

In many day-to-day cases, the cleaner and more accurate terms are:

• Material misrepresentation (the COI suggests coverage the policy does not provide)
• Unfair trade practice (in some states, depending on statutes/regulations)
• Unauthorized policy-form activity (if the COI effectively acts like a custom coverage form)
• E&O exposure (if the certificate holder relies on the COI and suffers a loss)

That said, if someone knowingly inserts false wording to induce a contract award, payment, or reliance, the risk level goes way up. Even where the exact label varies by jurisdiction, the legal and professional consequences can include regulatory complaints, civil liability, licensing trouble, and a very uncomfortable conversation with the carrier’s claims department.

The Real Risk: Detrimental Reliance and E&O Claims

Producers sometimes hear “a COI doesn’t change coverage” and assume they’re safe. Not quite. Industry guidance also warns about detrimental reliance: if a certificate holder reasonably relies on a misleading COI and gets hurt, the COI issuer may still face liabilityeven if the underlying policy never changed.

Insurance educators and legal commentators have been making this point for years. The policy may stay exactly what it was, but the dispute shifts to whether someone made a false representation and whether another party reasonably relied on it. That is where E&O claims are born.

IRMI’s commentary underscores how common the problem can be in contract-heavy industries. Their analysis of contractor certificates found a high rate of material misrepresentation when comparing what certificates implied versus what the actual policies and endorsements provided. That is not a typo-level issue. That is a process problem.

Additional Insured Confusion Is the Usual Suspect

If COIs had a “most wanted” poster, additional insured status would be in the center. Most COI fights come down to one question: “Does this certificate actually mean I’m covered as an additional insured?”

Often, the answer is: not by itself.

Certificate holder ≠ additional insured

A certificate holder is just the recipient of the certificate. An additional insured is someone actually added to the policy by endorsement or qualifying automatic endorsement language. Those are not the same thing, and New York DFS has expressly said so.

Contract language still matters

In many blanket additional insured endorsements, the key is the written contract requirement. If the endorsement grants AI status when required by written contract, then the contract and endorsement drive coveragenot the COI wording. That is why experienced coverage lawyers tell companies to request and review the actual endorsement, not just the certificate.

Typos and project descriptions can create panic

Insurance Journal’s Big I Insights piece addresses a common nightmare: the COI lists the wrong project name or address. The article’s core point is useful: the COI typically does not alter the policy’s AI grant, but mistakes can still trigger disputes, delays, and reliance arguments. So even when the policy is legally stronger than the certificate, sloppy COI drafting still causes expensive headaches.

Can a COI Ever Matter in Court?

Yesbut usually not in the way people hope.

Courts often repeat the general rule that COIs do not create coverage. But case law also shows narrow exceptions and edge cases involving agency authority, estoppel, or reliance. Some courts have treated COIs as evidence that can create factual disputes, especially when an authorized agent issued the COI and the certificate holder relied on it.

On the flip side, courts have also enforced the “information only” nature of COIs. A Washington Supreme Court case involving T-Mobile emphasized that the certificates did not create additional insured status where the policy and endorsements did not support it, and the court also highlighted the difference between a certificate holder and an additional insured.

The takeaway is not “COIs don’t matter.” The takeaway is: COIs matter a lot in litigation, just not as a substitute for the policy. They can become evidence of what was represented, who said what, whether reliance was reasonable, and whether an agent acted within authority.

What Producers Should Do Instead of Adding Unsupported COI Language

1) Compare the request to the actual policy and endorsements

Before typing anything into the COI, check the policy, the endorsements, and the contract insurance requirements. If the wording is not supported, do not “mirror the contract” on the certificate just to move the file forward. That shortcut is how routine certificate requests become claims files.

2) Send unsupported wording requests to the carrier

IA Magazine’s advice here is gold: if the wording is truly required, involve the carrier. Let underwriting or the carrier’s approved process determine whether an endorsement can be issued. Producers should not unilaterally create policy-like promises on a certificate.

3) Use precise, factual wording only

A COI should report what exists. If the insured has AI status by a specific endorsement, list the endorsement. If there are limitations, don’t imply broad guarantees. If the contract asks for something not present in the policy, the honest answer is not a longer sentenceit is a coverage gap conversation.

4) Train staff and standardize review

Many COI problems are process failures, not legal theory failures. Create a checklist for:

• Policy/endorsement verification
• Contract requirement comparison
• Approved COI wording library
• Escalation to carrier or management for custom requests
• Documentation of who requested what and how the request was handled

Boring? Yes. Effective? Also yes.

What Certificate Holders Should Do (Because They’re Not Off the Hook Either)

Owners, contractors, landlords, and public entities also contribute to COI chaos by demanding impossible wording. If you’re on the certificate-holder side, the best practice is simple:

1. Use approved COI forms
2. Request the actual endorsement when additional insured status matters
3. Review policy terms, not just the certificate summary
4. Stop requiring “guarantee” language on the COI that the policy does not contain

A COI can support contract administration, but it should not be used as a DIY coverage amendment kit.

Bottom Line

Does adding language to a COI constitute fraud? Sometimes that word is too broad, and sometimes it is exactly the word a regulator or plaintiff might use if the facts are bad enough. The safer, more practical answer is this: adding unsupported language to a COI is a serious misrepresentation and compliance risk, and in many states it directly violates certificate-of-insurance laws.

If the policy does not say it, the COI should not say it. If someone needs the coverage changed, the carrier must change the policy. Everything else is just expensive optimism in a 1-page form.

Experience-Based Scenarios and Lessons From the Field (Extended Section)

The following examples are composite, real-world-style scenarios drawn from common insurance workflows. They are not legal advice, but they reflect the kinds of disputes that repeatedly show up in agencies, construction projects, and claims reviews.

Experience #1: The “Can You Just Add This One Line?” School Contract

A small commercial contractor wins a job for a local public school renovation. The contract administrator sends a COI requirement sheet with a long custom statement that sounds authoritative and deeply suspicious. It includes wording that the policy “covers all operations, all subcontractors, and all exposures related to the project” and implies compliance with every insurance requirement in the contract.

The producer knows the CGL policy has limitations, and the additional insured status depends on a specific endorsement plus a written contract. The insured is pushing hard: “Please just put it on the certificate so we can start Monday.” This is the exact moment where good agencies earn their reputation. Instead of typing the sentence, the producer documents the request, explains that the COI cannot amend the policy, and sends the issue to the carrier for endorsement review.

The result? The project start is delayed by 48 hours, but the insured gets a clean explanation and a proper endorsement path. It feels painful in the moment, but it prevents a much bigger mess later. The lesson: a short delay is cheaper than a five-year E&O lawsuit.

Experience #2: The Additional Insured Box Was Checked… But Nothing Was Endorsed

On a fast-moving construction job, an account manager checks the “additional insured” notation in the COI description because the contract requires it. The problem: no AI endorsement was actually issued yet, and the policy’s blanket endorsement would not apply until a written contract was executed. The contract was signed two days after work began.

Months later, an injury claim comes in. The upstream party tenders to the subcontractor’s carrier and attaches the COI like it is a golden ticket. Claims denies AI status based on endorsement conditions and contract timing. The certificate holder is furious and points to the COI. The agency then spends weeks digging through emails, binder timelines, and contract drafts to explain what happened.

The policy may still control, but the COI created expectations that the policy did not satisfy. The lesson: certificates are not harmless summaries when they overstate statusthey become evidence of what someone was told.

Experience #3: The Wrong Project Address Triggered a Coverage Panic

A producer issues three COIs for three jobs with the same general contractor. Everything is correct except one line: the description box lists the wrong project address on one certificate. The actual policy and AI endorsement are fine, and the written contract requirement is also fine. But after a major loss, the carrier’s initial review flags the mismatch. The general contractor interprets that as “coverage denied.”

Cue emergency calls, angry voicemails, and a compliance meeting nobody wanted. After counsel and claims review the endorsements and contract, the coverage analysis returns to the policy language and the COI typo becomes a side issue. But the admin cost is massive. The insured loses confidence in the agency, the certificate holder demands more proof on future jobs, and the agency creates a new two-person COI QA process.

The lesson: even when a COI does not legally change coverage, inaccuracies still cost time, trust, and money.

Experience #4: The Best Outcome Is Usually the Least Dramatic One

A property manager asks for a COI statement guaranteeing “primary and noncontributory, waiver of subrogation, notice of cancellation, and full indemnification compliance.” The account executive does not panic and does not argue. They respond with a simple checklist:

• Here is the COI on the approved form.
• Here are the endorsements that support AI, primary/noncontributory, and waiver where applicable.
• Here is what the policy says about notice rights.
• Here is what cannot be certified because it is contractual, not policy language.

No drama, no fake wording, no mystery. The property manager gets what can be verified, the insured understands any remaining gaps, and the record is clean. It is not flashy, but it is exactly how strong insurance operations are supposed to work.

The biggest field lesson across all these scenarios is simple: COI discipline is risk management. The agencies that treat certificates as technical documentsnot customer service freebieshave fewer claim surprises, fewer compliance headaches, and better client relationships in the long run.

SEO Tags