Pay Transparency Laws Just Expanded Again — Here's What HR Operations Actually Needs to Do

Here's the situation: as of this year, 16 states plus D.C. now have statewide pay transparency laws on the books, and Virginia just joined the list — its law took effect July 1. If you're posting jobs in California, Colorado, Connecticut, Hawaii, Illinois, Maine, Maryland, Massachusetts, Minnesota, Nevada, New Jersey, New York, Rhode Island, Vermont, Virginia, or Washington, this isn't optional reading. And if you post remote roles, pay attention to that last part, because it applies to more of you than you think.

I've sat through enough of these rollouts to know the pattern by now. Legal sends a summary. HR operations gets a list of "action items." And then three months later, someone in recruiting posts a role without a pay range because nobody updated the template, and now you're explaining to the CHRO why you're out of compliance in a state you didn't realize you were hiring in.

What These Laws Actually Require (and Where They Differ)

This is the part that trips people up: it's not one law. Each state wrote its own version, and the requirements aren't identical. California, Colorado, and New York are the strictest — they require a pay range in essentially every job posting, full stop. Other states only require disclosure after an interview, upon request, or at the point of hire. Some laws cover job applicants only; a growing number now cover current employees requesting information about their own role too.

This may vary by state and by industry, and laws get amended, so treat this as a starting checklist, not a substitute for your own legal counsel confirming your specific obligations.

The Part Everyone Forgets: Remote Postings

Here's the one that catches multi-state employers off guard every time. If you post a remote role that could be performed from California, and you're headquartered in a state with no pay transparency law, you are very likely still subject to California's requirements — because the job could be performed there. The safe operational default most compliance teams land on is: if your remote posting is open to candidates in any pay-transparency state, write the posting to the standard of the strictest law that could apply. It's more work up front. It's a lot less work than fixing forty postings after the fact.

What HR Operations Should Actually Check This Week

1. Pull your live job postings and sort by state. Not your template — your actual live postings. Templates drift. What's posted right now is what you're liable for right now.

2. Confirm your ATS is enforcing the pay range field, not just offering it. A field that recruiters can skip past is a field that will get skipped past, especially under deadline pressure. If your applicant tracking system allows a posting to go live without a range in a covered state, that's a system gap, not a training gap.

3. Check whether your policy covers current employees, not just applicants. Several of these laws now require you to provide pay range information to existing employees who request it about their own position — not just to candidates. If your process only lives in recruiting, it's incomplete.

4. Get your remote-posting default in writing. Don't leave "which states does this apply to" as a judgment call made fresh every time someone posts a req. Put the default in your job posting SOP so it's consistent regardless of who's doing the posting that week.

5. Loop in whoever owns comp bands. If your posted ranges don't match your actual internal pay bands, transparency laws don't just create a compliance risk — they create an internal equity conversation you'll be having whether you planned for it or not.

One Last Thing

I know this reads like a to-do list, because it is one — that's kind of my whole job. But I'd push back gently on treating this purely as a compliance exercise. Employees increasingly expect pay ranges as a baseline, not a courtesy, regardless of what your state technically requires. Getting ahead of that, rather than doing the minimum your legal team says you can get away with, tends to save you the compliance headache and the trust problem at the same time.

I'll be checking our own postings again this week. If you haven't looked at yours since the last state law took effect, now's a good time.

Questions? Reach out anytime.

support@workplayengage.store

WorkPlayEngage is a product of Dieza Publishing. © 2026 WorkPlayEngage. All rights reserved.

Privacy & Security Note: WorkPlayEngage templates are native Google Sheets. We do not host your data, and we never have access to your employee names or internal metrics. Your engagement remains 100% private within your organization’s Google Drive.

Play:
Baby Pool
Big Guess
NFL Survivor Pool (Coming Soon)
Super Bowl Squares (Coming Soon)
Office Bingo (Coming Soon)

Learn:
How It Works
Shop
Baby Pool
Big Guess
Our Story

Blog:
Employee Engagement
HR Operations
Office Culture
Games & Activities
Whitepapers & Guides

Help

WorkPlayEngage:
Our Story
Contact Us
Blog
Privacy Policy

Social Media