HOAcrew
All resourcesInsurance

How to Verify a Vendor's Certificate of Insurance (and Why One Check Isn't Enough)

HOAcrew TeamJuly 8, 20267 min read

A certificate of insurance (COI) is the piece of paper a vendor hands over to prove they are covered. The problem is that boards treat it as a one-time formality — collect it at signing, file it, forget it. But a COI is a snapshot of coverage on the day it was issued. Policies get canceled, lapse for non-payment, or simply expire, and the certificate in your file keeps looking valid long after the coverage is gone.

Here is how to actually verify a COI when you receive it, and how to keep it verified for the life of the contract.

What you are looking at on a COI

Most certificates use the standard ACORD form. The fields that matter to a board:

  • The insured — this must be the exact vendor doing your work, matching the name on the contract. A certificate for a related or differently named entity does not protect you.
  • The insurer(s) — the actual insurance companies providing coverage.
  • Coverage types and limits — general liability, workers' compensation, auto, and any umbrella/excess coverage, each with per-occurrence and aggregate dollar limits.
  • Policy numbers and effective/expiration dates — the window during which coverage is active.
  • The certificate holder — this should be your association.
  • The description box — where "additional insured" status and other special terms are often noted.

Step 1: Confirm the coverage types and limits meet your requirement

Before you can verify a COI, your association has to have written down what it requires. The figures are your board's to set, and the usual source is your own insurer or lender — the carrier writing your master policy will tell you what it expects a vendor on the property to carry, and larger jobs generally warrant more. Get that number from your agent, put it in the vendor policy and the contract, and then you have something to check a certificate against.

What the requirement should name:

  • General liability, at a per-occurrence limit and an annual aggregate your board has set for the risk.
  • Workers' compensation for any vendor with employees. This is the coverage that keeps an injured worker's claim from landing on the association. Do not waive it casually.
  • Auto liability if vehicles are used on the property.

Check that the certificate actually shows these coverages at or above your association's own limits — not just that insurance "exists."

Step 2: Confirm the dates are current

Look at the expiration date on every policy line. "Current" means active today, not "was active when they signed." A certificate showing a policy that expired last month is not proof of anything. If any coverage has lapsed or is within a few weeks of expiring, get an updated certificate before work continues.

Step 3: Confirm additional insured and, ideally, primary/non-contributory

This is the step boards most often miss, and it is the one that matters most when something goes wrong.

  • Additional insured status means your association is covered under the vendor's policy for claims arising from their work. Without it, the vendor's insurance protects the vendor — and your association may be left arguing with their insurer, or paying out of your own policy.
  • Primary and non-contributory language means the vendor's coverage pays first, before your association's policy is tapped.
  • Waiver of subrogation prevents the vendor's insurer from turning around and coming after your association to recover what it paid.

Not every certificate will include all of these, and the exact language should track what your contract requires. Confirm the additional insured status is actually reflected — a promise in the contract is not the same as it appearing on the certificate.

Step 4: Make sure the certificate is real

Certificates can be edited, faked, or issued for coverage that was later canceled. A certificate is a representation, not a guarantee. For any significant contract:

  • Confirm with the issuer. The certificate lists the insurance agency or broker that produced it. A quick call or email to that agent confirms the policy is active and the certificate is genuine.
  • Watch for edited PDFs. Mismatched fonts, altered dates, or numbers that do not line up are red flags.
  • Match names exactly. The insured on the certificate must match the entity on your contract.

Step 5: Set up ongoing monitoring — this is the part everyone skips

Here is the core problem: even a perfectly valid certificate tells you about coverage on its issue date. A policy canceled next month for non-payment leaves you exposed, and nobody sends you a notice. The certificate in your file still looks fine.

Real verification is not an event — it is a process. That means:

  • Track every vendor's expiration dates and request a renewed certificate before each one lapses.
  • Re-confirm coverage periodically, not just at renewal, since mid-term cancellations happen.
  • Do not let a vendor keep working on an expired certificate. The gap between "expired" and "renewed certificate received" is exactly when an uninsured incident hurts the most.

For a community with several vendors, this is a real administrative burden — a calendar of expiration dates, reminders, and follow-ups. It is also the single biggest gap between "we have certificates on file" and "we are actually protected."

A quick verification checklist

For each vendor, before work begins and at every renewal:

  • Insured name matches the contracted vendor exactly
  • General liability at or above the limit your association set
  • Workers' compensation present (if they have employees)
  • All policies active today, not expired
  • Association named as additional insured, per contract
  • Certificate confirmed with the issuing agent for significant contracts
  • Expiration dates logged for follow-up before they lapse

Where a platform closes the monitoring gap

The verification steps above are straightforward once; the hard part is doing them for every vendor, forever, without letting one slip through a lapse.

That is the part a platform carries. On HOAcrew an admin reads each certificate — carrier, limits, expiry — and files what the document actually says, correcting any figure the certificate does not carry before a board ever sees it. The dates are then stored and held to a stated renewal window: 30 days for insurance, none for a competency certificate. Once the window closes, the company cannot bid for or be awarded new work at your community until the document is current again. Every company's coverage status reads at a glance in one dashboard.

HOAcrew is where a board runs this. Vetted independent local companies submit proposals against the scope you publish; your board compares them side by side, selects one, and the contract is between your community and the company it chose. HOAcrew verifies the three documents that decide a bid — general liability, workers' compensation and the credential that company's trade requires, and every expiry date is held against the limits your community sets — often the number its own insurer or lender asks for. Every company's own invoice arrives in one view, with the visit records beside it.

A certificate on file is not proof of coverage — it is proof of a moment. Verification is a standing routine, and the point of putting it somewhere durable is that the routine outlasts the board that started it.