The conversation most HR leaders are dreading is not the regulatory audit. It is the one with the employee who submits an Article 7 request, receives the average pay data for comparable roles broken down by sex, and walks into the HR Director's office with a number and a question.
That conversation is coming. The directive makes it available to every employee from June 2026. The only variable is whether the company is ready to have it on structured terms — or is forced to have it on reactive ones.
This article maps what internal salary transparency actually requires under the directive, how to communicate pay structure before the first request arrives, and where most SMEs discover that the problem is not the communication. It is the structure that should have been communicated. For a full overview of what the directive requires across all obligation areas, the SME guide covers the complete scope.
What does the directive actually require internally?
Article 7 gives any employee the right to request the average pay of colleagues doing equal work or work of equal value, broken down by sex. The request must be answered within two months. It cannot result in any adverse treatment.
Article 6 requires that the criteria used to set pay are accessible to employees — documented, gender-neutral, and applicable to every role.
Neither of these is a disclosure requirement in the sense of publishing individual salaries. They are accountability requirements. The company must be able to answer a specific question, and the answer must come from a structure, not from a judgment made on the day the question was received.
Where does the gap between "we have the data" and "we can answer this" appear?
Most companies have pay data. Salaries are in the HRIS. Bonus records exist somewhere. Contracts have job titles.
What most companies between 100 and 500 employees do not have is the layer above that data — the structure that makes it interpretable. Salary ranges per role or level. A documented job evaluation methodology that defines what counts as work of equal value. Gender-neutral criteria that explain why each role sits where it does in the pay structure.
Without that layer, an Article 7 request produces one of two outcomes. A number that is accurate but unexplained — which often generates more questions than it answers. Or a delay while someone tries to reconstruct a structure that the request assumed already existed.
Neither outcome is a good position to be in two months after June 2026.
The directive defines comparable work as equal work or work of equal value — not just the same job title. An employee in operations can request pay information about a role in finance if a reasonable case can be made that the two roles are comparable in skill, effort, responsibility, and working conditions. How a company defines its comparator groups determines the scope of every Article 7 response. Narrow definitions invite challenge. Broad definitions require a methodology capable of supporting them.
What does internal transparency actually mean?
There is a version of internal salary transparency that most HR teams fear: employees comparing individual salaries, discovering differences, and drawing conclusions without context. That is a real risk — but it is a risk that comes from having a pay structure that cannot be explained, not from the act of making it visible.
The directive does not require publishing individual salaries. It requires that a specific question — the average pay for comparable roles, broken down by sex — can be answered accurately and within two months. That is the scope of the obligation.
A company with a documented pay structure — defined salary ranges, a consistent job evaluation methodology, gender-neutral criteria applied to every role — can answer that question without fear. The structure does the explaining. The number is the output of a process, not an arbitrary decision. That is the position worth building toward.
How do you communicate pay structure before the requests arrive?
Proactive communication is significantly easier than reactive disclosure. A company that explains its pay framework to employees before anyone submits a request controls the framing. A company that discloses in response to a request does not.
Communicate the framework before the numbers. The first conversation should not be about specific salary ranges. It should be about how pay is structured — the job families, the levels, the criteria that determine where a role sits. Employees who understand the framework interpret numbers in context. Employees who receive numbers without context interpret them against their own assumptions.
Share salary ranges by level, not by individual. The range for each level in each job family is the appropriate unit of communication under the directive. It provides context without requiring individual salary disclosure. It also makes the principle of equal pay for equal work and work of equal value concrete — the range is the operational expression of that principle.
Address the pay criteria explicitly. Explain what the criteria are for pay decisions — initial offer, promotion, annual increase. That the criteria are objective and gender-neutral. That comparable roles are evaluated using a consistent methodology. This is not activist language. It is the legal framework in which every company with 100 or more employees in EU member states is now operating, and saying so directly is both accurate and appropriate.
Be specific about what the range means. A salary range of €40,000 to €60,000 tells an employee very little without context about where the distribution actually sits within it. A company that can say "the majority of people at this level sit between €44,000 and €52,000" is having a more honest conversation than one that discloses the band alone.
Where does the control concern come from — and what to do with it?
The concern HR Directors most often raise is not about disclosure. It is about what happens when employees see the data and feel they are being paid unfairly.
That concern is legitimate. But it is a concern about what the pay structure reveals, not about the act of communicating it. A company with a documented, defensible pay structure — where decisions are traceable, ranges are consistent, and differences are explainable — has far fewer uncomfortable conversations when pay becomes transparent. The structure absorbs the question.
A company that has made pay decisions without a documented framework has more to explain. Transparency surfaces that gap. But the gap was always there. The directive does not create it. It makes it visible.
Where do most companies sit right now?
Internal salary transparency is not something that happens to a company. It is something a company designs. The companies that manage it well had the structure in place before anyone asked — and communicated it before the directive required them to.
Where does pay diagnostic work actually start?
The smallest observable step is understanding where the company's pay structure and communication readiness currently sit — across the five principal obligation axes of the directive, including pay criteria accessibility and salary range documentation.
ReadinessCheck™ takes about 20 minutes and requires no salary data. It produces a position view by axis — scored observationally, 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 employee submits the request.
Across the directive's five obligation axes — before your employees ask.
ReadinessCheck™ takes about 20 minutes and requires no salary data. Observational, deterministic.
Start the ReadinessCheck →