There is a question that has been asked in almost every hiring conversation in Europe for the past twenty years. "What are you currently earning?" Sometimes phrased more softly — "what does your current package look like?" — but the intent is the same. Anchor the offer to the candidate's history. Reduce negotiation risk. Close faster.
From 7 June 2026, that question is prohibited under Article 5 of the EU Pay Transparency Directive across EU member states.
This is not a procedural change. It is a structural one. The question was doing real work in most hiring processes — and the companies that understood what work it was doing will find the adjustment more manageable than those who treated it as a neutral icebreaker.
What was the question actually doing?
Salary history anchoring is efficient. It gives the hiring company an information advantage: the company knows what it will take to move the candidate, without revealing what it was prepared to pay. Offers land closer to the candidate's floor than the company's ceiling. Over time, across hundreds of hires, this compression of offer ranges produces exactly the pay disparities between women and men that the directive is designed to correct.
The logic is straightforward. If a candidate's pay history sits below the market range for comparable roles, anchoring a new offer to that history extends the pattern into the next job. The new employer did not create the disparity. But they inherited it, compounded it, and passed it forward.
Article 5 breaks the chain. Not by requiring equal pay — the principle of equal pay for equal work and work of equal value was already established in EU law long before this directive. But by removing the mechanism most commonly used to perpetuate historical differences.
What replaces the salary-history question?
In place of salary history, Article 5 requires two things.
First: a salary range must be provided for every advertised role before the first interview. Not during offer negotiation. Not after the screening call. Before the candidate meets anyone. The range must be based on objective, gender-neutral criteria — which means it needs to come from somewhere. A pay band, a level framework, a job evaluation. Not from what the last person in the role was earning, and not from what the company thinks the candidate will accept.
Second: the question is prohibited. The restriction is not limited to the formal interview. A hiring manager asking during a casual first call falls under the same restriction. The question is off the table at every stage of the process.
Candidates can still share their salary expectations voluntarily. What the directive prohibits is soliciting or using salary history as a basis for an offer. If a candidate volunteers what they are looking for, that information can inform the conversation. What is off the table is asking what they currently earn, or structuring an offer around the answer.
What real problem does Article 5 expose?
Most HR teams understand the prohibition quickly. The harder question is the one it creates: if salary history is not available as an anchor, what is the anchor?
The answer is a salary range. And a salary range, to mean anything, needs to come from a pay structure — job families, levels, documented bands, criteria that explain why the range sits where it does.
For companies that already have this, Article 5 changes very little operationally. The range is disclosed. The candidate evaluates. The conversation moves forward with information on both sides.
For companies that have set pay offer by offer — informed by benchmarks, by manager intuition, by what the budget allowed that quarter — Article 5 does not just change a question. It surfaces the absence of a structure that was never built.
That is the gap most SMEs are sitting in right now. Not bad intent. Just a hiring process that was never designed to function without salary history as an input.
What does the new hiring conversation look like?
The opening changes. Instead of learning what the candidate earns and calibrating from there, the conversation starts with a defined range already disclosed. The candidate knows what the role pays. The company knows what it can offer. The negotiation, if there is one, happens within a structure rather than around one.
This is actually a cleaner conversation. It removes the information asymmetry that made salary negotiation feel like a game — where candidates tried to reveal as little as possible and hiring managers tried to extract as much as possible, and both sides knew exactly what was happening.
A documented salary range, derived from a consistent pay framework and applied equally to every candidate for the role, is one of the few hiring practices that is simultaneously more compliant, more efficient, and more honest than what it replaces.
Where does the process need to change?
Salary ranges per role and level. Every open role needs a documented minimum and maximum before it is advertised. Not a placeholder. A range derived from a pay band framework, consistent with what comparable roles pay internally, and defensible if a candidate or a regulator asks how it was set. The article on communicating salary ranges internally covers how to build and present that structure to the team before the first candidate asks.
Job postings updated. The salary range needs to appear in the advertisement or be available before the first interview. Most ATS platforms and job boards were not configured with this workflow in mind. Test the disclosure process before it becomes mandatory.
Hiring managers briefed. The salary history question needs to be removed from every stage of the process — structured interviews, screening calls, informal conversations. A briefing is not enough on its own. The question needs to come off the interview guide, off the screening template, and out of the habit of every manager who has been asking it for fifteen years.
Offer construction redesigned. Without salary history as an anchor, offers need to be built from two inputs: the salary range for the role, and internal equity — what comparable roles in the company pay. This is where most SMEs discover that the problem is not the question they can no longer ask. It is that they never built the structure that makes the answer possible without it.
Where do most companies sit right now?
The salary range is not a concession to candidates. It is the output of a pay structure that should have existed already. For companies that built it, Article 5 changes very little. For those that did not, it makes visible a gap that was always there.
Where does pay diagnostic work actually start?
The smallest observable step is understanding where the company's pay structure and recruitment process currently sit relative to Article 5.
ReadinessCheck™ takes about 20 minutes and requires no salary data. It produces an observational position view across the directive's obligation axes — including salary range readiness and pay criteria documentation — with the patterns that are hardest to close identified first.
It is not a legal opinion. It is not a compliance certification. It is a structured observation, useful in deciding what to build before the first candidate asks for the range.
HireGapCheck™ produces a defensible salary range for any role.
Based on the internal pay structure and the four criteria the directive uses to define comparable work. No salary history required. Observational, deterministic. Built for companies between 100 and 500 employees.
Try the Offer Builder →