Most companies preparing for June 2026 are focused on equal work. Same role, same tasks, same level. If two people are doing the same job and one earns significantly more than the other, that is the problem they are trying to solve.
That is the easier problem. Regulators are trained to look for the harder one.
Article 4 of the EU Pay Transparency Directive establishes the principle of equal pay for equal work and for work of equal value. The second phrase is the one that most SMEs are not yet prepared for — and the one that will define what regulatory audits actually examine.
This article is not a legal interpretation. It maps the distinction as the directive defines it, explains why it surfaces where it does, and describes the three positions a company can be in when the question arrives. For a broader overview of what the directive requires across all obligation areas, the guide for 100 to 500 FTE covers the full scope.
What does "work of equal value" actually mean?
Two roles are of equal value when their aggregate weight across four criteria is comparable. Those criteria are skill, effort, responsibility, and working conditions.
Skill covers formal qualifications, technical knowledge, and applied competencies. Effort covers physical, cognitive, and emotional demands. Responsibility covers the scope of decision-making, accountability for people or resources, and the consequence of error. Working conditions cover schedule, physical environment, travel requirements, and risk exposure.
The title is irrelevant. The department is irrelevant. What matters is the evaluated weight — how a role scores across these four dimensions when assessed through a documented, gender-neutral methodology.
A logistics coordinator and a finance analyst at the same level. A warehouse operations lead and an internal communications manager. Roles that have never been formally compared because there was never a reason to. Article 4 creates the reason. What auditors ask is not whether you intended to pay them equally — it is whether you built a framework capable of making that determination.
The directive does not prescribe a specific job evaluation methodology. It requires that whatever methodology a company uses is transparent, documented, consistently applied, and gender-neutral by design. An undocumented methodology is, in regulatory terms, equivalent to an absent one. The methodology is auditable. The intent is not.
Why is this structurally different from equal work?
The principle of equal pay for equal work is operationally straightforward. The comparator is obvious — same title, same tasks, same context. Observed differences in that setting require explanation, but the starting point is clear.
Work of equal value requires something that most SMEs have never built: a common evaluation framework that allows comparison across roles that share nothing on the surface. The comparison is not between identical jobs. It is between jobs that are comparable in aggregate weight — even if the people doing them would not recognise each other's daily work.
This is not a difficult concept. It is a structural requirement that most pay processes were never designed to satisfy, because for decades no one asked them to.
Where does the distinction surface in practice?
Three scenarios make the equal-value standard visible in operations.
When an employee requests pay information
Article 7 gives any employee the right to request average pay data for colleagues doing comparable work, broken down by sex. Comparable work is defined as equal work or work of equal value.
If a company responds to this request by identifying comparators only within the same job title, that response may be too narrow. A role in a different function, evaluated as comparable under the four criteria, is a valid comparator. An employee can challenge a definition that excludes roles of equal value — and the burden of justification sits with the company, not the employee.
During pay gap reporting
Article 9 requires reporting by category of worker. Categories must reflect comparable work — not org chart structure, not department, not cost centre. A category that happens to contain only employees of one sex will attract regulatory attention regardless of how it was constructed. The question is not whether the outcome was intentional. It is whether the methodology was defensible.
In a joint pay assessment
If the reported pay gap in any category exceeds 5%, a joint pay assessment is mandatory under Article 10 unless the difference can be explained by objective, gender-neutral factors. That assessment requires demonstrating that role comparisons were made correctly — using a methodology that existed before the assessment was triggered, not one constructed to respond to it.
What does a defensible position look like?
A company in Position 3 by June 2026 is in a defensible position. A company in Position 1 will be answering retrospectively — building documentation in response to questions it was not prepared to receive.
What audit logic do regulators follow?
The entry point is the pay gap report. The question beneath the numbers is: how were your categories constructed, and can you demonstrate that roles were grouped using a methodology that does not embed gender-related factors?
A company that answers with a documented evaluation framework, consistently applied, meets the structural standard. A company that answers with market benchmarks does not. External benchmarks reflect historical pay patterns between women and men. The directive is designed to correct those patterns — not validate them.
The distinction between equal work and work of equal value is, in the end, the distinction between a company that built a pay structure and a company that made a series of individual pay decisions. Both may produce similar pay levels. Only one can explain them to a regulator.
Where does pay diagnostic work actually start?
The smallest observable step is understanding where your company sits across the five obligation axes of the directive, including pay criteria documentation and job evaluation readiness.
ReadinessCheck™ takes about 20 minutes and requires no salary data. It produces a position view by axis, with the patterns that are hardest to close identified observationally.
It is not a legal opinion. It is not a compliance certification. It is a structured observation, useful in deciding what to address first.
Across the directive's five obligation axes — before the audit question arrives.
ReadinessCheck™ takes about 20 minutes and requires no salary data. Observational, deterministic.
Start the ReadinessCheck →