COI tracking: spreadsheet vs software
A spreadsheet is enough for a handful of vendors. Learn what breaks as you grow, what software should do, and what to look for when you choose.
A spreadsheet is a fine way to track certificates of insurance (COIs) when you have a handful of vendors and one person who owns the list. It stops working when the list grows, when more than one person edits it, or when someone has to check each certificate against written requirements. This page explains where that line is, what good software does, and how to choose.
When a spreadsheet is enough
A spreadsheet works if all of these are true:
- You have roughly ten vendors or fewer, and they rarely change.
- One person updates the sheet and reads every certificate.
- Your requirements are simple, such as general liability limits and an expiration date.
- You are comfortable setting your own calendar reminders.
In that situation, software adds cost without much benefit. A well-kept sheet beats a tool nobody opens.
What breaks as it grows
Most spreadsheet failures are not about the spreadsheet. They are about the work around it.
- Nobody reads the certificate for you. Someone types the dates and limits by hand. A transposed digit or a misread policy period can turn a lapsed policy into a green row.
- Dates are entered, not checked. The sheet shows what the last person typed, not what is on the document.
- Nobody chases renewals. A column that says "expires in 12 days" does not email the vendor or their insurance agent. Someone has to remember to do it, for every vendor.
- No per-requirement check. A single "COI on file" column hides the questions that matter: are the limits high enough, is additional insured shown, is waiver of subrogation shown, is the certificate holder correct.
- Version chaos. PDFs live in email, a shared drive, and someone's downloads folder. Copies of the sheet multiply.
- No audit trail. When a claim or an audit comes up, you cannot easily show what you had on file, when you received it, and what you did about gaps.
What software should do
Good COI software handles the repetitive parts and leaves judgment to you:
- Read the certificate. It pulls insurer, policy dates, limits, and checked boxes from the ACORD 25 so nobody retypes them.
- Compare to your requirements. You set limits and endorsements once, ideally per vendor type or project, and every certificate is checked against them.
- Flag specific gaps. "Each occurrence is below the requirement" is useful. "Non-compliant" is not.
- Send reminders. Vendors, and ideally their agents, hear about expiring or deficient certificates without you writing each email.
- Let vendors upload without an account. If a subcontractor has to create a login to send a PDF, many will email it instead and the system loses its point.
- Keep history. Every upload, check result, and reminder is stored.
Remember that reading a certificate is not the same as confirming coverage. A certificate is informational, and software that reads it will only be as reliable as the document. For high-risk work, ask for endorsement copies or policy declarations.
What to look for when choosing
- Accuracy review. Can you see what the tool extracted next to the original document, and correct it? Ask how errors are caught.
- Who owns the data. Can you export your vendors, certificates, and history? What happens to them if you cancel?
- Pricing. Look at how cost scales: per vendor, per project, per user, or flat. Check for free tiers to test with real documents.
- How it treats vendors. Vendors deal with many of your peers. Tools that demand accounts, fees, or repeated data entry from vendors slow down compliance. Tools that let vendors reuse one certificate across customers help everyone.
- Fit with your requirements. Check that it handles the endorsements you actually require, not just limits and dates.
- Plain support. Insurance rules vary by state, carrier, and contract. A tool should show you the gap, not claim to give legal or insurance advice.
A minimal spreadsheet if you stay with one
If you keep a spreadsheet, use one row per vendor per policy type, with these columns:
| Column | Purpose |
|---|---|
| Vendor legal name | Must match the contract and the certificate |
| Policy type | General liability, auto, workers' comp, umbrella |
| Insurer and policy number | Quick lookup for claims |
| Effective and expiration dates | The most common failure |
| Each occurrence and aggregate limits | Compare with the requirement |
| Required limits | So the gap is visible |
| Additional insured, waiver, primary and non-contributory | Yes or no, from the certificate and endorsements |
| Certificate holder correct | Yes or no |
| Date received and file link | One home for the PDF |
| Reminder sent and next action | Keeps renewals from slipping |
Sort by expiration date every week, and set a reminder 30 days before each expiry.
Check this automatically
With ComplySub you set your requirements once. Vendors upload their certificate through a link, with no account, and ComplySub reads it and flags specific gaps: limits too low, missing additional insured, waiver of subrogation, or primary and non-contributory wording, a wrong certificate holder, or an expired or expiring policy. It reminds the vendor and their insurance agent, and subcontractors get one compliance packet to share with every general contractor. Subcontractors with one certificate use it free, and general contractors can start free with up to five vendors.
This guide is general information, not legal or insurance advice. Insurance and licensing rules vary by state, carrier, and contract; confirm what applies to you with your insurance professional, attorney, or licensing board.