Pay Transparency by State: What a Small Business Actually Has to Do in 2026

You wrote a job posting, you were about to hit publish, and someone — a board member, a candidate, a nagging memory of a LinkedIn post — said: "wait, don't you have to put the salary in there now?"

The honest answer is: maybe. It depends on where the work happens, how many people you employ, and which year it is, because the list of states with rules keeps growing. Five years ago this was a Colorado curiosity. Today around a dozen states and the District of Columbia have some version of a pay-disclosure law, and they do not agree with each other on the details.

I've spent twenty years inside people operations watching compliance rules go from "thing a couple of big states do" to "thing that quietly applies to your eight-person remote team." Pay transparency is one of the fastest-moving examples I've seen. So this is the plain-English version: what's actually required, the patterns that let you reason about any state, the one trap that catches employers who think they're exempt, and the single default that covers most of it without a lawyer on retainer.

The short version

If you don't want to read the whole map, here's the move that covers you in nearly every situation: put an honest salary range in every job posting, everywhere, by default.

It's almost never wrong. No state penalizes you for being more transparent than required. It removes the question of "does this state count" for the role you're hiring. It satisfies the on-request states automatically. And it happens to be a hiring advantage, which I'll get to at the end. The only places you need to do more than a range are a handful of states that also want a benefits description or an application deadline — and I'll name them.

If that's all you needed, take it and go. If you want to understand why, so you can make the call on any state without re-reading an article every time, keep going.

Why this is suddenly everywhere

Colorado went first, in 2021, with a posting law that required a salary range and even a benefits description. For a while it was the outlier — you'd see job ads that said "not available to Colorado applicants," which was companies trying to dodge one state's rule.

That didn't hold. New York, California, Washington, and Illinois followed. Then a second wave — Maryland, Minnesota, New Jersey, Vermont, Massachusetts — with more arriving on a near-annual cadence. The "carve out the state" workaround got restricted. And the laws started reaching past their own borders through remote work, which is the part most small employers miss.

The practical takeaway isn't "memorize twelve statutes." It's that this is now a permanent, expanding feature of hiring in the U.S., and the smart posture is to build your process around it once rather than react state by state.

The five patterns that actually matter

Every one of these laws is a different combination of the same handful of variables. Learn the variables and you can read any state's rule in about a minute.

1. Who's covered (the employee threshold)

This is where states differ most. Some have no threshold at all — one employee in the state and you're covered (Colorado, Maryland, Washington D.C.). Others kick in at 4 (New York), 10 (New Jersey), 15 (California, Washington, Illinois), 30 (Minnesota), or 50 (Hawaii) employees. And "employees" sometimes means everyone you employ nationwide, not just the ones in that state — Illinois counts your whole headcount toward its 15.

2. What you actually disclose

Three flavors. Most states want a good-faith pay range in the posting. A few want more than the range — Colorado, Washington, and Minnesota also require a general description of benefits and other compensation, and Colorado adds the date the application window closes. And one state, Rhode Island, isn't a posting rule at all — it requires you to give the range to an applicant on request and to new hires, which is exactly why "just post it" covers you there too.

3. The remote-work reach (this is the trap)

Here's the part that catches the small employer who's sure they're exempt. Most of these laws apply not just to jobs physically located in the state, but to remote roles that could be performed by someone in the state, or that report to a manager or office there. So a fully-remote company headquartered in Texas, hiring a remote coordinator, can be on the hook for New York's or California's rule the moment a New York or California resident could plausibly fill the seat. "We're not in that state" is not the shield people think it is.

4. No open-ended ranges

Where a range is required, it has to be a real one — lowest to highest you genuinely expect to pay. "$60,000 and up" or "up to $90,000" doesn't satisfy the laws that bother to define it (Colorado, Minnesota, New Jersey, and others say so explicitly). If the role pays a fixed rate, post the fixed rate. The point is good faith, not a number so wide it's meaningless.

5. The extras some states bolt on

A few states add obligations beyond the posting itself: promotion notices to current employees (New Jersey, Illinois), a healthcare-benefits disclosure before the first interview (D.C.), and salary-history bans that prohibit asking what a candidate made before (Rhode Island, D.C., and many others). These don't change the posting much, but they change your process — worth knowing which ones apply to you.

The states with an active rule right now

As of mid-2026, these eleven jurisdictions each have a dedicated page here with the specifics — threshold, exactly what to disclose, penalties, and the official source — so you can confirm the detail for wherever you're hiring:

• New York — 4+ employees, range in the posting
• California — 15+ employees, pay scale; strong remote reach
• Colorado — no threshold; range + benefits + application close date
• Washington — 15+ employees; range + benefits + other comp
• Illinois — 15+ employees (counted nationwide); pay scale + benefits
• Maryland — no threshold; range + benefits + other comp
• Rhode Island — all sizes; disclose on request, not in the posting
• Hawaii — 50+ employees; rate or range in listings
• Minnesota — 30+ employees; range + benefits, no open-ended
• New Jersey — 10+ employees; range + benefits + promotion notice
• Washington, D.C. — no threshold; range + pre-interview benefits disclosure

Two more are already live as of this writing and just don't have their own page here yet: Massachusetts (employers with 25+ Massachusetts employees, effective October 2025) and Vermont (5+ employees with at least one in Vermont, effective July 2025). Dedicated pages for both are on the way.

The list grows. If you're reading this a year from now, assume a couple more states have joined — which is another reason the "post the range everywhere" default beats playing whack-a-mole.

What to actually do

Here's the operator's checklist. Seven moves, in order.

1. Default to posting an honest range on every job, everywhere. This is the whole game for most employers. It satisfies the in-posting states, the on-request states, and the remote-reach trap in one decision.
2. Make the range real. Lowest to highest you'd genuinely pay. No open-ended figures. If it's a fixed rate, say the fixed rate.
3. Add benefits and a close date where required. For Colorado, Washington, and Minnesota, include a short general description of benefits and other compensation. Colorado also wants the date the posting closes. One reusable block of text handles this for every posting.
4. Watch remote roles especially. If a role can be done from anywhere, treat it as covered by the strictest state a likely applicant could sit in. Don't try to thread the needle.
5. Don't exclude states. The "not open to [state] applicants" trick is restricted in the places it mattered and reads terribly to candidates everywhere. Skip it.
6. Mind the process extras. If you hire in D.C., disclose healthcare benefits before the first interview. If you hire in New Jersey or Illinois, make reasonable efforts to tell current staff about promotions. And drop the "what did you make before?" question from your interviews — the salary-history ban is now common enough that it's a good universal default anyway.
7. Keep records and re-check quarterly. Several states require you to keep the ranges and job descriptions you used (Maryland says three years). And because the map changes, put a recurring 30-minute calendar block to check whether a new state now applies to you.

That's it. Most of this collapses into "write one good range and one benefits blurb, reuse them, and don't get cute about remote." The administrative weight is small once the habit is set.

The part nobody tells you: it's a hiring advantage

Employers treat pay transparency as a compliance chore, and that's a missed read. Candidates — especially the good ones with options — self-select toward postings with a range and away from the ones that hide it. Posting the number filters out the people who'd waste three interviews only to balk at the offer, and it signals that you're a company that doesn't play games on comp. For a small business competing against bigger names on something other than salary, that signal is worth more than the compliance box it checks.

So the framing I'd push: you're not grudgingly complying with a dozen statutes. You're adopting a hiring practice that happens to also be the law in a growing number of places. That's a much better way to carry it.

Closing

The rules will keep multiplying — more states, more edges, the occasional city ordinance that's stricter than its state. You can either track every one of them as it lands, or you can build your posting process around the safe default now and stop thinking about it: honest range on every job, benefits blurb where required, no open-ended numbers, no excluding states, records kept, a quarterly glance at the map.

Do that and the dozen-state patchwork becomes a non-event — a paragraph in your posting template instead of a fire drill every time you open a req. That's the whole point of building the system once instead of reacting to it forever.