Pay Transparency Laws by State: 2027 Compliance Guide

Pay transparency compliance in the United States is a jurisdiction-by-jurisdiction problem, not one national posting rule. Employers recruiting across multiple states, hiring remotely, or moving employees through promotions and transfers may need to account for different salary-range disclosure triggers, employer-size thresholds, benefits requirements, employee-request rights, salary-history restrictions, recordkeeping rules, and local ordinances.

For 2027 planning, the most important new deadline currently on the calendar is Delaware's statewide pay transparency law, which takes effect September 26, 2027. Virginia's statewide job-posting range requirement took effect July 1, 2026, and Maine's new pay-range posting law took effect July 29, 2026. Existing requirements in California, Colorado, Illinois, Massachusetts, Minnesota, New Jersey, New York, Vermont, Washington, Washington, D.C., and other jurisdictions remain part of the compliance map.

Legal review notice: This guide provides general operational information, not legal advice. It was reviewed on August 25, 2026. Pay transparency, equal pay, salary-history, recordkeeping, and local requirements can change. Before relying on this guide for a live posting or employment decision, confirm the current statute and agency guidance for every applicable jurisdiction and consult qualified employment counsel.

Client-reference verification note: This article was restructured around the client-provided 2026 U.S. Pay Transparency Laws Executive Reference Guide. Every federal, state, and municipal jurisdiction listed in that reference is addressed below. Legal statements were then rechecked against current government or legislative sources. Where the client reference and current official sources differ, this guide identifies the difference rather than silently carrying forward an outdated or broader statement.

Why Pay Transparency Laws Matter for Multi-State Employers

Pay transparency has moved from an HR best practice into a legal requirement in many jurisdictions. For organizations operating across states, recruiting nationally, or hiring remote employees, the challenge is the patchwork itself: one jurisdiction may require a salary range in the job advertisement, another may require disclosure only before an offer or after an interview, and another may add benefits, internal opportunities, employee requests, or recordkeeping obligations.

The compliance question is therefore broader than, "Did we put a salary range in the posting?" Employers increasingly need a repeatable process for determining which rule applies, what must be disclosed, what evidence supports the range, and how the same approved information is carried through the careers site, applicant-tracking system, recruiter brief, job board, internal opportunity, offer process, and employee request.

Federal Pay Transparency Baseline

There is no single general federal law that requires private employers nationwide to include a salary range in every ordinary job posting. Federal law still creates an important compensation baseline, however, and state pay-transparency rules sit on top of those protections.

What Changes for 2027?

The 2027 compliance calendar is not only about laws that begin in 2027. Employers entering 2027 must also account for state rules that became effective during 2025 and 2026 and may already apply to their active postings.

• Virginia: Beginning July 1, 2026, Virginia requires wage or salary ranges in job postings and hiring advertisements and prohibits seeking an applicant's wage or salary history. See the Virginia Department of Labor and Industry guidance.
• Maine: Public Law 2025, Chapter 771 was enacted and signed April 24, 2026. Because it was a nonemergency law from Maine's Second Regular Session, it took effect on the session's general effective date, July 29, 2026. Employers with 10 or more employees must include the prospective range of pay in covered postings; employees can request the range for their current position, and position/pay history records must be maintained. See Maine LD 54 / HP 18.
• Delaware: House Substitute 2 for House Bill 105 was signed September 26, 2025 and takes effect September 26, 2027. It applies to employers with more than 25 employees and requires salary or wage range information plus a general description of benefits in covered postings, along with applicant access and recordkeeping requirements. See the Delaware General Assembly bill record.

Important correction to the client reference: the client PDF lists Delaware with a 2025 effective date. Official Delaware records show that the law was signed on September 26, 2025 but becomes effective September 26, 2027.

Pay Transparency Laws by State and Jurisdiction

The table below keeps every state and district included in the client reference and adds the operational distinctions that matter for a 2027-ready workflow. It is a compliance reference, not a substitute for jurisdiction-specific legal advice.

Municipal and Local Pay Transparency Rules

State law is not the only layer. Cities and counties can impose additional or more specific requirements. The client reference identifies New York City, Ithaca, Westchester County, Jersey City, Cincinnati, Toledo, Philadelphia, and Kansas City. Those local rules do not all do the same thing. Some require ranges in postings; others focus on salary-history inquiries or later-stage pay-scale disclosure.

Not Every Pay Transparency Law Is a Job-Posting Law

One of the easiest ways to misread the state map is to treat every transparency law as the same requirement. The client reference itself includes several different legal models, and a compliant workflow needs to preserve those differences.

• Posting disclosure: California, Colorado, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, Washington, Washington, D.C., Virginia, Maine, and, beginning in 2027, Delaware use some form of job-posting or advertisement disclosure within their scope.
• Later-stage or request disclosure: Connecticut and Nevada are important examples where disclosure can be triggered by an applicant request, offer, completed interview, promotion, transfer, or employee request rather than only by a public job advertisement.
• Benefits and other compensation: Colorado, Illinois, Maryland, Minnesota, New Jersey, Washington, and Delaware's 2027 law are among the jurisdictions where employers need to look beyond the base salary range and check benefits or other-compensation disclosure requirements.
• Salary-history restrictions: Nevada, Washington, Washington, D.C., Virginia, Cincinnati, Toledo, Philadelphia, Kansas City, and other jurisdictions restrict how salary history can be requested or used.
• Employee rights: several states require employers to provide current employees with range information at specific points or on request, and federal law protects wage discussions for employees covered by the NLRA.

How Remote and Multi-State Job Postings Change the Analysis

The original draft overstated the remote-work rule by suggesting that one remote posting can simply be treated as subject to every state's law and solved by publishing one broad national range. That is not a reliable legal test. Each jurisdiction defines its geographic trigger differently.

For example, California guidance applies its posting rule when a position may ever be filled in California. Washington guidance can reach remote postings that could be filled by a Washington-based employee. New York's statewide law can cover work performed outside New York when the position reports to a New York supervisor, office, or worksite. Vermont defines covered remote jobs using its own relationship to a Vermont office or work location. Delaware's 2027 law includes its own Delaware-based and non-international remote-position language.

A national disclosure policy can still be a useful administrative choice, but it is a company policy choice, not proof that every jurisdictional requirement has been satisfied. For every posting, the compliance owner should map:

1. The physical work location and any permitted remote locations.
2. The employer entity and headcount threshold that applies.
3. Whether the opportunity is external, internal, a promotion, or a transfer.
4. Whether the jurisdiction requires a range, fixed rate, benefits, other compensation, a job description, an application deadline, or another disclosure.
5. Whether there are applicant or employee request rights even when no posting is required.
6. Whether a third-party recruiter or job board is involved and who controls the published content.
7. What records must be retained and for how long.

What Makes a Salary Range Defensible?

Many state laws use a good-faith concept, but the statutory definition and evidence standard are not identical everywhere. A compensation team should therefore separate the legal question from the operating question.

The legal question is what a specific state requires. The operating question is whether the organization can reproduce the basis for the range it published. That is easier when the role has a current job description, a documented level or grade, an approved job architecture, current market context, a salary structure, and an approval record. CompBldr's Market Benchmarking workflow can support the compensation-data and range-governance side of that process, but software does not determine which law applies or guarantee legal compliance.

For a deeper California-specific example of how good-faith range language interacts with job structure and recordkeeping, see the California pay transparency law guide.

Existing Employees, Promotions, Transfers, and Wage Discussions

Pay transparency obligations do not stop at recruiting. The client reference specifically calls out employee rights, and several jurisdictions require range disclosure during employment.

California employees can request the pay scale for their current position. Connecticut requires range disclosure at hire, when an employee's position changes, or on the employee's first request. Massachusetts requires disclosure at specified promotion, transfer, and request points. Nevada provides a range for a promotion or transfer when the statutory conditions are met and the employee requests it. Maine requires disclosure of the range for the employee's current position on request. Washington requires range disclosure for certain internal transfers and promotions on request.

Separately, the National Labor Relations Act protects covered employees' right to discuss wages. Employers should not treat a pay-transparency rollout as permission to adopt wage-secrecy rules. State and local laws can add their own protections.

Penalties and Enforcement Risk Vary by Jurisdiction

There is no single nationwide penalty schedule for pay transparency violations. Enforcement authority, cure periods, civil penalties, complaint procedures, private rights, and retaliation protections differ from state to state and can change through amendments or regulations.

For that reason, this guide does not reuse one penalty figure across jurisdictions. The safer process is to link each internal legal register entry to the official statute or agency guidance, record the last review date, and have counsel validate the enforcement section that applies to the employer's actual workforce and posting footprint. Local rules can also be stricter. Jersey City, for example, states that violations of its pay-transparency ordinance can carry fines of up to $2,000.

How to Build a 2027-Ready Pay Transparency Compliance Process

A strong 2027 process treats legal monitoring and compensation governance as connected but separate responsibilities. The law determines what must be disclosed. The compensation system determines whether the employer can produce and maintain an approved range consistently.

1. Maintain a jurisdiction register. Track state and local law, effective date, employer threshold, geographic trigger, posting fields, internal-opportunity rules, applicant/employee rights, salary-history restrictions, recordkeeping, source URL, owner, and last legal review date.
2. Map each requisition before publication. Capture work location, remote eligibility, reporting location, employing entity, headcount, and whether the opportunity is a new job, promotion, or transfer.
3. Validate the job before validating the range. Confirm job description, family, level, grade, and location. A range attached to the wrong job is still a governance failure even when the number itself looks plausible.
4. Use an approved compensation basis. Connect the posting range to a governed salary structure and relevant market benchmarking evidence rather than a recruiter-created estimate with no owner.
5. Build the exact disclosure package. Depending on the jurisdiction, that may include salary/wage range, fixed rate, benefits, other compensation, job description, application timing, or another required statement.
6. Synchronize every posting channel. Check the careers site, ATS, recruiter copy, external job board, social post, internal posting, and agency brief. A compliant master record does not help if a stale third-party copy remains live.
7. Handle promotions, transfers, and employee requests separately. Do not assume the external posting workflow satisfies internal disclosure rights.
8. Preserve the evidence. Keep the approved range, job/grade basis, effective date, approver, posting snapshot, changes, and any records specifically required by the jurisdiction.
9. Review laws on a defined cadence. Recheck before a new state launch, before opening remote eligibility, when a law's effective date approaches, and at a scheduled legal-review cadence rather than relying on an old spreadsheet indefinitely.
10. Run legal and compensation QA before publish. Legal determines whether the rule applies. Compensation validates the job and range. Recruiting validates the posting. No one function should silently own all three.

A Practical 2027 Compliance Checklist

• The job's physical and remote work locations are documented.
• The correct employing entity and employer-size threshold have been checked.
• The team has confirmed whether the opportunity is external, internal, a promotion, or a transfer.
• The salary or wage range reflects the approved job/grade and the employer's actual compensation intent.
• Benefits and other compensation are included when the applicable rule requires them.
• The job description and other posting fields are included when required.
• Salary-history questions have been removed where prohibited.
• Employee-request and internal-mobility rights have a separate workflow.
• Third-party recruiters and job boards have the same approved disclosure data.
• Posting snapshots, range versions, and required records are retained.
• The internal legal register links to the current official statute or agency guidance.
• The review date is current enough for the posting, especially for a 2027 law or newly amended rule.

What the Client Reference Adds to the Compliance Model

The client reference is useful because it frames pay transparency as more than a recruiting-field requirement. It connects salary disclosure, employee rights, wage-discussion protections, equal-pay law, state and local variation, and the need for fair, consistent, well-governed compensation practices. That broader framing is now preserved throughout this article.

At the same time, the reference should not be treated as the final legal source. Its Delaware effective date needed correction, its Oregon row was broader than the statewide job-posting law we could verify, and several municipal entries are salary-history rules rather than salary-range posting mandates. The revised guide keeps all of those jurisdictions while distinguishing what each rule actually does.

The Bottom Line for HR and Compensation Teams

There is no single "pay transparency law" that a national employer can check once and reuse everywhere. By 2027, employers need a controlled workflow that can answer five questions for every opening: Which jurisdiction applies? What must be disclosed? When must it be disclosed? What approved compensation evidence supports it? What record proves the process was followed?

Virginia and Maine are already part of the 2026 operating environment, while Delaware becomes a major 2027 deadline on September 26, 2027. Existing state and local rules remain active and continue to evolve. Multi-state employers should build the compensation foundation once, maintain the legal rule set separately, and connect the two through a documented review and approval process.

For employers operating in Europe as well as the United States, keep the legal frameworks separate. The EU Pay Transparency Directive guide for US employers covers the EU operating model, national implementation, worker requests, reporting, and governance.