Prevailing Wage Responsibilities for Washington Contractors at Every Tier

Washington State’s prevailing wage framework is built on a chain of responsibility that runs from the contracting public agency to the general contractor to every subcontractor at every tier. Obligations flow downward through each layer of the contracting hierarchy, and so does exposure. A compliance failure anywhere in the chain can create liability at every level above it.

By the time a general contractor (GC) is on site and crews are working, certain compliance decisions have already been made, or missed. Understanding the full scope of your responsibilities as a contractor, and knowing when each responsibility comes due, is the difference between a smooth project closeout and a retainage dispute or L&I investigation.

Before You Sign: The Three Questions to Ask

Public agencies are required to include prevailing wage information in contract documents, but not all of them do. Omissions happen — sometimes because the agency doesn’t know the project is covered, sometimes because the information was simply left out. When prevailing wage requirements are missing from a contract, the contractor who doesn’t notice has a problem.

Before signing a contract for any project, ask three questions:

1. Is this project funded by public dollars? Tax revenue, government grants, bond proceeds, federal or state appropriations — any public funding stream is enough.

   
   

2. Was this project solicited by a municipality or agency? Cities, counties, school districts, port districts, public hospital districts, and similar entities are all municipalities under Washington State law.

   
   

3. Is this a "turnkey" project? A turnkey project is one where a private developer builds a building and a public agency has already agreed to lease, rent, or buy at least half of it before construction starts. The developer builds it and hands over the keys. Because public money is paying for the space, prevailing wage applies to the construction, even though every contract on the job is between private parties. The 50% threshold matters. Below that, this test doesn’t apply.

If the answer to any of these questions is yes, then prevailing wage likely applies. If the contract documents don’t reflect that, the right move is to go back to the soliciting party before work begins and ask for the contract to be revised. Prevailing wage applies because of how a project is funded, not because the contract says so. If the language is missing and you build the job anyway, the wages are still owed, and you will be in the middle of the fight over who pays them.

Responsible Bidder Requirements: Yours and Your Subs'

Every contractor working on a Washington State public works project must meet the responsible bidder criteria set out in RCW 39.04.350 and RCW 39.06.020. The agency verifies this for the GC before award. The GC is then responsible for verifying it for every subcontractor (“sub”) they hire, and in turn, those subs are responsible for verifying it for every sub-tier below them, and so on.

The criteria are the same at every tier:

• Valid Unified Business Identification (UBI) number, registered with Washington State

• Current contractor registration and any applicable specialty licenses for the work being performed

• No current debarment from public works bidding

• Completed L&I Public Works and Prevailing Wage Law training, or an applicable exemption

• Current workers' compensation coverage

L&I’s Verify a Contractor tool pulls all of this together in one place: registration status, licenses, workers' comp, training completion, and any strikes or debarments. Making this check part of every subcontractor onboarding process is the clearest protection against inheriting a subcontractor’s compliance problems. A sub who doesn’t meet responsible bidder criteria should not be on a public works project. Discovering that after they’ve been working is a harder conversation than verifying them before they start.

The Pre-Project Compliance Checklist

Before work begins, every contractor on a Washington State public works project should be able to answer the following questions without hesitation:

• What are the scopes of work and the trades required to complete it?

• What are the applicable prevailing wage rates for each trade?

• What is the exact classification of work as it will be performed?

• What is the county and effective date for the project?

• Are there apprentice utilization requirements, and what are the journey-to-apprentice ratio requirements for each trade?

• What are the overtime and double-time requirements for each classification of worker?

• What postings are required at the job site?

This isn’t an exhaustive list; it’s the floor. A contractor who can’t answer these questions before the first crew hits the ground is setting up certified payroll errors, classification problems, and potential violations that are considerably harder to fix retroactively than proactively.

Intents: File Immediately on Award

The statement of intent to pay prevailing wages must be filed as soon as the project is awarded: for the prime contractor, upon contract award; for subcontractors, upon award of their subcontract. Don’t wait for construction to begin.

The intent must accurately identify the prevailing wage rates and trades to be employed, the county where work will be performed, and the correct hiring contractor relationship. Any error in the hiring contractor field (i.e. a sub listing the prime instead of the first-tier who actually hired them) creates a hierarchy problem that can affect retainage release at project end. That problem is easy to fix the day the intent is filed, and considerably less easy six months later.

Keep in mind: payment cannot be released by the agency until all intents are filed and approved. That dependency runs through the entire project. If a lower-tier sub’s intent is wrong or missing, it can delay payment to the prime.

Certified Payroll: Weekly, Retained, Complete

Certified payroll records are created weekly and must be filed to the PWIA portal at least once a month. The submission has to cover every week within the project dates, including weeks when no work was performed. A no-work record for a silent week is still a required submission.

And required records don’t stop at the payroll form itself. Contractors are required to retain the following records for at least three years after project acceptance:

• Certified payroll records for every week of the project

• 4x10 work agreements, if applicable

• Fringe benefit information

• Employee authorizations for deductions

• Any other documentation supporting the records as submitted

That’s three years after acceptance, not after completion, not after the contractor’s last day on site. Final acceptance by the agency starts the clock, and that date can be well after the last nail was driven.

Flow-Down: Your Obligation Doesn't Stop at Your Subcontract

Every GC is required to include prevailing wage obligations in each subcontract they issue, along with a flow-down clause requiring those subs to pass the same obligations to every tier below them. This isn’t optional language; it’s the mechanism by which the entire compliance chain is maintained.

In practice, flow-down means that a fourth-tier subcontractor on a project is bound by the same prevailing wage requirements as the prime because those requirements were written into every subcontract from the prime down. A contractor who issues subcontracts without prevailing wage language has broken the chain, and the liability for what happens below them is harder to manage as a result.

Flow-down applies to the wage requirements themselves, the responsible bidder verification obligation, the intent and affidavit filing requirements, and the certified payroll maintenance obligation. If your subcontract doesn't include it, add it. And if you aren't certain what your current subcontracts say, or whether your subs are passing the same language on to their own subs, let's talk. Finding a broken link in the chain before award costs a conversation. Finding it at closeout costs considerably more.

Contractor Retainage: Optional, But Regulated

Public agencies are required to withhold retainage. Contractors are not. But if a contractor chooses to withhold retainage from a subcontractor on a public works project, RCW 60.28.011 governs how it works.

A contractor may withhold no more than 5% of the money earned by any subcontractor, sub-subcontractor, or supplier. That is the same cap the public agency is held to on the prime contract. Whenever a contractor holds a subcontractor’s money this way, the contractor owes that subcontractor interest at the same rate the contractor is receiving on its own reserved funds. Retainage held from a sub is not free money to sit on. Whatever the public agency’s reserved funds are earning flows down.

A subcontractor also has a way out. At any point before the project is formally accepted, a sub can ask the contractor to post a bond covering that sub’s portion of the retainage. The contractor has 30 days to provide it and can only refuse for good cause, if the bond isn’t commercially available, or if the sub won’t pay its share of the premium. Once a public agency accepts a bond in lieu of retainage from the contractor, the contractor has to accept the same kind of bond from its own subs and release their retained funds within 30 days.

The timing on the public agency side sets the outer limit for everyone below it. Sixty days after all contract work is complete, the public agency must release the retainage in full. (The statute uses the term "public body" for what this article calls a public agency.) That release is subject to Chapter 39.12 RCW, which is where the intents and affidavits come back around. If a fourth-tier sub never filed an affidavit, nobody’s retainage moves.

One caution. RCW 60.30.010 sets out a different retainage regime, with a 15-day response window and 1% monthly interest. That chapter covers private construction and expressly does not apply to public improvement contracts. If your office runs both, don’t carry the private rules onto a public job.

FAQ: GC and Subcontractor Prevailing Wage Responsibilities in Washington

What should a GC do if prevailing wage information is missing from a contract? Ask three questions: Is the project funded by public dollars? Was it solicited by a municipality? Is it a turnkey project? If any answer is yes, request that the contract be revised to include prevailing wage requirements before work begins.

What responsible bidder requirements apply to subcontractors on Washington public works projects? The same criteria that apply to the GC: valid UBI, current contractor registration and applicable specialty licenses, no debarment, L&I prevailing wage training completion, and current workers’ compensation. GCs are responsible for verifying these criteria for every sub they hire, and those subs must verify them for their own lower-tier contractors.

When must a statement of intent be filed in Washington? Immediately upon award. For the prime contractor, upon contract award. For subcontractors, upon award of their subcontract. Filing should not wait for construction to begin.

How long must certified payroll records be retained on a Washington prevailing wage project? At least three years after the date of final acceptance of the project by the contracting agency. Records include certified payroll forms, 4x10 agreements, fringe benefit documentation, and employee deduction authorizations.

What is a prevailing wage flow-down clause? A flow-down clause is contract language requiring the receiving subcontractor to pass prevailing wage obligations, including the requirement to include the same language, to every subcontractor they hire in turn. It is how the compliance chain is maintained from the prime contract to every tier below.

Can a contractor withhold retainage from a subcontractor on a Washington public works project? Yes, up to 5% of the money earned by that subcontractor. The contractor must pay interest to the subcontractor at the same rate the contractor is receiving on its own reserved funds. A subcontractor may also ask the contractor to post a bond covering the subcontractor’s portion of retainage, and the contractor must provide it within 30 days absent good cause. None of this is complicated on its own. It gets complicated when a project carries forty subcontracts across four tiers and nobody has checked whether the chain actually holds. If you have questions about where your obligations start and stop, or you want a second set of eyes on your flow-down language before the next award, let’s talk.

[Disclaimer: This article is intended for general informational purposes only and does not constitute legal advice. Because the application of chapter 39.12 RCW, RCW 39.04.350, RCW 39.06.020, and RCW 60.28.011 depends on the specific facts and circumstances of each project, including the terms of the contract and any additional requirements imposed by the contracting agency, contractors should consult qualified legal counsel regarding their obligations under Washington law.]