Pay Transparency Laws 2026: Virginia, Maine, Delaware & the Multi-State Hiring Trap

If your job postings have looked the same since 2023, this is the summer to check. Two states added salary-range requirements to their books in the last eight weeks alone — Virginia on July 1 and Maine on July 29 — and a third, Delaware, has a law on the calendar for September 2027 that hiring teams are already being told to plan around now. Meanwhile the states that moved first are no longer in a grace period: Massachusetts closed out its first year of active enforcement in October, and New Jersey's regulator has been assessing real penalties for over a year.

None of this is really "news" in the sense of a single event. It's a trend that keeps compounding, one state legislative session at a time, and 2026 has been an unusually busy year for it. What follows is a state-by-state look at what actually changed, why the enforcement risk is no longer theoretical, and the specific trap this creates for any team hiring across more than one state — which, for most employers running a single job board or ATS, is most of them.

The map, as of this summer

A state requiring a salary range in the posting itself — not just "on request," which is a weaker and older generation of these laws — now includes at minimum California, Colorado, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont and Washington, plus Washington D.C. Colorado was first, back in 2021; the rest followed at a steady clip.

Three more arrived or are queued in 2026 alone:

Virginia — effective July 1, 2026 (SB 215). Requires a good-faith wage or salary range in public and internal postings for external hires, promotions and internal transfers, and separately bans employers from seeking an applicant's salary history. What makes Virginia's version unusual is enforcement: the law creates a private right of action, gives employers a 15-business-day cure window after written notice, and — notably — lets anyone, not just an applicant or employee, send that notice. A posting that's missing a range is flaggable by a third party who was never going to apply for the job.
Maine — signed April 24, 2026, effective July 29, 2026 (LD 54). Applies to employers with 10 or more employees and requires a "range of pay" in job postings, whether the posting comes directly from the employer or through a third party (a staffing agency, a job board, a recruiter). Positions paid solely by commission get an explicit carve-out, but they still have to say so.
Delaware — signed September 26, 2025, effective September 26, 2027 (HB 105). Applies to employers with more than 25 employees. First offense draws a written warning; each subsequent violation carries a civil penalty of $500 to $10,000, enforced by the Delaware Department of Labor. Records of job descriptions and wage rates have to be kept for at least three years after an employee separates.

Delaware's effective date is a year out, which is exactly why it belongs in this piece now rather than next August. A law with a long runway is the one hiring teams are most likely to file away and forget until the quarter it actually lands.

The states that already have a track record

The newer laws are interesting because of what's coming. The older ones are interesting because of what's already happened.

Massachusetts' salary-range law took effect October 29, 2025, covering employers with 25 or more employees and requiring wage ranges in job postings, in offers for new positions, and on request from current employees. It's enforced exclusively by the Attorney General's office, and the penalty structure escalates deliberately: a warning for a first offense, up to $500 for a second, up to $1,000 for a third, and — starting at the fourth offense — civil penalties that can run from $7,500 to $25,000 per violation. Employers get a two-business-day cure window through October 2027, after which that grace period disappears. Ten months in, Massachusetts is no longer a "new law" in any meaningful sense; it's an active enforcement regime with a real ceiling on the fine.

New Jersey's Pay and Benefits Transparency Act has been live even longer — since June 1, 2025 — and requires employers with 10 or more employees to include wage ranges and a general benefits description in job postings, and to notify current employees of promotional opportunities. There's no private right of action, so it can't turn into direct litigation from a candidate, but the state Department of Labor can and does levy penalties: up to $300 for a first violation and up to $600 for each one after that. Smaller numbers than Massachusetts, but over a year of live enforcement means "we didn't get around to updating our template" is no longer a plausible excuse to a regulator asking about it.

Put those two together and the shape of the trend is clear: the states that led on pay transparency aren't easing off. They're settling into steady-state enforcement, with penalty structures built to escalate for employers who don't fix the problem after being told.

Why this is a worse problem for remote and multi-state postings than it looks

Here's the part that trips up hiring teams who've only skimmed the headlines: these laws generally apply based on where the job can be performed, not where the company is headquartered. A remote-eligible role posted by a New York-based employer can trigger Colorado's requirements, Washington's, Illinois's — whichever states the role is actually open to, because the whole point of the laws is protecting applicants in that state, not regulating companies incorporated there.

The practical consequence: a single job posting for a remote or multi-state role has to satisfy the strictest applicable law among every state it reaches, not the law of wherever the req originated. A generic "competitive salary" posting that's fine in a state with no requirement at all can be a live violation the moment it's also visible to an applicant in Colorado or New York. Most applicant tracking systems don't handle this distinction automatically — the range field, if it exists at all, is usually one field per job, not one per audience.

This is also where "good faith" stops being a throwaway phrase. Several of these statutes specifically require the posted range to be one the employer actually intends to pay, set in good faith — not a defensive placeholder spanning, say, $40,000 to $250,000 to cover every possible candidate. Regulators reviewing complaints are looking at whether the range is real, and a range wide enough to be meaningless invites exactly the kind of scrutiny it was meant to avoid.

A working checklist, not a compliance memo nobody reads

For a talent-acquisition or HR team hiring across more than one US state in 2026, the useful version of this article is short:

Inventory where each open req is actually postable from, not just where it's headquartered. Remote and hybrid roles need the broadest applicable range.
Treat the salary range as a required field for every posting, not an optional one filled in only for states where it's obviously mandatory — the whole point of "strictest applicable law" is that the mandatory list is bigger than most teams assume, and it keeps growing.
Keep the range genuine. A range that's obviously padded to avoid ever being wrong is the pattern several of these laws were specifically written to catch.
Retain the records. Delaware and Maine both require multi-year recordkeeping of the ranges posted and paid — which means a posting's range needs to be preserved somewhere after the req closes, not just live on the page while it's open.
Re-check your template on every new hire in a new state, because the applicable law can change the moment a role becomes open to a new location — and, per Virginia's model, the person who notices a gap doesn't have to be a candidate.

Where this sits for us

We build hiring software at NiceHire — job postings, structured pipelines, screening — and this is exactly the category of requirement that has to live inside the workflow a recruiter uses every day, not in a policy document HR sends around once a year. A salary-range field that's easy to skip is a field that will get skipped under deadline pressure, and a law like Virginia's — where anyone can flag a missing range, not just a candidate — makes "we'll fill it in later" a genuinely risky habit rather than a minor oversight. That's the standard we think any hiring platform, including ours, should be measured against: not whether the feature exists somewhere in the product, but whether the default behavior makes the compliant choice the easy one. We don't have a specific product claim to make here today — this is a workflow-design problem we're actively thinking about, not a solved one — but it's exactly the kind of trend that should change how a hiring platform is built, not just what a compliance team reads about it.

Sources: Virginia Department of Labor and Industry — new legislation effective July 1, 2026; Morgan Lewis — "Virginia Law Will Require Pay Transparency, Restrict Employers from Seeking Wage History"; Morgan Lewis — "Maine Passes Pay Transparency Law"; Morgan Lewis — "Delaware Passes Pay Transparency Law: Implications for Covered Employers"; Ogletree Deakins — "Delaware's New Pay Transparency Requirements to Take Effect in 2027"; Ogletree Deakins — "New Jersey's Tightened Pay Transparency Requirements Take Effect June 1, 2025"; Massachusetts Attorney General — "Pay Transparency in Massachusetts"; Seyfarth Shaw — "Massachusetts Pay Transparency Law Takes Effect: What Employers Need to Know".