Pay Transparency Laws by State: Which States Require Salary Range in Job Postings

The same job posting is legal in Texas and a seven-figure class-action exposure in Washington.

That is the practical shape of US pay-transparency law in 2026. There is no federal posting-disclosure statute. Every obligation comes from state or city law.

Washington has run the surface enforcement test for two years. Over 300 class-action lawsuits have been filed since June 2024, nearly all in King County Superior Court, against Adidas, Insight Global, Albertsons, and dozens of other employers — for postings missing a salary range. After Branson v. Washington Fine Wine & Spirits, LLC (Wash. Sept. 4, 2025), an applicant does not need to apply in good faith to recover the $100–$5,000 statutory damages.

New York City can fine an employer up to $250,000 for an uncorrected violation. Goldman Sachs paid $215 million in 2023 to settle the gender pay-and-promotion class action — Chen-Oster v. Goldman Sachs Group — that pay-transparency disclosure rules were written to surface earlier. California has narrowed enforcement further: SB 642 (Stats. 2025, Ch. 468) took effect January 1, 2026, extending the Equal Pay Act statute of limitations to 3 years and tightening the "good faith estimate" to the range the employer "reasonably expects to pay for the position upon hire" — a measurably narrower test than the prior role-range definition.

As of May 2026, 13 states plus the District of Columbia have effective pay-transparency laws; Maine and Virginia take effect later in 2026, and Delaware follows in 2027. Seven city ordinances layer on top of state law (NYC, Jersey City, Ithaca, Cincinnati, Toledo, Cleveland, Columbus). Posting without a range may be optional where the law has not taken effect, but it is already litigation-bait in Washington and a routine enforcement target in the covered states — geography is the rule.

Skip to the state-by-state table →

Quick reference

• 13 states + DC have effective pay-transparency laws as of May 2026: California, Colorado, Connecticut, DC, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, New Jersey, New York, Rhode Island, Vermont, and Washington.
• 3 enacted laws are not effective yet: Virginia (July 1, 2026), Maine (July 29, 2026), and Delaware (HB 105, September 26, 2027; 26+ employees).
• 7 city ordinances that ADD to or stand independent of state law: New York City (up to $250K penalty), Jersey City, Ithaca, Cincinnati, Toledo, Cleveland, Columbus (enforcement delayed to 1/1/2027).
• The "good faith estimate" standard — most state laws require employers to post the range they reasonably believe at the time of posting they're willing to pay a successful applicant. California's SB 642 (1/1/2026) narrowed this to "the range the employer reasonably expects to pay for the position upon hire" — a tighter test than the prior broader-range definition.
• No federal pay-transparency law. EEOC's Strategic Enforcement Plan FY2024-2028 names equal pay as a priority and the EEO-1 reporting collects demographic data, but no federal statute requires posting salary ranges. The federal Equal Pay Act of 1963 prohibits sex-based pay discrimination but doesn't require disclosure.
• The simplest defensive posture for multi-state employers: post a range that satisfies the strictest applicable state for any role that could be performed in any pay-transparency state. Most class-action exposure traces back to "we forgot one state in our posting template."

The 5 Most Expensive Pay Transparency Mistakes

1. Posting a remote job from a state with no pay-transparency law without including a range. Washington's class-action wave (300+ filings since June 2024, including 31 brought by a single Seattle law firm in a one-week sweep against Adidas, Insight Global, Albertsons, and others) targets exactly this pattern — multi-state employers posting remote roles without a range, getting picked up by Washington-based candidates with private-right-of-action standing. After Branson v. Washington Fine Wine & Spirits (Wash. Sept. 4, 2025) confirmed that an "applicant" need not apply in good faith, the per-applicant exposure on a single non-compliant posting scales with click-through volume, not just bona-fide hires.

   Colorado, California, and New York interpret their statutes to reach remote roles that residents of those states could perform; "we don't have offices in Washington" is not the carve-out you think it is. If the role can be performed remotely by a Washington (or CA, CO, NY) resident, the range is required.

2. Using a range so broad it fails the "good faith estimate" test. Posting $50,000–$200,000 for a single role to dodge the disclosure requirement is the most-cited failure pattern. Per NYC's guidance, "good faith" means "the salary range the employer honestly believes at the time they are listing the job advertisement that they are willing to pay the successful applicant(s)." California's SB 642 sharpened this to "upon hire" — narrowing it further. A range that spans 4x the low end is presumptively not good faith; courts and state agencies have so held.

3. Ignoring third-party postings. Most state laws (CA, IL, ME, NJ, NY, others) explicitly extend the disclosure requirement to third-party postings — recruiters, job boards (LinkedIn, Indeed), staffing agencies. The employer remains responsible. "Our recruiter posted it without the range" is not a defense; the employer's exposure is the same.

4. Failing to post a range when promoting or transferring internally. Massachusetts (effective 10/29/2025), New York, and Virginia (effective 7/1/2026) explicitly extend the disclosure requirement to internal job openings — promotions, transfers, and similar opportunities. Many employers focus on external postings and forget the internal HRIS / careers page; that's a routine violation pattern in MA + NY litigation.

5. Ignoring the salary-history-ban parallel. Almost every state with a pay-transparency law also has a salary-history ban: cannot ask the applicant about prior pay, cannot screen based on prior pay, cannot retaliate against an applicant who declines to share. Pay-transparency laws and salary-history bans reinforce each other; violating either one weakens the employer's defense to the other. New Jersey, Connecticut, California, Washington, and others routinely package both obligations into the same enforcement action.

Skip to the state-by-state table →

The federal floor — there isn't one

No federal statute requires employers to disclose salary ranges in job postings. The closest federal touchpoints are downstream:

• The Equal Pay Act of 1963 (29 U.S.C. § 206(d)) prohibits pay discrimination based on sex for "substantially equal work." It does not require disclosure; the burden is on the employee to discover and prove a disparity.
• Title VII of the Civil Rights Act of 1964 prohibits pay discrimination on the broader protected-class basis (race, color, religion, sex, national origin).
• FLSA § 215(a)(3) prohibits retaliation against workers who discuss wages — a related but distinct concept from posting disclosure.
• EEOC EEO-1 reporting collects demographic data for establishments with 100+ employees; the pay-band "Component 2" data collection was paused after 2018 and not restored. The EEOC Strategic Enforcement Plan FY2024-2028 names "advancing equal pay" as a targeted priority — meaning more systemic investigations using pay-band analytics, but still no posting-disclosure mandate.

Federal contractors — the parallel OFCCP layer

Federal contractors and subcontractors operate under a parallel pay-equity regime even though no posting-disclosure rule applies:

• Executive Order 11246 + 41 CFR 60-2.17(b)(3) require contractors with 50+ employees and $50,000+ contracts to maintain a written affirmative action program that includes annual in-depth compensation analyses to identify race-, sex-, or ethnicity-based pay disparities. The analysis isn't published; it's retained as a compliance record and produced on OFCCP audit.
• Executive Order 13665 (Final Rule effective January 11, 2016; 41 CFR Part 60-1) makes it a contract-compliance violation to discharge or discriminate against employees or applicants who inquire about, discuss, or disclose their own or coworker pay — the federal-contractor analog to the salary-discussion protections most pay-transparency states extend to private-sector workers. Contractors must include the EEO clause and provide the OFCCP-prescribed Pay Transparency Notice.
• OFCCP Directive 2022-01 clarified compensation-analysis evidentiary requirements for audit submissions.

The practical effect for federal contractors: a posting in a state without a pay-transparency law is still subject to OFCCP non-retaliation rules and the methodology behind the offered pay must withstand the annual compensation analysis. The state pay-transparency posting rule, where one applies, is the public-disclosure layer; the OFCCP framework is the internal-analysis layer. Both can be in scope for the same role.

For the deeper recordkeeping framework that supports compensation-analysis retention and downstream wage-discrimination defense, see our recordkeeping requirements by state guide.

The federal-state asymmetry is the load-bearing point: all meaningful pay-transparency posting obligations come from state and city law. Posting a salary range in Florida is optional; posting one in Washington is litigation-bait if missing.

The "good faith estimate" standard

The cross-state mechanic. Most pay-transparency laws use a "good faith estimate" standard for what range to disclose. Per NYC's official guidance:

"'Good faith' means the salary range the employer honestly believes at the time they are listing the job advertisement that they are willing to pay the successful applicant(s)."

That language — or close variants — appears in California, Colorado, Connecticut, Illinois, Massachusetts, New York, Virginia, Washington, and most other state statutes. The standard is not numeric (no statute sets a maximum range width) but is enforced through reasonableness: an employer posting $50,000–$200,000 for a single role with no role-specific structure to support that breadth fails the good-faith test in practice.

California's SB 642 — the "upon hire" refinement

California's SB 358 introduced pay-scale disclosure in 2023. SB 642 (Stats. 2025, Ch. 468), signed by Governor Newsom in October 2025 and effective January 1, 2026, amended the definition of "pay scale" in Labor Code § 432.3 to read, verbatim:

"(m)(1) 'Pay scale' means a good faith estimate of the salary or hourly wage range that the employer reasonably expects to pay for the position upon hire."

The job-posting requirement under § 432.3(c)(3) is equally direct:

"An employer with 15 or more employees shall include the pay scale for a position in any job posting."

And the third-party extension under § 432.3(c)(5) reaches every recruiter, job board, and staffing agency the employer uses — the employer's exposure follows the posting, not the platform.

The "upon hire" phrase is load-bearing. Pre-SB-642, employers could defensibly post a range that covered the full salary trajectory for the role (entry through senior, $90K–$180K). Post-SB-642, the range must reflect what the employer expects to pay the actual successful candidate — typically a narrower window. The Equal Pay Act statute of limitations was extended in the same bill to 3 years (with up to 6-year recovery periods), expanding enforcement reach. The "wages" definition was also expanded under § 1197.5 to include total compensation: incentive comp, expense reimbursement, stock awards, etc. — relevant for downstream pay-equity claims.

Range-width discipline

Practitioner consensus and state-agency interpretation treats overly broad ranges as failing the good-faith test:

• NYC: Guidance has flagged $50K–$200K-style ranges as non-compliant where the role doesn't justify that breadth.
• Washington: 300+ class actions filed since June 2024 have specifically targeted unreasonable ranges plus missing-range postings. RCW 49.58.110 requires that "the employer must disclose in each posting for each job opening: (i) the wage scale or salary range, except where the employer is offering only a fixed wage amount for the opening, the employer must disclose the fixed wage amount rather than a scale or range; and (ii) a general description of all of the benefits and other compensation to be offered to the hired applicant." Statutory damages run $100–$5,000 per violation (sliding scale set by the 2025 EPOA amendments).
• Colorado: Department of Labor enforcement has issued cure-or-pay notices for ranges that don't reflect actual hiring data.

The defensive posture: the range should reflect the actual offer the employer would extend if a strong candidate accepted today. If the role has multiple levels (entry / mid / senior) at materially different pay scales, post separate listings — not a single range that spans them all.

State-by-state coverage — the structural patterns

The active and already-enacted state laws fall into four practical patterns:

California sits in a hybrid bucket: 15+ employees (anywhere; 1+ in CA triggers application), but covers third-party postings explicitly and is the most expansive in scope. Each state's specific threshold, scope, and penalty structure is in the table below — read carefully for any state where you have workers or post jobs that could reach residents.

California — the deepest and most expansive

California has the most comprehensive pay-transparency regime in the country, with three load-bearing statutes:

1. CA Labor Code § 432.3 (SB 358, eff 2023) — pay-scale disclosure in job postings.
2. CA Labor Code § 1197.5 (Equal Pay Act) — broader equal-pay prohibition; SB 642 amendments extend statute of limitations and broaden "wages" definition.
3. CA Government Code § 12999 (SB 1162, eff 2022) — pay-data reporting to the CA Civil Rights Department (CRD).

The combined regime requires employers with 15+ employees (including any worker in CA) to: (a) post pay scale in every job listing (including third-party postings); (b) provide pay scale to current employees on request; (c) refrain from asking applicants about prior pay; (d) for employers with 100+ employees nationwide with 1+ in CA, annually report mean/median hourly rates by sex/ethnicity/race × job category to the CRD.

Things California employers consistently miss

Third-party postings count. A recruiter or job-board posting (LinkedIn, Indeed, ZipRecruiter) without the pay scale is the employer's violation, not the third party's. § 432.3(c)(3) explicitly extends the obligation to "any third party that the employer engages to announce, post, publish, or otherwise make known" the job.

Remote-eligible postings reach CA workers. CA interprets § 432.3 to apply to any role that could be performed by a CA worker, including remote roles posted by out-of-state employers. The "we have no offices in CA" defense doesn't work for remote-eligible roles.

SB 642's "upon hire" narrowing is enforceable now. California Labor Commissioner enforcement has been actively pursuing ranges that fail the upon-hire test since January 1, 2026. The 3-year statute of limitations (6-year recovery) applies to Equal Pay Act claims filed on or after 1/1/2026.

The pay-data reporting (SB 1162) is separate from the posting disclosure. Many employers handle one and forget the other. RY 2025 reports were due May 13, 2026. RY 2026 reports (due May 2027) will use 23 SOC job categories (up from 10 EEO-1 categories) — payroll systems and HRIS configurations need adjustment.

For the broader California compliance stack (overtime, breaks, recordkeeping, final paycheck), see our overtime rules by state, meal and rest break laws, and recordkeeping requirements by state guides.

A worked walkthrough — multi-state posting compliance

Suppose Acme Robotics, a Texas-headquartered company with 80 employees nationwide, posts a remote staff engineer role on LinkedIn. The role is open to candidates anywhere in the US. Compensation philosophy is one national band with no geographic differentiation: $165,000–$195,000 base, 15% target bonus, equity. Here's what posting compliance looks like for the same job depending on who applies:

• Texas residents apply. No state pay-transparency obligation. TX has no salary-history ban or posting-range law. A posting without a range is legal.
• California, Washington, New York, Colorado residents apply. Range required. § 432.3 (CA), RCW 49.58.110 (WA), NY Labor Law § 194-b (NY), Colorado Equal Pay for Equal Work Act § 8-5-201 (CO) all reach remote roles a resident could perform. A posting without $165,000–$195,000 and a benefits description is litigation-bait.
• NYC, Jersey City, Ithaca, or Cleveland residents apply. City ordinance applies on top of state law. NYC's penalty escalates to $250,000 for an uncorrected violation.

Acme's choice:

• (a) Post one range nationally — $165,000–$195,000 base, 15% target bonus, equity, US-standard benefits. Satisfies every state. Maximum simplicity; minimum exposure. This is what 90%+ of multi-state employers do once they've been through one round of compliance counsel.
• (b) Post regionally tiered ranges — $175,000–$195,000 for CA / WA / NYC candidates; $155,000–$180,000 elsewhere. Legal if the regional structure reflects actual compensation practice (cost-of-labor differentials applied consistently). Defensible only if Acme can document how the tiers were set — not a workaround to dodge the upper-tier range.
• (c) Omit the range and exclude pay-transparency states from the posting. Acme would need to credibly exclude 16+ states + 7+ cities from a remote-eligible engineering role. Practically untenable — one CA resident clicking apply on a posting Acme "didn't intend" to reach them triggers § 432.3 exposure. Not recommended; this path is what produced most of the Washington class actions.

The math on getting it wrong in Washington. Acme posts the role for 90 days without a range. 412 Washington residents click apply. Under Branson, none of them need be bona fide. At the statutory floor of $100 per applicant, exposure is $41,200; at the ceiling of $5,000, it's $2,060,000 — plus attorneys' fees and costs under RCW 49.58.110. Acme's defensive cost (writing one range into the posting template): zero. This asymmetry is why the defensive posture matters operationally even for employers without a single Washington office.

The defensive default for any multi-state employer: post one range that satisfies the strictest applicable state for any role that could be performed in any pay-transparency state.

State-by-state table

State pay-transparency posting requirements as of May 2026. Verify with the specific state DOL or AG before relying for material compliance decisions; state-specific guidance continues to evolve.

City-level ordinances that ADD to state law or apply independently:

The 34 states + Puerto Rico without a statewide pay-transparency law as of May 2026: Alabama, Alaska, Arizona, Arkansas, Florida, Georgia, Idaho, Indiana, Iowa, Kansas, Kentucky, Louisiana, Michigan, Mississippi, Missouri, Montana, Nebraska, Nevada, New Hampshire, New Mexico, North Carolina, North Dakota, Ohio (state-level; OH cities Cincinnati / Toledo / Cleveland / Columbus have ordinances), Oklahoma, Oregon, Pennsylvania, South Carolina, South Dakota, Tennessee, Texas, Utah, West Virginia, Wisconsin, Wyoming.

Note on Oregon: Oregon's Equal Pay Act (2019) prohibits salary-history inquiries but does NOT require salary range disclosure in postings. Oregon is in the "no posting-disclosure law" bucket despite having other significant pay-equity protections.

What's NOT a pay-transparency issue (disambiguation)

Several adjacent obligations get conflated with pay-transparency posting requirements. They reinforce each other in practice but are legally distinct, with separate statutes, separate penalty structures, and separate enforcement paths. A complete compliance posture covers all four; treating them as a single rule misses load-bearing details.

• Pay-data reporting — annual aggregate filings to a state agency (CA Civil Rights Department under SB 1162; IL Equal Pay Registration Certificate; MA EEO-style submissions). The data flows from the employer to the regulator, not to applicants on a posting. Two employers with identical postings can have very different pay-data reporting obligations depending on size, state, and sector.
• Salary-history bans — prohibitions on asking an applicant about prior pay, screening based on it, or retaliating for declining to share. Nearly every pay-transparency state has one (CA, CO, CT, DC, IL, MA, NJ, NY, OR, WA, others), but states like Oregon have a salary-history ban without a posting-range requirement. The two travel together politically but are independent legally.
• Equal-pay-for-equal-work claims — the substantive prohibition on paying employees of one protected class less than another for substantially equal work. Federal Equal Pay Act (29 U.S.C. § 206(d)), Title VII, and state analogs (CA Labor Code § 1197.5, CO Equal Pay for Equal Work Act, NY Labor Law § 194) all live here. A posting can be fully transparent and still produce an equal-pay claim if the actual paid rates are discriminatory; conversely, a missing-range posting violation doesn't itself prove pay discrimination.
• Wage-discussion rights — the NLRA-grounded right of employees to discuss their pay with each other. FLSA § 215(a)(3) reinforces with anti-retaliation. Confidentiality clauses that prohibit pay discussion are unlawful regardless of whether the state has a posting-disclosure law.

The takeaway: when the legal team's pay-transparency audit lands, treat it as one of four parallel obligations, not as the whole pay-equity stack. The other three operate independently and have their own exposure profiles.

Multi-state and remote workers

The intersection of remote work + pay-transparency laws creates the largest single source of class-action exposure for multi-state employers. Three practical scenarios:

• California-headquartered employer with remote roles available nationwide. Every posting must comply with § 432.3 (CA, including SB 642's "upon hire" narrowing) regardless of where applicants come from. Workers in CO, WA, NY, IL, MA, MN, NJ, VT additionally trigger their state's law.

• Texas-headquartered employer posting a remote engineering role on LinkedIn. No TX obligation, but the role's reachability by CA / WA / CO / NY / IL / MA / MN / NJ / VT / DC residents creates exposure under those states' laws. The defensive posture is one posting with a range that satisfies the strictest applicable state.

• DC-based employer with a Maryland-resident commuter and an in-DC remote worker. DC's pay-transparency law applies (1+ employee in DC); the MD law also applies (1+ employees, no size threshold). Both ranges must be disclosed; MD's benefits-and-other-compensation requirements add to DC's healthcare-benefits requirement.

For pay-stub disclosure obligations that follow the work-location-not-headquarters rule, see our pay stub requirements by state guide — the same "work-location controls" principle governs both areas.

The simplest defensive posture: post one range that satisfies the strictest applicable state for any role that could be performed in any pay-transparency state. Audit your posting templates by state where you have or could have workers.

Recent changes (2024-2026)

State pay-transparency expansion has accelerated through 2025-2026 and is expected to continue through 2027. Load-bearing dates:

• October 1, 2024 — Maryland Wage Range Transparency Act effective.
• January 1, 2025 — Illinois (820 ILCS 112/10 amendments) + Minnesota effective.
• June 1, 2025 — New Jersey effective.
• July 1, 2025 — Vermont (Act 155, H.704) effective.
• October 27, 2025 — Cleveland, OH ordinance effective.
• October 29, 2025 — Massachusetts (Frances Perkins Workplace Equity Act, Chapter 141 of 2024 Acts) effective.
• December 3, 2025 — Columbus, OH ordinance effective; enforcement delayed to January 1, 2027.
• January 1, 2026 — California SB 642 amendments effective ("upon hire" narrowing, 3-year SOL, expanded "wages" definition).
• March-April 2026 — Virginia HB 636 / SB 215 signed by Governor Spanberger.
• May 13, 2026 — California pay-data reporting (SB 1162) for RY 2025 due to CA Civil Rights Department.
• July 1, 2026 — Virginia HB 636 / SB 215 effective.
• July 29, 2026 — Maine LD 54 takes effect.
• September 26, 2027 — Delaware HB 105 takes effect.
• September 4, 2025 — Branson v. Washington Fine Wine & Spirits, LLC (Wash. Supreme Court): an "applicant" under the Equal Pay and Opportunities Act need not be bona fide to recover statutory damages. Expanded standing for the class-action wave.
• 2025-2026 — Washington class-action wave. Over 300 class actions filed against multi-state employers — Adidas, Insight Global, Albertsons, and many others. Washington's 5-business-day cure period for non-compliant postings remains in effect until July 27, 2027, after which L&I can pursue penalties without first allowing correction. Statutory damages run $100–$5,000 per violation under the 2025 EPOA amendments.

If you discover your postings are missing the range

Most pay-transparency violations are discovered during routine HR audits or by candidates who apply, notice the omission, and file a complaint or class action. Common remediation steps:

1. Audit your job-posting library across every state where you have workers or post jobs. Pull a list of every active and recently-active posting. For each, verify: range present, range is good-faith (not overly broad), benefits description present where required (CO, IL, MA, MD, MN, NJ, NY, WA), third-party postings include the range.

2. Identify state and city threshold for each posting. A 25-employee company with a NYC-based worker has NYC obligations but may not yet trigger California's 15-employee threshold. Map your employee count by state and city before applying the rules.

3. Decide on a multi-state posting template. Default: one range that satisfies the strictest applicable state for any role that could be performed in any pay-transparency state. Region-specific posting templates work if your compensation structure genuinely varies by region — but the structure has to be real, not a workaround.

4. Use the cure periods. Washington's 5-business-day cure period runs until July 27, 2027; NYC has a 30-day first-time cure; Virginia has a 15-day cure after written notice. Identify violations and cure them BEFORE penalties attach. Don't wait for a complaint.

5. Set up a state-tracking system. Pay-transparency laws are expanding rapidly. New states (Delaware 2027, others pending) and new cities (Columbus enforcement begins 2027) keep adding to the compliance footprint. Subscribe to state DOL / AG bulletins for every state you have workers in.

6. Audit salary-history-ban parallels. Most pay-transparency states also prohibit asking applicants about prior pay. The two obligations co-exist; violating one weakens the defense to the other. Refresh hiring-team training annually.

7. Document your good-faith methodology. When ranges are challenged, the employer's defense is that the range reflected what the employer "reasonably believed at the time of posting they were willing to pay a successful applicant." Document the methodology: comparable internal pay, market data sources used, role-level scoping. The methodology, not the range itself, is often what determines good-faith.

How pay-transparency intersects with other wage-and-hour obligations

Pay transparency is a posting-time disclosure rule. The compliance work it requires plugs into the broader wage-and-hour framework most multi-state employers are already operating:

• Recordkeeping under FLSA § 11(c) + state retention laws. The methodology that produced the posted range — comparable-employee pay data, market-data sources, role-level scoping decisions — is the documentation an employer will need if a range is later challenged as failing the good-faith test. Our recordkeeping requirements by state guide walks the FLSA § 516 + per-state retention rules that govern this paper trail; pay-transparency methodology lives inside that framework, not separate from it.
• Pay stubs and wage statements. Once a candidate accepts an offer at a posted rate, the rate flows into each pay period's wage statement. CA Labor Code § 226's nine required items, plus the Naranjo derivative-claim cascade, mean that an incorrect posted-vs-paid rate compounds into wage-statement liability the employer didn't anticipate. See our pay stub requirements by state guide for the § 226 mechanic.
• Overtime regular-rate calculation. A posted "$165,000–$195,000 base + 15% target bonus" range is also a representation about the regular rate of pay for overtime calculations. Non-exempt employees paid under a posted range with bonus structure trigger the FLSA § 778.115 weighted-average regular-rate recompute. Our overtime rules by state guide covers the regular-rate mechanic; the posted-range disclosure plugs directly into it.
• Multi-state work-location rules. Pay-transparency obligations follow the applicant's location, which means they follow the same work-location-not-headquarters principle that governs pay stubs, recordkeeping, and meal/rest breaks. The simplest defensive posture across all four areas is one master record of "which state does each role attract candidates from" — not separate state mappings per compliance area.

The operational implication: don't treat pay-transparency as an HR-recruiting-team-only concern. The methodology, the paper trail, and the downstream compensation operations are the same systems that handle the rest of wage-and-hour compliance. Wire them together once.

The through-line

Pay transparency is one of the fastest-moving areas of state employment law in 2026. Thirteen states + DC have effective laws today; Virginia and Maine take effect in mid-2026; Delaware adds one in late 2027; multiple cities have layered their own ordinances on top. The federal floor is zero — there is no federal pay-transparency law — so every obligation is state-specific. Multi-state employers can't avoid the patchwork; they have to navigate it.

The single highest-leverage operational practice: post one range per role that satisfies the strictest applicable state, document the good-faith methodology that produced the range, and audit your job-posting library quarterly against the states-and-cities where workers live or could be hired. Most class-action exposure traces back to a missed state in the posting template. The compliance cost of doing it right is small; the exposure of getting it wrong scales with workforce size and time.

Sources

Federal framework

• 29 U.S.C. § 206(d) — Equal Pay Act of 1963 (Cornell LII)
• EEOC Strategic Enforcement Plan FY2024-2028
• EEOC EEO-1 Data Collection

State statutes — pay transparency

• California: SB 642 (2025); SB 358 (Labor Code § 432.3); SB 1162 (Government Code § 12999, pay-data); CA Civil Rights Department Pay Data Reporting
• Colorado: Equal Pay for Equal Work Act (8-5-201 et seq.)
• Connecticut: Public Act 21-30 (CGS § 31-40z)
• DC: Wage Transparency Omnibus Amendment Act of 2024 (Chapter 14A)
• Hawaii: Act 203 (2023; SB 1057)
• Illinois: 820 ILCS 112/10
• Maine: LD 54 / Public Law 2026, Chapter 771
• Maryland: Wage Range Transparency Act (Ch. 271, 2024)
• Massachusetts: Chapter 141 of the Acts of 2024 (Frances Perkins Workplace Equity Act)
• Minnesota: Minnesota Statute § 181.173
• New Jersey: P.L.2024 c.91 (pay transparency)
• New York: NY Labor Law § 194-b
• Rhode Island: RI § 28-6-22 (Pay Equity Act)
• Vermont: Act 155 (H.704, 2024)
• Virginia: HB 636 / SB 215 (2026)
• Washington: RCW 49.58
• Delaware: HB 105 / House Substitute 2 (2025; effective 2027)

City ordinances

• New York City: NYC Commission on Human Rights — Pay Transparency
• Jersey City: Council Ordinance 21-076
• Ithaca, NY: Ithaca Pay Transparency Law
• Cincinnati, OH: Cincinnati Pay Equity Ordinance
• Toledo, OH: Toledo Pay Equity Act
• Cleveland, OH: Cleveland Codified Ordinances § 671 (eff 10/27/2025)
• Columbus, OH: Columbus City Ordinance 2898-2025 (eff 12/3/2025)

Industry / enforcement coverage

• GovDocs — Pay Transparency Laws by State
• Paycor — Pay Transparency Laws by State 2026
• Jackson Lewis — Navigating 2026: Pay Transparency Laws and Employer Obligations
• Rippling — Pay Transparency Laws by State
• Trusaic — Pay Transparency Compliance: Class Action Lawsuits
• Ogletree — Virginia and Maine Enact Pay Transparency Laws to Take Effect in July 2026
• Morgan Lewis — Virginia Pay Transparency Law
• Seyfarth Shaw — California SB 642 Pay Transparency Amendments