What you'll learn
- A Distinct Legal Requirement From Pay Transparency
- What Gets Restricted — and Why the Specifics Vary
- The Practical Screening-Process Gap Most Employers Miss
- Penalties and Enforcement
- Building a Compliance Process That Doesn't Depend on Tracking 20+ State Rules Individually
Salary history bans get discussed alongside pay transparency laws so often that the two are frequently treated as the same requirement, but they're legally distinct — one restricts asking about a candidate's prior pay, the other requires proactively disclosing what the employer intends to pay — and more than 20 states now restrict salary history inquiries in some form, making this arguably the broader compliance surface of the two. This guide covers exactly what gets restricted and why the specifics vary meaningfully by state, the practical screening-process gaps (legacy ATS fields, habitual phone screen questions) that quietly violate a policy that looks compliant on paper, the enforcement variation across jurisdictions, and why a single unified company-wide policy is generally more defensible than tracking dozens of state-specific rules individually.
A Distinct Legal Requirement From Pay Transparency
Quick answer
Salary history bans restrict an employer's ability to ask candidates about their current or past compensation, or to rely on that information — whether obtained by direct inquiry or through a background check — in making hiring or compensation decisions. These laws are legally and historically distinct from the pay transparency requirements covered elsewhere in this series, which instead require employers to proactively disclose the range they intend to pay. A state can have a salary history ban without a pay transparency law, a pay transparency law without a salary history ban, or — as is increasingly common — both together as separate provisions within the same broader statute.
More than 20 states, along with numerous cities and localities (including several within states that don't have a statewide ban), now restrict salary history inquiries in some form, making this one of the more geographically widespread state-level employment compliance requirements currently in effect — arguably broader in raw jurisdiction count than pay transparency requirements, even though pay transparency tends to receive more attention in general HR compliance discussion.
The policy rationale behind these laws is straightforward: using a candidate's prior salary to set a new offer risks perpetuating historical pay gaps forward into new roles, since an underpaid candidate's low prior salary becomes the anchor for their next offer, compounding rather than correcting any prior underpayment. Salary history bans are frequently framed, including in legislative history for several of these laws, as a direct pay equity intervention rather than simply a transparency measure.
What Gets Restricted — and Why the Specifics Vary
Quick answer
The most common form of restriction prohibits employers from asking a candidate directly about their current or prior salary, wage, or compensation history during the hiring process. Some states extend this further, also prohibiting employers from seeking this information through other channels, such as a candidate's current or former employer, a background check provider, or public records, closing an obvious workaround where an employer avoids asking the candidate directly but obtains the same information through a third party instead.
A second, distinct layer of restriction addresses what happens if a candidate volunteers their salary history without being asked — some states permit an employer to consider voluntarily disclosed information in setting compensation, while others restrict even relying on voluntarily disclosed salary history for this purpose, treating the ban as protecting against the downstream effect on compensation-setting regardless of how the information was obtained. This distinction matters operationally: a policy that only trains recruiters not to ask the question may still permit a compliance gap if a candidate volunteers the information and a hiring manager uses it anyway in a state where that use is separately restricted.
A smaller number of jurisdictions also specifically address screening: prohibiting an employer from refusing to interview, hire, or promote a candidate solely because they decline to disclose their salary history when asked — closing a workaround where a technically permissible question ('what did you make previously? you don't have to answer') becomes a de facto requirement because declining to answer functions as a disqualifying signal in practice.
Salary history bans and pay transparency laws are legally distinct requirements that frequently get conflated — a state can have one without the other, and more than 20 states plus numerous cities now restrict salary history inquiries, making this a broader compliance surface than pay transparency alone even though the two are often discussed together.
The Practical Screening-Process Gap Most Employers Miss
Quick answer
The most common real-world compliance gap isn't a deliberate policy violation — it's a legacy applicant tracking system field, a standard phone screen script, or a recruiter's habitual opening question ('so what are you currently making?') that predates the relevant state's ban and was never updated once the law took effect. Recruiters who've asked this question as a matter of routine practice for years, across many states, need explicit retraining specific to which states restrict the question rather than a general awareness that 'some states have this rule now.'
Application forms and applicant tracking system intake fields are a particularly common source of quiet noncompliance — a standard 'current salary' field embedded in an ATS template, applied uniformly across all candidates regardless of the specific state they're applying from, can create a compliance violation in every covered state even if no individual recruiter ever asks the question verbally. Auditing intake forms and ATS field configurations for state-specific conditional logic — showing or hiding the salary history field based on the candidate's state — is a concrete, structural fix that removes reliance on individual recruiter discipline entirely.
For multi-state employers, the operationally simplest approach is frequently to remove salary history questions from the hiring process entirely, company-wide, rather than maintaining state-by-state conditional logic across every touchpoint (application forms, phone screen scripts, background check authorizations) — since a single unified 'we set offers based on the role and market data, not prior salary' practice, sourced from the kind of compensation benchmarking work covered in our guide to salary benchmarking for offers, satisfies every state's restriction simultaneously without needing to track which specific rule applies where.
Penalties and Enforcement
Quick answer
Enforcement mechanisms and penalty structures vary considerably by state and locality — some route through a state labor department or civil rights agency's administrative process, similar to the pay transparency laws covered elsewhere in this series, while others provide a private right of action allowing an affected candidate to sue directly. Given this variation, a multi-state employer facing a specific salary history complaint should confirm the applicable enforcement mechanism for that specific jurisdiction rather than assuming a single enforcement pattern applies uniformly everywhere.
Beyond direct penalty exposure, a documented pattern of salary-history-based compensation decisions — even without a specific complaint ever being filed — can become relevant evidence in an entirely separate pay equity claim, since a plaintiff alleging current pay disparities may point to historical salary-history-based offer decisions as part of the causal chain explaining how the disparity originated and persisted. This connects salary history ban compliance directly to broader pay equity risk management, not just to the specific statutory penalty for the history-question violation itself.
Related reading
Building a Compliance Process That Doesn't Depend on Tracking 20+ State Rules Individually
Quick answer
Given the sheer number of jurisdictions now covered by some form of salary history restriction, and the meaningful variation in exactly what each one restricts, the most defensible practical approach for most multi-state employers is a single company-wide policy prohibiting salary history inquiries and reliance on volunteered salary history in compensation decisions — treating the most protective state's standard as the company-wide default rather than maintaining granular state-by-state exceptions that are harder to audit and more prone to a recruiter simply forgetting which specific rule applies to which candidate.
Replace salary history questions with structured compensation-expectation conversations grounded in transparent, market-based range disclosure — see our guide on compensation benchmarking for how to build defensible ranges that make the salary history question genuinely unnecessary rather than merely prohibited, since a recruiter equipped with an accurate, well-researched range for the role has little practical need to ask about a candidate's prior pay in the first place.
Audit your ATS, application forms, and background check authorization templates specifically for legacy salary history fields, and pair this policy work with the affirmative disclosure requirements covered in our broader guide on pay transparency laws across the US — the two categories of law frequently apply to the same hiring process simultaneously, and a single revised job requisition and offer workflow can be built to satisfy both at once.
The specific scope of what's restricted varies meaningfully by jurisdiction — some laws ban only asking about prior salary, others additionally ban relying on voluntarily disclosed salary history to set compensation, and a few restrict screening out candidates who decline to answer — so a single 'don't ask about salary history' policy can still leave real gaps depending on which specific state's law actually applies.
Frequently asked questions
Common questions about talent acquisition and how InCruiter helps teams solve them.
InCruiter Editorial Team
AI Hiring Research · Interview Intelligence · Enterprise Talent Strategy
The InCruiter editorial team covers AI-driven hiring, interview intelligence, and modern talent acquisition strategy. Our guides draw on platform data from 2,000+ hiring teams, conversations with talent leaders, and published research in industrial-organizational psychology.
