For businesses managing a small number of vendors, a spreadsheet is a reasonable place to start tracking certificates of insurance. It costs nothing, requires no setup, and works well enough to catch the most obvious compliance gaps.
This article gives you a field-by-field breakdown of what your spreadsheet should capture, a sample layout you can copy into Excel or Google Sheets, and a clear look at where spreadsheets stop working — so you can make an informed decision about when to move on.
Why a Spreadsheet Can Work
The case for starting with a spreadsheet is straightforward. You probably already have Excel or Google Sheets. Your team already knows how to use it. And for a business with 10–20 vendors, a well-structured spreadsheet is genuinely sufficient — as long as someone is checking it consistently.
Spreadsheets also offer complete flexibility. You can add columns for your specific requirements, create conditional formatting to highlight upcoming expirations, and share access with multiple team members without paying for additional licenses.
The problems come later, and they're worth understanding before you get there.
Fields Every COI Tracking Spreadsheet Should Include
A common mistake is building a spreadsheet that only captures the certificate's earliest expiration date — or just a single "expiry" field per vendor. This misses the fact that most certificates contain multiple policy lines, each with its own renewal date.
Below are the fields your spreadsheet needs, organized by category.
Vendor information
- Vendor name — the legal business name as it appears on the certificate
- Vendor contact name — the person on your team's regular contact at that vendor
- Vendor contact email / phone — direct contact for certificate requests
- Vendor category — e.g., maintenance, construction, technology, landscaping
- Date added — when this vendor was added to your roster
- Active / inactive status — whether this vendor is currently engaged
Insurance agent information
- Agent / broker name — who issued the certificate
- Agent email / phone — for direct certificate requests
Certificate details
- Certificate received date — when the current certificate was filed
- Certificate file location — link to the document or file path
Coverage lines (one column per coverage type)
- General liability — expiration date
- General liability — per occurrence limit
- General liability — aggregate limit
- Workers' compensation — expiration date
- Auto liability — expiration date
- Auto liability — limit
- Umbrella / excess — expiration date
- Umbrella / excess — limit
- Professional liability — expiration date (if applicable)
Compliance status
- Additional insured status — Yes / No
- Overall compliance status — Compliant / Expiring Soon / Expired / Missing
- Next renewal due — the earliest upcoming expiration across all coverage lines
- Notes — any exceptions, waivers, or follow-up needed
Sample Spreadsheet Layout
The table below shows a simplified version of the core tracking fields. Copy this structure into Excel or Google Sheets, then add the additional columns listed above for a complete setup.
| Vendor Name | Category | GL Expiry | WC Expiry | Auto Expiry | Next Due | Status | Certificate on File |
|---|---|---|---|---|---|---|---|
| Apex Plumbing | Trades | 09/15/2025 | 09/15/2025 | 09/15/2025 | 09/15/2025 | ✓ Compliant | apex_plumbing_coi_2025.pdf |
| Green Grounds LLC | Landscaping | 03/01/2025 | 06/30/2025 | N/A | 03/01/2025 | ⚠ Expiring Soon | green_grounds_coi_2024.pdf |
| Summit Electric | Electrical | 01/31/2025 | 01/31/2025 | 01/31/2025 | 01/31/2025 | ✗ Expired | summit_electric_coi_2024.pdf |
| CleanRight Services | Janitorial | 11/30/2025 | 11/30/2025 | N/A | 11/30/2025 | ✓ Compliant | cleanright_coi_2025.pdf |
| TechServ Inc. | Technology | — | — | — | — | ⚠ Missing | Not on file |
Tip for Google Sheets: Use conditional formatting to color-code the Status column automatically. Set "Expired" rows to red, "Expiring Soon" to yellow, and "Compliant" to green. This makes your compliance status visible at a glance without having to read every row.
The Limitations of Spreadsheets
A spreadsheet works as long as someone is actively maintaining it. The problems that show up most often aren't design problems — they're process problems that the spreadsheet has no mechanism to prevent.
No automated alerts. A spreadsheet is a passive document. It doesn't send you an email when a certificate is about to expire. You have to remember to open it, sort by the "Next Due" column, and manually identify what needs attention. In a busy operation, this review gets postponed — and expirations slip through.
No version history for documents. When a vendor sends a new certificate, you update the spreadsheet and presumably save the new PDF somewhere. But there's no automatic link between the record in the spreadsheet and the document on file, and old certificates tend to get overwritten rather than archived. In litigation, proving what coverage a vendor had on a specific date requires having the historical certificate — not just the current one.
Data quality depends entirely on manual entry. Every date in your spreadsheet was typed by a person reading a certificate. Typos happen. Fields get skipped. A single digit wrong on an expiration date means your tracking system has bad information — and you won't know until something goes wrong.
No audit trail. If a compliance gap causes an incident, one of the first questions will be: who updated this record, and when? A spreadsheet has no answer to that question.
Collaboration creates problems. When multiple people maintain the same spreadsheet, data integrity degrades quickly. Formats change, rows get accidentally deleted, and it becomes unclear who is responsible for keeping the data current.
Compliance Risks of Manual Tracking
The compliance risks of spreadsheet-based tracking aren't hypothetical. They show up in predictable ways:
Undetected expirations. The most common failure mode. A policy expires and no one notices because the spreadsheet wasn't checked on the right day. Work continues with an uninsured contractor. Weeks or months pass before the lapse is discovered — often when a new certificate request reveals how long ago the previous policy expired.
Expired certificates treated as current. When spreadsheets are not updated consistently, teams continue treating vendors as compliant based on stale data. The certificate on file is 14 months old. The policy expired 2 months ago. But the spreadsheet still shows last year's dates.
Inconsistent enforcement. When compliance is managed manually, it tends to be enforced more rigorously with some vendors than others. High-volume vendors with strong relationships get reminders; smaller vendors get overlooked. The liability exposure doesn't care about the size of the relationship.
When to Upgrade to Software
There's no universal threshold, but these are the common inflection points:
25–30 active vendors. Below this number, a disciplined spreadsheet process is manageable. Above it, the manual overhead becomes significant enough that errors become nearly inevitable.
Staff turnover. When the person who maintains the spreadsheet leaves, the institutional knowledge about the process often leaves with them. Rebuilding the spreadsheet and the associated workflows from scratch takes time your compliance program can't afford to lose.
After a compliance miss. If an expired certificate has ever caused a problem — or if you've ever discovered a lapsed policy during a routine check — the spreadsheet has already demonstrated its failure mode. That's the right time to move to a system that alerts you before the expiration, not after.
When you're spending more than 2 hours per week on COI administration. That's time spent requesting certificates, updating records, sending reminders, and chasing vendors. Software eliminates most of that work.
The honest assessment: A spreadsheet is better than nothing. But it's a tool for managing compliance manually, and manual compliance programs have a failure rate proportional to how busy the people maintaining them are. The question isn't whether the spreadsheet can work — it's whether your team will maintain it consistently when things get busy.
Frequently Asked Questions
Can I use the same spreadsheet for multiple properties?
You can, but it gets complicated quickly. Add a "Property / Location" column and filter by property when reviewing. As your portfolio grows, consider separate sheets per property or move to a system designed for multi-location management.
How do I handle vendors whose policies have different expiration dates across coverage lines?
Track each coverage line in its own column with its own expiration date. Your "Next Due" column should use a MIN() formula across all expiration date columns for that row — that way it always shows the earliest upcoming expiration, regardless of which policy line expires first.
What formula should I use for the Status column?
A simple IF/TODAY() formula works. For example: =IF(F2<TODAY(),"Expired",IF(F2<TODAY()+30,"Expiring Soon","Compliant")) where F2 is the "Next Due" date. Adjust the 30-day window to match your preferred lead time for requesting renewals.
Should I store the actual PDF certificates in the spreadsheet?
Don't embed PDFs in the spreadsheet — it makes the file unwieldy. Instead, create a consistent folder structure in your file system or Google Drive, and link to each vendor's folder from a "Certificate Location" column in the spreadsheet.
What's the minimum viable version of this spreadsheet?
If you're just getting started, the five essential columns are: Vendor Name, General Liability Expiry, Workers' Comp Expiry, Certificate on File (Yes/No), and Status. You can add the rest as your process matures.
Conclusion
A well-structured spreadsheet is a reasonable starting point for COI tracking. The template and field list above give you a foundation that covers the core compliance requirements for most vendor types.
The honest limitation of any spreadsheet is that it's only as good as the process around it. It won't remind you when to check it. It won't contact vendors automatically. And it won't catch a data entry error that causes you to believe a policy is current when it isn't.
Use the spreadsheet to build the habit of tracking. As your vendor count grows and the manual overhead increases, that's the signal to move to a system that runs the process for you.
Ready to automate what the spreadsheet can't?
COI Tracker replaces your spreadsheet with automated expiration alerts, vendor self-upload, and a live compliance dashboard — starting at $89/month.
See Plans and Pricing →