Washington Pay Transparency. Single-State Compliance.
Cascade Logistics. Seattle. Monday, 8:47 AM PT.
An interactive scenario about an L&I complaint over a missing posting range, a warehouse lead disciplined for discussing pay, and Washington's quiet rule that "market rate" is not a defence under the Equal Pay and Opportunities Act.
One state. Four overlapping RCW provisions. One day to make three decisions.
VP of People at Cascade Logistics. A 320-person logistics company headquartered in Seattle. Every employee is in Washington.
Your pay bands have not been updated in 18 months. This morning, the Washington Department of Labor & Industries opened a compliance review of your latest annual pay data report. Within the hour, a senior engineer will email you invoking RCW 49.58.110.
This is a choose-your-own-adventure scenario. You will face three real decisions that a VP of People encounters when Washington's Department of Labor & Industries comes knocking, and your choices shape how the story unfolds.
The 4 Stakeholder Bars (top right)
Each bar starts at 50%. Your decisions shift them. There’s no perfect answer. only trade-offs.
Washington Stack
Washington has the strictest pay transparency framework in the country. RCW 49.58.110, the Equal Pay Act, the Pay Data Report, and the salary-history ban work together. Your decisions must account for all four.
Legal References
Law references appear throughout. Click them to read the relevant statute.
RCW 49.58.110. Pay Range in Postings.
Employers with 15+ employees must include in every job posting (1) the wage scale or salary range, AND (2) a general description of all benefits and other compensation offered. The wage scale must be posted, not provided on request. Any current employee may also request the wage scale for their current position.
RCW 49.58.020. Equal Pay for Similarly Employed Workers.
The standard is "similarly employed", broader than the federal "equal work" test. "Market rate" is not a defence. Permissible justifications: a documented seniority or merit system, education or training, regional cost-of-labor variation, or a bona fide job-related factor consistent with business necessity. Negotiation outcome and prior salary fail.
RCW 49.58.030. Pay Discussion Protection.
An employer cannot prohibit, retaliate against, or discipline an employee for inquiring about, disclosing, comparing, or discussing wages with another employee. A "performance" write-up issued the day after a pay-discussion incident is presumed retaliatory. Burden shifts to the employer.
RCW 49.58.100. Salary History Ban.
Employers cannot seek the wage or salary history of an applicant. They cannot rely on it as a factor in setting compensation, even if the applicant volunteers it. The wage scale, on the other hand, must be provided to the applicant on request after an initial offer.
You're halfway through your first coffee when Legal forwards you an email marked URGENT. RESPONSE REQUIRED.
"Dear Ms. Reyes, This Department has received a complaint filed by an applicant alleging that Cascade Logistics posted job listings for positions in Washington without the wage scale or general description of benefits required by RCW 49.58.110. Our public-records review of your careers page confirms that at least fourteen (14) current listings lack the required pay scale and benefits disclosure."
"Separately, the same complaint references retaliation against an internal employee for discussing wages, in possible violation of RCW 49.58.030. We are opening a parallel inquiry on that allegation."
"Under RCW 49.58.060, each violation may carry actual damages or statutory damages of $5,000 per affected worker, whichever is greater, plus attorney fees. Please provide a written response within ten (10) business days, including (1) your remediation plan for the posting violations, and (2) documentation of the wage-discussion incident referenced in the complaint."
"Sincerely, Investigator J. Tanaka, Employment Standards Section, Washington Department of Labor & Industries"
Before you can finish reading, Jordan Reeves, Head of Recruiting, calls from down the hall.
"Diana, I just saw L&I letter. Fourteen postings. I counted them. They're right. None of them have a pay scale."
You "How did fourteen postings go live without ranges?"
Jordan "Because nobody built a check into the ATS. The template defaults to 'competitive compensation.' Most hiring managers don't override it."
You "And our pay bands? They're 18 months old."
Jordan "Worse. Our L5 engineering band on file says $95K to $125K. We hired three people last quarter at $130K to $142K because the market moved. The posted range, if we put one up, doesn't match what we've actually been paying."
You "So if we publish the band on the postings, we're publishing a number that contradicts our offer letters."
Jordan "And L&I is asking for documentation of the bona fide factors we used to set comp in the affected job category. Plus they want a written response on the retaliation allegation. That part scares me more than the postings. We have ten business days. What do we tell them?"
L&I has identified fourteen non-compliant job postings under RCW 49.58.110, plus a parallel inquiry into a wage-discussion retaliation allegation under RCW 49.58.030. Each posting violation may carry $5,000 in statutory damages or actual damages, whichever is greater, plus attorney fees. The retaliation claim is potentially worse: RCW 49.58.020 exposure stacks on top, and a presumption of retaliation kicks in if discipline followed a wage-discussion incident.
You have ten business days to respond. Your pay bands are 18 months stale, and whatever numbers you commit to will ripple through the entire company.
How do you respond?
"Update every pay band to current market and put a compliant pay scale on every active posting within 48 hours. Then we respond to L&I with a corrective action plan AND a commitment to a privileged pay equity audit run through outside counsel."
Jordan "The audit is going to show that six current employees are below the new minimum of their own band. And probably that the retaliation allegation will stick."
You "I know. We find it before L&I does. Privileged audit, then remediation. We choose the order."
By Friday, the updated postings are live. Your response to L&I includes a corrective action plan, a timeline, and a confidential commitment to a privileged pay equity audit. Senior Deputy Director Alvarez's office acknowledges receipt and notes that the voluntary audit will be considered in any further enforcement evaluation.
RCW 49.58.110 penalties are per-employee, per-posting. Proactive remediation is a mitigating factor in L&I enforcement. Crucially, committing to a privileged pay equity audit run through outside counsel does two things: it surfaces the RCW 49.58.020 exposure before a plaintiff's attorney does, and it creates an attorney-client privileged process that, properly run, protects the working papers from civil discovery while preserving your obligation to remediate.
"Fix the 14 postings. Respond to L&I addressing exactly the posting violation. The pay gap finding is a separate matter we'll evaluate internally."
Jordan "What if L&I asks for the bona fide factor documentation? They specifically requested it in the letter."
You "We send what we have. We don't manufacture documentation we don't have."
Your response addresses the 14 postings. Senior Deputy Director Alvarez's office writes back: "Your response is silent on the Pay Data Report disparity finding and on the bona fide factor documentation requested in our original correspondence. Please advise within ten days whether Cascade Logistics intends to provide this documentation, or whether we should proceed under our independent investigative authority."
Responding only to what was asked is technically permissible. But L&I asked for two things: the posting remediation AND bona fide factor documentation under RCW 49.58.020. Answering only the easy half signals to the regulator that the harder half is the part you cannot defend. The follow-up letter is worse than the original because now you have demonstrated awareness of the gap without willingness to address it.
"Ask outside counsel to request a 30-day extension. We need time to assess the full exposure before we commit to a remediation plan."
Jordan "And the 14 postings that are live right now without a pay scale?"
You "They stay up while we figure out the right numbers. I don't want to post ranges we'll have to change in two weeks."
Senior Deputy Director Alvarez's office denies the extension request. Response: "The violations identified are ongoing. Each day a non-compliant posting remains active constitutes a continuing violation under RCW 49.58.110. The Department is also notifying you that, pursuant to our authority under Government Code section 12930, we are escalating Cascade Logistics's file to the formal investigative track."
Meanwhile, a candidate screenshots one of the still-live postings. LinkedIn post: "Cascade Logistics is under L&I investigation for missing pay scales. And the postings are STILL up." 800 likes and climbing. By midday, three named class-action firms have posted advertisements targeting current Cascade Logistics employees in Seattle.
Unlike some regulations that freeze penalties once you acknowledge the issue, RCW 49.58.110 treats each day a non-compliant posting remains live as a continuing violation. Requesting an extension while the postings stay up does not pause the clock. It runs it. Worse, L&I has discretion to escalate to formal investigation under RCW 49.58.060. Once that happens, the timeline is no longer yours to manage. What you are really delaying is not compliance. It is confronting the pay band problem underneath.
You've responded to L&I, or at least started to. While you were drafting, this landed in your inbox from Lauren Mitchell, Senior Engineer.
"Hi Diana, Under Washington RCW 49.58.110, I'm formally requesting the pay scale for my current position (Senior Software Engineer, L5). I understand the company is required to provide this upon request. Thank you."
You pull up the compensation file for Senior Software Engineers (L5) in Seattle:
| Employee | Title | Years | Rating | Salary |
|---|---|---|---|---|
| Lauren Mitchell | Sr. Software Engineer | 4.5 | Exceeds | $118,400 |
| Brian Kowalski | Sr. Software Engineer | 3.5 | Meets | $142,000 |
| Gap | −16.6% | |||
Same title. Same level. She has a year more experience and better ratings. He was hired during the Q3 2024 talent crunch at a 20% market premium. Everyone knew it was a market adjustment. The question is whether "the market" is a valid explanation.
Under Washington's Equal Pay and Opportunities Act, it's not.
Cascade Logistics's legal team has listed three reasons for the $23,600 gap between Lauren and Brian. Under Washington's Equal Pay and Opportunities Act, which of these can legally justify a pay difference?
Click each to mark it LEGAL or ILLEGAL, then submit.
0 of 3 marked
"Thank you for the call, Diana. I'll be direct."
She shares her screen. On it: her last three performance reviews, her offer letter, and the text of RCW 49.58.110.
"Two weeks ago, a recruiter from Stripe told me they'd start me at $145K for the same role. I wasn't looking, but I ran the numbers. That's when I started asking questions internally."
"I can't confirm exact numbers, but based on conversations, I believe I'm significantly below at least one male colleague at the same level. He was hired after me. His ratings are lower."
"Under RCW 49.58.110, I have the right to request the pay scale for my position. I'm making that request formally."
Lauren has invoked RCW 49.58.110. Washington law requires you to provide the pay scale for her position. But your L5 band is 18 months old and doesn't reflect the premiums you paid during the talent crunch. Whatever number you share will either confirm her suspicion or create a new problem.
"Lauren, I'm going to update our L5 band to reflect current market rates. I'll have the updated pay scale to you by end of week. And I'm going to be straight with you. I think you're right that there's a gap worth looking into."
Lauren "I appreciate that. But Diana, when I get that pay scale and see where I sit versus where Brian sits, we both know what the next conversation is going to be."
You "I know."
Lauren "I don't want to leave Cascade Logistics. I want Cascade Logistics to be the kind of company that fixes this without me having to hire a lawyer."
She pauses.
Lauren "But I will hire one if I have to."
RCW 49.58.110 requires employers to provide the pay scale for the position. Sharing an outdated band that doesn't match what you're actually paying creates discoverable evidence of a broken system. Updating first is more work.but it's defensible work.
"Lauren, here's the L5 pay scale: $95,000 to $125,000."
A pause.
Lauren "The max is $125K?"
You "That's the current band on file, yes."
Lauren "Then how is someone at the same level making more than $125K? Because I know they are. Either the band is wrong, or someone is being paid outside the system. Both of those are problems."
She's right. Brian's $142K blows through the top of the band. You've just given Lauren proof that Cascade Logistics's compensation framework is broken.or selectively applied.
Sharing a pay scale that doesn't match reality creates worse evidence than sharing nothing. If Lauren's lawyer later discovers Brian is paid $17K above the band maximum, the outdated scale becomes Exhibit A: proof that the company doesn't follow its own rules.
"Lauren, I want to make sure I give you accurate information. Let me pull the data together properly. Can I get back to you in two weeks?"
Lauren "Two weeks for a number you should already have?"
She's polite about it. But you can hear the Stripe offer ticking in the background.
Lauren "I'll wait two weeks. But Diana.the fact that it takes two weeks to tell me the pay range for my own job title tells me something about how this company thinks about pay. And it's not great."
She accepts Stripe's offer eleven days later. She doesn't file a complaint. She doesn't need to.she just leaves. And she tells the other three women on the engineering team why.
Under WashingtonWashington’s Equal Pay Actrsquo;s Equal Pay and Opportunities Act, Lauren had the right to know the pay scale for her position. Taking two weeks to produce a number you should already have signals that pay data isn’t managed. which is exactly the conclusion she drew. The compliance cost was +1. The real cost was losing a top-performing engineer to a competitor who publishes ranges publicly. Under RCW 49.58.110, maintaining current pay scales isn’t optional. it’s a recordkeeping requirement.
Tom Brennan has modeled three scenarios against Cascade Logistics's Washington exposure. Click each card to see the full breakdown.
Under RCW 49.58.020, "market rate" is explicitly not a defence. If Lauren files, back pay plus equal liquidated damages is the floor, not the ceiling. And the RCW 49.58.110 posting violations remain open.
RCW 49.58.110 posting fix clears the immediate L&I finding. The privileged audit surfaces and remediates RCW 49.58.020 exposure before a plaintiff's attorney does. L&I enforcement priorities give weight to voluntary remediation in mitigation.
A class action attorney has already tagged Cascade Logistics employees in LinkedIn posts about Washington pay equity rights. Lauren has spoken to an employment lawyer. The RCW 49.58.110 posting violations are public record. Any applicant can see them. So can L&I.
Before the CFO meeting, reflect. There's no right answer.but where you stand shapes how you lead. Click on the grid to place yourself.
Tom Brennan, the CFO, has run the numbers.
Brennan "If we update every pay band to current market and level up everyone who's below the new minimum, that's $2.1 million annually. That's 1.8% of revenue."
"If we adjust only the people who've formally complained. Lauren today, maybe two or three more. That's $280K. A fraction."
"I know which number the board will prefer. And I'm guessing you're about to tell me why the smaller number is actually the more expensive one."
You "Lauren alone: if she files under the Washington Equal Pay and Opportunities Act, we're looking at the salary differential times every year she's been underpaid.that's roughly $94K in back pay. Plus liquidated damages equal to that amount. Plus her attorney's fees. And 'market rate' is explicitly not a defense in Washington."
Brennan Long pause. "How many more Laurens are there?"
You "I don't know yet. That's the problem."
He looks at the spreadsheet again. "Present your options at the leadership meeting tomorrow."
Brennan wants targeted fixes. $280K. Your General Counsel just told you a class action attorney has been advertising on LinkedIn, tagging Cascade Logistics employees in posts about Washington pay equity rights. Three more employees have filed RCW 49.58.110 pay scale requests this week.
The CEO is in the room. She'll back whoever makes the stronger case.
"The full audit will cost us $2.1 million in remediation, phased over twelve months. Here's what it buys: a defensible position if L&I investigates our Washington pay data report. A response to the class action attorney circling our employees. And a story we can tell candidates.we fixed it before anyone made us."
Brennan "I don't love the number. But I like the alternative less. The last company L&I went after settled for $15 million."
The CEO nods. "Do the audit. Under privilege. And Diana. I want a timeline on my desk by Friday."
A privileged pay equity audit, conducted under attorney-client privilege with outside counsel, lets you find and fix gaps before they become lawsuits. The key: the audit itself may be protected from discovery. Individual complaint-by-complaint fixes are not.
"Two tracks. Track one: resolve Lauren's case now. Market adjustment, back pay differential, done. Track two: commission a pay equity analysis over Q2. Full remediation starts next comp cycle."
Brennan "When you say 'pay equity analysis'.does that create documents that a plaintiff's attorney can subpoena?"
You "If we run it through outside counsel, it's privileged."
Brennan "Then run it through outside counsel. And make sure Lauren signs something."
Lauren accepts the adjustment. She doesn't sign a release.her lawyer tells her not to. The analysis reveals 11 more employees with similar gaps. You're back in Brennan's office in six months with a bigger number.
Running the pay equity analysis through outside counsel creates attorney-client privilege. meaning the analysis itself may be protected from discovery in litigation. This is smart legal strategy. But privilege protects the document, not the underlying facts. When the analysis reveals 11 more gaps, those employees still have the same rights Lauren exercised under WashingtonWashington’s Equal Pay Actrsquo;s Equal Pay and Opportunities Act. Privilege buys time and strategic control. it doesn’t eliminate the obligation to remediate.
"This is the right approach. We handle the squeaky wheels. We don't go looking for problems."
Narrator Six weeks later, Lauren's attorney files a complaint with the Washington Department of Labor & Industries. The complaint doesn't just cover Lauren. It names 11 other women in the Seattle office, all at L4 or L5, all paid below male comparators.
"Please be advised that our clients, twelve current and former employees of Cascade Logistics's Seattle office, have filed a complaint with the Washington Department of Labor & Industries alleging systemic violations of Washington Labor Code Section 1197.5 (Equal Pay Act). We are also evaluating claims under RCW 49.58.110 for failure to maintain compliant pay scales."
The complaint-by-complaint approach lasted six weeks.
A L&I complaint naming 12 employees transforms an individual pay dispute into a systemic discrimination claim. Under WashingtonWashington’s Equal Pay Actrsquo;s Equal Pay and Opportunities Act (§1197.5), each employee can recover the full pay differential for up to four years, plus interest, plus attorney’s fees. The complaint also opens the door to RCW 49.58.110 enforcement. failure to maintain compliant pay scales is a separate violation. “We handle squeaky wheels” is not a compensation strategy. it’s a litigation accelerator.
Read Cascade Logistics's draft Compensation Policy. Click on any section that contains a compliance violation.
Some sections are compliant. Click Submit when you've flagged all the problems you can find.
Cascade Logistics Inc.
Compensation Policy 2026. Draft for Review
Section 2. Job Posting Policy.
"Pay scales will be included in job postings for positions physically located in Washington. Fully-remote roles, roles where the hiring manager has not finalised the band, and confidential executive searches may use 'competitive compensation' language at the recruiter's discretion."
Section 3. Workforce Demographics
Total headcount: 2,200 across 5 states. Gender split: 61% male, 39% female. Breakdown by level, function, and location available in the HRIS.
Section 4. Pay Setting Methodology
"Compensation is determined by market benchmarking, individual negotiation, and prior salary history where available and legally permitted."
Section 5. Pay Scale Disclosure
"Pay scales will be provided to Washington employees upon written request to their HRBP. Requests will be processed within 30 business days."
Section 6. Pay Data Reporting
Cascade Logistics will file the annual Washington Pay Data Report with the Department of Labor & Industries as required by Government Code Section 12999, categorizing employees by establishment, job category, race/ethnicity, and sex.
Section 8. Pay Discussion Policy
"Employees may discuss their own compensation with colleagues. However, sharing compensation data of other employees obtained through HR system access or managerial authority is prohibited and may result in disciplinary action."
0 section(s) flagged
RCW 49.58.110. Wage scale and benefits description in every posting (15+ employees). Wage scale on request for current employees and post-offer applicants.
RCW 49.58.020. Equal pay for similarly-employed workers. "Market rate" is not a defence.
RCW 49.58.030. Employees may discuss wages. Discipline for doing so is presumed retaliatory.
RCW 49.58.100. Salary history ban. Cannot ask. Cannot use, even if volunteered.
RCW 49.58.060. Enforcement: actual damages or $5,000 statutory damages per violation, whichever is greater, plus attorney fees.
You scored . Every choice had a cost. Try a different path?