Washington State Pay Transparency Law: Employer Compliance Guide

What Changed — and Why Washington Employers Should Pay Attention

Picture this: your recruiting team posts a software engineering role on your careers page, LinkedIn, and a niche tech board. Three days later, HR receives a candidate inquiry pointing out that none of the postings include a salary range. Under Washington's pay transparency rules, that omission is not just a missed best practice — it is a potential statutory violation, and the same role listed on multiple platforms can multiply your exposure.

Washington has been one of the more demanding US states on this front. Its Equal Pay and Opportunities Act (EPOA), codified in RCW 49.58, requires employers meeting a certain size threshold to include a wage scale or salary range, a general description of benefits, and other compensation in every posting for a position to be filled in Washington. That combination — range plus benefits — goes further than most state disclosure laws, which typically require only a salary range.

This guide covers what Washington's washington pay transparency law actually requires, who it applies to, what "general description of benefits" means in practice, and what you should have in place before your next posting goes live. Requirements can and do change — confirm the current rule text in RCW 49.58 and with your employment counsel before treating anything here as a final compliance determination.

Who the Washington Pay Transparency Law Covers

Washington's EPOA applies to employers with a threshold number of employees who are recruiting for positions that will be performed, at least in part, in Washington State — including fully remote roles where the worker would be based in Washington. The law was amended in 2023 to extend the posting requirement; confirm the current employee-count threshold directly with the Washington State Department of Labor & Industries (L&I) or against the current RCW 49.58 text, as the threshold changed with that amendment.

A few practical points employers frequently get wrong:

Out-of-state employers recruiting remote workers are covered. If you are headquartered in Texas but posting a remote role open to Washington residents, your posting falls under the EPOA for the Washington-based applicants who will see it. Many employers discovered this exposure only after receiving enforcement inquiries.

Third-party postings count. If you engage a staffing agency or use a job board, the posting obligation does not disappear. Employers remain responsible for ensuring that postings made on their behalf include the required disclosures.

The rule applies to promotions as well as external hires. Washington requires employers to notify current employees when an opportunity is available, which has implications for internal mobility processes, not only external recruiting.

What Must Be in Every Covered Job Posting

Washington's posting requirement has three disclosure components. All three must appear in the posting itself — it is not sufficient to say "compensation discussed during the interview process."

1. Wage scale or salary range. The posting must state the range the employer reasonably expects to pay for the position — typically the minimum and maximum of the band established for that role. If your organization does not have a formal pay structure, you will need to establish one before you can post compliantly. A range must reflect a genuine good-faith estimate; a range spanning from minimum wage to $500,000 for a mid-level coordinator role would not meet the spirit of the requirement.

2. A general description of benefits. This is the element that distinguishes Washington from most other state laws. Employers must describe the benefits available for the position — health insurance, retirement plans, paid time off, and similar items. The statute does not require an exhaustive schedule of benefits; a general description is the standard. In practice, many employers include a brief bullet list (e.g., medical/dental/vision, 401(k) with employer match, paid vacation, parental leave).

3. Other compensation. This covers additional forms of pay — bonuses, equity, commissions, shift differentials, and similar items that are part of the total compensation picture for the role.

If your organization's pay ranges are defined at the job-band level — where each level in a job family has a documented minimum, midpoint, and maximum — producing the required range for any posting becomes a matter of looking up the band rather than improvising a number. Organizations without a band structure typically take longer to post compliantly and are more likely to post ranges that are inconsistent across similar roles, which creates its own compliance risk. Our complete guide to building a job band structure walks through how to build that foundation if you are starting from scratch.

Penalties and Enforcement Under the EPOA

Washington's L&I enforces the EPOA. Employees and applicants have the right to file complaints, and the department can investigate and assess civil penalties for violations. The specific penalty amounts per violation are not included in the available data; confirm the current penalty schedule in RCW 49.58 or directly with L&I before making any compliance-cost estimates.

What the statute structure does make clear:

• Violations are assessed per posting, not per employer per year. A single role posted across multiple platforms without required disclosures can generate multiple violations.

• Retaliation against employees who exercise their rights under the EPOA — including asking about pay ranges — is separately prohibited and carries its own remedies.

• Applicants who were denied required salary range information upon request have a private right of action, which means exposure is not limited to administrative penalties.

The enforcement pattern in Washington mirrors what other states have found: early enforcement tends to focus on employers who have made no effort to comply, but the bar for "effort" rises as the law matures and industry awareness increases. Operating without a documented pay structure today carries more risk than it did at the law's original enactment.

Pay transparency requirements can change — effective dates, thresholds, and penalty structures are amended by the legislature. Always confirm current requirements against RCW 49.58 or with your Washington employment counsel before publishing a job posting.

Building Compliant Postings: A Practical Approach

Compliance here is ultimately a data problem: you need a defensible, documented pay range for every role before the posting goes live. Organizations that manage compensation in disconnected spreadsheets — a common state for companies under 250 employees — often find that they cannot produce a compliant range quickly because no one has formally set one.

A practical sequence:

Step 1 — Establish or confirm your job bands. For each role you anticipate posting, you need a defined minimum and maximum. If you are benchmarking against Bureau of Labor Statistics Occupational Employment and Wage Statistics (OEWS) data, note that OEWS covers wage estimates for approximately 830 occupations across roughly 530 geographic areas, based on a sample of about 1.1 million establishments — it is the public-domain benchmark source and a defensible anchor for most roles (U.S. Bureau of Labor Statistics, 2025). Map your role to the relevant Standard Occupational Classification (SOC) code and use the percentile range appropriate to your market position.

Step 2 — Document the benefits package. Draft a standard benefits description block you can attach or adapt for each posting. This does not need to be a full HR handbook excerpt — two to four lines covering the major categories is typically sufficient.

Step 3 — Establish a review checkpoint before posting. Add a pre-publish checklist step: does this draft posting include (a) the salary range, (b) the benefits description, and (c) any other material compensation? That checkpoint catches omissions before they become violations.

Step 4 — Extend the process to third-party channels. Send the compliant posting template — including compensation disclosures — to every platform and agency that will distribute it. Document when and where the compliant version was sent.

If you are also posting in Colorado or Illinois, note that their disclosure requirements overlap in some areas but differ in others — our guides on Washington's neighbor state Colorado and Illinois pay transparency cover those differences. For a side-by-side view of which states are active and what each requires, the pay transparency laws by state — 2026 overview is the fastest reference.

Washington in the Broader US Pay Transparency Landscape

Washington was an early mover among US states. The subsequent wave of legislation — now spanning a substantial and growing number of jurisdictions — has broadly followed its model of requiring a range rather than simply permitting pay discussion. State counts vary by methodology and continue to change as new legislation passes: one commonly cited figure places the count at 18 states plus Washington, D.C. with active statewide laws as of 2026 (Rippling, 2026); another methodology counts 25 jurisdictions including localities as of late 2025 (Brightmine, 2025). The point is directional: multi-state employers are increasingly managing pay transparency obligations across a patchwork of rules, and Washington is one of the more detailed ones.

The common thread across all of them is that compliance begins with having documented pay ranges. An employer who has invested in a formal band structure — minimum, midpoint, maximum for each level in each job family — can answer a Washington posting requirement, a California audit request, and an employee pay-equity inquiry from the same source of truth. An employer managing compensation informally across spreadsheets has to reconstruct an answer for each situation, under time pressure, often inconsistently.

Our pay transparency compliance hub tracks requirements across active jurisdictions as they evolve.

Getting Your Postings Ready

Washington's law has been in effect long enough that "we are still figuring out our process" is a thin defense. The practical bar is clear: know your range, document your benefits, put both in the posting before it goes live.

If your organization does not yet have a formal pay band structure — or if your bands exist in a spreadsheet that no one fully trusts — that is the upstream problem to solve. Once bands are in place, producing a compliant Washington posting is a five-minute task. Without them, every posting is an improvisation with compliance risk attached.

The Pay Transparency Job Posting Kit includes a ready-to-use posting template covering Washington's three-part disclosure requirement, along with templates calibrated to the other seven US states in our pay-transparency generator (California, New York, Colorado, Illinois, Massachusetts, Minnesota, and Rhode Island). Download the kit to start from a compliant draft rather than a blank page.

For a complete picture of how to structure the underlying pay bands that make every posting defensible, start with the job band structure guide. ```