COI Tracking for General Contractors: The Complete Guide

For a general contractor, COI tracking is the system that makes sure every subcontractor on every project carries the insurance their subcontract requires — verified before mobilization and kept verified through the life of the project. Done right, it's the difference between a sub's accident being the sub's claim and it being yours.

Most GCs have a version of this system. It usually has the same weakness: it tracks whether a certificate exists, when the real exposure lives in whether the coverage is right. A certificate can be current, signed, and filed in Procore while the policy behind it is missing the completed-operations endorsement your subcontract requires — and that gap won't surface until a claim does, possibly years after closeout.

Here's how to run tracking that actually closes that gap, at project scale.

Track against the subcontract, not a checklist

Every verification answer depends on one question: what did this sub agree to carry? Requirements differ by trade tier, by project, and by owner — the requirements your owner's contract flows down to you become the floor for what you flow down to subs. So the first piece of infrastructure isn't software; it's a requirements schedule per project: each sub, their trade tier, their required limits and endorsement forms, extracted from the actual subcontract. If your coordinator has to open the subcontract PDF to know what to check, the checking degrades to "looks current."

(For what the requirements themselves should say — limits by trade, CG 20 10 vs CG 20 37, sample subcontract language — see our subcontractor insurance requirements guide.)

The pre-mobilization gate is 80% of the system

A sub who hasn't mobilized answers emails: they want to start, and they want their first pay app processed. A sub mid-project does not. That asymmetry should shape the whole workflow:

• No compliant COI, endorsements attached → no mobilization. Not "COI received" — reviewed and compliant, which are different events separated by three to five rounds of correction with the sub's insurance agent.
• Tie compliance status to pay apps. A payment hold is the only chase mechanism that runs itself. Most claims-made arguments and endorsement corrections resolve remarkably fast when a pay app is waiting on them.
• Time-box exceptions in writing. Superintendents will need someone on site tomorrow; it happens. Make the exception explicit, dated, and short — an undocumented exception is just non-compliance with extra steps.

What breaks mid-project

Projects run 12–36 months; policies renew every 12. So every sub on an eighteen-month job will renew at least once mid-project, and renewal is where compliant subs quietly stop being compliant — a new carrier, a lower umbrella, an endorsement that didn't carry over. Three patterns to build around:

Renewal waves. Sub policies cluster around common renewal dates. When eight certs arrive in the same week, the review queue is exactly where verification gets shallow. Watch the renewal calendar and start the chase before expiration, not after.

The silent lapse. Mid-term cancellations for non-payment don't announce themselves. The tell is usually indirect — a cert that doesn't arrive at renewal, an agent who stops responding. Treat silence as a lapse until proven otherwise.

Sub-tier subs. Your subs' subs have no contract with you, so their coverage is only as good as the flow-down language in your subcontract and your sub's enforcement of it. On self-perform-light projects this is the largest pool of unverified risk on site. At minimum, require subs to certify their lower-tier compliance; on high-hazard scopes, require the certs themselves.

Closeout is not the end

Completed-operations claims — defect, water intrusion, structural — arrive after the work is done, which is precisely why the CG 20 37 endorsement exists and why your subcontract (like most) requires coverage to be maintained for years after completion. A tracking system that archives the file at closeout is dropping the requirement exactly when it starts mattering. Keep post-completion verification on the calendar for the duration the subcontract requires, typically two to three years and sometimes through the statute of repose.

The honest math

Per sub, done properly: fifteen-plus minutes to review a cert and its endorsements against the subcontract, several rounds of agent correspondence per gap found, once at onboarding and again at every renewal. On a project with thirty subs, that's a real part-time job; across a GC's active portfolio, it's a full-time one — which is why the verification layer is what quietly erodes when the team is busy, and why "we collect certs" so often stands in for compliance.

That loop — reading each cert and endorsement stack against the subcontract, flagging gaps down to the missing form number, and chasing the sub or their agent by email, phone, and text until the corrected cert is on file — is exactly what Tightrope's agent Travis runs continuously, across every sub and every renewal.

FAQ

What COIs should a general contractor collect? One from every subcontractor before mobilization — with endorsement forms attached, not referenced — plus renewals through the project and for the post-completion period the subcontract requires. High-hazard lower-tier subs deserve direct verification too.

How long should a GC keep subcontractor COIs? Through the completed-operations tail — commonly 2–3 years after substantial completion, and many GCs keep them through the statute of repose in their state. The claim that arrives in year four will ask what coverage existed in year one.

Does Procore track COI compliance? Construction management platforms store certificates and track dates. The verification layer — endorsements against subcontract requirements — and the correction chase are the parts they don't do, and the parts where claims are won or lost.

---

Want to know what's actually in your subs' certificate stack? Run a few through Travis on Tightrope's free plan — upload the certs and your requirements, and see what surfaces.