Certificate of Insurance (COI) Tracking for General Contractors: A Practical Guide

A general contractor is typically exposed to a subcontractor's uninsured work in a way that's easy to underestimate until something actually happens on site. If a subcontractor's employee is injured, or their work damages the structure or a neighboring property, and that subcontractor's insurance has lapsed, the general contractor is often the party left holding the exposure, either directly or because the project owner and their insurer come looking for someone to cover the loss. A certificate of insurance on file, current and matching what the contract requires, is the GC's basic evidence that a subcontractor is actually covered, not just that they were covered when the project started.

This is worth stating plainly, because it's easy to treat a COI as if it were the coverage itself. A certificate of insurance is a summary document, usually prepared and issued by an insurance broker, showing that a policy exists and describing its basic terms: coverage types, limits, and the policy period. It is not the insurance policy, and holding a certificate doesn't guarantee that a specific future claim will be covered. The Texas Department of Insurance's certificate of insurance guidance states this directly: a certificate may only include terms that are actually in the policy, and it can't be used to imply rights beyond what the policy or an executed endorsement provides. The actual policy, with its exclusions and conditions, is what governs whether coverage applies when something happens. Tracking certificates is a practical and necessary way to monitor whether coverage appears to be in place across your subcontractors, but if a real question comes up about whether a specific loss is covered, that question goes to the policy and the insurer, not the certificate on file.

Receiving a certificate isn't the same as receiving a valid one. A surprising number of certificates that technically exist in a project file don't actually satisfy what the contract requires. Check each one against the following before treating it as sufficient.

• The named insured matches the actual subcontractor entity performing the work, not a parent company, an affiliate, or a misspelled version of the name on the contract
• Additional insured status is shown for your company, if your contract requires it, since general liability coverage existing is not the same as your company being named as an additional insured on it
• Coverage types match what the contract specifies: general liability, workers' compensation, auto liability, and umbrella or excess coverage where required
• Coverage limits meet or exceed the minimums your contract requires, not just whatever limits the subcontractor happens to carry
• The policy period actually covers the current and anticipated duration of the work, including any extensions already known about

It's tempting to file a COI away once it arrives and consider that subcontractor's insurance handled. A certificate missing required additional insured language, or showing limits below what the contract requires, or naming the wrong entity, creates functionally the same exposure as having no certificate at all, it's just harder to notice because something is sitting in the file. Reviewing what a certificate actually says, not just confirming its presence, is the step that gets skipped most often under deadline pressure.

A single project with a handful of subcontractors is manageable with a simple list. The pattern breaks down once you're running several projects at once, each with its own set of subcontractors, some of whom work across more than one project simultaneously with different policy periods or coverage on file at each. Reviewing certificates project by project means opening every project's file individually to find what's expiring soon, which is exactly the kind of review that gets postponed when things get busy, right up until something expires. A tracking approach that lets you see every certificate expiring soon across your whole business, not just within one project folder, is what actually catches a lapse before it becomes a problem on site.

"The subcontractor is responsible for keeping their own insurance current" is true, and it's also not useful on its own, since you're the one who needs the current certificate in hand, not just the sub. Assign a specific person to own requesting and reviewing updated certificates, and set that reminder well before the current certificate's expiration date rather than on it, so there's real time to follow up if a renewal is delayed.

What coverage types, limits, and additional insured terms a specific contract should require depends on the project, the client, the jurisdiction, and the risk involved. This guide describes a general practice for tracking and reviewing certificates, not a statement of what any particular project or contract requires. Confirm your actual insurance requirements with your attorney or insurance broker.

ConstruDo's permit and insurance reminders let you record each subcontractor's certificate expiration date and get a scheduled reminder before it arrives, across every subcontractor and every project you're running, in one place. It doesn't review or verify what's on the certificate for you, that part still requires someone actually reading it against the contract, but it removes the part of this problem that's purely about remembering a date before it's too late to act on it. Assigning the follow-up as a task with an owner and due date is a practical way to make sure the reminder turns into an actual request for an updated certificate.