State compliance · Oregon

Oregon general contractors face some of the broadest subcontractor liability in the country — here is what you are actually on the hook for

Between ORS 656.029's double-premium WC penalty, CCB licensing requirements, post-Yeatts employer liability, and SB 426's new joint wage law, Oregon stacks exposure on GCs in ways most other states don't. Knowing what to verify — before work starts — is the only real protection.

Construction crew working on a commercial job site in the Pacific Northwest

Most general contractors know they are supposed to collect certificates of insurance before a sub starts work. Fewer understand that in Oregon, that baseline is not close to sufficient. Oregon has layered a set of statutory obligations on top of the standard COI requirement — a CCB licensing regime with its own insurance minimums, a workers' compensation penalty structure that doubles unpaid premiums, an employer liability law that the courts have significantly expanded, and a brand-new wage liability law that went into effect January 1, 2026 and has no contractual escape hatch. Each one represents a category of exposure that a COI alone will not catch.

This is a state where the compliance checklist for a responsible GC is longer than in most of the country — and where the consequences of skipping items are concrete and well-documented. Here is what each layer actually means.

Workers' compensation: Oregon's double-premium penalty under ORS 656.029

Oregon uses a competitive workers' compensation market — private carriers alongside the state-fund option at SAIF Corporation — rather than a monopolistic system like neighboring Washington. That competition is good for pricing. What it also means is that coverage verification falls entirely on you as the GC, because there is no centralized state fund that would automatically catch a sub with lapsed coverage.

Under ORS 656.029, if a subcontractor on your job site does not carry workers' compensation insurance and one of their workers is injured, you — the general contractor — become liable for the injured worker's benefits as the indirect employer. The state does not just ask you to cover the claim. Oregon also imposes a penalty equal to twice the workers' comp premium that should have been paid, with a minimum fine of $1,000. If the noncompliance continues after a notice is issued, that fine escalates to $250 per day with no cap on total exposure.

This is not a theoretical scenario. Smaller subs let WC policies lapse when cash is tight — the coverage is expensive and renewals are easy to defer. The sub has no incentive to tell you. The first time you may learn about the lapse is when an incident occurs and the insurer pulls the policy number and finds it cancelled. At that point ORS 656.029 has already activated and you are working backward through a penalty calculation on top of a live workers' comp claim.

The verification step that catches this before it becomes a problem is straightforward: require a certificate of insurance showing active WC coverage before authorizing any work, track the policy expiration date, and require a fresh certificate at renewal. A lapse mid-project is just as damaging as no coverage at the start.

CCB licensing: it's not enough that you're licensed — your subs need to be too

Oregon's Construction Contractors Board (CCB) requires every contractor and subcontractor performing work in Oregon to hold a current CCB license. This is where a lot of GCs run into trouble with an assumption: your CCB license does not cover work performed by your subcontractors. Each sub must be independently licensed, and you are responsible for verifying that license before they set foot on the job.

The insurance minimums embedded in CCB licensing are worth knowing specifically because they vary by license tier:

  • Residential general contractors: $500,000 general liability aggregate minimum
  • Commercial general contractors, Level 1: $2,000,000 general liability aggregate minimum
  • Specialty contractors: minimums vary by category

Hiring an unlicensed subcontractor carries a penalty of $1,000 per violation for a first offense, escalating to $5,000 or more for subsequent violations under OAR 812-005-0800. The CCB can also suspend your own license for repeated violations. Oregon makes it straightforward to check: the CCB's online license lookup shows current status, expiration, and active insurance on file. There is no reason to skip this step — and no defense available after the fact that you didn't know the sub was unlicensed.

The practical compliance requirement here goes beyond the COI. You need the sub's CCB license number, and you need to verify it is current before each project, not just at initial onboarding. Licenses expire. Insurance lapses. A sub who was CCB-compliant when you first added them to your vendor list may not be six months later.

The Employer Liability Law after Yeatts: why delegating safety to subs is not enough

Oregon's Employer Liability Law (ORS 654.305) imposes liability on "indirect employers" — including general contractors — for injuries to workers of subcontractors under certain conditions. The law predates most modern construction practice, and its interpretation has shifted significantly.

For decades, GCs operated under the assumption that retaining inspection authority without direct control over how work was performed was enough to avoid ELL liability. If you reserved the right to inspect safety practices but delegated actual safety management to the sub, the thinking was that you were protected. The Yeatts decision by the Oregon Court of Appeals eliminated that assumption. Under the current interpretation, a GC can face ELL liability when:

  • The GC and sub are engaged in a common enterprise and the GC has control over the conditions that created the risk
  • The GC provides detailed instructions about how the work is performed
  • The GC contractually retains the right to inspect safety or require additional measures — even if it never exercises that right

That third point is the one most GCs don't expect. Standard subcontract language that reserves the GC's right to inspect safety conditions — language that GCs include specifically to maintain quality control — has been used as a basis for ELL liability. The contractual right to inspect, without more, can be enough.

ELL liability is not capped the way workers' comp claims are. It opens the door to direct negligence litigation with uncapped damages. And because it flows from the structure of the relationship rather than from any specific act, the best protection is ensuring the sub has robust liability insurance in place — so that if ELL exposure materializes, there is a policy to respond to it.

SB 426: Oregon's new joint wage liability (effective January 1, 2026)

Senate Bill 426 is the newest layer of Oregon's subcontractor liability framework, and it is the one that most GCs are still absorbing. Effective January 1, 2026, Oregon makes general contractors jointly liable for unpaid wages owed by any subcontractor at any tier — not just direct subs, but subs of subs.

The provision that makes this particularly significant is what the law prohibits: you cannot contractually shift this liability. Standard indemnification clauses that require subcontractors to hold the GC harmless for wage claims are explicitly invalidated by the statute as applied to SB 426 liability. If your second-tier concrete sub fails to pay their workers prevailing wages on a public project, you are jointly on the hook for those wages, and your contract with your direct sub does not protect you.

The Oregon Bureau of Labor and Industries (BOLI) enforces prevailing wage requirements on public works projects over $50,000. Prevailing wage rates in Oregon are set by BOLI by trade and by region and are updated periodically. A sub who is paying below prevailing wage — whether intentionally or because they miscategorized the work — creates joint liability that flows up to you even if you paid your direct sub correctly and on time.

The practical implication: for public works projects in Oregon, compliance verification now has to extend to wage practices, not just insurance and licensing. For most SMB GC teams, that means at minimum requiring certified payroll reports from all subcontractor tiers and having a clear record of what you asked for and when.

The Oregon compliance checklist before work starts

Taken together, these four exposure layers mean that the pre-work compliance gate for Oregon GCs has to cover more ground than a standard COI request. Before any subcontractor begins work on an Oregon job, you need:

  1. Current COI showing active general liability coverage — with limits meeting CCB minimums for the license tier, your company listed as additional insured, and an endorsement confirming additional insured status on the policy (not just checked on the certificate)
  2. Current COI showing active workers' compensation coverage — from a licensed carrier, with the expiration date tracked so you catch renewals before the policy lapses mid-project
  3. Current CCB license number verified against the CCB online database — not just at initial onboarding, but at the start of each project
  4. For public works projects over $50,000: certified payroll compliance confirmation — either direct certified payroll reports or written acknowledgment of prevailing wage obligations, covering all sub-tiers

The fourth item is new as of 2026 and most GC teams do not yet have a workflow for it. The first three have been baseline requirements for years, but the verification step — actually checking that the documents are current rather than assuming they are — is where the process breaks down in practice.

The document management problem at scale

A GC with five active subcontractors on a single project has five COIs to track, five CCB license expirations to monitor, five workers' comp renewal dates to stay ahead of, and — on public work — five certified payroll workflows to manage. Multiply that by multiple concurrent projects and a rotating vendor roster and the manual version of this process becomes unmanageable quickly.

This is the problem Send The Proof is designed to address. Each vendor has a secure upload link — no login required — where they (or their agent directly) submit their COI, license documentation, and any other required proof. The system tracks expiration dates across the entire vendor roster and sends automatic renewal alerts 30 days out, so you are not discovering a lapsed WC policy after an incident. Every submission is timestamped and retained in the vendor's audit record — the kind of documented due diligence that matters when an Oregon agency is asking what you had on file and when.

The first five vendors are free. The paid plan is $29.95 per month — a straightforward trade against the ORS 656.029 double-premium penalty alone, which starts at $1,000 for a first violation and has no cap on daily accruals.

Related: the financial exposure when a lapsed COI meets a jobsite incident, the full COI collection system for GC teams, and the subcontractor compliance checklist.