COI tracking spreadsheet template (free download)

A COI tracking spreadsheet template is a sheet with one row per vendor certificate and the columns you need to see, at a glance, whether each certificate is current and where its PDF is filed. The template on this page has those columns, eight example rows, and a second tab of column instructions. Download it below, replace the sample rows with your vendors, and use the weekly routine that follows.

What does a COI tracking spreadsheet need to track?

A working sheet holds the vendor, the carrier, the policy number, each coverage line with its limit, whether you are named as additional insured, the expiry date, the certificate holder, and the location of the proof file. Anything less and you will find yourself opening the PDF to answer a question the sheet should have answered.

Here is what each column is for, and why it earns its place.

• Vendor. The legal name as printed on the certificate. Trade names are fine in conversation, but the name on the certificate is the one a claim gets filed under.
• Carrier. The insurer for each coverage line. One certificate can list several carriers, so the template gives each coverage line its own row and repeats the vendor.
• Policy number. From the certificate. It is how the carrier finds the policy if you ever need to ask about it.
• Coverage line. General liability, auto, workers compensation, umbrella, professional liability. Keep the names consistent so you can filter.
• Limit. The per-occurrence and aggregate figures as printed. Record what the certificate says, not what your contract asks for; the gap between the two is the point of the next column.
• Meets requirement. Yes or no against the limit your contract or lease requires. You set the requirement; the sheet only records whether the printed limit reaches it.
• Additional insured. Yes or no, and only yes if the certificate or an attached endorsement says so. A checkbox in the description box is not the same as an endorsement.
• Expiry. The policy expiration date for that line. This is the column you sort by.
• Certificate holder. The entity named on the certificate. If it names your old address or a sister company, it is worth a follow-up.
• Proof location. A link or path to the PDF. Without it, you will be searching a shared drive every time someone asks for the file.

What is the weekly routine?

Once a week, sort the sheet by expiry, contact every vendor with a certificate expiring inside 30 days, and file each replacement certificate before you update its row. That order matters: update the row first and you will eventually have a sheet that says "current" next to a file that does not exist.

The routine takes about twenty minutes for fifty vendors if the sheet is clean. Add a Last checked column and put the date in it every time you touch a row, so the next person can see what is stale. Keep a Status column limited to four values: Current, Expiring, Expired, and Missing. Anything more granular tends to drift.

When a vendor sends a new certificate, do four things. Save the PDF with a filename that includes the vendor name and the expiry date. Update the proof location. Update every coverage row for that vendor, not just the one you were chasing. Then set Last checked.

Where do COI spreadsheets go wrong?

Most COI spreadsheets fail at the same points: the additional insured column gets filled in from memory, expiry dates get typed wrong, two people edit at once, and nobody gets a reminder. None of these is a flaw in the spreadsheet itself. They happen because the sheet depends on one person's attention, and that person has other work.

The additional insured column is the most common quiet error. Someone reads "additional insured" in the description box, marks yes, and there is no endorsement behind it. Your broker or attorney can tell you what wording your contracts need; the sheet can only record what the certificate shows.

Typed dates are the second. A 2026 that should be 2027 makes an expired certificate look current for a year. Copy the date from the PDF rather than reading it aloud across the desk.

Concurrent edits are the third. Shared drive sheets let two people overwrite each other's rows without either noticing. If more than one person maintains the sheet, agree on who owns which vendors.

When does a spreadsheet stop working?

A spreadsheet stops working when the number of certificates outgrows the weekly routine, or when the person who kept it leaves and nobody else knows the rules. A third moment is quieter: someone asks what you held on a given date, and the sheet has no history.

That is the point at which it is worth moving the sheet into a system that treats each certificate of insurance as a record with a history: one that keeps every version of the proof file, records who changed what, and sends renewal reminders by email and in-app at the lead windows you set instead of relying on someone remembering to sort by expiry on Monday. Atlasafe does that for the certificates you track, inbound from vendors and outbound as issued, and it imports the spreadsheet you are about to download so you do not start from zero. It flags gaps against the requirements you define; coverage decisions stay with your carriers and brokers.

Whether you move or not, the template below is a sound place to start. If you want the wider context, read our guide to certificate of insurance tracking.