Subcontractor COI tracking
Subcontractor COI Tracking: A Simple Workflow for Small and Mid-Size GCs
Once you have more than a dozen active subcontractors, "I'll check when I have time" stops working. This is the weekly and monthly routine that keeps COI tracking from piling up.
When email stops being enough
There is a threshold most GC offices hit somewhere between 15 and 25 active subcontractors. Below that, one admin can hold the whole picture in their head and catch most problems before they become job-site issues. Above it, gaps start appearing.
A sub's certificate expired in March. Nobody noticed until the owner asked for updated proof in April. Your admin went looking, found the certificate from last year, and spent an afternoon trying to reach the sub's insurance agent. The sub could not start until Wednesday.
That is not a one-time mistake. That is what happens when COI tracking depends on memory and a spreadsheet nobody opens unless something has already gone wrong.
The weekly COI review
Set aside 20 to 30 minutes every Monday morning โ or the first business day of the week โ to answer three questions:
- Which subcontractors have certificates expiring in the next 30 days?
- Did any renewal requests from last week get a response? If yes, did the certificate arrive and get reviewed?
- Are any subs scheduled to start work this week who do not have a current certificate on file?
Those three checks take less time than you think, especially if your tracking document is up to date. The purpose is not to audit every sub every week โ it is to catch the ones that are about to become problems before they do.
If Monday's review produces action items, assign them before the meeting ends. A follow-up email that never gets sent is the same as not doing the review.
The monthly COI audit
Once a month, do a fuller pass over your active subcontractor roster. The questions are slightly different:
- Are all subs you paid in the last 30 days in the tracker with a current certificate?
- Have any subs been added to jobs without their certificate being collected first?
- Are the coverage limits on file still correct for the jobs they are working? Requirements sometimes change mid-project.
- Has anything changed in the sub's contact information that would affect where renewal reminders get sent?
The monthly audit is also when you clean up closed-out subs. Remove or archive entries for companies you have not used in several months so the active list stays usable.
How to handle the certificate when it arrives
When a sub sends an updated certificate โ whether it came from a renewal reminder or a new job request โ do not let it sit in email as an attachment. That is how it gets lost.
A reliable intake habit looks like this:
- Open the certificate and confirm the insured name, certificate holder, coverage types, limits, and expiration dates
- Mark any field that does not match your requirements before filing anything
- Save the PDF to your document location with a consistent naming convention (sub name + expiration year works)
- Update the tracker row: new expiration date, status changed to current, date reviewed, and who reviewed it
- Set or update the renewal reminder date based on the new expiration
Steps one through five take five minutes per certificate. The mistake most offices make is step one and step five โ they file the PDF without reviewing it and never update the reminder. Then the expiration date in the tracker is wrong and the reminder never fires.
What to do when a sub does not respond
Send the first renewal reminder 60 to 90 days before expiration. If you do not hear back within a week, send a second message. If the certificate expires before the sub responds, the decision is straightforward: they cannot work on your jobs until proof is received.
Document the follow-up attempts in your tracker. If the issue ever comes up during an audit or a claim, "we sent three requests and have no record of a response" is a very different position than "we are not sure if we followed up."
Some subs drag their feet on renewals because insurance renewals cost them money. A firm policy โ no current COI, no work โ communicated clearly during onboarding removes most of the friction. The subs who push back hardest are usually the ones whose coverage has lapsed.
Keeping the tracker accurate without making it a full-time job
The goal is a system one person can maintain in under an hour a week for a roster of 30 to 50 active subs. If it takes longer than that, something in the intake or review process has more manual steps than it should.
The most common time drain is hunting for PDFs that were never saved in the right place. Fix the saving habit first. After that, most of the tracking work becomes a quick scan for status and expiration dates rather than an archaeological dig through email.
COI tracking is not a compliance checkbox. It is the thing that determines whether a sub can legally start on Monday and whether you have proof when someone asks.
One place for every subcontractor COI, expiration date, and renewal reminder.
CertKeeper helps general contractors keep subcontractor COIs, expiration dates, and renewal reminders in one simple place. If your team is still chasing certificates from email and spreadsheets, request early access and we'll help you see whether CertKeeper fits your workflow.
Request early access