Salary-History Bans: The Question You Must Stop Asking Referees

Most US employers have removed the compensation question from their job application form and their interview guide. Far fewer have removed it from the reference questionnaire, and that is where a salary history ban still catches reference checks. The reason is simple: these laws generally restrict seeking pay history, not merely asking the candidate. If your recruiter calls a former manager and asks what the candidate was paid, the law does not care that the candidate was not in the room.

This is a narrow problem with a cheap fix. It is also one of the easiest compliance failures to prove, because the offending question sits in writing inside a template your team has used dozens of times.

Key Takeaways

• Salary-history restrictions generally prohibit seeking pay history from any source, including a current or former employer, not only from the applicant.
• Massachusetts law bars seeking wage or salary history from the prospective employee or a current or former employer. California bars seeking it "personally or through an agent", which reaches recruiters acting for you.
• A compensation field left in a reference questionnaire is written evidence of a prohibited inquiry, repeated on every candidate it was used for.
• Asking about salary expectations is generally still permitted. Asking what someone used to earn generally is not.
• Coverage varies by state and city, so employers hiring in more than one location should build one process to the strictest rule they face.

What these laws actually prohibit

There is no single federal salary-history ban. The restrictions come from state and local law, and a substantial number of states plus various cities and counties now have some version, with public-sector-only coverage in several. The drafting differs, but three prohibitions recur: a bar on asking for pay history, a bar on relying on it to decide whether to make an offer or what to pay, and a bar on seeking the information at all, phrased broadly enough to cover third-party sources.

Massachusetts is the clearest example. Its equal pay provision prohibits an employer from seeking the wage or salary history of a prospective employee "from the prospective employee or a current or former employer". California takes a different route to the same place: an employer may not, orally or in writing, personally or through an agent, seek salary history information about an applicant. "Through an agent" is doing real work in that sentence. It covers your recruiting agency, your RPO partner, and the contractor running your reference calls. Colorado's Equal Pay for Equal Work Act simply prohibits an employer from seeking the wage rate history of a prospective employee, with no qualifier limiting the source.

Read those together and the operating rule is obvious. The question is prohibited because of what you are trying to learn, not because of who you asked.

Why the referee call is the exposure nobody audits

Reference checking sits in a blind spot. Legal review lands on the application form, the careers site and the interview guide, because those are the documents counsel is shown. The reference questionnaire is treated as an operational artifact owned by recruiting, inherited from a previous system and never re-read.

Plenty of legacy templates ask a referee to confirm "salary or rate of pay at the time of leaving" alongside dates and job title. That line probably predates the ban in your state. It is still a request for pay history directed at a former employer, and under the Massachusetts or California phrasing it is the exact conduct described.

The practical risk is not usually a regulator reading your template. It is a candidate who was told the range, was then offered less, and later learns from a friendly former manager that your recruiter asked what they used to make. That sequence turns a documentation oversight into a pay-setting allegation, and state pay-equity regulators and private plaintiffs are where this kind of claim now lands. The US Equal Employment Opportunity Commission enforces federal pay discrimination law under Title VII and the Equal Pay Act, which is a separate track, but the underlying evidence is the same: what you knew about prior pay and what you did with it.

Ask, do not ask

The line is easier to hold once you separate the forward-looking question from the backward-looking one. Expectations are about the role you are filling. History is about a pay decision someone else made, possibly a discriminatory one, which is why these laws exist.

• Asking the candidate about salary expectations or desired compensation - Generally prohibited: Asking the candidate what they currently or previously earned
• Stating or posting the pay range for the role - Generally prohibited: Asking a referee or former employer to confirm a salary, rate or bonus
• Asking a referee to confirm job title, dates, duties and performance - Generally prohibited: Including a compensation field on a reference form or scorecard
• Confirming pay the candidate volunteered without prompting (where permitted) - Generally prohibited: Setting the offer by reference to prior pay, however you learned it
• Asking about non-pay benefit needs relevant to the offer, such as start date - Generally prohibited: Requiring prior pay to meet a minimum or maximum before consideration

Two cautions on the permitted column. Voluntary disclosure is a real exception in several states, but it is narrow: the candidate must offer the figure unprompted, and a recruiter who nudges has destroyed it. Some jurisdictions allow the inquiry only after an offer with compensation has been negotiated, which makes post-offer verification a safer moment than a pre-offer reference call.

Fixing it: a one-afternoon audit

Treat this as a document sweep rather than a policy project. Pull every artifact where a pay question could live and strip the field, then close the gap that lets it come back.

• Inventory the templates. Reference questionnaires, call scripts, application forms, interview guides, screening scripts, offer approval forms and any spreadsheet where recruiters log candidate data. Our free reference check templates show what a pay-free reference form looks like.
• Delete the field, do not just relabel it. A field renamed "current package" is the same inquiry. Remove the row so no one can fill it in.
• Replace it with something you actually need. Scope of responsibility, budget or headcount managed, and seniority of the role are legitimate reference questions that tell you what you were using pay as a proxy for.
• Brief anyone asking on your behalf. Agencies, RPO providers and contract recruiters are the agents these statutes name. Put the prohibition in the scope of work.
• Check historical records. If prior pay sits in candidate files, decide with counsel what happens to it and keep it away from whoever approves offers.
• Lock the process. When every referee answers the same approved question set, the improvisation that reintroduces the question disappears. Structured automated reference checks help because the questions are fixed in the workflow and responses are logged, so you can show what was asked. The same logic applies to AI skill assessments, which measure what a candidate can do rather than what a previous employer paid them.

Hiring across several states

Running a different reference script per state is how this failure happens. Someone uses the version for a state with no ban on a candidate who will work in a state that has one. Location of the role, of the candidate and of the recruiter can all be argued to matter, and the answer is not uniform.

The defensible design is one national process built to the strictest rule you face: no pay history question anywhere, no compensation field on any form, expectations conversations only, and pay ranges shared proactively. You lose nothing, because prior pay was never good evidence of what someone is worth in a different role. For the wider design problem, see Multi-State US Hiring: Building a Consistent Reference Check Process Across States, and for question wording generally, EEOC-Safe Reference Check Questions for United States Employers. More material on hiring process compliance sits in our HR and pre-employment resources.

Related Resources

• Automated Reference Checks for Employers
• Free Reference Check Templates and Question Sets
• AI Skill Assessments for Hiring Teams
• EEOC-Safe Reference Check Questions for United States Employers
• Multi-State US Hiring: Building a Consistent Reference Check Process Across States
• HR and Pre-Employment Resources and Articles
• US Equal Employment Opportunity Commission

Frequently Asked Questions

Can I ask a former employer to verify a salary the candidate already told me?

Be careful. Several states let you confirm pay the candidate volunteered unprompted, others allow confirmation only after an offer with compensation has been negotiated, and some permit the candidate rather than the former employer to do the confirming. Directed at a third party, it is the harder version of the exception to rely on.

Does a salary-history ban apply if the role is remote?

Often yes, and frequently under the law where the employee will work rather than where your office sits. Some local ordinances also reach recruiting activity in their jurisdiction. Since a remote requisition attracts candidates across many states, a single pay-free script beats determining coverage per applicant.

What if our applicant tracking system has a salary field we cannot remove?

Ask the vendor to hide or disable it for affected requisitions, and in the meantime remove it from every form and script your team reads from. An unfillable field cannot generate the inquiry. Do not leave it visible with an instruction not to use it.

Is the ban about pay equity or about privacy?

Pay equity. Anchoring a new salary to a previous one carries forward any discrimination baked into the earlier figure, so the remedy is to remove the input entirely. That is why relying on the information is prohibited even where you obtained it lawfully.

Do these rules stop me asking about performance or conduct?

No. These restrictions are specific to compensation. Job-related questions about duties, performance, reliability, attendance and eligibility for rehire remain available, and those are the ones that predict how a hire works out.

This article is general information for US employers and is not legal advice. Confirm your obligations with employment counsel in the states where you hire.

Check the Questionnaire, Not the Policy

A salary-history ban is one of the few obligations you satisfy by deleting something. The exposure is not in your policy document, it is in the reference questionnaire your team opens every week. Open that file today, remove the compensation row, and tell every agency working for you that the question is off the list.