What Happens If a Subcontractor Doesn't Have Insurance

Almost everything written about hiring an uninsured subcontractor covers a single scenario: something goes wrong, someone gets hurt or something gets damaged, and the bill lands on you instead of the sub. That is real, and it is the bigger number. But it distracts from a second consequence that is easy to miss because it doesn't depend on luck at all.

If you use a subcontractor who cannot produce a certificate of insurance, your own insurer will very likely charge you for it at your next policy audit — whether or not anything ever went wrong on the job. That cost is closer to certain than contingent. Almost nothing else written on this topic separates the two, which is a problem, because they call for different responses: one is a reason to keep good records, the other is a reason to stop the work.

Most general liability and workers' compensation policies for contractors are audited annually. The insurer compares what you estimated at the start of the year — payroll, subcontractor spend, revenue — against what actually happened, and adjusts the premium to match.

Subcontractor payments are part of that comparison. The auditor asks for a certificate of insurance covering the policy period for every subcontractor you paid. If you can't produce one for a given subcontractor, standard premium-audit practice across general liability and workers' compensation carriers is to reclassify what you paid that subcontractor as your own payroll — and rate it at your own job classification, which is frequently a higher rate than the subcontractor's own trade would have carried. A specialty electrical sub with no certificate, for example, gets folded into your book at your rate, not theirs.

This happens on profitable jobs with a clean safety record. The audit doesn't ask whether anyone got hurt; it asks whether you can prove the subcontractor was insured. On a project with meaningful subcontractor spend, the retroactive premium adjustment from a handful of missing certificates can be a five-figure surprise that shows up months after the job is finished and the money is already spent.

The fix costs nothing and takes no more than a filing habit: collect the certificate before the subcontractor starts, and keep it somewhere you can actually produce it at audit time. Our vendor COI requirements checklist covers exactly what a certificate needs to show to count.

Workers' compensation is no-fault: an injured worker doesn't have to prove anyone was negligent to be entitled to benefits. That protection has to come from somewhere, so most states have built a backstop into their workers' compensation statutes usually referred to as the statutory employer (or statutory employee) doctrine. Construction-law commentary on the subject counts roughly 44 states plus the District of Columbia as having some version of it on the books, though the exact mechanics vary by state.

The plain-English version: if a subcontractor doesn't carry workers' compensation and one of the subcontractor's own employees is hurt on your project, the law in most states does not let that worker go uncompensated just because their direct employer cut corners on insurance. Responsibility for the benefits shifts up the chain to the general contractor, regardless of how many people the subcontractor employs or how the subcontract is worded.

This is the part worth knowing precisely: in the jurisdictions that recognize the doctrine, a general contractor who obtained a valid certificate of insurance from the subcontractor before work began is generally not treated as the statutory employer for that claim — the certificate is what shifts the exposure back to the subcontractor's own policy. A general contractor who skipped that step, or accepted a certificate that had already expired, doesn't get that protection. Whether the certificate was collected on time, not just whether one exists somewhere in a file, is what the law is actually testing.

The instinct is to assume your own general liability policy will absorb a claim caused by a subcontractor's work, the way it would absorb one caused by your own crew. It usually won't. Commercial general liability policies are underwritten around your own operations and employees; damage or injury caused by an independent contractor's negligence commonly falls outside that, unless you've specifically arranged coverage for subcontracted work — which most small operations haven't.

So if an uninsured subcontractor causes a fire, a flood, a collapse, or injures a bystander, and their own policy doesn't exist to respond, the claim looks for the next solvent party with a policy. That's usually you, and your policy may exclude exactly this scenario — meaning the money comes directly out of the business rather than from any insurer at all. This is the same mechanism covered in the real cost of a lapsed vendor policy, except a subcontractor who never had insurance is a certainty going into the job, not a policy that quietly expired without anyone noticing.

Separate from insurance, it's worth knowing that federal workplace-safety enforcement doesn't neatly separate a general contractor from its subcontractors either. Under OSHA's long-standing multi-employer citation policy, an agency can cite a general contractor for a safety hazard that a subcontractor created, if the general contractor is found to have had a reasonable opportunity to detect and correct it because of its supervisory control over the site — a status referred to as the 'controlling employer.' Federal appeals courts have repeatedly upheld this framework.

This isn't an insurance mechanism, and it operates independently of whether the subcontractor was insured. But it's part of the same picture: hiring a subcontractor who cuts corners on insurance often correlates with cutting corners on safety, and the general contractor can end up answering for both.

State mechanics vary enough that a single national description would be misleading, so here is one state's version as a worked example rather than a rule that applies everywhere. California maintains a state-administered fund, the Uninsured Employers Benefits Trust Fund (UEBTF), that pays medical treatment, wage-loss, and permanent-disability benefits to a worker injured while working for an employer who was illegally uninsured for workers' compensation — then pursues the uninsured employer to recover what it paid, according to the California Department of Industrial Relations.

California law also treats an unlicensed subcontractor's workers as the hiring party's own employees for workers' compensation purposes in some circumstances, according to construction-law practitioners writing on the subject — meaning hiring cheaply because a subcontractor lacks a license and insurance can convert their crew into your payroll obligation, not merely a claim you have to defend. If you operate in California or any other state, confirm the current mechanics with your broker or an attorney rather than relying on a general description like this one; state statutes in this area are specific and change.

Yes, and in some states and for some project types you're required to. Requiring proof of insurance as a condition of doing business is standard, enforceable contract practice, not a courtesy. Many state contractor-licensing regimes also condition the license itself on carrying insurance, which means an uninsured subcontractor may not be legally entitled to perform the work at all, independent of anything you put in your own contract.

The practical version of 'no' is a gate, not a conversation held under deadline pressure. Build the requirement into the subcontract and the vendor-onboarding process, not into a judgment call made by whoever is running the site the day the crew shows up. Our guide to requesting a certificate of insurance from a vendor covers how to ask so the first certificate that comes back is actually usable, including templates for the initial request and the pre-expiry renewal ask.

Discovering a gap after work has already started is common — a certificate that looked fine at onboarding quietly expired, or a subcontractor never sent one in the first place and nobody chased it. Handle it in this order.

One subcontractor is a phone call. A general contractor running several jobsites, or a property manager with dozens of vendors, is running the same check dozens of times a month, against certificates that expire on their own unrelated schedules. This is exactly where manual tracking in a spreadsheet breaks down first — not on the check itself, but on remembering to run it before the next payment goes out.

The two consequences in this guide call for two different kinds of help. The premium-audit exposure is solved by never letting an uninsured subcontractor get paid without a certificate on file in the first place — a mechanical, repeatable check. The statutory-employer and liability exposure is solved by the same discipline applied consistently: a valid certificate collected before work starts, on every subcontractor, every time, with nobody's memory as the backstop.

That's the gap CoverSynx is built to close. It gives each subcontractor a link to submit their certificate without creating an account, reads it, checks it against the coverages and endorsements you require, and flags anything missing before you approve them to start — with reminders before every renewal so the same gap doesn't reopen a year later. It assists verification; it doesn't certify coverage or replace a call to your broker on anything that looks wrong. For the broader collection and renewal process, see how to track certificates of insurance, and for the specific case of general contractors and subs, our subcontractor COI tracking page covers the workflow in more detail.

Patterns that show up repeatedly in real compliance files and audit findings.