What Insurance Should You Require From Every Subcontractor?

Clear subcontractor insurance requirements protect the GC long before there is a claim. The right insurance package helps keep injuries, property damage, vehicle accidents, and subcontractor mistakes from rolling uphill to the builder who hired the trade.

Too many contractors collect a certificate of insurance once, drop it in a folder, and assume they are covered. That is not risk management. It is hope. You need minimum coverage standards, a way to review the certificate, and a system for watching expiration dates before a sub comes back to site uninsured.

Why requiring sub insurance protects the GC

When a subcontractor causes a loss, the first lawsuit often names everyone connected to the project: the sub, the GC, the owner, and sometimes the property manager or developer. If the sub has proper coverage and the required endorsements, their policy becomes part of the defense and claim-paying structure instead of leaving the GC exposed.

Insurance requirements also create a quality filter. Subs who resist basic paperwork, cannot produce a current COI, or let policies lapse are often the same subs who create scheduling, billing, and supervision headaches later.

The 4 coverages every GC should require

1. General liability

This is the baseline. Require at least $1 million per occurrence and confirm the aggregate limit is acceptable for your jobs. General liability responds to third-party bodily injury and property damage claims arising from the sub's operations.

2. Workers compensation

If the sub has employees, workers comp should be non-negotiable. Without it, an injured worker can create immediate pressure on the GC and trigger ugly coverage questions with your own carrier.

3. Auto liability

If the sub drives company trucks, trailers, or service vehicles to the site, auto liability belongs in the requirement stack. Vehicle losses often happen off the jobsite but still drag the project into the claim.

4. Umbrella or excess liability

Umbrella coverage adds extra limits above primary policies. For higher-risk trades, larger projects, or builders with strict owner contracts, an umbrella requirement gives another layer of protection when a claim outgrows the base policy.

How to read a certificate of insurance

A COI is a summary, not the actual policy. Still, it tells you a lot if you know what to check.

• Named insured: make sure the company name matches the subcontract you signed.
• Coverage types: confirm general liability, workers comp, auto, and umbrella appear when required.
• Limits: verify the per-occurrence and aggregate numbers meet your contract minimums.
• Effective and expiration dates: the policy must be active for the period the sub is on your job.
• Certificate holder: your company should be listed correctly.
• Description of operations: this is where project-specific notes or additional insured references may appear.

The important caution: the COI alone does not prove every endorsement. It is a useful intake document, but not the same thing as policy language.

Why additional insured status matters

If the subcontract requires the sub to name the GC as an additional insured, ask for the endorsement or clear proof it exists. That endorsement is what extends liability protection to the GC for claims arising from the sub's work. Without it, you may have a certificate that looks nice but delivers less protection than your subcontract promised.

On larger or owner-sensitive projects, upstream contracts often require the owner and GC to be listed as additional insureds. If you do not push that requirement downstream to the trades, the gap lands on you.

How to track expiration dates without chaos

Most policies renew annually, which sounds manageable until you have ten or fifteen regular trade partners. Then expirations start landing in random months while crews move across multiple active projects.

1. Create one master roster of all active subs.
2. Track general liability, workers comp, auto, umbrella, and license renewal dates separately.
3. Flag renewals at 60 days and again at 30 days before expiration.
4. Do not schedule returning subs until updated documents are in hand.
5. Store the newest COI where PMs, accounting, and field leadership can all find it.

The key is to make insurance review part of mobilization and invoice release, not an isolated office task nobody remembers until after a problem.

What happens when a subcontractor has a lapse

If a sub's policy expires and they keep working, your risk increases immediately. A claim during the lapse can trigger fights over defense, indemnity, and whether the GC knowingly allowed an uninsured trade onto the site. Your own carrier may also ask why the subcontractor compliance rules in your agreements were not enforced.

The right move is simple: pause mobilization or ongoing work until updated proof is received, confirm the coverage dates, and document the correction. Letting it slide because the sub is “almost done” is how avoidable losses become expensive lessons.

Put the insurance requirement in the subcontract, not just the email

The cleanest insurance tracking system still depends on the subcontract saying exactly what is required. Your subcontract should state the minimum limits, whether additional insured status is required, whether waiver of subrogation applies, and that updated certificates must be delivered before expired coverage is allowed back on site.

That written requirement matters when a sub pushes back. It gives the PM and accounting team something enforceable to point to, and it helps your own carrier see that you had a real compliance process instead of an informal request.

When a COI is not enough by itself

A certificate is a starting point, not the whole file. On bigger jobs or higher-risk trades, ask for the additional insured endorsement, umbrella evidence, and any project-specific wording your prime contract requires. If the owner contract is strict, your downstream paperwork has to be just as strict.

That extra review feels tedious until there is a claim. Then it becomes the difference between having the right paper in the file and finding out too late that the certificate looked better than the actual coverage.

Final takeaway

Insurance requirements are not admin clutter. They are part of how a GC buys risk down before the first bad day happens. The best system is simple: set minimum standards, verify the COI, require additional insured language where needed, and track renewal dates like they matter.

Because they do.