How General Contractors Track Subcontractor Insurance Certificates (Without the Last-Minute Fire Drill)

The Call You Get at 7 PM the Night Before a Job Starts

The scenario plays out constantly in the construction industry. A general contractor has a job starting tomorrow morning. Everything is lined up — crew, equipment, materials. Then the client's insurance broker calls. They need a certificate of insurance from the electrical subcontractor before anyone steps on site tomorrow. No COI, no work.

The GC opens email and starts searching. They find a COI. But when they look at the expiration date, it lapsed six weeks ago. They call the sub. No answer. They try the sub's office. Voicemail. By 9 PM they've exhausted their options. The job starts late. The client is irritated. The GC spent three hours managing a paperwork problem that should have been caught a month ago.

This isn't an edge case. General liability claims are the most common construction insurance claim type — and the documentation failures that enable disputes start exactly here, with COIs that nobody was tracking. For general contractors managing multiple active projects and a rotating cast of subcontractors, COI tracking is one of the highest-stakes administrative tasks in the business. Most GCs do it with a spreadsheet and good intentions.

Neither is enough.

What a Subcontractor COI Actually Needs to Cover

Most GCs know they need a COI from every sub. Fewer know exactly what they need to verify once they have it. An unexpired cert isn't automatically a compliant cert — there are several ways a COI can be current by date but still fail to meet contract requirements.

Here's what a GC actually needs to verify on every subcontractor COI:

• General liability coverage — Minimum limits are typically specified in your subcontract. The standard is $1M per occurrence / $2M aggregate for routine scopes; higher-risk work (roofing, excavation, structural steel) often requires $2M per occurrence. Check your subcontract, not just the cert.
• Workers' compensation — Required in virtually every state for any sub with employees working on your site. If a sub's worker is injured on your project and the sub has no WC coverage, your liability exposure is significant. Confirm the certificate shows active coverage, not just that the policy exists.
• Commercial auto liability — Required for any sub whose workers drive vehicles to or on the job site. A minimum of $1M combined single limit is standard for most contracts. Don't skip this one just because the scope seems low-risk.
• Umbrella or excess liability — Required for larger projects or higher-risk scopes. Typically $2M–$5M over the underlying GL coverage. Check your owner's contract — if you're required to carry umbrella coverage as the GC, you're likely required to flow it down to your subs.
• The GC as additional insured — This is the most commonly missed requirement. Your company needs to be named as an additional insured on the sub's general liability policy. A COI that shows valid coverage but doesn't name you as an additional insured provides much weaker protection in a claim. Verify the additional insured endorsement, not just the base coverage.
• Project-specific endorsements — Some owner contracts and lender requirements specify additional endorsements: completed operations coverage, waiver of subrogation, primary and non-contributory language. These need to be on the sub's COI, not just assumed.

The expiration date is only one of many things that can make a COI non-compliant. But expiration is the one that kills jobs — because it's the check that happens at the last minute, by the party with the least information, under time pressure.

Why the Spreadsheet Breaks Down for GC COI Tracking

Most GCs track subcontractor COIs in a spreadsheet: sub name, insurance company, policy number, expiration date. It looks like a system. For a GC running one or two projects with five subs, it holds together. Scale it up and it breaks down in three specific ways.

The volume problem. A mid-size general contractor routinely runs 20–30 subcontractors per active project across 5 or more simultaneous jobs. That's 100–150 COIs to track at any given time. Each has a different expiration date — most tied to the sub's annual policy renewal, which falls on different calendar dates for every sub. At that volume, a spreadsheet isn't a tracking system — it's a pile of data with no mechanism to surface what needs attention today. Nobody is opening the spreadsheet every morning to scan 150 rows for upcoming expirations.

The renewal chasing problem. Commercial insurance policies renew annually. Every year, every sub needs to send an updated COI. That renewal doesn't happen automatically from your perspective — you have to request it, the sub's broker has to generate it, and the sub has to forward it. Without a system that tracks what's expiring and automatically prompts outreach, GC project teams spend weeks every year in reactive firefighting mode: calling subs to get updated certs, following up when subs don't respond, and discovering at the worst possible moment that a cert lapsed two months ago.

The compliance gap. A COI arrives, gets filed in a folder or logged in a spreadsheet, and that's where the process ends. Nobody cross-checks the incoming cert against the actual subcontract requirements: Are the limits right? Is the GC listed as additional insured? Is the umbrella coverage flowing down as required? The cert is "on file" — but on-file and compliant are not the same thing. When a claim comes in, that distinction matters enormously.

What a Real COI Tracking System Needs

The good news: the system doesn't have to be complex. It does have to be intentional. For a GC managing an active sub roster, five things make the difference between a COI tracking process that works and one that generates last-minute fire drills.

1. A centralized sub/vendor database with attached COI documents. One record per subcontractor showing their current COI status, coverage types, policy limits, and the actual certificate document. When a client's broker asks for proof of coverage, you go to one place — not an email inbox, a shared drive folder with ambiguously named files, or a box of paper certificates in someone's office.

2. Expiration date alerts at 60, 30, and 7 days. Sent to whoever owns the sub relationship — the project manager, the project coordinator, or whoever is responsible for chasing the renewal. Not just a compliance manager who may not know which sub is on which job. The 60-day alert gives you time to request the updated cert before the sub's policy renews. The 30-day alert is the action trigger. The 7-day alert is the escalation point — if a cert is 7 days from expiring and nothing has happened, someone needs to make a call today.

3. Project-level grouping. Which subs are on which jobs matters. A cert expiring for a sub who is actively on Site A is a different urgency than one expiring for a sub whose scope wrapped up last month. Good COI tracking is organized around projects, not just a flat list of every sub you've ever worked with.

4. A quick audit view: "Show me every sub with a COI expiring in the next 30 days." This is the question you need answered weekly. Not "does this specific sub's cert look current?" but "what am I about to be surprised by?" A 30-day forward view lets you get ahead of issues instead of reacting to them.

5. An easy re-request workflow. When a COI expires or is about to, you need to contact the sub and request an updated certificate fast. The system should make that friction-free — a quick email to the sub's contact, a clear record of when the request was sent, and a way to log when the new cert comes in. Manual chasing without a workflow creates gaps: you send the email, the thread gets buried, and three weeks later you realize the sub never responded.

Stop Getting Surprised on Job Day

Most GCs don't find out a COI expired until it creates a problem — a job delay, a denied claim, a contract violation, or that 7 PM call from the client's broker the night before work starts.

CertTrack gives you a 30-day runway. Every expiring certificate triggers an automatic alert, so you know what's coming before it becomes an emergency. You chase the renewal when there's still time — not when the job is already stopped.

Add your subcontractors, log their COI details, and CertTrack handles the tracking from there. Alerts go out at 60, 30, and 7 days before each cert expires. When a job starts and someone asks for proof of coverage, you have it.

14-day free trial, no credit card required. Start free →