US pay transparency laws, state by state

No. As at September 2026 there is no federal statute requiring US employers to disclose pay ranges. The obligations are set state by state, and in some cases by city ordinance. Federal contractors face separate requirements, and equal pay obligations under federal law are distinct from disclosure obligations.

As at September 2026 the posting-disclosure jurisdictions are Colorado, California, Washington, New York State, Hawaii, the District of Columbia, Maryland, Illinois, Minnesota, New Jersey, Vermont and Massachusetts, together with city ordinances including New York City. Employee-count thresholds differ: the District of Columbia and Maryland apply to essentially all employers, while Hawaii applies only at 50 or more employees. Confirm the current position with counsel, because states amend these rules regularly.

In practice, yes. The obligations generally attach to where the work can be performed rather than where the employer is headquartered, so a posting advertised as remote across the US can be filled from a disclosure state and picks up that state's requirement. The practical result is that a remote-eligible US posting is governed by the strictest state it could be filled from, which is why many multi-state employers now apply one standard nationally.

A range reflecting what the employer genuinely expects to pay for the role at the time of posting. The recurring compliance problem is the range drawn so wide that it discloses nothing in practice. Several states have issued guidance treating implausibly wide bands as non-compliant, and at least one requires a fixed range with no open end. Anchoring the posted range to a real internal band for a single level, rather than covering several levels at once, resolves most of this.

In several states, yes. Washington and Maryland, among others, require a general description of other compensation and benefits alongside the base range. A base-only posting can be non-compliant in those jurisdictions even where the base range itself is sound. Because US total compensation is frequently weighted toward bonus and equity, a base-only disclosure also tends to understate the package to candidates.

They are separate obligations that are often confused. Pay transparency requires the employer to disclose what a role pays. A salary history ban prevents the employer from asking a candidate what they currently earn. A larger group of states restricts salary history questions than requires range disclosure, and employers who have addressed only the posting requirement frequently miss the second obligation.

Candidates now anchor to the top of a published band rather than to their own current salary, particularly in states that also prohibit salary history questions. Offer strategies built on an information advantage no longer work. The practical response is to set the posted range from external benchmark evidence and be prepared to explain where in the band an individual sits and why.

Yes, in a direction the legislation did not set out to achieve. Publishing different ranges for the same remote role across different states proved harder to sustain than compressing them, so many multi-state employers have narrowed published geographic differentials rather than defending each one. For remote-eligible roles this has been one of the clearest observable effects.

As one input, and a genuinely useful one. Published ranges give a continuous, dated, employer-stated record of what named competitors say they will pay in named locations, and movement in a competitor's posted ceiling is often an earlier scarcity signal than any survey. But a posted range is a policy band, not where offers land, so it should be paired with verified primary research rather than used alone.

Enforcement varies by jurisdiction and typically involves civil penalties per violation, with some states providing a cure period for a first breach and some allowing private claims. Penalties are generally modest per posting but can accumulate across many advertisements. The more material exposure for most employers is reputational and internal: a non-compliant or implausible range is visible to every candidate and every existing employee.

Map exposure before anything else: list every state you employ in, plus every state a remote-eligible role could be filled from. The second list is usually longer and it determines the actual obligations. Then decide a single posting standard as policy rather than per requisition, and audit band architecture for compression and overlap before publishing, because publishing makes an existing structure legible rather than fixing it.

No, and this is the gap most often missed. A published range tells candidates what you will pay. It says nothing about how many qualified people exist within reach of that number in that location. A compliant, well-evidenced range that no qualified person will accept is still a failed requisition. Counting the population reachable at a given band is a talent mapping question, not a compliance one.