Pay Transparency Laws by State: Disclosure Requirements

Pay transparency has moved from a handful of jurisdictions to a genuine compliance discipline in a few legislative sessions. The obligations come in four distinct forms — posting disclosure, disclosure on request, pay history bans, and pay data reporting — and an employer can be subject to all four in different states simultaneously.

The operational problem is that these laws attach to job postings, which are public, permanent, and screenshot-able. Unlike most HR compliance failures, a violation here is visible to every applicant, every competitor, and every plaintiff's firm running searches.

[VERIFY every jurisdiction, threshold, and effective date in this guide. This area changes every legislative session, several statutes have phased effective dates, and employer size thresholds differ. Confirm each against current state guidance before publishing.]

The Four Types of Obligation

Posting Disclosure States

Colorado was the first state to require pay ranges in job postings, and a substantial group has followed — including California, Washington, New York, Hawaii, Illinois, Minnesota, Maryland, New Jersey, Vermont, Massachusetts, and the District of Columbia, along with several city and county ordinances.

The requirements are not uniform. Key variables:

• Employer size threshold — ranges from a handful of employees to several dozen, and differs by state
• Whether benefits must be disclosed alongside the pay range, which several states require
• Whether the range must include bonuses, commissions, or other compensation
• Whether internal postings and promotional opportunities are covered — several states require notice of promotional opportunities to existing employees
• Whether third-party recruiters must comply, which they generally must
• Penalty structure and whether a cure period exists for a first violation

[VERIFY the current list, thresholds, and specific requirements for each.]

The Remote Posting Problem

This is where multi-state employers get caught.

Several states apply their posting requirements to remote positions that could be performed in the state — not only to positions physically located there. An employer headquartered in a state with no requirement, posting a fully remote role open to candidates anywhere, can be subject to the disclosure laws of every covered state a candidate could work from.

Three approaches, in descending order of risk:

1. Post ranges universally. Include a good-faith range on every posting regardless of location. Simplest, most defensible, and increasingly the market norm. It also removes the risk of a posting being scraped and syndicated into a covered jurisdiction without your knowledge.
2. Post ranges for covered jurisdictions, with geographic variants of the same posting. Workable but administratively heavy, and it fails when aggregators republish.
3. Exclude covered states from remote postings. Legally available in some cases, commercially poor, and expressly restricted in at least one state.

Note the syndication risk in approach 2: job aggregators republish postings without your control, and a posting created for one market can appear in a covered jurisdiction. Universal posting is the only approach that fully removes this.

Building a Good-Faith Range

Every posting statute requires the range to be made in good faith — the range the employer actually expects to pay for the role at the time of posting.

Bad-faith ranges are the most common compliance failure and the most visible. A posting stating $50,000 to $250,000 satisfies nobody, invites complaints, and damages the employer brand more than the disclosure would have.

To build defensible ranges:

• Have actual salary structures. Ranges cannot be disclosed if they do not exist. Employers without job architecture and pay bands must build them first — this is the real work, and it is why pay transparency laws have driven more compensation infrastructure investment than any prior regulation.
• Base ranges on market data and internal equity, documented.
• Keep the range genuinely reflective of what you would pay a strong candidate at the low and high ends.
• Use geographic differentials where you maintain them, and post the range applicable to the location.
• Document the basis for each posted range. If challenged, you need to show how it was derived.
• Review ranges at least annually and whenever market conditions shift.

Our Compensation Training covers structure design, and the Glossary of Compensation Terms defines the underlying concepts.

Pay History Bans

A larger and older group of states and localities prohibits employers from asking about or relying on an applicant's salary history. The rationale is that carrying prior pay forward perpetuates historical pay disparities across an entire career.

Common features:

• Prohibition on asking the applicant, and often on asking prior employers or searching public records
• Prohibition on relying on salary history in setting compensation, even if volunteered
• Permission to discuss salary expectations, which is generally allowed everywhere
• Permission to verify salary history after an offer including compensation terms has been made, in some jurisdictions

Practical steps: remove salary history fields from applications and applicant tracking systems, train recruiters and hiring managers on the specific prohibited questions, and instruct interviewers on what to do when an applicant volunteers the information unprompted — generally, do not record it and do not use it.

The interviewer training matters. A well-meaning hiring manager asking "what are you making now?" in a covered jurisdiction is a violation, and it is the single most common way these laws are breached.

Pay Data Reporting

Several states now require annual submission of pay data, separate from any federal obligation.

California's requirement is the most substantial, covering pay and hours worked by establishment, job category, race/ethnicity, and sex, with a separate report covering workers supplied by labor contractors. Illinois requires an Equal Pay Registration Certificate with associated data. Massachusetts has enacted wage data reporting obligations.

[VERIFY current requirements, thresholds, and deadlines for each — these are recent and have been amended.]

These filings are consequential beyond the filing itself: they produce a dataset that the state, and potentially plaintiffs, can analyze for disparities. Employers should run their own analysis before submitting, ideally under privilege, so that any disparity is identified and understood internally first.

The Internal Consequence Nobody Plans For

Posting ranges externally makes them visible internally, and existing employees will compare their pay to the range advertised for their own job.

This is not a side effect to be managed with communications. It surfaces real compression and equity issues that already existed and were previously invisible.

Prepare for it:

• Run a pay equity analysis before you begin posting ranges, ideally at the direction of counsel so the analysis and any remediation planning are privileged
• Identify employees below the range for their own role and decide what to do — the answer is usually adjustment, and it is better made proactively than in response to a complaint
• Prepare managers with talking points, because they will be asked within days
• Be ready to explain where an employee sits in a range and what moves them through it. "Because that's what you were hired at" is not an explanation that survives contact
• Budget for remediation. Employers that post ranges without adjusting outliers first create a documented, self-inflicted equity problem

Building the Compliance Process

4. Map your jurisdictions — every state and locality where you post, hire, or have remote employees
5. Decide on universal versus targeted posting — universal is strongly recommended
6. Build or refresh salary structures, because ranges require them
7. Update the ATS and posting templates so range fields are required, not optional
8. Brief third-party recruiters and staffing partners in writing — their postings are frequently your liability
9. Remove salary history from applications and train interviewers on what not to ask
10. Run a privileged pay equity analysis before external posting begins
11. Calendar pay data reporting deadlines where applicable
12. Review annually, because this area changes every legislative session

Frequently Asked Questions

Which states require salary ranges in job postings?

A growing group including Colorado, California, Washington, New York, Hawaii, Illinois, Minnesota, Maryland, New Jersey, Vermont, Massachusetts, and the District of Columbia, plus several local ordinances — each with its own employer size threshold and specific requirements. Verify the current list before relying on it.

Do these laws apply to remote job postings?

In several states, yes — the requirement attaches to remote roles that could be performed in the state, not only to positions physically located there. Because aggregators republish postings beyond your control, posting ranges universally is the only fully reliable approach.

What is a "good faith" salary range?

The range the employer genuinely expects to pay for the role at the time of posting, based on market data and internal structures, and documented. Extremely wide ranges are the most common compliance failure and are highly visible.

Can we ask candidates about their salary expectations?

Yes, in essentially every jurisdiction. What is prohibited in pay history ban states is asking about or relying on prior compensation. Train interviewers on the distinction — it is where most violations occur.

What happens if a candidate volunteers their salary history?

In most covered jurisdictions you may not rely on it in setting compensation, even when volunteered. Do not record it and do not use it.

Should we do a pay equity analysis before posting ranges?

Yes, and ideally at the direction of counsel so the analysis and remediation planning are privileged. Posting ranges makes internal disparities visible immediately, and it is far better to have identified and addressed them first.

The Bottom Line

Post ranges universally rather than by jurisdiction — it is simpler, more defensible, and immune to syndication. But do the internal work first: build real salary structures, run a privileged pay equity analysis, and budget for adjusting the employees who sit below the range you are about to publish for their own job. The external compliance is the easy half.

For structured instruction, explore our Compensation Training, work through the Compensation Checklist, or review HR Training by State.