Navigate Salary History Rules Across Locations

Employers can recruit across locations with different salary-history rules by using a location-aware hiring process: identify the candidate and expected work locations, remove prior-pay questions from applications and recruiter scripts, discuss compensation through ranges and expectations, train hiring teams on consistent language, and route jurisdiction-specific questions to legal or compliance review. This article is operational guidance for recruiting teams, not legal advice, and it should be paired with current state or local guidance before policy decisions are finalized.

Why multistate recruiting makes salary-history questions hard to standardize

Salary-history restrictions are difficult to manage in multistate recruiting because the hiring conversation often crosses more than one location. A candidate may live in one state, the role may report to another state, the company may be headquartered elsewhere, and the work may be remote, hybrid, or tied to a local office. Rules can also exist at the state or local level and may change over time.

That creates a practical problem for recruiters: the same casual question can carry different risk depending on where the candidate is located, where the work will be performed, and which jurisdictional rules apply. A recruiter who asks, “What are you making now?” may be following an old habit rather than an approved compensation process.

The safer operational approach is to standardize away from salary-history questions entirely where possible. Instead of asking about current or past pay, teams can build compensation conversations around:

• The posted or budgeted range for the role
• The candidate’s compensation expectations
• The scope, level, and responsibilities of the position
• Required skills, experience, and location factors
• Internal compensation criteria and market context where appropriate

For teams trying to navigate salary history rules across locations, the goal is not to memorize every jurisdiction in a recruiter’s head. The goal is to design a process that makes the preferred behavior easy, repeatable, and reviewable.

Some jurisdictions publish official guidance that employers can use as a starting point. For example, New York State provides public guidance on its salary history ban. Employers should still review current guidance for the specific locations involved and consult counsel for jurisdiction-specific decisions.

Start each role with candidate and work-location intake

Before compensation conversations begin, hiring teams should identify the location facts that may affect the process. This does not mean assuming that one location always controls the answer. It means gathering enough context to decide whether a standard workflow applies or whether the situation needs review.

A practical intake process may capture:

• Where the candidate is currently located
• Where the role is officially based
• Where the employee is expected to perform the work
• Whether the role is remote, hybrid, field-based, or office-based
• Whether the hiring manager, recruiter, or business unit is operating across multiple locations
• Whether the role will be posted in locations with known pay-transparency or salary-history restrictions

The intake step should happen early enough to shape the recruiter’s script, job posting review, and compensation workflow. If the organization uses one national recruiting process, location intake can still matter because edge cases may require a different review path.

For example, a remote role posted nationally may need a more conservative compensation conversation than a single-office role handled by a local recruiting team. A candidate who changes location during the process may also require the team to confirm whether the applicable process still fits.

The key implementation point is simple: do not wait until offer stage to discover that the recruiting team asked inconsistent compensation questions earlier in the funnel.

Replace salary-history questions with range, expectations, and role-scope prompts

Recruiters can standardize compensation conversations without asking prohibited questions by using prompts that focus on the role and the candidate’s forward-looking expectations, rather than the candidate’s past compensation.

Instead of asking:

• “What do you currently earn?”
• “What was your salary in your last role?”
• “Can you send your compensation history?”
• “What bonus did your previous employer pay?”

Teams can use more role-centered prompts such as:

• “The budgeted range for this role is X to Y. Does that align with what you are targeting?”
• “What compensation range would you need to consider this opportunity?”
• “Based on the scope we discussed, does the posted range fit your expectations?”
• “Are there compensation components, such as bonus structure or equity, that are important for you to understand as you evaluate the role?”
• “Let’s review the responsibilities, location expectations, and level so we can align on the appropriate range.”

Whether a specific phrase is permitted can depend on location and context, so employers should have legal or compliance teams review final scripts. But as an operating model, shifting from past-pay questions to expectations, range, and role scope gives recruiters a consistent way to keep the conversation moving.

This approach also improves candidate experience. Candidates often want to know whether the opportunity is aligned before investing time in interviews. A clear conversation about the role’s range, level, and expectations can reduce ambiguity without requiring prior-pay information.

Standardize recruiter scripts, application forms, and interview notes

A policy is only useful if it shows up in the tools recruiters use every day. Multistate hiring teams should review every place where salary-history questions might appear, including legacy application forms, screening notes, interview templates, intake documents, message templates, and hiring-manager worksheets.

The review should focus on both candidate-facing and internal materials. A question does not need to appear on a public application to create inconsistency. It may be buried in an intake call outline, a recruiter training deck, or an interview scorecard.

A stronger process usually includes three layers of standardization.

1. Candidate-facing language. Application forms, job posts, screening messages, and recruiter emails should avoid asking for prior compensation unless the organization has reviewed and approved that use for the relevant location. Where pay transparency rules apply, job posts may also need separate review for range disclosure requirements.
2. Recruiter conversation scripts. Recruiters should have clear language for common situations: early screening, candidate questions about range, hiring-manager pressure to ask about current pay, and negotiation after an offer is being prepared.
3. Internal documentation. Interview notes and compensation rationale should focus on objective criteria: role level, skills, experience, location, internal equity, budgeted range, and market data where appropriate. Notes should not rely on prior salary as a shortcut for determining value.

Standardization does not eliminate the need for legal review, but it reduces the chance that each recruiter improvises a different answer in each location.

A practical checklist for hiring teams recruiting across locations

Use this checklist as a starting point for a multistate or multi-location recruiting workflow. It is designed for process design, not as a substitute for jurisdiction-specific legal advice.

• Identify the role location, expected work location, and candidate location early in the process.
• Decide which location facts need to be captured before screening calls begin.
• Map the relevant salary-history restrictions for the locations where the organization recruits.
• Review official state or local guidance where available, and involve legal or compliance advisors for interpretation.
• Remove salary-history questions from application forms, screening questionnaires, recruiter scripts, and interview templates.
• Replace past-pay questions with approved prompts about pay expectations, posted range, budgeted range, role scope, skills, and location factors.
• Train recruiters and hiring managers on what they should ask, what they should avoid, and how to respond when candidates volunteer salary history.
• Document compensation decisions using objective criteria such as role level, responsibilities, skills, experience, market context, and internal compensation structure.
• Create an escalation path for remote roles, candidates who relocate, cross-border hiring, executive compensation, and unusual negotiation scenarios.
• Revisit the workflow periodically because salary-history and pay-transparency rules can change.

For implementation, many teams start with a simple audit: collect every form, script, note template, and recruiter enablement document that mentions compensation. Then classify each item as candidate-facing, recruiter-facing, hiring-manager-facing, or offer-stage. That makes it easier to update the highest-risk materials first.

How real-time candidate conversations can support pay discussions

Real-time candidate conversations can support better pay discussions when recruiters are trained on the right topics to cover. To keep the process consistent across locations, teams need reviewed language and a clear review path around those conversations.

MeeBoss is relevant here because it is built around direct conversations between job seekers and hiring teams. Chat to Apply lets candidates start a conversation with the hiring team instead of relying only on a one-click application. That kind of early dialogue can help employers understand the whole person beyond the resume and clarify fit, expectations, and role context sooner in the process.

For salary-history-sensitive conversations, the practical point is to pair real-time communication with clear recruiter guidance. Recruiters should know how to discuss:

• The role’s responsibilities and level
• The budgeted or posted range, where available
• The candidate’s compensation expectations
• Location or remote-work factors that affect the role
• Next steps if the candidate raises prior pay voluntarily

A real conversation can be more transparent than a static form, but it should not become an unstructured interview where every recruiter asks different compensation questions. Teams using conversational hiring workflows should treat compensation language as a trained part of the process.

When to route salary-history questions to legal or compliance review

Some situations should be routed to legal or compliance review before recruiters proceed. Escalation is especially important when the team is unsure which location rules apply, when the company is changing its application forms or recruiter scripts, or when a compensation conversation involves unusual facts.

Common escalation triggers include:

• The candidate, recruiter, hiring manager, and work location are in different jurisdictions.
• A remote role is open to candidates in many states or localities.
• A candidate relocates during the process.
• A hiring manager wants to ask about current or past pay.
• A candidate volunteers salary history and the recruiter is unsure how to handle it.
• The company is updating job postings, compensation ranges, or screening forms.
• The role involves executive compensation, commission-heavy pay, equity, or other complex compensation components.
• A state or local rule has recently changed.

Teams should also build a review habit before publishing job posts or compensation-related materials. MeeBoss encourages employers to confirm job-posting information before making a job public; in a legally sensitive compensation context, employers should apply the same discipline to salary ranges, role descriptions, and recruiter-facing language.

The right escalation process does not need to slow every search. It should give recruiters a clear line: use the standard script for routine situations, and ask for review when location, compensation structure, or candidate circumstances make the answer uncertain.

FAQ

How can employers recruit across locations with different salary-history rules?

Employers can recruit across locations by using a location-aware process. Start by identifying candidate and work locations, then map the relevant salary-history restrictions, remove past-pay questions from forms and scripts, train recruiters on approved compensation prompts, and route uncertain cases to legal or compliance review.

How can recruiters standardize compensation conversations without asking prohibited questions?

Recruiters can standardize compensation conversations by focusing on the role rather than the candidate’s past pay. Useful topics include the posted or budgeted salary range, the candidate’s pay expectations, the role’s responsibilities, required skills, location factors, and objective compensation criteria.

What should recruiters ask instead of salary history?

Recruiters can ask forward-looking questions such as whether the role’s range aligns with the candidate’s expectations, what range the candidate is targeting for a new opportunity, and which compensation components matter as the candidate evaluates the role. Final wording should be reviewed for the locations where the company hires.

What process helps multistate hiring teams comply with salary-history restrictions?

A practical process includes location intake, rule mapping, application and script review, recruiter training, consistent documentation of compensation criteria, and escalation of jurisdiction-specific edge cases. The process should be reviewed periodically because salary-history rules can vary by state and locality and may change.

Can a company use one national compensation script?

A single conservative script can help reduce inconsistent recruiter behavior, especially if it avoids prior-pay questions and focuses on range, expectations, and role scope. However, employers should not assume one script automatically satisfies every state or local rule. Legal or compliance review is still important for policy decisions.

What if a candidate volunteers their salary history?

Recruiters should be trained on how to respond before this happens. A common process is to redirect the conversation toward the role’s range, the candidate’s expectations, and the objective criteria used for compensation decisions. Because rules can differ by location, employers should have counsel review the exact handling guidance.

Does MeeBoss automate salary-history compliance?

MeeBoss is not a salary-history compliance system. Its relevant fit is conversational hiring: MeeBoss supports direct, real-time conversations between job seekers and hiring teams and helps employers get a fuller picture of candidates beyond the resume. Employers still need their own reviewed compensation scripts, policies, and legal or compliance guidance.