How Washington Contractors Avoid Insurance Coverage Gaps on Jobsites
Insurance gaps don't announce themselves. A subcontractor steps off a ladder wrong, or fire breaks out in a half-built kitchen, and only then does a contractor discover their policy left an exposure uncovered. In Washington state, where construction activity spans everything from dense urban projects in Seattle to rural custom builds east of the Cascades, the margin for error on coverage is thin. What separates a well-run operation from one that's blindsided by an uncovered loss? Knowing where the gaps appear and closing them before a claim lands.
Why Coverage Gaps Are Common on Washington Jobsites
Most gaps don't come from contractors who ignore insurance. They come from contractors who assume one policy handles everything. The truth is, general contractor insurance across Washington typically refers to a bundle of coverages that work together, but "together" only works if each policy is written to coordinate with the others. A general liability policy that excludes completed operations leaves you exposed the moment a client calls about water damage three months after project close.
The Subcontractor Problem
Subcontractors are one of the most frequent sources of unintended gaps. Many GCs assume that a subcontractor's own policy covers any damage or injury that the sub causes on the jobsite, and they're wrong. That assumption falls apart the moment the sub's policy has lapsed, carries insufficient limits, or excludes the type of work being performed. Washington courts have consistently held GCs liable for incidents caused by uninsured subs, especially on projects where the GC had supervisory control.
The practical fix? Straightforward enough. Collect certificates of insurance before work starts; verify that the sub's policy lists you as an additional insured; and check that the policy period covers the entire duration of the subcontractor's scope. Don't just collect the certificate and file it away without reading the endorsements. A certificate showing active coverage but carrying a completed-operations exclusion still leaves you holding the bag when a post-project claim arrives. You'll notice this mistake most often when the work spans multiple seasons or when claims emerge months later.
Completed Operations and Tail Coverage
Washington's construction defect statute of repose runs six years from completion under RCW 4.16.310. That means a claim can arrive years after your crew has packed up and moved to the next job. Standard occurrence-based general liability policies do cover completed operations, but only if the policy was active at the time of the incident AND the completed-operations coverage wasn't excluded or capped below your contract requirements. Some lower-cost policies quietly cap completed-operations aggregate limits well below the per-project limits your client expects.
Read those limits carefully before binding coverage. The catch is that many contractors skip this step entirely.
The Policies That Work Together to Fill Gaps
No single policy closes every exposure on a Washington jobsite. You need several policies layered so they coordinate rather than conflict.
General Liability vs. Builder's Risk
These two policies are frequently confused, and that confusion creates gaps. General liability covers bodily injury and property damage claims made by third parties, think a visitor who trips over materials or a neighbor whose fence gets damaged by your crew. Builder's risk covers the structure under construction itself: damage from fire, theft, vandalism, or weather. Only carry general liability? Then a fire that destroys the framing you've already completed is an uninsured loss. Builder's risk policies are typically project-specific, so you need a new policy or an endorsement for each new build. Check whether your builder's risk policy covers materials stored off-site; many don't, and theft from a staging area can be an expensive surprise.
Workers' Compensation Requirements in Washington
Washington is one of the few states where most private employers must purchase workers' compensation through the state-run fund, L&I (Labor and Industries), rather than from a private carrier. Sole proprietors and certain LLC members can elect to exclude themselves, but any employee on your payroll must be covered. The risk here isn't always noncompliance with the mandate; it's misclassification. Contractors who classify workers as independent contractors to avoid L&I premiums face personal liability for medical costs and wage replacement if L&I determines those workers were actually employees. Washington takes misclassification seriously, and audits in the construction sector aren't rare. Make sure your payroll classifications match the actual work being performed on every project.
Practical Steps to Audit and Close Your Coverage Gaps
A coverage review doesn't require an attorney or a long afternoon. It does require a systematic approach.
What to Review Before Each Project
Before your crew steps on a new jobsite, run through this checklist:
Confirm your general liability limits meet the contract's requirements, including any per-project aggregate endorsements your client specified.
Check that your policy covers the specific type of work in scope. Roofing, excavation, and demolition sometimes trigger exclusions on standard GC policies written for lighter commercial work.
Verify all subcontractors have active, conforming certificates with you listed as additional insured.
Confirm a builder's risk policy is in place (whether you're providing it or the owner is) and know exactly what it covers and what it excludes.
Review your commercial auto policy to confirm it covers any vehicles or trailers used to transport materials or equipment to the site.
Running this check at the start of each project takes under an hour; it catches most common gaps before they become claims.
Umbrella Policies as a Gap-Closing Tool
An umbrella or excess liability policy sits above your general liability, commercial auto, and employer's liability limits. On larger Washington projects, where contract minimums frequently reach $2 million to $5 million in aggregate coverage, an umbrella is often the most cost-effective way to meet those thresholds without repricing your underlying policies. Umbrella policies follow the form of the underlying policy, meaning they cover the same incidents in the same way. If your general liability excludes a particular exposure, the umbrella won't cover it either; the umbrella expands your limits but doesn't broaden your coverage. That distinction matters when you're reviewing a contract's insurance schedule and trying to confirm your program satisfies what the client requires.
Conclusion
Coverage gaps on Washington jobsites don't always stem from cutting corners. They often come from misreading what a policy actually covers, trusting a certificate without reading the endorsements, or assuming one policy does the work of several. The contractors who avoid insurance coverage gaps do so by treating coverage as a system, not a checklist item. They review subcontractor certificates; match their policy language to their contract requirements; layer their coverages intentionally; and stay current on Washington-specific rules like L&I obligations and the state's construction defect statute of repose. A few hours of review before each project costs far less than an uninsured claim.
