US Pay Transparency Laws — Multi-State Compliance
Ridgeline Financial — Denver, San Francisco, New York — Monday, 8:47 AM
An interactive scenario about pay transparency across state lines, salary range postings that went live without ranges, and what happens when your employees start comparing numbers.
Three states. Three different laws. One company trying to get it right.
VP of People at Ridgeline Financial — a 2,200-person financial services company with offices in Denver, San Francisco, New York, Dallas, and Miami.
Your company operates in five states. Three of them have pay transparency laws. Your pay bands haven't been updated in 18 months. Today, three things go wrong at once.
You're halfway through your first coffee in Denver when three Slack messages arrive in the span of four minutes.
First: Jordan Reeves, Head of Recruiting, from New York:
Second: An email from Aisha Patel, Senior Engineer in San Francisco:
"Hi Sarah, Under California SB 1162, 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."
"I'm looking at the LinkedIn post right now. The candidate — Marcus Webb — wrote: 'Applied to Ridgeline Financial in Colorado. No salary range posted. Isn't that illegal?' It has 340 likes and climbing."
You "It is. Colorado SB 23-105 requires salary ranges in every job posting for positions that could be performed in Colorado. Even remote roles."
Jordan "OK, but here's the thing — our pay bands haven't been updated in 18 months. If I post the L5 band from 2024, it's $95K to $125K. But we hired three engineers in Q4 at $130K–$140K because the market moved. The real range and the posted range won't match."
You "And if Aisha sees a posted range that starts below what she's making, that's one problem. If she sees one that starts above what she's making, that's a different problem."
Jordan "Exactly. So what do I post?"
A candidate has publicly flagged your missing salary range. Colorado law is clear: ranges are required in every posting. But your bands are stale, and whatever range you post will ripple through the entire company. Engineers talk.
The LinkedIn post is gaining traction. Every hour you wait, it gets worse.
What do you tell Jordan?
"Update the bands to reflect what we're actually paying. Then post ranges on every opening — every state, every role. If we're going to do this, we do it once."
Jordan "That's going to show that six current employees in Denver are below the new minimum of their own band."
You "I know. We fix that too. Better we find it than they do."
By Wednesday, the updated postings are live. Marcus Webb updates his LinkedIn post: "Ridgeline responded within 48 hours and posted ranges on every role. Respect." The post gets 200 more likes — but for the right reason this time.
Colorado SB 23-105 requires ranges in all postings for Colorado-performable work. NYC Local Law 32 requires the same for NYC roles. Going national eliminates the compliance patchwork — and shows candidates you're serious, not just checking boxes.
"Post ranges for Colorado, California, and New York openings. Texas and Florida stay as they are."
Jordan "Got it. But what happens when a candidate in Dallas sees the Colorado posting for the same role with a range, and their posting doesn't have one? They're going to ask."
You "We'll handle that as it comes."
It comes on Thursday. A Dallas recruiter forwards you a candidate email: "I noticed the same Senior Engineer role in Denver lists $105K–$140K. I'm interviewing for the Dallas version. Is the range different, or do you just not want to tell me?"
State-by-state compliance is technically legal, but it creates an inconsistency that candidates and employees will notice. The question isn't whether you're breaking the law in Texas — it's whether the disparity signals something you'd rather not explain.
"Pull the posting. Have Legal reach out to Marcus directly."
Jordan "And tell him what?"
You "That we're updating the posting and it'll be back up with the correct information."
Marcus screenshots the takedown. New post: "Ridgeline Financial took down the job posting instead of adding a salary range. Tells you everything you need to know about their culture." 1,200 likes. A reporter from Business Insider DMs him.
The Colorado Department of Labor opens a complaint file. Under SB 23-105, penalties run $500 to $10,000 per violation.
-2 ComplianceYou've handled the Colorado fire — or at least stopped it from spreading. Now Aisha's email is sitting in your inbox.
You pull up the compensation file for Senior Software Engineers (L5) in San Francisco:
| Employee | Title | Years | Rating | Salary |
|---|---|---|---|---|
| Aisha Patel | 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 California's Equal Pay Act, it's not.
"Thank you for the call, Sarah. I'll be direct."
She shares her screen. On it: her last three performance reviews, her offer letter, and the text of SB 1162.
"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 SB 1162, I have the right to request the pay scale for my position. I'm making that request formally."
Aisha has invoked SB 1162. California 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.
"Aisha, 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."
Aisha "I appreciate that. But Sarah — 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."
Aisha "I don't want to leave Ridgeline. I want Ridgeline to be the kind of company that fixes this without me having to hire a lawyer."
She pauses.
Aisha "But I will hire one if I have to."
SB 1162 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.
"Aisha, here's the L5 pay scale: $95,000 to $125,000."
A pause.
Aisha "The max is $125K?"
You "That's the current band on file, yes."
Aisha "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 Aisha proof that Ridgeline's compensation framework is broken — or selectively applied.
Sharing a pay scale that doesn't match reality creates worse evidence than sharing nothing. If Aisha'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.
"Aisha, 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?"
Aisha "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.
Aisha "I'll wait two weeks. But Sarah — 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.
+1 ComplianceBefore 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 — Aisha today, maybe two or three more — it'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 "Aisha alone: if she files under the California Equal Pay 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 California."
Brennan Long pause. "How many more Aishas 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 Ridgeline employees in posts about pay equity rights. Three more employees in California have filed SB 1162 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 the CRD investigates our California 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 the CRD went after settled for $15 million."
The CEO nods. "Do the audit. Under privilege. And Sarah — 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 Aisha'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 Aisha signs something."
Aisha 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.
+1 Compliance"This is the right approach. We handle the squeaky wheels. We don't go looking for problems."
Narrator Six weeks later, Aisha's attorney files a complaint with the California Civil Rights Department. The complaint doesn't just cover Aisha. It names 11 other women in the San Francisco office, all at L4 or L5, all paid below male comparators.
"Please be advised that our clients, twelve current and former employees of Ridgeline Financial's San Francisco office, have filed a complaint with the California Civil Rights Department alleging systemic violations of California Labor Code Section 1197.5 (Equal Pay Act). We are also evaluating claims under SB 1162 for failure to maintain compliant pay scales."
The complaint-by-complaint approach lasted six weeks.
-2 ComplianceRead Ridgeline Financial'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.
Ridgeline Financial Inc.
Compensation Policy 2026 — Draft for Review
Section 2 — Job Posting Policy
"Salary ranges will be included in job postings for positions located in Colorado, California, and New York City. For all other states, postings will use 'competitive compensation' language unless the hiring manager requests otherwise."
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 California employees upon written request to their HRBP. Requests will be processed within 30 business days."
Section 6 — Pay Data Reporting
Ridgeline will file the annual California Pay Data Report with the Civil Rights Department 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
CO SB 23-105 — Salary ranges required in all job postings
CA SB 1162 — Pay scale disclosure on request; pay data reporting to CRD
NYC Local Law 32 — Salary ranges required in all job postings
CA Equal Pay Act — Equal pay for substantially similar work; "market rate" is not a defense
Federal NLRA — Employees have the right to discuss pay; anti-discussion clauses are illegal
You scored . Every choice had a cost. Try a different path?