
When an employee asks why they earn less than a colleague, “that's just what the market pays” is no longer enough. The EU Pay Transparency Directive gives employees the right to understand how their pay compares with others doing the same work or work of equal value and requires employers to explain the criteria behind pay decisions.
Defensible pay comes down to two questions: Who is doing work of equal value, and can you objectively explain any pay differences between them?
Answering them takes six foundations working together. The first two establish the value of work and connect employees to the right roles. The remaining four help organisations make consistent pay decisions and explain differences.
Before explaining pay differences, you need a consistent way to assess the value of work. The Directive requires employers to identify categories of workers doing the same work or work of equal value, using objective, gender-neutral criteria such as skills, effort, responsibility and working conditions.
Levelling and evaluation provide the basis for those defensible pay comparisons, assessing roles against the demands of the work rather than job titles or historical pay decisions. This also helps address the historic undervaluing of roles traditionally performed by women.
When someone asks why their role is at level 5 rather than 6, you should be able to explain how that decision was reached.
You can evaluate every role individually or classify roles against a common framework. We recommend combining both: full point-factor evaluation for anchor and sensitive roles, with others classified against them. RoleEvaluate supports both approaches.
Evaluation establishes the relative value of roles, but an employee's pay must also reflect the work they actually do. Job architecture connects the two by organising evaluated roles into a consistent structure and mapping employees based on their responsibilities, not just their titles.
If someone is mapped to the wrong role, even a robust evaluation won't explain their pay. Common levels across an architecture also allow different jobs to be compared on the same scale. An engineer and a warehouse lead might do very different work but still be assessed as having equal value.
Job architecture also defines progression criteria, helping employees understand how to move between roles and levels. But when roles are assessed as having equal value, any pay differences need an objective explanation.
Once you know which roles are of equal value, you need to establish why people doing that work might be paid differently. Pay principles define the legitimate factors your organisation recognises, such as location, while ruling out previous salary or negotiating ability.
They also clarify your market position and how different contributions are rewarded. For example, you might recognise performance through bonuses or pay a separate premium for scarce skills rather than permanently building temporary market pressure into base salary.
A useful test is whether you could explain to employees what your organisation pays for and why and whether your decisions would support that explanation.
Pay bands bring together the value of work and what the market pays for it. Built around a consistent framework for assessing work of equal value, rather than negotiated independently for every role, they create a stronger basis for pay decisions.
Their width matters. Too wide and people doing work of equal value can earn very different amounts without a clear reason. Too narrow and there's little room to recognise legitimate differences.
Bands also make risk visible, from above-range hires to women clustering towards the bottom of a range. They support more consistent starting salaries too, placing new hires using agreed criteria rather than previous pay. As we explore in Building Defensible Pay at the Point of Hire, decisions made at the offer stage can create pay gaps that persist for years.
Pay principles define the reasons you're prepared to pay people differently. Contextual criteria explain how those reasons apply to individual decisions, without necessarily changing the value of the role.
For example, two managing directors may hold equally valued roles, but one is based in a high-risk location. The additional risk may justify a location or hardship premium without changing the underlying grade. Similarly, an employee who develops advanced Python skills doesn't automatically move to a higher level, although those skills may justify additional pay where they're relevant and genuinely scarce.
The distinction is between evaluating the role's demands and recognising legitimate circumstances that affect pay. Keeping these separate helps ensure grades remain consistent, while differences in pay are supported by objective, documented criteria that can be explained if challenged.
Market data helps set competitive pay bands and identify where skills shortages create pressure. But while it shows what other employers pay, it can't establish whether roles are of equal value or automatically justify differences.
Market rates can also reflect longstanding inequalities, including the historic undervaluing of work traditionally performed by women.
Market evidence can support a pay difference where there's a genuine, demonstrable skills shortage, but employers must show why it's justified and that the criteria are applied consistently and without gender bias.
Use market data to inform what you pay, not as your only defence for why people are paid differently.
Evaluation measures the value of work, while job architecture connects people to roles. Pay principles establish the rules, bands set the boundaries, contextual criteria explain individual differences and market data provides the price check.
Together, they turn pay from a series of judgement calls into a consistent system where decisions can be explained, evidenced and defended.
See how RoleMapper brings job evaluation and job architecture together to build a more consistent, transparent and defensible approach to pay. To learn more, watch our panel discussions on Defensible Pay: what stands up...and what doesn't