Washington · Compliance · Updated April 2026

EPOA: salary range required in every job posting.

Washington's Equal Pay and Opportunities Act (RCW 49.58) requires employers with 15+ employees to disclose the wage scale or salary range, plus a general description of benefits, in every job posting. The 2024 expansion (SHB 1905) extended coverage to all forms of postings including third-party aggregators. The 2025 amendment (SB 5408, effective July 27, 2025) added a 5-day cure window for non-compliant postings (through July 27, 2027 only), but statutory damages of $100-$5,000 per violation still apply for un-cured violations. Salary history bans also apply (cannot ask, but can confirm voluntarily disclosed).

Coverage
15+ employees
Cure window
5 days (until 2027)
Damages
$100-$5,000
Active

EPOA Job Posting Compliance

Validates job postings for required salary range and benefits description before publish. Tracks third-party aggregator distribution. Surfaces cure-window opportunities when violations identified.

Block posting without salary range
Track aggregator distribution
Surface cure-window opportunity
Always running

What those rules do as job postings are created.

The hero card configuration: Block on missing range, Flag on aggregator visibility, Critical on cure window.

Block · posting without salary range

When a Washington job posting (or one targeting WA workers) lacks a wage scale/salary range or benefits description, the publish blocks. Required content must be specific (not "competitive") and include the actual range, not a single number.

Flag · aggregator distribution tracking

When a posting distributes to third-party aggregators (Indeed, LinkedIn, etc.), Teambridge tracks where it appears. SB 5408's safe harbor for aggregators applies if the original posting was compliant.

Critical · cure-window opportunity

When a non-compliant posting is identified, Teambridge surfaces the 5-day cure window (available through July 27, 2027). Curing within the window prevents penalties; the cure must be complete and timely.

Skip the configuration

Deploy EPOA in your Teambridge.

Tell us about your Washington workforce and recruiting. We'll spin up EPOA validation and 27 other Washington policies in a sandbox tenant.

Or book a 30-min walkthrough. We respond within 4 business hours.

The rule, plainly stated

Salary range, benefits description, in every posting.

Washington's pay-transparency rule was significantly tightened by SHB 1905 (2024) and again by SB 5408 (2025). The trajectory is clear: stricter content requirements, broader posting coverage, with a temporary cure window for transition.

RCW 49.58.110; SHB 1905 (2024); SB 5408 (2025): An employer with fifteen or more employees shall disclose in each posting for each job opening the wage scale or salary range, and a general description of all of the benefits and other compensation to be offered to the hired applicant. A posting includes any solicitation intended to recruit job applicants for a specific available position.

Coverage and content requirements

Employers with 15+ employees nationwide must include in every job posting: (1) the wage scale or salary range (an actual range, not a single number or 'competitive' language), (2) a general description of all benefits offered (health, retirement, paid leave, bonuses, etc.). The posting requirement applies to internal and external postings, postings on third-party aggregators (Indeed, LinkedIn), and remote roles where Washington applicants might apply.

SHB 1905 (2024) expansion

The 2024 expansion clarified that 'posting' includes any solicitation to recruit, however published. This caught third-party aggregator listings, social media recruiting, and even informal solicitations. The expansion also added the private right of action for affected applicants, with statutory damages.

On autopilot

Teambridge gates job postings before they go live.

EPOA compliance is structurally simple — but the breadth of 'posting' (catching third-party aggregators) means employers need systematic discipline.

01 · Posting validation pre-publish

Range + benefits required.

When a job posting is created, Teambridge validates it includes a specific wage scale/salary range (not 'competitive') and a benefits description. Missing or non-specific content blocks the publish.

02 · Aggregator distribution tracking

Where the posting appears.

When the posting distributes to third-party aggregators, Teambridge tracks the destinations. If an aggregator strips required content, the safe-harbor analysis runs — original posting compliance is what determines employer liability.

03 · Cure-window response

5-day correction.

When a non-compliant posting is flagged (via complaint, audit, or internal scan), Teambridge surfaces the cure-window deadline (through July 27, 2027). Operators can correct the posting within 5 days to extinguish liability.

04 · Statutory damages exposure

Per-violation tracking.

Each non-compliant posting represents a separate violation. Pattern violations across multiple postings aggregate damages. Real-time exposure dashboards help operators understand cumulative liability.

Free · No commitment

Still evaluating? Get a free Washington compliance audit.

Send us your existing Washington scheduling and pay configuration. Our compliance team returns a written audit within 5 business days — every Washington-specific exposure ranked by risk and back-pay liability.

FAQ

People also ask.

What does Washington EPOA require?
Employers with 15+ employees must include wage scale/salary range and a general description of benefits in every job posting. The range must be specific (not 'competitive' or 'DOE'). Coverage extends to third-party aggregators.
What changed with SB 5408 in 2025?
Three changes effective July 27, 2025: (1) 5-day cure window for non-compliant postings (sunsets July 27, 2027), (2) third-party aggregator safe harbor if original posting was compliant, (3) clarified $100-$5,000 statutory damages per violation.
What if I post on Indeed or LinkedIn?
If your original posting on the platform was compliant and the aggregator/platform incorrectly displayed or stripped content, the safe harbor (post-SB 5408) protects you. If the original posting was non-compliant, you're liable regardless of where it appears.
Do I have to include benefits?
Yes — a general description of all benefits offered. Specifics like 'medical, dental, vision insurance; 401(k) with match; 15 days PTO; remote work' are typical. Vague language like 'competitive benefits' isn't sufficient.
Are remote roles covered?
If a Washington-based applicant could be hired (i.e., the role is open to WA residents), EPOA applies. Remote-friendly postings that exclude WA can avoid coverage but must clearly exclude — typically as 'not available in: WA'.
What about salary history?
RCW 49.58.100 separately prohibits asking applicants about salary history. You can ask about salary expectations and confirm voluntarily disclosed history but cannot demand or research it. Violations have their own penalty structure.
How does Teambridge handle this?
Job postings validate against EPOA requirements before publish. Aggregator distribution tracks where postings appear. Non-compliant postings surface with cure-window deadlines. Statutory damages exposure aggregates across multiple postings for visibility.