Pay Transparency Laws: What Small Employers Must Do

Every guide to pay transparency opens with a number of states, and the numbers do not agree from one guide to the next. This guide gives its own count once, in the next section, and spends the rest on what a small employer needs: which laws can reach your postings, what a compliant posting contains, what a violation costs, and how one template can cover nearly every state.

That disagreement tells you something important: the number of states is not a useful fact, and chasing it is a trap. The question that actually decides whether you have a problem, and the one no guide leads with, is this: can the person you are about to hire do this job from a state that has a law?

If you post a remote role, the answer is almost certainly yes. In several states the duty attaches to the job rather than to your address. Maryland is the clearest case: no size threshold at all, and a labor department that says an out-of-state company recruiting a Maryland-based remote worker has to post the range.

FirstHR is not a law firm. This is general information rather than legal advice, the law here moves constantly, and if you hire across state lines you should have an employment attorney look at your job posting template once. It is a cheap hour.

The Wrong Question

"How many states have pay transparency laws?" is the question everyone asks, and it is close to useless.

Published sources put the figure at different numbers, and the gap comes from what each one decides to count. By the count this guide uses, fourteen states plus the District of Columbia require the range in the posting, Connecticut the newest of them since October 1, 2026.

So the count is a genuinely unstable fact, and building your compliance on it is building on sand.

What Pay Transparency Is

Pay transparency means being required to tell people what a job pays.

The movement started in Colorado. Its Equal Pay for Equal Work Act took effect on January 1, 2021, and it still asks the most of a posting: it applies to any employer with at least one employee in Colorado, requires a pay range and a benefits description in every posting for a job that can be done in Colorado, and requires notifying employees of promotional opportunities.

Everything since has been a variation on that theme, and the variation is the problem.

The Remote Job Trap

A remote job posting can put you under another state's pay transparency rules even when your own state has none. That is the part of this subject that matters most, and almost nobody writes about it.

Maryland put the position itself at the center of the test. Its labor department states that the wage range duty covers any posting for work performed at least in part in the state, that it binds out-of-state employers, and that it carries no employee-count threshold of any kind.

Colorado draws its line somewhere else, and the difference is worth knowing exactly. Its transparency requirements cover any employer with at least one person employed in Colorado. An employer with nobody there at the time of the hiring decision is outside the Act for that decision, even if it considers Colorado applicants.

What Colorado does not allow is opting out once you are covered. A remote posting counts even where it announces that Coloradans will not be considered, because work performable from anywhere is work performable in Colorado. The first person you employ in the state changes every remote posting you write afterward.

New York applies at just four employees, according to the employer guidance published by the New York Department of Labor. So the moment you write "remote" in a job posting, you have potentially opted into the rules of several states a candidate could work from.

Three Different Obligations, Constantly Confused

Part of why the numbers never agree is that three separate things get lumped together under one heading.

Being clear about which one applies to you matters, because they demand different actions. A posting state requires you to change your job advertisement. An on-request state requires you to train whoever answers the phone. A salary history ban requires you to change what your interviewers ask.

Those are three different fixes, in three different parts of your hiring process, and doing one does not do the others.

The Size Threshold, and Why You Are Probably Covered

The size threshold is lower than most owners assume, and in some states there is none at all. Small employers reach for the size exemption almost reflexively, on the assumption that these laws are aimed at big companies, so look at the actual numbers before you rely on it.

Read the top of the table again. Maryland and Virginia cover every employer, and Connecticut joined them on October 1, 2026. Colorado and the District of Columbia start at one employee, New York at four, and Vermont at five.

That produces a genuinely awkward result for a small business. A six-person company is exempt in California, where the threshold is fifteen, and covered in Maryland, Virginia, Colorado, the District of Columbia, New York, and Vermont. Your headcount does not give you a clean answer. It gives you a different answer per state.

And note what this does to the remote trap. Maryland pairs no headcount threshold at all with a duty that attaches to where the work can be performed rather than to where the employer sits. That combination is why a small business posting a remote job is in scope far more often than it expects.

Pay Transparency Laws State by State

States differ on three things: whether the range goes in the advertisement or only to whoever asks, how many employees you need before you are covered, and what has to sit next to the range. The table covers the states small employers ask about most, and Massachusetts gets a guide of its own here.

The Maryland row is the one to read twice. There is no size threshold at all, so a three-person company advertising a role that will be performed even partly in the state is covered, and the duty runs to internal postings as well. The state labor department publishes a disclosure form employers can use.

Virginia joined the no-threshold states on July 1, 2026, and it pairs the posting duty with a ban on seeking or relying on the wage history of an applicant. Maine arrived four weeks later, on July 29, 2026, at ten or more employees.

Minnesota and Hawaii sit at the other end, at thirty and fifty employees: the highest thresholds in this group, and the ones a small business is most likely to stay below. New Jersey lands in between at ten, and adds a duty to make reasonable efforts to tell current staff about promotions, per the New Jersey Department of Labor.

Rhode Island is an on-request state: the range goes to an applicant who asks, and the statute says the employer should offer it before compensation is discussed. Employees get it at hire, on moving into a new job, and on request. Nevada goes one step further and hands the range to every applicant who has completed an interview, asked for or not.

Connecticut is the newest posting state. Under Public Act 26-12, effective October 1, 2026, every employer, whatever its size, must put the wage or wage range and a general description of benefits in every public and internal job advertisement. The duty also reaches out-of-state positions that report directly to a Connecticut supervisor, office, or worksite.

States with no pay transparency law

Ohio, Utah, and Kentucky have no statewide requirement, and at state level that is the complete answer. Ohio is the complicated one, because four of its cities regulate what the state does not.

Cincinnati and Toledo require employers with fifteen or more employees to provide a pay scale on reasonable request once a candidate has a conditional offer, and both bar salary history questions. Cleveland goes further: since October 27, 2025 its ordinance requires the salary range in the posting itself, again at fifteen employees.

Columbus is the fourth. It has barred salary history questions since March 1, 2024, and its posting rule comes next: employers with fifteen or more employees in the city must put a salary range or scale in job postings, enforced from January 1, 2027.

Oregon belongs in a category of its own. There is no posting requirement, but its Equal Pay Act bars screening applicants on current or past compensation and permits a salary history check only after a conditional offer that names the pay. That applies to any employer with one employee working in the state.

A state without a posting law does not protect the companies headquartered in it, because what usually decides your exposure is where the work can be performed. A Utah or Kentucky business advertising a remote role that a Marylander could fill lands inside Maryland's requirements, not Utah's or Kentucky's.

Pay data reporting is a separate obligation

Pay data reporting is a separate duty from posting a range, and it starts at a far larger headcount. The two get confused because the California bill that created the posting duty also expanded the state's reporting program.

California requires private employers with 100 or more payroll employees to file an annual pay data report with the Civil Rights Department, broken out by job category, race, ethnicity, and sex. The practical read for a small employer: the posting rule can reach you, but the reporting rule does not. Revisit it if you cross a hundred people.

What a Good Faith Range Actually Is

Posting states require a range the employer genuinely expects to pay (a good faith or reasonable estimate, depending on the state). Employers routinely try to meet that requirement by posting a range so wide it says nothing, and regulators have noticed.

California sharpened the definition considerably. Per SB 642, effective January 1, 2026, a pay scale means a good faith estimate of the salary or hourly wage range that the employer reasonably expects to pay for the position upon hire.

The words "upon hire" are doing enormous work there. It is not what the role might pay after three years of good reviews. It is not the full band from entry to senior. It is what you would pay the person you are about to hire, now.

The uncomfortable implication, and the reason many employers resist this, is that you cannot post a good faith range for a role you have not thought about. If you do not know what the job is worth, the law is now forcing you to find out. That work starts with a written job description, which most small businesses also do not have.

What Must Actually Be in the Posting

More than the range, in several states, and this is where employers who thought they had complied discover they have not.

Two rows deserve emphasis.

Internal postings. An employer who carefully fixed their careers page and then promotes people via a quiet conversation in the kitchen has a gap. Several states extend the disclosure requirement to promotions and transfers, and Colorado requires that employees be notified of the opportunity before the selection is made.

Third-party postings. If a recruiter or a job board posts the role, the obligation is still yours. You cannot outsource compliance by outsourcing the posting, and this is a live risk for small businesses that use agencies precisely because they do not have an HR function.

Penalties, and Why They Add Up Faster Than You Think

The number that should get your attention is not the maximum fine. It is the word "per."

Per job. Colorado's official transparency guidance treats each job you advertise without the required disclosures as one violation, however many boards carry it. So an employer that has run non-compliant ads for a year has not committed one violation; it has committed one for every job it advertised.

Enforcement in Colorado is not theoretical either. The state Division of Labor Standards and Statistics publishes the running totals, and its table updated September 4, 2026 shows 2,984 transparency complaints filed since January 1, 2021, 24 citations issued, and $841,500 in citation fines before waivers and settlements.

Those same totals carry a reassuring half. Most employers never reach a citation, because a voluntary compliance letter goes out first, and the division puts the cure rate after that letter at 78.74 percent. Keep copies of your postings and the ranges you used, because those records are what you would produce if the division ever came asking.

The Strictest-State Strategy

The strictest-state strategy is the practical answer here, and it is the only one that survives contact with a small business.

Do not build a different job posting for each jurisdiction. That is a system that requires somebody to correctly identify the applicable law every time they post a role, forever, in a landscape that changes every legislative session. You will get it wrong, and you will get it wrong on the day you are busiest.

Instead: take the strictest applicable state as your baseline and use one template everywhere. It is the same logic that governs the rest of your HR processes: make the compliant path the only path.

Steps one and two produce a list worth writing down once. The Where We Hire sheet takes one row per state you employ in or could hire from, with that state's rule and the date you last read it. The Our Baseline sheet records, for each requirement, which state sets your standard and what your template does about it.

Step three is the part you paste. The block below is the compensation section of a posting, written to carry everything the strictest jurisdictions ask for. Fill in the range and the benefits line once per role, use it for the internal version as well, and send it to any recruiter posting on your behalf.

Is There a Federal Pay Transparency Law?

No, and the absence explains everything else about this subject.

The National Labor Relations Act row is worth pulling out, because employers get it wrong constantly. Per the National Labor Relations Board, most private-sector employees have a protected right to discuss their pay with each other.

That makes a handbook policy prohibiting employees from discussing their salaries unlawful for the non-supervisory staff the Act covers, in every state, whether or not the state has a pay transparency law. Such a policy has been unlawful for a long time, yet a surprising number of small business handbooks still contain one, copied from a template somebody found online.

The pay transparency nondiscrimination provision

Federal contractors used to carry one extra obligation here. A pay transparency nondiscrimination provision, in language prescribed by the Office of Federal Contract Compliance Programs, had to sit in their contracts and their employee handbooks, barring the contractor from disciplining anyone for discussing their own pay or a colleague's.

That obligation came from Executive Order 11246, which was revoked on January 21, 2025. The Department of Labor ordered that office to cease enforcement three days later, and contractors were told to wind down compliance by April 21, 2025.

The regulations caught up afterward. A final rule published on August 21, 2026 rescinds the implementing regulations, including the parts that carried the pay transparency nondiscrimination provision, and it takes effect on October 26, 2026.

So if that clause is still sitting in your handbook, it is no longer a federal contractor requirement. There is no harm in leaving it, because the National Labor Relations Act protects much the same thing for most private-sector employees, though not for supervisors. It is the pay secrecy clause above, not this one, that needs deleting.

Beyond Compliance

Beyond compliance, posting a range is a business decision, with a real cost and real benefits that have nothing to do with law.

What it costs you is the ability to underpay someone who does not know what the role is worth. That is the actual thing being lost, and it is worth being honest that some employers experience it as a loss.

What you get in exchange is that every applicant already knows the number works for them. Nobody goes through four interviews and then discovers you are twenty thousand dollars apart. Your candidate pool is smaller and enormously better qualified, in the specific sense that they have already accepted your economics, which shortens the whole recruitment process.

And there is a harder benefit. A posted range forces you to decide what the role is worth before you meet anybody, which prevents the most common source of internal pay inequity in a small business: paying whatever the individual negotiated.

Two people doing the same job on different pay, because one asked harder, is exactly the pattern these laws exist to break. It is also exactly the pattern an informal small business drifts into without ever deciding to.

Deciding the number in advance, and writing it down, is not a compliance chore. It is the foundation of a defensible pay structure, and you were going to need one eventually anyway.

So the benefits of pay transparency come down to three: fewer wasted interviews, a pay structure you can defend when someone challenges it, and a recruiting signal you get for nothing while competitors are still advertising a "competitive salary."

There is a second cost, and it arrives first. The people already on your team will read the range you posted and work out where they sit inside it. Have an answer ready before the posting goes live, because that conversation is coming either way.

Common Mistakes

These recur, and the first two account for most of the exposure.

The unifying error is treating this as a research problem. It is not. Research gives you a number that is wrong, from a chart that is out of date, about states you may not be in.

It is a template problem. Build one job posting that would satisfy the strictest state you could hire from, use it everywhere, and the research question dissolves. That takes an afternoon, and after it the only upkeep is the annual re-check.

Frequently Asked Questions