There's a particular kind of Friday afternoon panic that anyone who's run a jobsite knows well. A sub is scheduled to start Monday, someone in accounting flags that their certificate of insurance expired three weeks ago, and now you're on the phone with an agent who's already left for the weekend. Multiply that by forty trade partners across three active jobs, and you understand why insurance tracking quietly eats more of a project team's time than almost anyone budgets for.
It's not glamorous work. But an uninsured sub who gets hurt on your site, or who damages the building, can turn into a claim that lands on your policy, spikes your experience mod, and follows you for years. Getting this right is risk management in the most literal sense. Here's how to actually do it well, and where the right software earns its keep.
Why insurance tracking is genuinely hard
The difficulty isn't any single certificate. It's the churn. Every sub carries multiple policies, each with its own renewal date, and those dates don't line up with your project schedule or with each other. A general contractor running a handful of jobs is easily juggling a hundred-plus active certificates, and every one of them is quietly ticking toward an expiration you didn't put on your calendar.
Then there's the verification problem. A certificate of insurance is just a snapshot — an ACORD 25 form that says coverage existed on the day it was issued. It is not the policy, and it does not obligate the insurer to notify you if that policy gets canceled mid-term. The old "30 days notice of cancellation" language most people still expect? Insurers largely stripped that out years ago. So a cert can be technically valid the day you collect it and worthless a month later, and nobody tells you. That gap is exactly where projects get burned.
The coverages that actually matter — and the numbers to hold
Before you can track anything, you need a written insurance requirement in your subcontract, and it needs teeth. At minimum, for most commercial and multi-family work, you're looking for:
- Commercial General Liability (CGL) — typically $1M per occurrence / $2M aggregate, often with the aggregate applying per project. Watch for exclusions. A GL policy riddled with residential-work or EIFS exclusions on a multi-family job is a policy that won't pay when you need it.
- Workers' Compensation and Employer's Liability — statutory comp plus employer's liability, usually $1M/$1M/$1M. This is the one that protects you when a sub's employee gets hurt. Sole proprietors who "waive" comp for themselves are a recurring trap — if they bring a helper, you now have an uninsured worker on your site.
- Commercial Auto — $1M combined single limit, covering owned, hired, and non-owned vehicles. Any trade driving to your site needs this, and "non-owned" matters because half of them are using personal trucks.
- Umbrella / Excess — often $2M–$5M depending on the owner's requirements, sitting over the GL, auto, and employer's liability.
The single most common defect isn't a missing policy — it's inadequate limits or the wrong endorsements. Which brings us to the part everyone forgets.
Additional insured and waiver of subrogation: the endorsements do the work
A certificate that lists you as "additional insured" in the description box means almost nothing. What matters is the actual endorsement attached to the sub's policy — usually a form like CG 20 10 (ongoing operations) plus CG 20 37 (completed operations). Without both, you're covered while the sub is working and left exposed the day a defect surfaces after they've moved on, which is precisely when construction-defect claims tend to land.
Same story with waiver of subrogation. If a sub's employee gets hurt and their comp carrier pays, that carrier can turn around and sue you to recover. A waiver of subrogation endorsement blocks that. You want it on both the GL and the workers' comp.
The discipline here is simple to state and easy to skip: don't accept the certificate as proof of an endorsement. For anything that matters, ask for the endorsement page itself. A cert says "coverage exists"; the endorsement says "and it covers you."
Collection: make it a gate, not a chase
The teams that stay ahead of this treat a valid COI as a hard prerequisite to mobilization, in the same category as a signed subcontract and an approved submittal. No cert on file, no start date. Full stop.
Practically, that means the request goes out the moment a sub is awarded, not the week they're due on site. Give agents a written template of your exact requirements — limits, required endorsements, the correct additional-insured wording, the certificate holder name spelled the way the owner's contract demands. Agents produce a hundred certs a week; if you hand them your spec, you get it right the first time instead of round-tripping three revised certs.
This is also where subcontractor management software stops being a nicety. Instead of a shared folder full of PDFs named "COI_final_v2_REAL.pdf," you get a portal where subs (or their agents) upload directly, the system logs what came in and what's still outstanding, and every requirement is checked against a standard you set once. The point isn't automation for its own sake — it's turning a reactive chase into a status board you can glance at.
Expiration tracking: the calendar is the whole game
If you only get one thing right, make it this. Every policy has an expiration date, and coverage that lapses mid-project is a live liability the entire time it's lapsed.
Build in lead time. A good rule of thumb: fire the first renewal reminder 45 days before expiration, a second at 30, and escalate hard at 15. Agents are slammed at renewal season, and a cert that "should be easy" routinely takes two or three weeks to actually land in corrected form. If you start at expiration minus five days, you will have gaps. This is exactly the kind of tracking software handles better than a human — dated alerts, a dashboard sorted by soonest-to-expire, and automatic reminders that go out whether or not anyone remembered to look.
Requirements flow down — and they're not the same on every job
Your obligations to the owner flow down to your subs. If the prime contract demands $5M umbrella limits and names the owner and lender as additional insureds, those same requirements have to appear on your subs' certs, or you're absorbing the gap yourself. A sub who carries $1M and no umbrella might be perfectly fine on a tenant-improvement job and completely unacceptable on the high-rise across the street.
So requirements are per-project, not per-sub. The framer you use on both jobs needs a different cert for each. Tracking that by memory is how the wrong limits slip through; tracking it against project-specific requirement sets is how you catch it before mobilization.
When a sub isn't compliant
Have the answer decided before you need it, because the moment you need it is always inconvenient. When a cert lapses or comes up short:
- Flag it immediately and notify the sub and their agent in writing, with the specific deficiency named — not "your insurance is expired" but "your GL renewal is missing the CG 20 37 completed-operations endorsement."
- Set a hard deadline tied to their next scheduled work.
- If it isn't cured, they don't work. A pointed conversation about a stopped start date resolves more lapsed certs than a dozen polite emails.
- Track the resolution so it doesn't fall through — and so you have a clean record if a claim ever references that window.
The work-stoppage lever only works if you actually pull it. Subs learn fast which GCs enforce and which ones let it slide. Be the one who enforces, and your compliance rate climbs on its own.
Where the schedule and the certs meet
This is the connection most people miss. Insurance compliance and scheduling are the same problem viewed from two angles: who is on my site, when. Your look-ahead schedule already answers that question. The trades in your three- to six-week window are exactly the ones whose certs need to be current before they show up.
When you build a weekly work plan and see that drywall mobilizes in two weeks, that's your cue to confirm drywall's coverage is good through their scope — not to discover the lapse the morning they roll up with a crew. A short-interval schedule that names the trades entering the building is, in effect, a live list of whose insurance had better be verified. In LookAheadWall, the look-ahead lays out which trades are coming and when, which gives you the runway to reconcile that upcoming sequence against your compliance status while there's still time to fix a gap. The schedule tells you who's next; the cert file tells you whether they're clear to be there.
A practical checklist
- Write specific insurance requirements into every subcontract, with limits and named endorsements — never "insurance acceptable to Contractor."
- Require the actual additional-insured (CG 20 10 and CG 20 37) and waiver-of-subrogation endorsements, not just the cert box.
- Make a valid COI a hard gate for mobilization. No cert, no start.
- Verify the certificate holder name and project requirements match what the owner's contract demands.
- Watch workers' comp closely on small subs and sole proprietors — that's where uninsured helpers hide.
- Reminders at 45 / 30 / 15 days before expiration, with escalation.
- Keep every historical cert. Defect claims can surface years later, and you'll need proof of what coverage existed during a given window.
The bottom line
Insurance tracking will never be the part of the job you look forward to, but it's the part that quietly decides whether a bad day on site becomes a bad year in litigation. The teams that do it well don't rely on memory or a spreadsheet someone updates when they remember — they treat compliance as a gate, automate the reminders, verify the endorsements that actually pay, and tie the whole thing to the schedule that already tells them who's walking on site next week. Get those habits in place, and the Friday-afternoon panic mostly goes away. What's left is a clean file, insured trades, and one fewer way for the project to hurt you.