California's SB 642 Just Redefined 'Pay Scale.' Most Hiring Stacks Still Treat Salary as a Sentence.

On January 1, 2026, a California law called SB 642 — the Pay Equity Enforcement Act — takes effect and quietly tightens one of the most-copied compliance requirements in American hiring: the salary range on a job posting. It does three things that matter to anyone running a hiring pipeline, not just California employers, and none of them are about whether you disclose a range. They're about what the range is allowed to mean, how long you can be sued over getting it wrong, and what you have to be able to produce when someone asks.

That distinction — disclosure versus data integrity — is where most hiring stacks are exposed, and it's worth walking through exactly what changed before getting to why the second, quieter problem is the one worth fixing.

What SB 642 actually changes

California has required a salary range on job postings since SB 1162 took effect in 2023. SB 642 doesn't repeal that; it redefines the term "pay scale" under Labor Code Section 432.3 and raises the stakes for getting it wrong. Employment-law firms tracking the bill — Berkshire Associates, Polsinelli, Ogletree Deakins, ArentFox Schiff, CDF Labor Law, and Morgan Lewis all published near-identical breakdowns through late 2025 and mid-2026, which is itself a sign of how uncontroversial the reading is — converge on the same three changes:

1. "Pay scale" now means what you'd pay a specific hire, not the position in general. The old language let employers post the full range for a role — junior through senior, first day through year ten. SB 642 narrows the required figure to a "good faith estimate" of what the employer reasonably expects to pay upon hire. A posting that lists $70,000–$150,000 because that's the theoretical band for the title, when the actual budgeted range for this specific req is $70,000–$90,000, is no longer a good-faith estimate — it's a wide net cast to avoid saying the real number.
2. The window to sue got longer. SB 642 sets a three-year statute of limitations for civil actions alleging a pay-transparency violation, with a six-year lookback for obtaining relief on an existing one. A range posted in early 2026 can still be the subject of a claim in 2032, and evidence about what the employer actually intended to pay when they wrote it has to be producible that far out.
3. "Wages" got broader, and pay-equity demographic data has to be stored separately. The amendments expand what counts as compensation for equal-pay comparisons — stock and stock options are now explicitly in scope, not just base salary — and direct employers to keep demographic data collected for pay-data reporting apart from ordinary personnel records.

None of this is exotic. It's the second-generation version of a first-generation law: California required a number in 2023, found the number was doing less work than intended, and spent 2025 tightening what the number has to represent and how long you're on the hook for it.

California is the sharpest edge, not the only one

Pay-range disclosure is no longer a California-and-Colorado story. As of mid-2026, roughly 13 states plus Washington, D.C. require the salary range to appear directly in the job posting itself — including California, Colorado, Connecticut, Illinois, Maryland, Minnesota, New Jersey, New York, Rhode Island, Vermont, and Washington State — and a wider group of roughly 18 states-plus-D.C. require disclosure somewhere in the process, whether in the posting, on request, or at the offer stage. Delaware's own law, signed in September 2025, adds a "minimum to maximum" requirement tied to the employer's own pay scale, current equivalent employees, or the budgeted amount — the same "what would this role actually pay" framing SB 642 just formalized for California.

The remote-work wrinkle makes the patchwork bigger than a state-by-state map suggests: if a remote role could be filled by someone sitting in a covered state, or reports to a manager or office located in one, that state's disclosure rules can apply regardless of where the company is headquartered. A hiring team that has never opened an office in Illinois can still owe an Illinois-compliant posting because a candidate could plausibly work from Chicago.

The part that doesn't show up in a listicle: salary became a legal record, not a marketing field

Here's the operational problem underneath all of this. When a salary range was purely a disclosure requirement — post a number, satisfy the statute — a lot of hiring platforms and ATSes treated it accordingly: a short text field on the job-posting form, rendered as a string on the public listing, gone from institutional memory the moment the posting closed.

SB 642 makes that treatment expensive. A "good faith estimate... upon hire" is a claim about intent at a point in time, for a specific requisition, and a plaintiff now has up to six years to ask you to substantiate it. That means the range you posted needs to be traceable back to what you actually budgeted for that role, distinguishable from the range for a similar but differently-leveled role, and retrievable years after the req closed — not reconstructed from a hiring manager's memory or a deleted spreadsheet. A free-text "$70K–$150K DOE" string in a job description does none of that. It isn't structured, it isn't versioned, and it doesn't distinguish "the range for the title" from "the range for this specific opening," which is exactly the distinction the new law turns on.

The fix isn't legal, it's a data-modeling one: salary needs to live as structured fields — a minimum, a maximum, a currency, a pay period, and ideally a flag for whether it's negotiable — attached to the individual job record, not baked into prose. That's a low bar technically. It's also not the default in a lot of hiring software, where "salary" still means "whatever text goes between the location and the requirements section."

It's the kind of detail that's easy to verify by looking at the schema rather than the marketing page, so we'll say plainly what we found when we checked our own: every job posting in NiceHire stores salary as a structured record — minimum, maximum, currency, pay period, and a negotiable flag — rather than a single string, and has since the platform's initial schema. That's a fact about the shape of the data, not a compliance claim. Whether a given range is a good-faith estimate under SB 642 is a judgment call for the employer to make about their own budget, and populating min/max on a posting isn't currently required by the platform — an organization can still leave it blank the same way they could leave a free-text field vague. What structured storage buys you is the ability to make that judgment call auditable later: the number is a number, attached to a specific requisition, queryable years after the fact, instead of a sentence that has to be re-parsed out of a job ad nobody kept a clean copy of.

What this means for a hiring team right now

A few things worth doing regardless of where you're headquartered, because the compliance patchwork is trending toward "assume it applies" rather than "check if it applies":

• Separate the range for the title from the range for the requisition. If your job-posting process pulls a salary band from a compensation framework or leveling guide, make sure what gets published is the range for this opening's budget, not the theoretical ceiling for the title company-wide.
• Stop treating the posted range as disposable once the req closes. With a six-year lookback in California alone, the range — and ideally the reasoning behind it — needs to survive as long as the req record does, not just until the position is filled.
• Check remote-eligible postings against every state you'd actually accept an applicant from, not just where the role is based. A single remote req can trigger multiple states' requirements at once if the posting doesn't specify where the employer will and won't hire from.
• If your ATS or careers page renders salary as free text, ask where that text is stored. A compliant-looking listing today with no structured backing record is a liability the day someone asks what you meant by it.

The disclosure requirement was never really the hard part — most employers can write a number into a text box. What SB 642 and its peers are gradually forcing is the harder, less visible change: treating that number as a record that has to hold up under scrutiny years later, which means treating it as data from the start.

Sources consulted for this piece: Berkshire Associates, Polsinelli, Ogletree Deakins, ArentFox Schiff, CDF Labor Law, Morgan Lewis, Hunton Andrews Kurth, and Paycor's 2026 pay-transparency tracker. Facts were cross-checked across these independent sources for consistency before publication.