COI vs. AI Endorsement: Where Liability Leaks

The claim that got denied for a form nobody read

A roofing sub drops a bundle off a scaffold, damages a unit owner's lanai, and the association files against the vendor's general liability policy naming itself as additional insured. The certificate on file says the association is covered. The carrier denies anyway.

The reason: the certificate of insurance was accurate, but no additional-insured endorsement was ever issued naming the association. The cert had the box checked. The policy had no matching form. A certificate is a summary written by a broker's assistant. It confers no rights and amends no policy. Coverage lives in the endorsement.

This is the quiet failure mode across community management. The file looks complete. Every vendor folder has a green checkmark. Then a loss happens, an adjuster pulls the actual policy, and the endorsement that was supposed to protect the association does not exist or excludes the exact work being done.

What is the difference between a COI and an additional-insured endorsement?

A certificate of insurance is a summary document that states policy numbers, limits, and dates. It typically includes the disclaimer 'this certificate is issued as a matter of information only and confers no rights upon the certificate holder.' Read that sentence again. It is telling you the truth.

An additional-insured endorsement is a form (commonly ISO CG 20 10 for ongoing operations and CG 20 37 for completed operations) that actually amends the vendor's policy to cover the association as if it were a named insured for claims arising from the vendor's work. This is what a carrier honors.

The uncomfortable part: a large share of vendor files that look fully compliant contain a cert with the additional-insured box checked and no endorsement behind it. Nobody is lying. The broker checked the box because the client requested it. Whether the underwriter issued the form is a separate question that only gets answered when you ask for the endorsement itself.

Who should be named on whose policy?

Additional-insured requirements flow in two directions that boards routinely confuse. Vendors name the association on their general liability policy. The management company names the association (and often the board) on its own liability and errors-and-omissions coverage. Owners in a self-managed or hybrid arrangement should confirm they appear on the manager's policies, not just the vendors'.

The gap boards miss most often is the manager's professional liability. Boards check every vendor's GL and never ask the management company for its own additional-insured endorsement. If the manager's decision causes a loss, the association wants to sit inside that coverage, not litigate to get there.

The endorsement-verification checklist

Do not verify a certificate. Verify the endorsement. Run every vendor and the management company itself through this list before work starts and again at every renewal. The renewal check matters because a vendor can switch carriers mid-term and quietly drop the association from the new policy.

How an AI desk reads endorsement wording and flags mismatches

The reason endorsement verification rarely happens is that it is tedious, text-heavy, deadline-driven work that a busy manager pushes down the list until a claim forces it up. Reading a form number, checking a legal name character by character, and cross-referencing an exclusion against the scope of work is exactly the kind of documented, repetitive task that an AI agent handles well and humans hate.

At One Home Agent we built Victor Vendors to read the endorsement text, not just log that a cert arrived. Victor compares the actual form (form number, named entity, ongoing versus completed operations, exclusions, primary and noncontributory language) against the association's written requirement, and flags the mismatch before work starts and again at renewal. When a vendor's new carrier drops the completed-operations form, Victor catches it in the diary sweep, not after a defect surfaces.

“Every denied claim I have seen traced back to a document that was in the file and never actually read. The cert said covered. The endorsement said otherwise. Machines are patient enough to read the form. People are not, and they should not have to be.”

Todd Paton, Partner, One Home Agent

The pattern generalizes beyond insurance. Any requirement expressed as text against a checklist (license status, W-9 completeness, expiration diary) is a fit for AI vendor COI tracking. The agent does the reading and the flagging. It does not decide whether the coverage is adequate.

Why a human still confirms coverage adequacy

An AI agent can confirm the endorsement exists, names the right entity, and includes the right forms. It cannot decide whether a $1 million limit is enough for a 300-unit high-rise or whether a specific exclusion is acceptable for the risk. That judgment belongs to a manager, the board, and often the association's insurance counsel or broker.

This is the honest line on where the machine stops. Victor reads the wording and surfaces the gap. A human reads the surfaced gap and decides: accept it, require a higher limit, demand the missing endorsement, or refuse the vendor. The agent removes the excuse for not reading the form. It does not remove the accountability for the decision.