US Pay Transparency Laws — Multi-State Compliance
Ridgeline Financial — Denver, San Francisco, New York — Monday, 8:47 AM
An interactive scenario about a state attorney general investigation, pay gaps hiding in plain sight, and what happens when compliance catches up with you before you catch up with it.
Three states. Three different laws. Ten days to respond.
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. This morning, the Colorado Attorney General's office sent you a letter.
This is a choose-your-own-adventure scenario. You’ll face three real decisions that a VP of People encounters as state pay transparency laws take effect — 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.
Multi-State Complexity
Colorado, New York, and California each have different pay transparency requirements. Your decisions must account for all three simultaneously.
Legal References
Law references appear throughout — click them to read the relevant statute.
🏟 Colorado — SB 23-105
All job postings for work performable in Colorado must include a salary range and benefits description. Applies to remote roles that could be done from Colorado. Penalties: $500–$10,000 per violation.
🌇 New York City — Local Law 32
Employers with 4+ employees must include a good faith salary range in every job posting. “Competitive salary” is not a range. Current employees can request their pay range at any time. Penalties: up to $250,000.
☀️ California — SB 1162 + Equal Pay Act
SB 1162 requires salary ranges in all job postings (15+ employees). The California Equal Pay Act goes further: “market rate at time of hire” is NOT a valid justification for paying a woman less for substantially similar work. Only seniority, merit, and quantity/quality of production justify gaps.
The Multi-State Problem
When you operate in multiple states, the strictest standard wins. State-by-state compliance creates patchwork policies that candidates and employees will compare. The question isn’t just legality — it’s credibility.
You're halfway through your first coffee in Denver when Legal forwards you an email marked URGENT — RESPONSE REQUIRED.
"Dear Ms. Ward, This office has received a complaint alleging that Ridgeline Financial LLC has posted job listings for positions performable in Colorado without the salary and benefits information required under SB 23-105. Our review of publicly available job postings on your careers page confirms that at least fourteen (14) current listings lack salary range disclosures."
"Under SB 23-105, each posting constitutes a separate violation carrying penalties of $500 to $10,000. Please provide a written response within ten (10) business days detailing your corrective action plan."
"Sincerely, Deputy AG Laura Chen, Employment Compliance Division"
Before you can finish reading, Jordan Reeves, Head of Recruiting, calls from New York.
"Natalie, I just saw the AG letter. Fourteen postings — I counted them. They're right. None of them have salary ranges."
You "How did fourteen postings go live without ranges?"
Jordan "Because nobody built a check into the ATS. Denver, San Francisco, New York — they all use the same template. And the template doesn't have a salary field."
You "Wait — if Denver has no ranges, what about New York? Local Law 32 requires ranges too."
Jordan "I just checked. Six NYC postings have been saying 'competitive salary' for five months. And our California roles reference pay bands from 2024 — but we hired three engineers in Q4 at $130K–$140K because the market moved. The posted range says $95K–$125K. The real range doesn't match."
You "So we're non-compliant in three states simultaneously."
Jordan "And we have ten days to respond to the AG. What do we tell them?"
The Colorado AG has identified fourteen non-compliant job postings. SB 23-105 penalties run $500–$10,000 per violation. But the exposure is bigger than Colorado — New York and California postings are broken too.
You have ten business days to respond. But your pay bands are 18 months stale, and whatever numbers you commit to will ripple through the entire company.
How do you respond?
"We're not just fixing Colorado. Update every pay band to current market and post ranges on every opening — all five states. Then we respond to the AG with a company-wide corrective action plan."
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 the AG does."
By Friday, the updated postings are live across all states. Your response to the AG includes a corrective action plan, a timeline, and evidence of nationwide implementation. Deputy AG Chen's office acknowledges receipt and notes the voluntary scope of your remediation.
Colorado SB 23-105 penalties are per-violation — but proactive remediation is a mitigating factor. By going beyond what the AG asked (fixing all states, not just Colorado), you demonstrate good faith that reduces penalty exposure and pre-empts identical investigations from New York and California.
"Fix the 14 Colorado postings and respond to the AG addressing exactly what they asked. We'll clean up New York and California in the background."
Jordan "What if the AG asks whether we have the same problem in other states?"
You "They asked about Colorado. We answer about Colorado."
Your response addresses the 14 postings. Deputy AG Chen's office writes back: "We note that Ridgeline Financial operates in multiple jurisdictions with similar transparency requirements. Can you confirm that your remediation extends to all states in which you operate?" Now you're answering questions about what you didn't fix.
Responding only to what was asked is technically correct — but regulators talk to each other. A narrow fix in Colorado invites scrutiny from NYC and California. The AG's follow-up question is worse than their original letter because now you've demonstrated awareness of the problem without demonstrating willingness to fix it broadly.
"Ask Legal 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 ranges?"
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."
Deputy AG Chen's office denies the extension request. Response: "The violations identified are ongoing. SB 23-105 does not provide for a grace period. Each day a non-compliant posting remains active constitutes a continuing violation. We expect your corrective action plan within the original ten-day window."
Meanwhile, a candidate screenshots one of the still-live Colorado postings. LinkedIn post: "Ridgeline Financial is under AG investigation for missing salary ranges — and the postings are STILL up." 800 likes and climbing.
Unlike some regulations that freeze penalties once you acknowledge the issue, SB 23-105 treats each day a non-compliant posting remains live as a continuing violation. Requesting an extension while the postings stay up doesn’t pause the clock — it runs it. The AG’s denial was predictable: the fix (adding a range) is simple and immediate. What you’re really delaying isn’t compliance — it’s confronting the pay band problem underneath.
You've responded to the AG — or at least started to. But while you were dealing with Colorado, an email landed in your inbox from Aisha Patel, Senior Engineer in San Francisco.
"Hi Natalie, 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."
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.
Ridgeline's legal team has listed three reasons for the $23,600 gap between Aisha and Brian. Under California's Equal Pay 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, Natalie. 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 Natalie — 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 Natalie — 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 California’s Equal Pay Act, Aisha 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 SB 1162, maintaining current pay scales isn’t optional — it’s a recordkeeping requirement.
Tom Brennan has modeled three scenarios against Ridgeline's California exposure. Click each card to see the full breakdown.
Under California EPA, "market rate" is explicitly not a defense. If Aisha files, back pay + equal liquidated damages is the floor, not the ceiling. And Colorado still has the open posting violation.
SB 1162 reporting compliance clears California risk. Colorado posting fix prevents CDLE fines ($500–$10,000 per violation). NYC posting compliance removes Commission on Human Rights exposure (up to $250,000).
A class action attorney has already tagged Ridgeline employees in LinkedIn posts about California pay equity rights. Aisha has spoken to an employment lawyer. The Colorado posting violations are public record — any applicant can see them.
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 — 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 Natalie — 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.
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 Aisha exercised under California’s Equal Pay 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, 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.
A CRD complaint naming 12 employees transforms an individual pay dispute into a systemic discrimination claim. Under California’s Equal Pay 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 SB 1162 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 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?