COI spreadsheet guide
COI Tracking Spreadsheet for Subcontractors
A subcontractor COI tracker should answer three questions fast: who is current, who is expiring soon, and which rows still need review before work or payment continues.
Field notes
What to keep out of the cracks.
Worked example: a current date with an open review.
Illustrative row, checked October 7, 2026: Sample Electric has a GL expiration of January 31, 2027. The date is more than 60 days away, but the additional insured endorsement has not been reviewed. Keep these as two different statuses.
- Date status: current, based only on the entered expiration
- Review status: pending endorsement review, not cleared
- Next action: the assigned reviewer requests the endorsement and compares it with the contract
- Audit input: map the date you want checked to Earliest COI expiration; review other policy dates separately
Spreadsheet or software: choose by the work you need to record.
A spreadsheet can work when one person keeps dates, files, and follow-up notes together. When several people need shared document history, reminders, and recorded review decisions, start by auditing the roster you already have. You do not need to rebuild it to try the import workflow.
Start with the row, not the file.
A useful COI spreadsheet starts with one row per subcontractor. The file itself can live somewhere else, but the row needs to tell you what matters before payment, site access, or audit review.
- Company name, trade, project, contact, and owner
- Certificate received date and the person who reviewed it
- GL, workers comp, auto, and umbrella expiration dates
Separate date tracking from coverage review.
Expiration dates are easy for a spreadsheet to calculate. Coverage wording is where people get sloppy. Keep additional insured, waiver of subrogation, and notes in their own columns so a green date does not hide an unchecked requirement.
- Use one status column for renewal timing
- Use review flags for endorsement language
- Keep exception notes visible instead of buried in comments
Make the next action obvious.
A tracker only works when the next person can tell what to do. If a row is expired, it should say who owns the renewal request and whether accounting or the project team should wait.
Working checklist
Freeze the header row so the status columns stay readable.
Filter expired and expiring rows every week.
Keep formula columns locked or clearly marked.
Use a received date for every uploaded certificate.
Write renewal notes as dated facts, not memory aids.
Move to software when files, emails, and approvals split across people.
Next step
Check your dates, then carry the roster into a trial.
Start with a date audit of your existing spreadsheet. Your reviewed roster can stay in this browser for signup, then be restored in the import preview. Confirm the import in your trial before any account records are added.
Related resources
Keep the workflow connected.
Free Subcontractor COI Tracker Spreadsheet
Copy the starter spreadsheet before moving the workflow into software.
COI Tracking Spreadsheet for Subcontractors
Set up the spreadsheet columns that keep renewal and review work visible.
COI Renewal Email Template
Use a clear renewal request when coverage is close to expiration.
Subcontractor Insurance Compliance Checklist
Review dates, limits, endorsements, and exceptions in a repeatable order.
FAQ
Common questions.
What columns should a COI tracking spreadsheet include?
Use company name, contact, trade, project, certificate received date, GL expiration, workers comp expiration, auto expiration, umbrella expiration, endorsement review flags, owner, next action, and notes.
Can a spreadsheet verify a certificate of insurance?
No. A spreadsheet can track dates and review flags. It does not verify that a policy is valid, that the limits satisfy the contract, or that endorsement wording is enough for the job.
When should a contractor move beyond a spreadsheet?
Move when renewals are split across inboxes, when payment decisions depend on COI status, or when you need a record of who approved each exception.