How to track vendor insurance certificates

COI tracking fails in a predictable way. It is not that people do not know what to check — it is that the checking is front-loaded and the risk is back-loaded. Everyone verifies the certificate on day one, when they are motivated and the vendor is eager. Nobody re-verifies in month eleven, when the policy quietly lapses and the vendor is already on site.

A system that works has to survive that asymmetry. Here is the shape of one.

Step 1 — Write the requirements down once

Before anything can be tracked, there has to be something to track against. Write a requirement set per trade tier — not per vendor — covering coverage lines, limits, endorsements and the exact additional-insured entity wording. Three tiers is usually enough: low-hazard interior work, general trades, and high-hazard work such as roofing, structural and anything involving heat or heights.

Step 2 — Collect before work starts, not after

The only leverage you will ever have is the moment before the vendor is engaged. Make the certificate a condition of the first work order, send the required wording with the request, and address the request to the vendor's insurance agent with the vendor copied — the agent is the one who can actually produce the document.

Step 3 — Record the fields that matter, not the PDF

A folder full of PDFs is not tracking. What you need extracted into rows you can sort:

Step 4 — Verify against the requirement, in writing

Verification is a comparison, and comparisons should produce a recorded verdict: pass, fail, or missing, per requirement line, with a date and a person's name against it. That record is the thing you will want two years later when someone asks what you knew and when. A green cell in a spreadsheet with no history is not evidence.

Step 5 — Chase on a schedule, not on a feeling

Renewals are the entire operational cost of COI tracking. A cadence that works in practice:

1. Day −30: first reminder to the vendor's producer, with the vendor copied, naming the exact endorsements required.
2. Day −14: second reminder, same thread, slightly firmer.
3. Day −3: escalate to the vendor's owner or your operations contact.
4. Day 0: mark non-compliant and stop assigning work until resolved.
5. Day +7: final notice referencing the contract clause.

Step 6 — Keep the trail

Store every certificate version, every endorsement page, every chase message and every verdict, with dates. When a claim lands, the question is rarely "were they insured" — it is "what did you require, what did you check, and when did you know". A dated trail answers that in an afternoon. A shared drive does not.

When a spreadsheet stops working

A spreadsheet is genuinely fine below about twenty-five vendors with one requirement set. It stops working at the point where any of these becomes true:

• More than one requirement tier, so the comparison is no longer a single rule.
• More than one person maintaining it, so nobody is sure whose edit is current.
• Vendors working across multiple properties or owners with different requirements.
• Renewal reminders that depend on someone remembering to open the file.
• An audit, an owner request or a claim, where you need the history and not just the current state.

The honest framing: the spreadsheet does not fail because it is a spreadsheet. It fails because the work it implies — forty comparisons per certificate, a chase cadence per vendor, a version history per document — is more than the tool asks you to do, so it silently does not get done.