Pay Transparency Laws by State in 2026: What HR Teams Must Do Now
The Week the Law Changed — and the Spreadsheet Didn't
Picture this: it's the first Monday of 2026, and your hiring manager has just sent you three new job requisitions to post. You open your compensation spreadsheet — the same one you've been updating since 2021 — and realize you have no documented salary range for any of them. You know pay transparency requirements are expanding, but you're not certain which rules apply to your postings, whether your ranges need to cover remote candidates in other states, or what a defensible "good-faith estimate" actually looks like in writing.
You are not alone. Across the United States, HR teams at small and mid-size companies are navigating an increasingly complex patchwork of pay transparency laws by state in 2026 — some already in effect, some newly enacted, some still pending. Getting this wrong isn't an abstract risk: California treats each non-compliant job posting as a separate violation event, and Colorado has already assessed hundreds of thousands of dollars in fines against employers.
This article gives you a working map of where the law stands in 2026, what each major jurisdiction requires HR teams to do operationally, and how to build the internal structure you need to stay compliant as more states follow.
How Many States Have Pay Transparency Laws in 2026?
The count depends on methodology. Counting only statewide statutes, researchers report 16–18 states with enacted pay transparency laws as of 2026. When municipalities with their own ordinances are included, Brightmine counted as many as 25 jurisdictions in the United States where pay transparency laws have been enacted as of late 2025. Lift HCM reported in 2026 that 17 states plus multiple municipalities have active pay transparency laws — affecting an estimated 65% of U.S. employers.
The practical implication: if your company is large enough to post jobs publicly and hire across state lines, there is a high probability that at least one applicable jurisdiction's law already covers some of your postings, even if your headquarters sits in a state with no law of its own.
Two states joined the group in 2026: Maine, where pay-disclosure requirements took effect July 29, 2026, and Virginia, where requirements took effect July 1, 2026. Delaware is next in the pipeline — a law signed in September 2025 requires employers with 25 or more employees to include a good-faith pay range in publicly advertised postings, effective September 26, 2027.
The trajectory is clear. States are not retreating from pay transparency; they are expanding it, tightening it, and extending statutes of limitations on enforcement actions.
The operative question for HR is not whether your state has a law yet — it is whether any state where you post or where candidates are located does.
What the Major Jurisdictions Require: A Practical Summary
No two state laws are identical. Thresholds, definitions, scope, and penalties all vary. Here is what the verified requirements look like for the jurisdictions most likely to affect US employers right now. For states not covered in detail below, verify the current requirement directly with the relevant agency or employment counsel before your next posting cycle.
California
California has the most litigated pay-transparency regime in the country, and it tightened further on January 1, 2026.
Who it covers: Employers with 15 or more employees must include a pay scale in all job postings — including postings made through third-party platforms. The original requirement came from SB 1162 (effective January 1, 2023).
What changed in 2026: SB 642 (effective January 1, 2026) redefined "pay scale" as a good-faith estimate of the pay range the employer reasonably expects to pay upon hire — not simply an existing internal band. This matters: a range that reflects your internal structure but not your realistic offer range may not satisfy the new standard. SB 642 also extended the statute of limitations for civil actions involving willful pay-scale violations from three years to six years.
Penalties: Civil penalties run $100 to $10,000 per violation under Labor Code §432.3(f), with escalating fines for subsequent violations. Pay-data report failures carry separate penalties of $100–$200 per employee.
The multiplier risk: Each job posting lacking a required pay range is treated as a separate violation. Post the same role on five job boards without a compliant range, and you face up to five penalty events. For a detailed breakdown of how California calculates and assesses fines, see our pay transparency fines explained guide.
For the full California-specific compliance checklist, see pay transparency California.
Colorado
Colorado's Equal Pay for Equal Work Act was the template many later state laws followed, and its enforcement record is concrete.
Who it covers: Most Colorado employers, regardless of size, when posting roles that could be performed by a Colorado resident — including fully remote roles.
What it requires: Job postings must include a pay range, a general description of benefits, and other compensation (such as bonuses or commissions). Employers must also post promotional opportunities internally.
Penalties: Posting and notice violations carry fines of $500 to $10,000 per violation, with each non-compliant posting treated as a separate violation. As of July 1, 2024, Colorado had received 1,634 complaints and assessed $238,000 in fines against employers.
Remote-posting implication: If you post a role as "remote — open to candidates in the US," Colorado's regulators have taken the position that the posting applies to Colorado residents and therefore triggers EPEWA requirements. Many employers learned this the hard way in 2023–2024 by excluding Colorado from remote postings — a workaround Colorado's regulators have scrutinized.
For current Colorado-specific requirements, see pay transparency Colorado.
Other States to Verify Before Your Next Posting Cycle
Beyond California and Colorado, several additional states have enacted salary-range disclosure requirements that HR teams at multi-state employers must verify. These include — but may not be limited to — New York, Illinois, Washington, Maryland, New Jersey, Connecticut, Nevada, and Rhode Island. The specific employee-count thresholds, posting mechanics, and enforcement agencies differ in each.
This article does not reproduce the requirements for these states line by line, because those details change and must be verified against the current authoritative source for each jurisdiction. Before you post any role that could attract candidates from, or be performed in, one of these states, check directly with the relevant state labor agency or employment counsel.
What you should document for each state where you have applicants or employees:
- Minimum employer size threshold (some start at 1 employee; others at 15 or 25)
- Whether the law applies to remote postings
- Whether a range or a single figure is required
- Record-retention obligations
- The enforcement agency and penalty schedule
The Three Most Common Compliance Gaps — and How to Close Them
Most HR teams at companies under 250 employees stumble on the same operational problems, regardless of which state's law applies.
Gap 1: No Documented Salary Ranges to Post
If your compensation is managed in a spreadsheet with no formal band structure, you can still derive a good-faith range — but you have nothing to audit, nothing to defend, and no consistency across roles or hiring managers. When a candidate or regulator asks "how did you arrive at this range?" the answer cannot be "the hiring manager estimated it."
The solution is to build a basic band structure: a minimum, midpoint, and maximum for each role, anchored to an external reference. In the United States, the BLS Occupational Employment and Wage Statistics (OEWS) survey covers approximately 830 occupations across the nation, all 50 states, and roughly 530 areas, drawn from a sample of approximately 1.1 million establishments. That data is public, updated annually, and defensible as a benchmark anchor.
Here is how a simple band works: take the BLS OEWS median for a given occupation in your metro area as your target midpoint. Choose a band spread appropriate to the role's complexity — commonly 40–60% for individual contributor roles, wider for senior or highly variable positions. Then calculate:
- Band minimum = Midpoint ÷ (1 + Spread/2)
- Band maximum = Midpoint × (1 + Spread/2)
Example (illustrative): If the BLS OEWS all-occupation annual mean wage is $69,770, and you set a 50% spread for a mid-level role: Midpoint = $69,770; Minimum = $69,770 ÷ 1.25 = ~$55,800; Maximum = $69,770 × 1.25 = ~$87,200. Use your actual occupation-specific OEWS figure — this arithmetic is the method, not the answer.
For a deeper guide to building posting-safe ranges, see what is a posting-safe salary range and how to write a salary range in a job posting.
Gap 2: Ranges That Don't Reflect Realistic Offer Intentions
California's SB 642 (effective 2026) made this gap legally significant: a range must reflect what the employer reasonably expects to pay upon hire. A band that runs $40,000–$120,000 because no one ever narrowed it is not a good-faith estimate; it's a placeholder. Regulators and candidates now have a stronger basis to challenge ranges that appear designed to avoid disclosure rather than facilitate it.
The fix: when you build your band, also document your posting range — the narrower slice of the full band where you realistically expect to make an offer for this specific hire, given the seniority level, budget, and market conditions at this time. The posting range sits inside the band; the band is the governance structure; the posting range is what goes on the job description.
Gap 3: No Record-Retention Process
Ontario's ESA rules (effective January 1, 2026) require employers to retain postings, application forms, and 45-day interview notifications for a minimum of three years after a posting is removed. While that is a Canadian obligation, US enforcement agencies increasingly expect employers to be able to produce historical posting records in response to complaints.
The operational action: every time you post a role, save a dated copy of the posting — including the salary range as it appeared — to a shared drive or HRIS folder. This costs almost no time and becomes essential if a complaint is filed months later.
Building the Internal Structure Pay Transparency Laws Assume You Have
Pay transparency laws are written as if every employer already has a documented compensation structure. Most small and mid-size employers do not. The law does not care about that gap; it simply penalizes you for the outputs (missing ranges) without acknowledging the inputs (no band framework).
That is why the compliance action is not just "add a range to every job posting." It is "build the band structure that makes ranges consistent, defensible, and maintainable over time." A posting-level fix that is not grounded in a real band structure will produce inconsistent ranges across roles, ranges that drift from offer reality, and exposure the moment a candidate or regulator asks follow-up questions.
The components of a minimal compliant compensation structure are:
- A job leveling framework — defined levels (L1 through L4, or equivalent) with clear scope, autonomy, and impact criteria for each. Levels anchor bands to something other than "what we paid the last person."
- External benchmark data — BLS OEWS by SOC code and metro area, or Statistics Canada NOC-based wage percentiles by province, updated annually.
- A documented band for each level — minimum, midpoint, maximum, with the benchmark source and effective date recorded.
- A posting-range policy — written guidance on how hiring managers derive the posting range from the band, and who approves exceptions.
For a comprehensive guide to building this structure from scratch, see our job band structure complete guide.
The Remote-Posting Problem No One Warned You About
If your company posts any roles as remote — "US-based" or "open to all states" — you may be subject to the requirements of every state with a pay transparency law where a candidate could legally live and work. That is not a hypothetical; Colorado's regulators have explicitly addressed remote postings, and several other states take the same position.
The practical implication for a 75-person company in Ohio that posts remote roles:
- You may have no Ohio pay transparency obligation today.
- But your remote posting may trigger California's, Colorado's, New York's, and Washington's requirements simultaneously — because candidates in those states will see and apply to it.
- Each of those states may have different threshold requirements, different definitions of a compliant range, and different record-retention rules.
The safest approach is to build a band structure that produces a compliant, good-faith range for every role — and then post that range on every job description, everywhere. This is less onerous than managing state-by-state posting variants, and it positions you well as more states enact requirements over the next two to three years.
Your Pre-Posting Compliance Checklist for 2026
Before your team publishes any job posting this year, work through these steps:
Step 1 — Identify applicable jurisdictions. For every role, list the states where the role could be performed (including remote). Check whether any of those states has an active pay transparency law with a posting requirement. Verify thresholds (employee count, role type) with the relevant state agency or counsel.
Step 2 — Confirm you have a documented band for the role. If no band exists, build one before posting. Use a BLS OEWS or Statistics Canada benchmark as your anchor. Document the source, the date, and the calculation method.
Step 3 — Derive a posting range. The posting range is the good-faith slice of the band where you realistically expect to make an offer. Document how you arrived at it.
Step 4 — Format the range correctly. State requirements vary — some require a minimum and maximum; some allow a single figure. BC prohibits open-ended ranges ("$20/hr and up"). California requires a range that reflects expected hire pay, not the full band. Match your format to the strictest applicable requirement.
Step 5 — Save a dated record of the posting. Capture the full posting text, the salary range as posted, and the date. Store it for at least three years. Set a calendar reminder to verify the record-retention period for any new jurisdiction you enter.
Step 6 — Update your bands annually. BLS OEWS releases updated wage data annually. Your bands should reflect current market conditions, not 2022 figures.
Get Your Ranges Ready Before the Next Posting Cycle
The administrative burden of pay transparency compliance is real, but most of it is front-loaded. Once you have a documented band structure, producing a compliant posting range takes minutes. Without that structure, every new hire is a fresh compliance risk.
The Pay Transparency Job Posting Kit gives you the templates, worked examples, and policy language to build posting-ready salary ranges grounded in BLS OEWS benchmarks — whether you're documenting your first band or auditing 50 existing ones. If you want to manage the full band lifecycle in a structured tool rather than a spreadsheet, start a free trial of Job Band Builder and import your current roles in under an hour.
Pay transparency laws by state in 2026 are not going to simplify. Build the structure now, and the next round of new laws becomes an administrative update rather than a compliance scramble. ```
Ready to go beyond the guide?
Build a defensible, BLS-benchmarked band structure in under 30 minutes.