Track Certificates of Insurance: A Practical COI Compliance Guide

Last updated July 2026.

To track certificates of insurance, centralize every COI in one system with structured fields, verify each one against the coverage types, limits and endorsements your contract requires, and automate renewal reminders before each expiration date. The failure is almost never collecting certificates. It is noticing when one lapses or falls below your requirement.

A certificate of insurance is only useful if it is current, correct, and on file when you need it. The moment a vendor's policy lapses or a tenant's coverage falls below your requirement, the risk quietly shifts to you. Tracking certificates of insurance by hand, in a spreadsheet and a stack of PDFs, almost guarantees an expired COI slips through. This guide covers how to collect, verify, and track COIs so compliance stays continuous instead of becoming a fire drill.

What a certificate of insurance actually proves

A COI is a one-page summary issued by an insurer or broker that confirms a party carries specific coverage: general liability, workers compensation, auto, umbrella, and so on, with limits and effective dates. It is proof, not the policy itself. For anyone who hires vendors, manages property, or signs contracts, the COI is the evidence that the other side can cover a loss instead of leaving you to pay for it.

Why manual COI tracking fails

The usual setup is a spreadsheet of vendors, a shared folder of PDFs, and a person who is supposed to remember renewal dates. It breaks in predictable ways: a certificate expires and nobody notices until a claim, the limits on file are below your contract requirement, an additional insured endorsement is missing, or the newest COI was emailed to someone who left. Each gap is invisible until it costs you.

There is a fairly sharp threshold here. Somewhere around 20 to 30 vendors, the spreadsheet stops being the problem and the follow up becomes the problem: nobody has time to email six brokers a week chasing renewals. Manual COI tracking vs software works through where that line sits and what actually changes when you cross it.

How do you track certificates of insurance?

In three steps: collect every certificate into one system of record, check each against the requirement written into the contract, and set automatic reminders before expiration. Everything else is refinement. The three steps below are the whole method, and the order matters, because verifying certificates you have not centralized is how gaps hide.

Step 1: Centralize every certificate

Start by getting all certificates into one place with structured fields, not a folder of look-alike PDFs. A certificate of insurance tracking tool stores each COI with the holder, coverage types, limits, effective and expiration dates, and the documents attached, so you can see status at a glance instead of opening files one by one. Broader insurance tracking software does the same across policies and certificates together. The point is to turn a pile of paper into a live compliance view.

Step 2: Verify against your requirements

Collecting certificates is not the same as being covered. For each one, check that:

• Coverage types match what the contract requires (for example general liability and workers compensation).
• Limits meet or exceed your minimums, not just that a policy exists.
• Additional insured and waiver of subrogation endorsements are present when your agreement calls for them.
• Dates are current, with a clear renewal owner before expiration.

A certificate that exists but falls short of your requirement is a false sense of security, which is worse than a missing one because you stop looking.

This is the check that separates a filing cabinet from a compliance program, and it is worth being systematic about it.

The checkbox trap on that list deserves emphasis. A ticked additional insured box on a certificate is a statement by the person who typed it, not coverage. The endorsement is the document with legal effect. How to verify a certificate of insurance walks the whole form field by field.

Step 3: Automate renewals and expirations

The single biggest win is to stop relying on memory for dates. Set automatic reminders ahead of each expiration so you request the renewal before coverage lapses, and flag any certificate that drops out of compliance the day it does. Continuous monitoring beats an annual scramble, and it means a lapse becomes an alert instead of a surprise during a claim.

Reminders at 60, 30 and 15 days before expiration are the common pattern, sent to the vendor and its broker rather than to your own calendar, and how long certificates of insurance stay valid explains what you are counting down from. The broker is usually the one who actually issues the new certificate, so writing to the vendor alone adds a hop and a week.

What is the best way to manage certificates of insurance?

The best way is a single system of record that reads each certificate automatically, scores it against the rules your contract sets for that vendor type, and chases renewals without anyone remembering to. Spreadsheets can hold the data, but they cannot read a PDF, enforce a limit or send a reminder, which is where every manual program eventually fails.

Where COIs meet contracts and leases

Insurance requirements rarely live on their own. They are written into your vendor agreements and, for property owners and managers, into the lease itself, which specifies what coverage a tenant must carry and name you as additional insured. Pulling those requirements out of long lease documents is its own task; a lease abstraction service turns dense leases into a clean summary of the key terms, including insurance obligations, so the requirement you track a COI against actually matches what the lease demands. Tracking the certificate and knowing the requirement are two halves of the same job.

Frequently asked questions

How often should COIs be reviewed?

Continuously for expirations, and again at every renewal or contract change. Limits and endorsement requirements can change even when the vendor stays the same. Automated monitoring handles the expiration side; a human should revisit the requirement itself whenever the scope of work changes, because a vendor that starts doing roof work needs different coverage than the one that swept the lobby.

What is the most common compliance gap?

Expired certificates that nobody caught, followed closely by limits on file that are below the contract requirement. The third is a missing additional insured endorsement behind a ticked additional insured box. All three are invisible until a claim, which is exactly why they persist for years in programs that feel well run.

Do I need additional insured status?

If your contract or lease requires it, yes, and the certificate should show it. Without that endorsement, the other party's policy may not respond to a claim involving you. Ask for the endorsement document itself rather than accepting the checkbox, and read additional insured vs certificate holder if the two terms still feel interchangeable.

Can I track tenant and vendor COIs in one place?

Yes, and you should. The same expiration and limit checks apply whether the certificate comes from a subcontractor or a tenant. What differs is the requirement, not the mechanics, so a system that lets you attach a different rule set per vendor type covers both without running two processes. Teams running mixed vendor and tenant populations across many buildings usually land on COI tracking for facilities management for exactly that reason.

How long should you keep certificates of insurance?

Longer than they are valid. Keep each certificate for at least as long as a claim from that vendor's work can still be brought against you, commonly five to seven years after the contract ends and considerably longer for construction. The full retention guidance is in how long to keep certificates of insurance.

Put it together

Tracking certificates of insurance is about making compliance continuous: centralize every certificate, verify each one against your real requirements, and automate renewal reminders so nothing lapses unnoticed. Tie the requirement back to the contract or lease that created it, and a COI stops being a piece of paper you hope is current and becomes a status you can actually see.

If you are ready to stop running this out of a folder and an inbox, a COI tracking system reads every arriving certificate, checks it against your rules and chases the renewals for you, and certificate of insurance management software covers what to look for when comparing platforms.