Certificate of Insurance Tracking: A GC's Checklist for Renewals and Lapsed Coverage

Why COI Tracking Breaks Down on Busy Projects

A subcontractor's certificate of insurance (COI) expires on a Thursday. You don't find out until the following Monday, when the owner's rep asks for an updated file. Work was performed Friday. You now have a gap in coverage documentation, and depending on your contract language, that gap can expose you to uncovered claims and default notices.

This is not a rare scenario. It happens on projects of every size. The problem is almost never a lack of intent. Subs mean to renew. GCs mean to follow up. The problem is that COI tracking usually lives inside someone's email inbox or a shared folder that nobody audits until something goes wrong.

The checklist below gives you a repeatable process to close that gap.

Step 1: Collect the Right Documents Before Work Starts

Before any subcontractor or supplier sets foot on your project, collect the following:

• Certificate of Liability Insurance naming your company and the project owner as additional insureds
• Certificate of Workers' Compensation Insurance showing the correct state and classification codes
• Umbrella or Excess Liability endorsement if your subcontract requires it
• Additional insured endorsement (the actual endorsement page, not just the certificate)

A certificate alone does not guarantee additional insured status. The endorsement does. Make that distinction clear in your subcontract and enforce it from day one.

Verify that the limits on the certificate match your contract requirements before you sign off on mobilization. A subcontract requiring $2 million per occurrence with a $2 million COI on file is in order. A $1 million COI for the same subcontract is not.

Step 2: Log Every Policy and Its Expiration Date in a Central Tracker

Every COI you collect gets entered into a single tracking document. A spreadsheet works if you're disciplined. A purpose-built compliance module is better. At minimum, your tracker should capture:

• Subcontractor or vendor name
• Policy type (GL, WC, umbrella, auto)
• Carrier name and policy number
• Policy effective date and expiration date
• Coverage limits (per occurrence and aggregate)
• Additional insured status confirmed (yes/no)
• Projects the sub is active on
• Date the certificate was received and by whom

Do not rely on memory or folder names. A tracker with expiration dates is the only way to run systematic renewal alerts.

Step 3: Set Renewal Alerts at 60, 30, and 7 Days Out

Insurance policies typically renew annually. Build your alert schedule around that cycle:

• 60 days before expiration: Send a written request to the subcontractor asking them to confirm renewal with their broker. This gives them time to avoid a lapse.
• 30 days before expiration: Follow up if you have not received a new certificate. Flag the subcontractor's next pay application for hold pending receipt of updated COI.
• 7 days before expiration: Final notice. If no updated certificate is on file, issue a written notice that the subcontractor will be suspended from the project until coverage is confirmed.

Put these thresholds in your subcontract. When a sub knows that lapsed coverage triggers a payment hold, they respond faster.

Step 4: Tie COI Status Directly to Pay Application Approval

This is the single most effective enforcement mechanism available to a GC. Before any pay application is approved, the person processing billing checks the COI tracker. If the policy has lapsed or is within 7 days of expiration with no renewal on file, the pay application goes on hold.

Some GCs are reluctant to hold payment over an insurance lapse. Do not be. Your subcontract almost certainly requires current, valid insurance as a condition of payment. Enforcing that condition protects you from claims and keeps your subs current. A sub that experiences one payment hold for a COI lapse rarely lets it happen again.

Document every hold in writing: the date, the reason, and the specific policy that lapsed. This creates a clear record if a dispute arises later.

Step 5: Conduct a Full COI Audit at Project Milestones

Point-in-time alerts are necessary but not sufficient. Schedule a full audit of your active COI file at these milestones:

• Project kickoff (confirm all subs on the initial schedule are covered before mobilization)
• 30 days after Notice to Proceed (catch any subs whose policies were already nearing expiration when they started)
• At each major phase transition (structural, MEP rough-in, finishes)
• 90 days before substantial completion (identify any stragglers who will still be on site at closeout)
• Final closeout

A milestone audit takes less than an hour with a clean tracker. Without a tracker, it takes most of a day and you'll still miss something.

Step 6: Keep Expired Certificates in the File

When a COI renews, do not delete the old one. Archive it. If a claim surfaces two years after project completion, your defense depends on proving coverage was in place at the time of the incident. Expired certificates are evidence. Treat them as project records and retain them for at least as long as your state's statute of repose for construction defects, which typically runs six to ten years.

A Quick Checklist Summary

• Collect GL, WC, umbrella, and endorsements before mobilization
• Verify limits against subcontract requirements
• Log every policy in a central tracker with expiration dates
• Set alerts at 60, 30, and 7 days before expiration
• Tie COI status to pay application approval
• Audit the full file at project milestones
• Archive expired certificates for the life of the project records

Compliance tracking is easier when lien waivers, insurance, and certified payroll live in one place. EZBilling is built for that.