Multi-State Hiring: Managing Pay Transparency Across Jurisdictions
A remote role can trigger several states' disclosure laws at once. Here's how to manage pay transparency across multiple jurisdictions.
Rovaryn Digital · May 21, 2026
The Remote Posting Problem Nobody Plans for Until Friday Afternoon
Picture this: your company is headquartered in Chicago, you have a handful of employees working remotely in Colorado and California, and you just got approval to hire a senior account manager. The job will be remote — "work from anywhere in the U.S." — so your HR generalist drafts the posting, uploads it to your ATS, and syncs it to three job boards.
By the time it goes live, you may have triggered pay-transparency disclosure obligations in Illinois (where you're headquartered), Colorado (where some of your team already sits), California (same situation), Washington State, New York, New Jersey, and Washington D.C. — depending on how each jurisdiction interprets "remote" postings and how many employees you have in each state.
That is not a hypothetical designed to frighten you. It reflects the reality that as of 2026, 16 states plus Washington D.C. mandate salary disclosure in job postings, with Delaware joining in 2027 (Paycor / Nesco Resource, 2026). For any employer running a distributed team or posting roles open to remote applicants, multi-state hiring pay transparency is no longer a single compliance checkbox — it is a systems problem that requires a documented, repeatable approach.
By the end of this article you will understand which jurisdiction's rules apply to which posting, how to structure salary ranges that work across borders, and what documentation you need to show an employment attorney that your methodology was sound.
Why "Remote" Multiplies Your Jurisdiction Count
The central complexity in multi-state hiring pay transparency is this: disclosure obligations are not triggered only by where your company is incorporated or where your main office sits. They are triggered by where a worker could perform the job — and in some cases, by where the posting is accessible.
Each state that has enacted a pay-transparency posting law draws that line slightly differently. Here is what the current law requires in the jurisdictions most likely to affect a distributed US employer, based on the statutes and regulatory guidance in force as of mid-2026. Confirm the current threshold and effective date with the relevant authority or employment counsel before acting — these rules continue to evolve.
Colorado. The Equal Pay for Equal Work Act (SB19-085, effective January 1, 2021, amended January 1, 2024) applies to any employer with at least one Colorado employee. The Colorado CDLE's guidance has addressed remote postings directly: if a role can be performed in Colorado, the posting must include a salary range. As of July 1, 2024, the CDLE had assessed $238,000 in fines across 1,634 complaints (Trusaic citing Colorado CDLE, 2024). Fines run $500–$10,000 per violation, and each non-compliant posting is a separate violation (Colorado General Assembly, SB19-085, 2019). Verify the current CDLE guidance at cdle.colorado.gov.
California. SB 1162 / Labor Code §432.3 (effective January 1, 2023) applies to employers with 15 or more employees, with at least one in California. Civil penalties run $100–$10,000 per violation, and the same role posted across five platforms without a range may be treated as five violations (Employment Law Aid, 2026). California also requires employers to maintain job-title and wage-rate history records under §432.3 (Employment Law Aid citing CA Labor Code §432.3, 2026). Confirm current enforcement posture at the California DIR (dir.ca.gov) or with counsel.
Washington State. The Equal Pay and Opportunities Act (effective January 1, 2023) requires employers with 15 or more employees to disclose a wage scale or salary range plus a general description of benefits and other compensation (WA L&I, 2025). July 2025 amendments raised the stakes: statutory damages of $100–$5,000 per applicant, plus attorney fees; L&I civil penalties up to $500 for a first violation and up to $1,000 for subsequent violations (Epstein Becker Green, 2025). Verify current rules at lni.wa.gov.
New York State. Labor Law §194-B (effective September 17, 2023) applies to private employers with four or more employees, for jobs performed at least in part in New York. Penalties escalate from $1,000 to $2,000 to $3,000 per violation (SixFifty / Trusaic, 2026), with a maximum of $3,000 per violation (NY State DOL, 2023). Confirm at dol.ny.gov.
New York City. NYC's pay-transparency law has been in effect since November 1, 2022, enforced by the NYC Commission on Human Rights. Civil penalties can reach $250,000 per violation (Trusaic, 2025) — the highest per-violation exposure in any US jurisdiction covered here. If any applicant could plausibly work in New York City, that penalty ceiling is part of your risk profile. Confirm at the NYC Commission on Human Rights (nyc.gov/cchr).
Illinois. HB 3129 (effective January 1, 2025) requires employers with 15 or more employees to include pay scale and benefits in postings. Penalties escalate: $500 for a first offense, $2,500 for a second, $10,000 for a third or subsequent offense — with a seven-day cure period (MMR Ltd. citing HB3129, 2025). Illinois also requires employers to retain pay-scale and benefit information and the posting for each position for five years (Greenberg Traurig / Illinois DOL, 2024). Verify at illinois.gov/idol.
New Jersey. The Pay and Benefit Transparency Act (effective June 1, 2025) applies to employers with 10 or more employees working 20 or more calendar weeks. Civil penalties are $300 for a first violation and $600 for each subsequent violation (Ogletree Deakins, 2025). Under proposed regulations, the spread between a posting's minimum and maximum may be no more than 60% of the minimum (Saiber LLC, 2025) — a structural constraint that affects how you define salary bands for roles posted into New Jersey. Verify current regulatory status with the NJ Department of Labor (nj.gov/labor) or counsel.
Washington, D.C. The Wage Transparency Omnibus Amendment Act (effective June 30, 2024) applies to private employers of any size — one or more D.C. employees — and requires disclosure of minimum and maximum projected pay in all postings. Civil fines are $1,000 for a first offense, $5,000 for a second, and $20,000 for subsequent offenses (Mercer, 2024). Verify at does.dc.gov.
Massachusetts. An Act Relative to Salary Range Transparency (effective October 29, 2025) applies to public and private employers with 25 or more Massachusetts employees. Penalties escalate from a warning to up to $500, then up to $1,000, then up to $25,000 for a fourth or subsequent offense — with a two-business-day cure period through October 29, 2027 (Mintz, 2025). Verify at mass.gov/ago.
For a comprehensive, regularly updated state-by-state reference, see our pay-transparency laws by state guide.
The Jurisdiction-Trigger Question: Which State's Rules Apply?
When a posting could be performed in multiple states, the default safe harbor for multi-state hiring pay transparency is to assume the most demanding applicable rule governs and build your posting to satisfy it. That is not a legal opinion — it is a documentation posture you can explain to an employment attorney.
Walk through these questions for every open role:
- Is the role tied to a specific physical location? If yes, that jurisdiction's law applies (assuming you meet the employee-count threshold). If the role is remote-eligible or fully remote, continue.
- Which states have employees today who could perform this role? Each state where you employ people is a potential trigger under the relevant law.
- Does the posting explicitly exclude any state? Some employers add language such as "not available to applicants in [state]" to remove a jurisdiction from scope. Whether that exclusion is effective depends on the jurisdiction. Confirm the current guidance for each state with the relevant authority or counsel.
- Does the posting specify a salary range? If the role appears on a public job board — even if your intent is to hire only in one state — applicants in other covered states may apply. When they do, the law of their state may apply.
The practical output of this analysis is a jurisdiction matrix for each open role: a short document identifying which state laws apply, the thresholds your company meets, the posting requirements under each, and the range you are posting. That matrix is also your first line of documentation if a complaint is filed.
Structuring Salary Ranges That Work Across Borders
Once you know which jurisdictions are in scope, the next question is structural: do you post one salary range for the role, or location-differentiated ranges?
A salary range (also called a pay band or compensation band) is the span between the minimum and maximum you are prepared to pay for the role. The range spread — how wide the band is, expressed as a percentage of the midpoint — reflects seniority latitude, geographic variation, and the range of qualifications you are prepared to consider. A tighter spread (say, 20–30%) signals a well-defined role with limited seniority variance. A wider spread (50%+ of midpoint) may be appropriate for a senior individual-contributor role where experience spans are broad.
The NJ proposed-regulation constraint is worth flagging here: under proposed New Jersey rules, the spread between minimum and maximum may be no more than 60% of the minimum (Saiber LLC, 2025). A band of $60,000–$100,000 has a spread of $40,000, which is 66.7% of the $60,000 minimum — and would exceed that proposed cap. If you are posting a role open to New Jersey applicants, confirm the current regulatory status of this constraint with counsel and size your band accordingly. Verify at nj.gov/labor.
Geographic differentials are a second complication. A software developer role that pays at the 50th percentile for San Francisco will sit well above the median for the same occupation in a mid-sized Midwestern metro. When your posting covers both geographies, you have two defensible options: post a single range that encompasses the full geographic spread (wider band, more transparency about the upper bound), or post location-differentiated ranges that reflect local market data. Our guide to geographic pay differentials walks through the mechanics of building market-indexed bands by metro. If you operate across multiple locations and need a framework for when to split ranges by geography, the location-based range sets guide addresses that decision directly.
When building ranges anchored to market data, we use BLS Occupational Employment and Wage Statistics (OEWS) — the federal dataset that produces wage estimates for over 800 occupations across national, state, and metropolitan-area geographies from a sample of approximately 1.1 million establishments (BLS, May 2025). BLS OEWS data is reported at the 10th, 25th (where available), 50th, 75th, and 90th percentiles. Always name the dataset, the geography, and the reference year on any wage figure you use in a posting or in your methodology documentation, and confirm the current figure at bls.gov/oes before setting a range. For more on what the posting itself needs to contain, see what to include in a salary range posting.
If your workforce or applicant pool extends into Canada, note that British Columbia's Pay Transparency Act (since November 1, 2023) requires all employers to include the expected salary or wage, or a range, in publicly advertised postings — and open-ended ranges are explicitly prohibited (Stikeman Elliott, 2023; MLT Aikins, 2025). Ontario's pay-transparency rules (effective January 1, 2026) apply to employers with 25 or more employees; a posted range cannot exceed $50,000 unless the role or the top of the range pays over $200,000 annually, and employers must retain each publicly advertised posting for three years after it is taken down (Littler, 2025; HRPA, 2026). Canadian wage benchmarks come from Statistics Canada's Employee Wages by Occupation (NOC) dataset, which is a different taxonomy from the US BLS Standard Occupational Classification — US and Canadian figures must be presented separately, in their own currency (USD vs. CAD), with their own reference year. See the live dataset at open.canada.ca. For the remote-pay policy framework that ties these geographic and cross-border decisions together, see our remote pay policy tiers guide.
Documentation: What You Need Before the Complaint Arrives
Posting a range is the visible compliance act. Documentation is what makes it defensible.
For any multi-state role, the minimum documentation package includes:
- The methodology statement — which dataset you used (e.g., BLS OEWS, May 2024, national or state-level for [SOC code]), what percentile you anchored to (e.g., the 50th percentile for the relevant geography), and what range spread you applied.
- The jurisdiction matrix — which state laws you evaluated, the employee-count threshold you assessed, and the resulting determination that each law did or did not apply.
- The posting record — a copy of the posting as it appeared on each platform, with the date published, because California treats the same undisclosed role on five platforms as five separate violations (Employment Law Aid, 2026), and Illinois requires retaining pay-scale and benefit information for each posting for five years (Greenberg Traurig / Illinois DOL, 2024).
- Version history — if you update the range mid-cycle (for example, after the BLS releases new OEWS data or the role's scope changes), document the old range, the reason for the change, and the date.
This is the documentation package that matters when an employment attorney asks: "Show me how you built this range." A Google Sheet with a BLS number pasted in is a starting point. A timestamped, methodology-stamped record with the SOC code, the data vintage, the range spread, and the jurisdictions evaluated is defensible documentation.
Managing the Ongoing Compliance Cycle
Multi-state hiring pay transparency is not a one-time setup. The compliance landscape is actively shifting — as of 2026, an estimated 65% of U.S. employers are affected by active pay-transparency laws across 17 states and multiple municipalities (Lift HCM, 2026) — and the BLS OEWS releases new national, state, and metro estimates annually (the May 2025 OEWS was released May 15, 2026 — BLS, 2026). Each new release is an occasion to review whether your posted ranges still reflect current market data and to re-run the methodology documentation.
Build a quarterly review into your HR calendar: pull the current OEWS estimates for your key occupations, compare them to your posted ranges, and flag any role where the market has moved materially. Document the review, even if no ranges change. That record of deliberate, periodic review is itself a piece of your compliance posture.
For a consolidated view of active state laws, penalty schedules, and effective dates, bookmark the pay-transparency resource hub.
Your Next Step: Build Ranges That Cover Every Jurisdiction in Your Hiring Footprint
If you are managing multi-state hiring pay transparency with a spreadsheet and a browser tab for each state's DOL website, you already know the hours it consumes — and the audit trail it does not produce. Salary Range Builder is built specifically for HR generalists and People Ops leads at 10–200 person companies who need to generate a compliant, methodology-stamped salary range without a dedicated comp team or an enterprise software budget.
The Pay Transparency Compliance Kit at /store/pay-transparency-compliance-kit gives you the structured templates for the jurisdiction matrix, the methodology statement, and the posting record — the three documents an attorney will ask for. Salary Range Builder's Professional and Business tiers add the US and Canadian geographic-adjustment calculator, multi-location range sets, and watermark-free PDF output you can attach to that documentation package directly.
Start with a 14-day free trial — no free tier, no credit card guesswork, and same-day activation. One avoided pay-transparency penalty in any of the jurisdictions above covers several months of an Essentials subscription; verify the exact penalty figure with the relevant state authority before using it in your own ROI calculation.
Multi-state hiring pay transparency is a systems problem. Build the system once, document it, and stop rebuilding it every Friday afternoon.
Get new guides in your inbox
One email when a new article goes live. Unsubscribe with one click.
