A GC based in Texas won a project in California in 2024. They applied their standard Texas insurance requirements to every subcontractor on the job. Within 60 days, they discovered that California's contractor licensing laws mandate specific insurance structures that their Texas-based requirements did not address. Three subs were technically non-compliant under California law despite meeting every requirement in the subcontract.

Vendor insurance compliance is not uniform across the United States. State contractor licensing statutes, prevailing wage laws, public project specifications, and endorsement requirements create a patchwork that multi-state GCs must navigate on every project.

This guide maps the key variations that affect how GCs structure and enforce vendor insurance compliance programs.

State Contractor Licensing and Insurance Mandates

Every state has its own contractor licensing framework, and most tie specific insurance requirements to licensure. When your subcontractor holds a state license, their insurance must meet that state's minimums — regardless of what your subcontract specifies.

States with mandatory minimum insurance for licensed contractors:

State	Workers' Comp Required?	GL Minimum	Bond Requirement	Notable Provisions
California	Yes (no exceptions)	$1M per occurrence for C-39 roofing	Varies by license class ($15K-$150K)	Contractors must list license number on COI
Florida	Yes (4+ employees)	Not state-mandated	Not required for subs	Workers' comp exemptions for corporate officers
Texas	No state mandate	Not state-mandated	Not required	Workers' comp is elective — verify carefully
New York	Yes (no exceptions)	Not state-mandated	Varies by municipality	Disability benefits insurance also required
Illinois	Yes (no exceptions)	Not state-mandated	Not required	Specific roofing contractor licensing with insurance requirements
Georgia	Yes (3+ employees)	Not state-mandated	Not required	Residential contractor requirements differ from commercial
Colorado	Yes (no exceptions)	Not state-mandated	Not required	Specific requirements for asbestos abatement contractors
Washington	Yes (no exceptions)	Not state-mandated	$12K surety bond for registered contractors	Industrial insurance (state fund) required
Oregon	Yes (no exceptions)	Not state-mandated	$20K surety bond for licensed contractors	Construction Contractors Board oversees compliance
Nevada	Yes (no exceptions)	Required for licensure	Varies by license class	License bond amounts tied to monetary limit of license

Critical takeaway for multi-state GCs: Your subcontract insurance requirements set the floor. State licensing requirements may raise that floor without your knowledge. When onboarding subs in a new state, verify state-specific mandates before assuming your standard requirements suffice.

Prevailing Wage Project Requirements

Prevailing wage projects — typically publicly funded work governed by federal Davis-Bacon Act or state equivalents — impose additional insurance considerations that affect vendor compliance programs.

Workers' compensation on prevailing wage projects. In states where workers' comp is elective (such as Texas), prevailing wage projects funded with federal dollars effectively require coverage through Davis-Bacon compliance obligations. Your vendor compliance program must flag prevailing wage projects and enforce workers' comp requirements even in states that otherwise allow opt-out.

Fringe benefit impacts on insurance costs. Prevailing wage rates include fringe benefit calculations that affect insurance premium computations. Subs sometimes carry lower coverage limits because their insurance costs eat into already-tight prevailing wage margins. This creates a compliance tension: the sub needs adequate insurance but faces financial pressure to minimize it.

Certified payroll and insurance verification. Some public agencies require proof that subcontractors' workers' compensation policies are active and rated correctly for the classifications of work being performed. Your compliance program should verify that the workers' comp classification codes on the certificate match the actual work the sub performs on your prevailing wage project.

States with strong prevailing wage enforcement affecting insurance compliance:

New York: Rigorous prevailing wage enforcement with insurance verification tied to contractor registration
Massachusetts: Monthly certified payroll submissions with insurance verification
California: DIR registration required for public projects, including insurance documentation
Illinois: Prevailing wage compliance linked to contractor registration and insurance filings
New Jersey: Public works contractor registration with insurance verification requirements

Public Project Insurance Specifications

Public project owners impose insurance requirements that exceed commercial project standards. These requirements flow down to subcontractors through your subcontract, creating additional vendor compliance obligations.

Common public project insurance specifications GCs must flow down:

Higher minimum limits. Public projects routinely require $2M to $5M per-occurrence GL limits and $5M to $10M aggregate limits — double or triple typical commercial project requirements. Your vendor compliance program must flag public project subs and apply the elevated requirements.

Specific additional insured requirements. Public entities require additional insured status on both the GL and umbrella/excess policies. The endorsement must name the public entity specifically — blanket additional insured endorsements may not satisfy the specification. Some agencies require ISO endorsement form CG 20 10 (for ongoing operations) and CG 20 37 (for completed operations) specifically.

Professional liability for design-build. Public design-build projects increasingly require professional liability (errors and omissions) coverage from subcontractors performing design work. This applies to MEP subs with design responsibilities, precast concrete suppliers providing engineering, and specialty contractors performing delegated design. Minimum limits range from $1M to $5M depending on the project size and the sub's design scope.

Pollution liability. Environmental remediation, demolition on older structures (asbestos, lead), and projects near waterways may require contractor's pollution liability coverage. Some public agencies make this a blanket requirement for all subs regardless of scope.

Railroad and utility requirements. Projects adjacent to railroads require railroad protective liability coverage naming the railroad company. Projects near or crossing utility infrastructure may require specific utility damage coverage endorsements.

State-Specific Endorsement Requirements

Beyond coverage types and limits, some states require specific endorsement language that affects vendor compliance verification.

California. The state requires that workers' compensation policies carry an "All States" endorsement or specifically list California. Policies issued in other states that do not name California may not provide valid coverage for California operations. Verify the Information Page of the workers' comp policy, not just the certificate.

New York. Disability benefits insurance and paid family leave insurance are required in addition to workers' compensation. These are separate policies (or endorsements) that many out-of-state subs do not carry. GCs must verify three coverages — workers' comp, disability benefits, and paid family leave — for every sub performing work in New York.

Louisiana. The state has unique insurance regulations including the Direct Action Statute, which allows injured parties to sue the insurer directly. This affects how additional insured endorsements function and may require specific endorsement language acknowledging Louisiana's direct action rights.

Texas. Because workers' compensation is elective, GCs must verify whether each sub carries workers' comp or has opted for non-subscription status. Non-subscribing employers carry different liability exposure, which may require higher GL limits or alternative injury benefit program documentation.

Florida. Corporate officers can exempt themselves from workers' compensation coverage. Verify whether sub owners/officers have filed exemptions and whether this creates coverage gaps for individuals performing physical work on your project.

Building a Multi-State Compliance Program

GCs operating across multiple states need a compliance framework that accommodates jurisdictional variation without creating administrative chaos.

Step 1: Create a state requirements overlay. Maintain a reference document that maps each state's unique requirements on top of your base compliance standards. When a project is set up in a new state, the overlay triggers additional verification steps specific to that jurisdiction.

Step 2: Automate state-specific rule application. If your compliance software supports location-based rule sets, configure state-specific requirements that automatically apply when a project is assigned to a particular state. This prevents reliance on compliance staff remembering jurisdictional nuances.

Step 3: Verify sub licensure in the project state. A sub licensed in Georgia is not necessarily licensed in Alabama, even for a project two miles from the state line. Verify that each sub holds a valid contractor's license (where required) in the state where the project is located.

Step 4: Monitor regulatory changes. State insurance and licensing regulations change. Assign a quarterly review of legislative updates in your active states. Your insurance broker and construction attorney should flag changes that affect subcontractor insurance requirements as part of their service.

Step 5: Train project teams on state-specific requirements. When a project team is assigned to work in a state different from their home base, brief them on the unique compliance requirements of that jurisdiction. A 30-minute briefing prevents months of non-compliance.

Multi-State Compliance Coordination Challenges

Managing vendor insurance compliance across multiple states introduces specific operational challenges.

Subs working across state lines. A mechanical contractor headquartered in Connecticut working on your project in Massachusetts needs Massachusetts workers' comp coverage, not just their Connecticut policy. Verify that the sub's workers' comp policy includes coverage for the project state, either through an "All States" endorsement or a specific state listing.

Rate classification variations. Workers' compensation classification codes and rates vary by state. A sub's NCCI classification code for electrical work in Ohio may carry a different rate and reporting structure than the same work in Pennsylvania. This does not typically affect your certificate review, but it affects premium audits that can retroactively impact coverage validity.

Endorsement language inconsistencies. An additional insured endorsement that satisfies requirements in Texas may not meet specifications in New York. Public agencies in different states interpret "primary and non-contributory" language differently. When in doubt, have your insurance broker review the actual endorsement language — not just the certificate notation.

Frequently Asked Questions

Do we need different insurance requirements for every state we operate in? You need a base set of requirements that meets the highest standard across your operating states, plus state-specific overlays for unique requirements. For example, your base GL requirement might be $2M per occurrence (meeting most states' needs), with a New York overlay adding disability benefits and paid family leave verification, and a California overlay adding license number verification on certificates.

How do we handle subcontractors who are licensed in one state but working in another? Verify that the sub holds a license in the state where the project is located (if that state requires licensing). Verify that their insurance covers operations in the project state. Workers' comp is the most common gap — many state policies require specific state endorsements or an "All States" endorsement to provide coverage outside the home state.

What happens if a sub's insurance meets our contract requirements but not the state's licensing requirements? State licensing requirements take precedence. If a state requires a minimum $500K GL for licensed roofers and your subcontract only requires $300K, the sub must carry $500K to maintain their license. Operating without proper insurance can result in license suspension, which creates a different compliance problem — an unlicensed contractor performing work on your project.

How do we keep up with changing state insurance regulations? Subscribe to legislative tracking services focused on construction regulation (your construction attorney should provide this). Join your state's AGC chapter, which monitors regulatory changes affecting contractors. Schedule quarterly reviews of regulatory updates with your insurance broker. Budget 4 to 6 hours per quarter for regulatory monitoring across your active states.

Are there federal insurance requirements that override state variations? Federal projects carry their own insurance specifications through FAR (Federal Acquisition Regulation) clauses. Davis-Bacon prevailing wage requirements effectively mandate workers' comp even in states where it is elective. Federal flood insurance requirements apply to projects in designated flood zones regardless of state. Beyond these, state requirements generally govern unless the federal specification is more stringent.

How do we manage vendor insurance compliance for projects that cross state lines (pipelines, highways, rail)? Linear projects crossing state lines require compliance verification in each state the project touches. Workers' comp coverage must be valid in every state where work occurs. Licensing requirements must be met in each jurisdiction. Create a compliance matrix by project segment, mapping each segment to its governing jurisdiction and applicable requirements.

Multi-state vendor insurance compliance demands a platform that adapts to jurisdictional requirements automatically. Request a demo of SubcontractorAudit to see how state-specific compliance rules, automated certificate verification, and multi-project dashboards simplify compliance across every state you operate in.