Top COI Tracking Mistakes and How to Fix Them

Short answer: The biggest COI tracking mistakes are using one checklist for every vendor, storing the PDF away from its status, treating the certificate as the policy, and relying on an unowned reminder. Fix them by tying each vendor to its requirements, evidence, reviewer, next action, and expiration date.

COI tracking rarely fails in one dramatic moment. It usually slips a little at a time. A certificate arrives in the wrong inbox. A limit is copied into the wrong row. A vendor changes its legal name. Three months later, nobody can explain why the record says “approved.” These small gaps are fixable when the workflow makes them visible.

The Mistakes That Show Up Most Often

1. Using one requirement list for every vendor

Requirements should follow the work and the agreement. Copying a general liability checklist to an auto-heavy vendor or a professional service provider can create false confidence. Record the requirement by project or vendor type, then document any approved exception.

2. Tracking dates without the document

An expiration date in a spreadsheet is not evidence. Keep the original certificate, the review note, and the date in one record. If the date was entered manually, make it clear who checked it and when.

3. Treating a COI as the insurance policy

A certificate summarizes insurance information. It does not rewrite the policy or prove every endorsement. If the contract requires additional insured status, waiver of subrogation, primary and noncontributory wording, or a special coverage, request the relevant evidence from the broker.

4. Missing names and project details

Check the named insured, certificate holder, project address, and legal entity. “Close enough” names create problems when a certificate is reviewed by a client, auditor, or claims team.

5. Marking a gap without assigning the next action

“Incomplete” is a status, not a plan. Write what is missing, assign a person, set a date, and record the vendor or broker response. A specific request is easier for everyone to finish.

6. Waiting until expiration day

Renewals take time, especially when a broker needs to correct a certificate or add an endorsement. Set follow-up before the deadline. Use alerts at 30, 14, and 7 days as a baseline, then change the timing for projects with longer approval cycles.

A Simple Repair Process

1. Normalize the record: Use one vendor name, one project or property, and one current certificate.
2. Copy the requirement: Record coverage, limits, dates, holder, endorsements, and special wording from the contract.
3. Review the evidence: Compare each requirement to the certificate and request the policy endorsement when necessary.
4. Assign the gap: Name the owner, the vendor contact, the missing item, and the due date.
5. Close the loop: Save the corrected certificate and the reason for approval with the record.

The Five-Minute Audit Test

Pick five vendors at random and ask someone who does not maintain the list to answer these questions:

• Where is the current certificate?
• Which contract requirements were checked?
• Who reviewed it and when?
• When does each policy expire?
• What is the next action if a requirement is missing?

If the answers take more than a few minutes, the issue is probably the workflow rather than the person maintaining it. A COI tracking system should make those answers easy to find.

Spreadsheet or Software?

A spreadsheet is fine for a small, stable vendor list with one owner. For larger lists, multiple properties, or frequent renewals, software can connect document storage, requirements, alerts, vendor uploads, and reports. Compare the trade-offs in why spreadsheets fail for COI tracking or start with the COI requirements checklist.

Frequently asked questions