CA Equal Pay Act · Federal EPA · CO Equal Pay for Equal Work Act
60 days. 14 states. Three different definitions of "equal". Build one framework that satisfies all of them.
Briefing
Tuesday, 7:13 AM. 58 days left. The CEO's email: "David — you have 60 days to build a compensation framework that works across every state we operate in. Start from scratch." You are David Park, Director of Total Rewards at Ridgeline Financial — three acquired companies, three pay philosophies, 2,200 employees across 14 states. The legal team has stopped returning the CFO's calls.
Company Context — Ridgeline Financial
Before you can build pay bands, you need evaluation criteria — the factors that determine how roles are classified. These become the backbone of your multi-state compliance defence.
California's standard: "substantially similar work". Colorado: "equal work". Federal EPA: "equal work" under similar conditions.
The wrong combination is indefensible in court. The right combination is a shield.
Choose up to 6 criteria. Some combinations fail validation.
CA Equal Pay Act (§1197.5): "Substantially similar work" — skill, effort, responsibility, similar working conditions. Not identical. Similar.
CO Equal Pay for Equal Work Act: "Equal work" — similar to federal EPA, includes working conditions explicitly.
Federal Equal Pay Act: "Equal work" on jobs requiring equal skill, effort, responsibility under similar conditions.
CA's "substantially similar" test is broader than Federal EPA's "equal work" — you'll justify more pay differences under CA. Design to the strictest standard.
You share a preliminary framework with Elena. She's read it twice before the meeting starts.
Elena Vasquez
"David, apply these criteria consistently and my SF senior engineers land in the same band as senior legal counsel in New York. That's absurd."
David Park
"Under 'substantially similar work', CA doesn't require identical work — just comparable skill, effort, responsibility. Senior engineers and senior counsel both require advanced credentials, independent judgment, significant outcomes."
Elena Vasquez
"Engineers build the product. Lawyers manage risk. The market pays engineers 30% more — are we ignoring that?"
Priya Mehta
"The market also has a documented gender gap at senior level. Use market data to justify the difference and we're importing that gap and calling it policy."
Elena Vasquez
"I'm not asking you to bake in discrimination. I'm asking you to acknowledge a real ML talent shortage that 'working conditions' doesn't capture."
Elena has a point. The ML talent shortage is real. Don't pay competitively, lose the engineers who run the product.
Priya is also right. Market data carries a 16% gender gap at senior level. Use it as primary justification and you import the gap.
Give the CEO a position. It becomes part of the documented framework.
How does Ridgeline's framework treat market data?
The CFO loves it. Elena loves it. But when Priya runs the numbers, the framework replicates the existing 16.6% gap — because market data at Ridgeline's job levels has a 16% gender gap built in.
Worse: under California Equal Pay Act §1197.5, "prior salary alone" is explicitly not a valid affirmative defence. Courts have extended this reasoning to "market rate alone". If this framework gets audited, Ridgeline will need to explain why roles that meet the substantially similar work standard are paid differently — and "the market told us to" won't be enough.
You document the decision and move forward. The CFO signs off. In 18 months, Rachel Torres will have to defend it in court.
-3 ComplianceElena isn't thrilled — she wanted market data to lead. But when you show her that the framework still allows market premiums above the internal band floor for demonstrated scarcity skills, she accepts it.
Priya re-runs the gap analysis. The 16.6% median gap reduces to 9.3% once roles are correctly classified under the new criteria. The remaining gap needs explanation — but now you have a documented methodology that shows the criteria, not the market, drove the classification.
You document the decision: market data as an input, not a driver. This is the distinction that survives court scrutiny under CA's bona fide factor defence.
+3 ComplianceThe framework is legally clean. Priya confirms the criteria are applied consistently. Elena files a formal objection with the CEO, arguing the framework will make Ridgeline uncompetitive in the ML engineering market.
The CEO calls you. He needs a modified version that acknowledges market realities without using market rate as a justification. You're going to have to add market as an input anyway.
No score impact — you'll get a second chance to position this correctly. The underlying CA Equal Pay Act foundation is intact.
0 ComplianceBefore finalising the framework, you need to assess where the risk is concentrated. Ridgeline operates in 9 states with active pay equity laws. Not all of them carry the same enforcement risk.
Place each jurisdiction on the grid based on: likelihood of enforcement action (x-axis) and severity of financial exposure if action occurs (y-axis). See the multi-state exposure overview.
Select a state chip below, then click on the grid to place it. Place all 6, then grade.
0 of 6 placed
Framework almost done. The CFO has one last question:
"How much of this process do we document? Outside counsel says detailed documentation could be discoverable. If we document a methodology that creates a gap we can't explain, we've handed the plaintiff's attorney their case."
The CHRO disagrees: "Without documentation, we can't prove good faith. A documented process is our best defence."
Both right. The question is what you document and how.
What documentation approach do you recommend?
The documentation is comprehensive. Every classification decision is recorded. The calibration discussions are minuted. The gap analysis is attached.
In 18 months, when Rachel Torres is in court defending the Keisha Washington case, she'll have a complete record of how the framework was built in good faith. That record will also show where the gap is — and Rachel will have to work with it rather than around it.
Full documentation is the high-integrity approach. It's also the highest-exposure approach. But a well-built framework can survive scrutiny. A framework built to avoid scrutiny usually can't.
This approach and the attorney-client privilege approach are both correct. What matters more than which you choose is that you choose one deliberately — and that the framework itself is defensible.
+3 ComplianceThe final framework is documented and defensible. The analysis that got you there — including the gap analysis that showed 9.3% remaining after classification — is protected by attorney-client privilege.
Outside counsel reviews every piece of sensitive analysis before it's committed to discoverable form. The calibration discussions that produce the framework are privileged. The final framework itself is public.
This is the most legally sophisticated approach. It protects Ridgeline's candid internal analysis while still producing a documented, defensible methodology. Rachel Torres will appreciate it in 18 months.
+3 ComplianceThe framework is clean. The documentation is minimal. The CFO is satisfied.
But in discovery, opposing counsel won't just ask for the framework. They'll ask for emails, Slack messages, meeting agendas, and calendar invites from the 60-day period. They'll reconstruct the process from fragments — and fragments without a coherent narrative often look worse than a documented gap.
A poorly documented process doesn't protect you. It just makes you look like you had something to hide. The good faith defence requires a paper trail — not its absence.
-1 ComplianceRidgeline now has a framework. Whether it survives 18 months depends on the decisions you made here.
The framework David builds here is the same one Rachel Torres defends in Module 5. Built well, it's a shield. Built to avoid scrutiny, it's a liability.
Framework criteria selection (max 3)
Skill, effort, responsibility — excluded market rate, strategic importance, revenue contribution. Statutory factors under CA, CO, Federal EPA. Invalid criteria make the framework indefensible.
Market data positioning (max 3)
Treat as input, not primary driver. CA courts rejected "market rate" as standalone affirmative defence. As determining factor it imports gender gaps.
Risk map accuracy (max 3)
Placing CA in the high-high quadrant — above Colorado — is the decisive call. Underestimating CA is the common mistake.
Documentation strategy (max 3)
Full documentation OR attorney-client privilege — both full marks. Minimal earns none. Good faith requires a paper trail.
CA Equal Pay Act §1197.5 — affirmative defences
Four defences: seniority, merit, quantity/quality of production, bona fide factor other than sex. "Prior salary" and "market rate alone" excluded.
CO SB 19-085 / SB 23-105 — equal work standard
Covers jobs requiring substantially similar skills, effort, responsibility under similar working conditions.
Federal Equal Pay Act — the baseline
Minimum floor for all employees. CA and CO are stricter. Build to CA, the other two are covered.