Subcontractor Compliance Tracking for General Contractors: Stop Chasing COIs by Hand
Subcontractor compliance tracking for GCs: what to check on each COI, W-9, lien waiver and license, a weekly routine, and when payments should block.
Subcontractor compliance tracking means knowing, for every sub on every active job, that their insurance, W-9, license and lien waivers are current, and catching a lapse before a payment goes out or a crew shows up on site. Most general contractors do it in a spreadsheet that records an expired certificate perfectly well but can't stop anything from happening because of it.
The usual failure looks like this. A draw gets held two days before payroll because a sub's certificate of insurance expired eleven days ago. The project manager hears about it from the owner's rep, not from anything internal. Whoever runs the spreadsheet is also running payroll, chasing change orders and answering three job sites, so the sheet gets checked when something has already gone wrong.
Below is what to check on each document, a weekly routine that works on paper, and the point where compliance should be wired into the systems that pay people. That last part is where our custom CRM development and automation work comes in.
The documents, and what to actually check on each
| Document | What to check | When it goes stale | Check it |
|---|---|---|---|
| Certificate of insurance | General liability, workers' comp, auto and umbrella limits against your subcontract; you listed as certificate holder | On each policy's own expiration date | At onboarding, before each job, before each payment |
| Additional insured endorsement | The actual endorsement naming you, not just a checked box on the certificate | When the underlying policy renews | With each new policy period |
| W-9 | Legal name and tax ID match the name on the subcontract and invoices | When the sub's entity or tax ID changes | Before the first payment |
| License | Active status with the state board, in the right trade and classification | On the license's renewal date, or on suspension | At onboarding and before each new job |
| Lien waivers | Conditional before payment, unconditional after it clears, matching the amount and date | Every payment creates a new one | With every payment, no exceptions |
| Bond, where required | Bond amount and surety match the job's requirement | Job by job | Before the sub mobilizes |
The rows that hurt most are the ones with their own clocks. Insurance policies renew on dates that have nothing to do with your project schedule, and a sub with three policies has three dates.
Why the spreadsheet stops working around twenty subs
Track five subs and a notebook is fine. At forty subs across six jobs, with three or four policies each, you're watching well over a hundred expiration dates, plus a lien waiver for every payment. Nobody is bad at this on purpose. The volume outruns one person checking a sheet once a week.
Owners and lenders also ask more often now, through audits, draw requirements and contract clauses. A sheet that's right most weeks is hard to defend when the one week it was wrong is the week a claim happened.
The real cost when a certificate lapses
The expensive scenario is the one every broker raises first. If a sub's coverage lapses mid-job and their crew causes a loss, the GC can end up holding liability the sub's insurer should have carried. That's the risk worth designing around, and it's a reason to get your broker's view on your own contract language.
The common cost is time. Someone emails for a renewed certificate, waits, emails again, checks the limits, files it, and updates the sheet. Multiply by every sub and every renewal and it's a meaningful slice of a week, done by someone whose time is already spoken for.
A weekly routine that works before you buy anything
Fifteen minutes on the same day each week.
- Sort by expiration date. Anything expiring in the next 30 days gets a renewal request today, by email, with the exact coverages and limits you need listed.
- Check this week's payments. For every sub being paid, confirm the certificate is current and the conditional waiver for this amount is signed. No waiver, no check.
- Collect last week's unconditional waivers. Every payment that cleared should now have its unconditional waiver on file.
- Check new subs against the license board. Before anyone new mobilizes, look up the license status yourself.
- Log what's missing. One list of open items, with the date each was requested.
If that routine takes far longer than fifteen minutes, or it's the first thing skipped in a busy week, you've outgrown the spreadsheet.
What's on the market
Dedicated certificate-tracking platforms such as Billy, BCS, SmartCompliance and illumend collect certificates, read the coverage, chase renewals and alert you before something expires. Some connect to Procore or to insurance agency systems. Lien waiver tools are a separate category, usually priced per waiver or by monthly subscription. Pricing varies by sub count and features, so get quotes at your real roster size.
| Approach | Cost shape | Catches expirations ahead of time | Can block a payment | Fits |
|---|---|---|---|---|
| Spreadsheet and the weekly routine | Staff time only | Only if someone sorts the sheet | No | Under ten active subs |
| Lien waiver tool | Per waiver or monthly | No, waivers only | No | Waiver-heavy GCs tracking insurance elsewhere |
| Dedicated COI platform | Monthly, by sub count | Yes, with automatic renewal requests | Usually not, it alerts | GCs whose main risk is insurance lapses |
| Compliance wired into your job and payment system | One-time build plus upkeep | Yes | Yes | GCs with 20 or more subs across several jobs |
Why the payment step is where compliance should live
A standalone certificate tool is useful. It's also one more login, and it doesn't know a sub is about to be paid. The strongest setup ties compliance status to the step that pays the sub, so an expired certificate or a missing waiver holds the payment automatically and tells the PM why.
That's the pattern we follow when we build. On the Grit Construction project, the gain came from connecting scattered manual steps into one system rather than automating each one alone, and the owner got back 10+ hours a week on invoicing and reminders. Compliance works the same way. It pays off as one part of a workflow automation setup that already knows which sub is on which job and when each one gets paid.
Count your open items this week
Run the weekly routine once, honestly, and count the open items at the end. A five-person GC with two jobs and a short list is fine on paper. A firm with forty subs and a list that never gets shorter needs a system. If you're not sure which you are, book a call with Ben and bring the list. We also do this kind of process mapping as operations consulting when the fix is a better routine rather than new software.
Common questions
What documents should a general contractor collect from subcontractors?
At minimum a certificate of insurance with the coverages and limits your contract requires, a W-9, a current license where the trade needs one, and lien waivers with each payment. Many GCs also collect the additional insured endorsement itself, not just the certificate, plus a signed subcontract and any safety documents the owner requires.
How often should I check subcontractor insurance?
Check every certificate when the sub is onboarded, again before each job starts, and again before every payment. Set alerts at 30 and 14 days before each policy's expiration date so renewals get requested before they lapse, not after.
Can I track subcontractor compliance in a spreadsheet?
With fewer than ten active subs and one person who owns it, yes. The weak point is that a spreadsheet can't stop anything. It records an expired certificate but can't hold the payment, so it depends on someone checking it at the right moment every time.
Should I pay a subcontractor whose insurance has expired?
Check your subcontract and talk to your broker or attorney, but most GCs put a hold on payment until a current certificate arrives, because an uninsured sub on site can leave the GC holding a claim. The cleanest way to enforce it is a rule that blocks the payment automatically when the certificate on file is out of date.
