California Passes Bills Amending the Equal Pay Act

California just did that very California thing where it looks at a law, nods politely, and then says,
“Cool. Now let’s make it stronger… and also a little more specific… and also please stop posting salary ranges
that look like lottery jackpots.” In late 2025, the state passed two billsSB 642 and SB 464that tighten up
pay equity enforcement, sharpen pay transparency rules, and upgrade pay data reporting so it’s more actionable
(and less “we tried our best”).

If you hire in California, manage compensation, post jobs, or simply enjoy sleeping at night, these amendments
matter. They touch everything from what “pay scale” means on job postings to how long employees have to bring
equal pay claims, to what counts as “wages” when you’re comparing pay. And if you’re an employee, they expand
language and remedies in ways that may make it easier to spotand challengepay disparities.

Quick refresher: what California’s Equal Pay Act already does

California’s Equal Pay Act (anchored in Labor Code section 1197.5) is built around a simple idea:
if two people do substantially similar work under similar working conditions, their pay should not be lower
because of protected characteristics. This is not a “same job title” lawit’s a “same essential work” law.

“Substantially similar work” is broader than you think

The comparison looks at a composite of skill, effort, and responsibility, plus similar working conditions.
Translation: if two roles walk like a duck and quack like a duck, calling one “Senior Duck Wrangler II”
doesn’t automatically get you off the hook.

What employers can use to justify pay differences

The law allows pay differentials if the employer can show the gap is fully explained by legitimate factors such as:
seniority, merit, production-based systems, or a bona fide factor other than protected traits (think education,
training, experience), applied reasonably and consistent with business necessity. Importantly, California has long
pushed back on using prior salary as a magic wand to justify gaps.

The 2025 bills amending pay equity rules: SB 642 and SB 464

Here’s the high-level view:

• SB 642 updates Equal Pay Act language and enforcement mechanics (including non-binary inclusive language),
  tightens the definition of “pay scale” for postings, expands the timeframe for claims, and clarifies what “wages” include.
• SB 464 adjusts pay data reporting rules (reported to the Civil Rights Department), including how demographic
  information must be stored, when penalties apply, and how job categories expand to create more granular reporting.

SB 642: the Equal Pay Act gets sharper (and more modern)

1) The law moves beyond “opposite sex” language

SB 642 replaces outdated wording that framed comparisons as “opposite sex” and shifts it to “another sex,” aligning
the statute with modern understandings of sex and gender and reducing ambiguity for non-binary workers.
This is not just a vocabulary upgradestatutory language matters in litigation, policy writing, and enforcement.

2) The “pay scale” definition is narrowed to what you expect to pay upon hire

California’s pay transparency rules already require many employers to include a pay scale in job postings.
SB 642 tightens what counts as that “pay scale” by defining it as a good-faith estimate of the salary or hourly
wage range the employer reasonably expects to pay upon hire.

In plain terms: if your posting says “$60,000–$200,000” because you someday might pay a unicorn-level candidate
a galaxy-brain salary, that range may be harder to defend if it’s not genuinely what you expect to offer at the point of hire.
SB 642 doesn’t demand perfect precision (it allows estimates), but it does demand honesty.

3) More time to sue, and potentially more back pay at stake

One of SB 642’s biggest practical impacts is the claims timeline. The bill extends the filing window for certain equal pay
civil actions to three years after the last date the cause of action occurs, and clarifies that the cause of action can occur when:
an unlawful pay decision is adopted, when a person becomes subject to it, or each time compensation is paid as a result.

It also states that employees may seek relief for the full period a violation exists, capped at six years.
That can materially change employer exposure (and employee leverage) in disputes that simmer quietly before anyone notices.
It also means documentation and consistency matter more than everbecause you can’t “hand-wave” away a long-running practice.

4) “Wages” means more than base pay

SB 642 clarifies that “wages” and “wage rates” include all forms of paynot only salary or hourly rate but also
categories such as bonuses, stock and stock options, profit sharing and bonus plans, and benefits like vacation/holiday pay
and certain allowances.

Why it matters: two employees might have the same base pay, but if one gets a richer bonus structure, more equity,
or better benefits tied to compensation, the total “wages” picture can look very different. SB 642’s approach makes it
harder to hide pay disparities in the “fine print” of compensation packages.

5) Extra pressure on job postings, applicants, and recordkeeping

SB 642 also reinforces the ecosystem around pay transparency and salary history. Employers still need to provide a pay scale
upon request to applicants, include pay scale in job postings for covered employers, and maintain certain records. It also
interacts with rules limiting salary history inquiriesmeaning hiring teams should be careful about how they gather compensation
context (asking about salary expectations is generally treated differently than asking what someone used to make).

SB 464: pay data reporting becomes harder to ignore

Pay data reporting is the state’s way of saying: “Don’t just tell us you’re fairshow your work.” SB 464 updates California’s
reporting framework under Government Code section 12999, which requires certain employers to submit annual pay data reports
to the California Civil Rights Department (CRD).

1) Demographic data must be stored separately from personnel files

SB 464 requires that demographic information gathered for pay data reporting purposes be collected and stored
separately from employees’ personnel records. This is both a privacy-minded move and a compliance signal:
keep the reporting pipeline clean, controlled, and auditable.

2) Penalties get more “mandatory”

Existing law already allowed enforcement mechanisms if a report wasn’t filed. SB 464 strengthens consequences by requiring
courts to impose civil penalties in certain situations when employers fail to file the required pay data report after being requested
to do so by the CRD. In other words: the state is less interested in “pretty please” and more interested in “file the report.”

3) Job categories expand to 23 starting in 2027

The bill expands the number of job categories used in pay data reporting to 23 beginning January 1, 2027.
This is aimed at producing a more precise view of workforce composition and pay patterns, because broad categories can hide
meaningful differences in role type and seniority.

Practically, it means employers should start preparing earlymapping job titles to the new categories, cleaning HRIS data, and
aligning internal job architecture so reporting isn’t a frantic spreadsheet marathon every spring.

4) Reporting calendars are realand they’re not waiting for you

The CRD publishes guidance and deadlines for annual reports (including portal tools, templates, and FAQs). If you’re a covered employer,
treat reporting like a recurring compliance deliverable, not a “sometime after Q2 when life calms down” project (because it won’t).

Why California keeps tightening pay equity rules

Pay equity laws often evolve in response to two realities: (1) pay gaps persist even when laws exist, and (2) transparency and enforcement
tend to drive change faster than polite encouragement. California’s approach has been to steadily expand protected categories, broaden what counts
as comparable work, reduce secrecy around pay, and give agencies and workers more workable tools to enforce the rules.

SB 642 arrives on the heels of earlier reforms (like the shift from “equal work” to “substantially similar work” and expansions that added
race and ethnicity protections). SB 464 builds on the state’s newer pay data reporting infrastructureturning it into something closer to a
spotlight than a flashlight.

Specific examples: what these amendments look like in real life

Example 1: the “salary range wider than the Pacific Ocean” job posting

A company posts a role with a pay range of $70,000–$190,000 “to stay flexible.” Under SB 642’s “upon hire” framing, the employer should ask:
what do we actually expect to pay a new hire? If the genuine hiring range is more like $90,000–$120,000, posting a mega-range can invite scrutiny,
confusion, and mistrustplus it undermines the purpose of transparency.

Example 2: equal base pay, unequal total compensation

Two employees in substantially similar roles both earn $120,000 base. But one receives a 20% bonus target and equity grants while the other gets
a 5% bonus target and no equity. If the difference correlates with protected traits and can’t be justified by legitimate factors, SB 642’s broader
“wages” definition makes it harder to pretend “everything is equal because base pay matches.”

Example 3: a pay decision made years ago still matters today

An employee was placed into a lower pay band three years ago due to a questionable “market adjustment” decision. Under SB 642’s cause-of-action framing,
each paycheck affected by the decision can mattermeaning the timeline and potential recovery may extend further than employers expect, especially if the
practice continued over time.

Employer playbook for 2026 and beyond

Compliance here isn’t just about avoiding penaltiesit’s also about recruiting, retention, and reputation. Pay transparency is a culture signal:
it tells candidates and employees whether your compensation system is intentional or improvised.

1) Clean up job postings and third-party posting workflows

• Define pay ranges that reflect what you reasonably expect to offer upon hire.
• Standardize range-setting (who approves it, what data supports it, how often it updates).
• If recruiters or platforms post your jobs, make sure they receive and display the pay scale consistently.

2) Document your compensation factors like you might need to explain them later

California equal pay defenses work best when they’re real and consistent. “We pay more because vibes” is not a recognized compensation framework.
A defensible system typically includes:

• Job leveling and clearly defined role expectations
• Structured ranges (bands) supported by market data
• Clear rules for offers, promotions, and adjustments
• Documentation of bona fide factors (education, experience, scope, performance, locationwhere legitimately relevant)

3) Run a pay equity auditand make it useful

Don’t just produce a report; produce decisions. A practical audit looks for disparities among substantially similar roles and asks:
Are differences explained by legitimate factors? Are those factors applied consistently? Are there “historical artifacts” (old offer practices,
manager discretion, inconsistent leveling) that still shape pay today?

4) Upgrade recordkeeping and reporting pipelines

• Maintain job title and wage rate history records as required.
• Ensure demographic data used for pay data reporting is stored separately from personnel files (SB 464).
• Start mapping jobs to the expanded category structure ahead of the 2027 transition so you’re not doing taxonomy in a panic.
• Build a calendar for CRD reporting deadlines and internal data validation steps.

5) Train hiring managers (and not just once)

A surprising amount of compliance risk comes from casual conversations. Train teams to:

• Use posted pay scales consistently in offers
• Avoid salary history questions
• Ask lawful questions about salary expectations in a structured way
• Document compensation decisions clearly and consistently

Employee perspective: how to use pay transparency constructively

Pay transparency isn’t only about lawsuits; it can also support healthier negotiations and clearer career paths. Employees can:

• Ask for the pay scale for a role they’re applying to (or their current role, where applicable).
• Compare compensation holistically (base + bonus + equity + benefits).
• Track job scope changes over timebecause “same title” doesn’t always mean “same work.”
• Raise concerns using internal channels first when appropriate (HR, compensation teams, compliance hotlines).

One practical tip: if you’re trying to understand fairness, focus on role scope and requirements. “Substantially similar work” is about what the job demands,
not who has the fanciest title on LinkedIn.

FAQ: fast answers to common questions

Does SB 642 mean every job posting range must be tiny?

Not necessarily. It means the range should reflect a good-faith estimate of what you expect to pay upon hire. Ranges can still be rangesjust not fiction.

If base pay is equal, are we safe?

Not automatically. SB 642’s “wages” clarification emphasizes total compensation, including certain benefits and variable pay. Pay equity is a full-package conversation.

Will SB 464 change who has to report pay data?

The core reporting framework remains focused on covered employers, but SB 464 strengthens how data is handled and how penalties apply, and expands job categories in 2027.
If you already report (or should), the compliance bar is rising.

On-the-ground experiences: what this looks like when real people do the work (extra 500+ words)

Policies are tidy. Payroll is not. Here are several “realistic composite” experiences that tend to surface when companies and employees live inside pay equity rulesnot as
abstract legal concepts, but as Tuesday afternoon problems.

1) The “range got posted… but nobody told recruiting” moment

A mid-sized company updates its internal pay bands and proudly announces that all job postings will include salary ranges. Great! Then a hiring manager forwards an old
job description to an external recruiter, who posts it without the updated pay scale. Candidates start asking why the company’s website shows one range while the recruiter’s
version shows nothing. Internally, nobody is trying to be sneakythere’s just no workflow. The fix is boring but powerful: one source of truth (a job posting template tied to
approved pay scales), plus contracts and checklists for vendors so third-party postings mirror internal compliance.

2) The “we pay fairly… except for the fossils” problem

Many organizations discover that their newest hires are paid more consistently than long-tenured employees. That’s not always discrimination; sometimes it’s market drift:
hiring salaries rise quickly, while annual increases creep. But the optics are rough, and the disparities can become legally risky if they line up with protected traits or
inconsistent role leveling. The most effective teams treat this as a systems issue: they do a compression review, decide where adjustments are needed, and write down the
rationale so it’s clear this was a proactive equity movenot a reaction to a threat.

3) The “same base pay, different bonus math” surprise

A company standardizes base pay ranges but leaves bonus targets to manager discretion (“because every team is different”). In practice, bonuses become the new salary history:
a quiet, negotiable number that can widen gaps. When leadership finally compares bonus targets across substantially similar roles, they find patterns that nobody intended.
This is where SB 642’s broader view of “wages” feels very real. The experience many teams report is that the hard part isn’t setting a policyit’s making sure the policy
touches all the pay levers, not just the obvious one.

4) The “job titles are creative, reporting categories are not” headache

Pay data reporting becomes dramatically harder when job architecture is messy. Roles like “Growth Ninja,” “Customer Happiness Hero,” or “Marketing Ops Wizard” might be fun,
but they’re a compliance migraine when you need consistent categorization. Teams often end up doing a late-night translation project: mapping each internal title to standardized
job categories, validating it with department heads, then discovering that two people with the same internal title do meaningfully different work. The experience tends to push
organizations toward clearer leveling and standardized job familiesnot because it’s trendy, but because reporting and fairness are nearly impossible without it.

5) The employee experience: transparency reduces guesswork (and rumor mills)

For employees, posted pay scales and clearer definitions can reduce the psychological tax of “Am I being underpaid, or is this just my anxiety talking?” When pay ranges are
visible and managers can explain how offers are set, employees report fewer hallway rumors and more productive conversations: “Here’s where I am in the band; what would move me
higher?” That doesn’t eliminate conflict, but it changes the tone. The best outcomes come when transparency is paired with a growth frameworkskills, scope, and performance
expectationsso pay progression feels like a path, not a mystery box.

The common thread in these experiences is simple: compliance is easiest when compensation is intentional. The more pay is driven by informal exceptions, manager-by-manager
improvisation, or “we’ve always done it that way,” the more likely the company is to run into the twin problems of inequity and distrust. SB 642 and SB 464 are, in many ways,
California telling employers: “Write it down. Make it consistent. And if it’s not consistent, fix it.”

Final thoughts

SB 642 and SB 464 reflect California’s ongoing push toward pay equity through transparency, clearer definitions, and stronger enforcement mechanics. For employers, the best
strategy is to treat these amendments as an opportunity to strengthen compensation systemsbefore compliance becomes crisis management. For employees, the changes may offer
more clarity, more time, and more meaningful comparisons across total compensation.

Note: This article is for informational purposes only and does not constitute legal advice. For guidance specific to your organization or situation,
consult qualified employment counsel or compliance professionals.