How GCs and Property Managers Should Track Subcontractor COIs (Before One Lapses)

The certificate of insurance is valid on the day you receive it. That's not the same as saying the underlying policy is active on the day your sub is on site doing work — which could be three, six, or nine months later. A six-month-old cert with a policy that renewed in January and wasn't re-bound tells you nothing useful about today's coverage. This is the core problem with COI tracking: the document is a snapshot, not a live feed.

For a general contractor running one or two projects with a handful of known subs, this is manageable by memory and phone calls. For a GC or property manager with 30, 50, or 100 active subs across multiple projects, it becomes an exposure that surfaces at the worst possible moment — when something goes wrong and you discover the sub's policy had lapsed two months earlier.

This guide covers why lapse exposure is more common than most GCs realize, what a real tracking system looks like, and the practical options for managing it without building a back-office insurance department.

Why the Lapse Problem Is Bigger Than You Think

The typical sub's GL policy renews annually. If you collected their certificate in April, the policy renews the following April. If the sub missed a payment, switched carriers, or let the policy lapse for any reason, there's no automatic notification to you — certificates don't come with expiration alerts. You only learn the policy lapsed when you need to verify it.

Cancellation notice provisions on certificates — the "30-day notice of cancellation" language — sound reassuring but are largely unenforceable. The notice goes to whoever is listed as the certificate holder, and it relies on the insurer sending it and the correct address being on file. In practice, many GCs never receive cancellation notices even when policies are cancelled mid-term. The notice provision is a contract statement, not a reliable alert system.

What a lapsed sub certificate actually means for you

If an uninsured sub causes bodily injury or property damage on your site, the injured party will look to the most solvent defendant — which is typically you, the general contractor. Your GL policy provides coverage for your own liability, but if you're sued because a sub you hired caused harm while uninsured, you're defending that claim on your own policy. That claim goes against your limits, affects your loss runs, and can increase your premium at renewal.

Some GC GL policies include coverage for the actions of uninsured subs, but this varies by carrier and policy language, and it typically comes with an additional premium charge and a sub-limit. You cannot assume your policy covers what your subs should have covered. The best protection is verified, current insurance from every sub on site.

The sub-contractor-as-employee risk

Beyond the claim exposure, an uninsured sub can create a workers' compensation liability. If a sub who has no WC coverage is injured on your site and is later determined to be an employee rather than an independent contractor — a determination driven by how much control you exercised over their work, not how you paid them — your WC policy may be responsible for that claim. Texas allows most private employers to opt out of workers' compensation, but the misclassification exposure is real and the stakes are high.

What Good COI Tracking Looks Like

The mechanics of an effective COI tracking system have three components: initial collection, endorsement verification, and ongoing expiration monitoring. Most tracking failures happen at the third step, because the first two happen naturally at project setup and the third requires sustained attention that doesn't have a natural trigger.

Initial collection: more than just getting a cert

When you onboard a new sub, you need the certificate and the underlying endorsements, not just the cert. A certificate is a summary — it lists policy numbers, limits, and named entities, but it doesn't confirm the endorsement language actually matches what's on the policy. The three endorsements that matter most for GC contracts are:

• Additional insured: The cert may show you as an additional insured, but the endorsement form matters. ISO CG 20 10 covers ongoing operations; CG 20 37 covers completed operations. Most GC contracts require both. A CG 20 33 (blanket scheduled AI) provides narrower coverage and may not satisfy your contract requirements. Ask for the actual endorsement form, not just the certificate notation.
• Primary and noncontributory: This language must appear either on the certificate's description of operations section or, better, be backed by an actual policy endorsement. "Certificate says P&NC" and "policy has a P&NC endorsement" are not the same thing. The certificate doesn't change the policy.
• Waiver of subrogation: Required on GL, auto, and workers' comp by most GC contracts. Again, verify the endorsement, not just the cert notation.

Expiration monitoring: the part that breaks

Annual policies expire. Policies are cancelled mid-term. Policies are changed in ways that affect your coverage as an additional insured. None of these events will be automatically communicated to you. Your tracking system needs to generate alerts before expirations, not after.

At a minimum, your system should flag expiring certificates 45 to 60 days in advance — enough lead time to request a renewal certificate before the policy actually expires, and enough buffer to chase the sub if they don't respond promptly. A 30-day alert is too short; subs who renew through brokers often don't receive their new certificate until after renewal, and your 30-day window becomes 10 days of actual chasing time.

Renewal certificate collection: the chase

The renewal certificate doesn't appear automatically. Someone has to request it from the sub, verify that the coverage hasn't changed materially, confirm the endorsements are still correct, and update the tracking record. This is routine for a handful of subs and a real workload for 50. The process needs to be systematized: a standard request template, a defined follow-up cadence (initial request, 10-day reminder, escalation to project manager), and a clear rule about what happens if the renewal cert isn't received before expiration.

That rule — what happens if a cert isn't renewed — needs teeth to be effective. "We'll ask again" isn't a policy. "Sub is off site until we receive a current certificate" is. Most subs will produce a certificate within 24 hours when the alternative is suspension from site.

The Manual Tracking Failure Math

A GC managing 30 active subs with annual policy renewals is dealing with 30 expiration events per year, spread across 12 months. That's 2-3 renewals per month. For each renewal: send the request, wait, follow up, receive the cert, verify the endorsements, update the record. At 30 minutes per renewal on average — optimistic — that's 15 hours per year on COI renewals alone, before accounting for mid-term changes, new sub onboarding, or certificate requests from project owners.

At 75 subs, the math breaks: ~37 renewals per year, averaging more than 3 per month, with overlapping follow-up cycles. At this scale, tracking in a spreadsheet means things fall through the gaps. And the thing that falls through is a lapse that appears six months later when a sub causes a claim.

The spreadsheet problem

Spreadsheet tracking fails for three reasons. First, spreadsheets don't alert — someone has to open the spreadsheet, sort by expiration date, and identify what needs attention. This requires remembering to check the spreadsheet, which doesn't happen consistently when you're running active projects. Second, spreadsheets don't verify — they record what you entered, not whether the endorsements on the cert actually match your contract requirements. Third, spreadsheets don't integrate with the rest of your project management workflow, so the COI check becomes a manual step that gets skipped under schedule pressure.

Build, Buy, or Broker: Your Three Options

Build: internal tracking with a proper system

If you have the administrative capacity, a dedicated database or project management tool with reminder functions is more reliable than a spreadsheet. The key features you need: expiration date fields with configurable alerts, a document repository (so you can retrieve the actual cert and endorsements, not just a record that you have them), and a status field that tracks whether renewal is in progress or overdue.

This works for GCs with consistent administrative staff and a manageable sub count (under 40 active). The limitation is that verification of endorsement adequacy still requires human judgment — a database record that says "CG 20 10" doesn't confirm the cert actually has it.

Buy: compliance software

Purpose-built COI tracking platforms (Procore, Textura, myCOI, and others) handle the alert, collection, and document-storage problems. The better platforms add rule-based verification — you define what coverage is required for a sub category, and the system flags certs that don't meet requirements. This addresses the endorsement verification problem that manual tracking can't handle at scale.

These platforms cost $300 to $2,000+ per month depending on the scale and features, and they require setup to configure your requirements correctly. For GCs with 50+ active subs and complex multi-project operations, the cost is usually justified by the administrative time saved and the exposure reduced.

Broker: offload the renewal chase

A broker who actively manages your sub COI compliance on the holder side handles the renewal collection and basic verification for you. This is the highest-leverage option for GCs who don't want to add administrative headcount or buy a software platform. The broker tracks expiration dates for all your subs, sends renewal requests, chases non-responders, and delivers a current certificate file.

The limitation is that a broker can't enforce your site-access rules — they can tell you a cert has lapsed, but the decision to remove a sub from site is yours. And not all brokers offer this service; it requires a broker who is actively invested in the operational side of your compliance, not just placing policies.

COI Requirements by Project Type

The specific coverage requirements you need from subs vary by the type of work being performed and the project owner's contract requirements. A general framework for Texas commercial work:

These are minimums. Public work projects, large commercial GC contracts, and owner-required insurance programs (OCIPs/CCIPs) may impose higher limits or specific carrier requirements. Always read the contract language — your sub requirements flow from your obligations to the project owner.

When a Sub Can't Get the Coverage You Require

Some subs — particularly sole proprietors in high-hazard trades, very small operations, or subs with loss history — will tell you they can't get the coverage you require, or can only get it at a limit below your contract minimum. This creates a practical problem.

Your options are limited. You can require the sub to obtain coverage as a condition of using them (most subs will find a way if the contract depends on it). You can require a higher hold-harmless agreement that shifts contractual liability to them, though this is only meaningful if they have assets to satisfy a judgment. Or you can decide not to use them on this project. What you cannot do safely is use an uninsured sub on a project where your contract with the owner requires all subs to carry specific coverage — that puts you in breach of your own contract if a claim surfaces.

For subs who are legitimately having trouble getting coverage, referring them to a broker who specializes in their trade class — including high-hazard trades — is a good-faith step that resolves the problem for both of you. See our guides on subcontractor insurance requirements in Texas and the COI guide for more on what subs need to deliver.

Integrating COI Tracking Into Your Workflow

The practical challenge is that COI tracking is an administrative task that competes with the immediate demands of running projects. The only tracking systems that work reliably are ones that are embedded in the natural workflow — not separate tasks that have to be remembered.

A few integration points that work in practice:

• Sub onboarding: COI before PO. Make the purchase order or subcontract conditional on receiving a compliant certificate. This creates a natural collection point without requiring a separate reminder process.
• Project closeout: verify certs are current for completed-ops period. Your contract with the project owner likely requires subs to maintain completed operations coverage for a period after the job closes. Verify this at closeout, not two years later when a claim surfaces.
• Monthly calendar alert: review expirations. If you don't have a system with automatic alerts, a recurring monthly calendar block to review the expiration list takes 20 minutes and catches issues 30+ days ahead.

Frequently Asked Questions

Does the 30-day cancellation notice on the certificate protect me?

Not reliably. The cancellation notice provision requires the insurer to send notice to the certificate holder's address of record. In practice, notices are sent to the wrong address, go to the wrong person, or aren't sent at all. Treat it as a courtesy provision, not a reliable alert system. Build your own tracking rather than depending on carrier notifications.

Can I just require subs to send me a new cert every year automatically?

You can require it contractually, and many GCs do. But "required" and "it happens reliably" are different things. Subs have their own priorities. An automated requirement works when there's a consequence for non-compliance (site access, payment withheld) and when someone on your side is actually checking that the certs arrive. The requirement without the follow-through doesn't solve the lapse problem.

What if a sub renews with a different carrier and doesn't tell me?

The new cert will show different policy numbers, a new carrier, and potentially different limits or endorsements. If you're not collecting the renewal cert, you have no visibility into this. Carrier changes are entirely legitimate — a sub can switch carriers at renewal — but the new policy needs to meet your requirements and you need a current cert to verify it does.

If a sub's cert lapses and there's a claim, whose policy pays?

If the sub has no coverage, the injured party claims against the sub directly and against you as the GC who hired them. Your GL policy responds to your own liability exposure, but you're defending a claim that should have been covered by the sub's insurance. This affects your limits, your loss runs, and your premium. The cost of a lapse enforcement system is always less than the cost of one significant uninsured claim. See our guide on general contractor insurance in Texas for more on how GC policies respond to sub-related claims.