Job Evaluation: The Question Behind Every Pay Decision

Sooner or later it happens in every company. Two people on the same team, doing what looks like the same job, find out they're paid differently. Maybe it came up over lunch. Maybe someone saw a figure they weren't supposed to see. Maybe a new hire walked in earning more than a colleague who'd been there four years.

The person goes to their manager and asks a simple question: why?

That moment tells you almost everything about how an organization actually makes pay decisions. It's the moment a real job evaluation is supposed to prepare you for. Because in a lot of companies, the honest answer is some version of "that's how it worked out." Negotiated here, matched there, adjusted at some point by someone who has since left. For years, "that's how we've always done it" and "it was a management call" were enough. People accepted them, or at least stopped asking.

They don't anymore.

A few things shifted at the same time. Pay transparency rules are spreading across markets, and they don't only ask you to publish numbers, they ask you to stand behind them. Internal equity moved from an HR concern to a board-level risk. And employees simply talk now, openly, across teams and across companies. The combined effect is that the gap between what you pay and what you can explain about why you pay it has become very visible, very fast.

The problem usually isn't the salaries

Here is the thing we see in nearly every organization we work with: the issue is rarely the salary levels themselves. People are far more reasonable about pay differences than managers assume. What they can't tolerate is the absence of a shared logic behind those differences.

When there's no clear job architecture underneath compensation, every exception becomes a question mark. And every unanswered question mark, given enough time, hardens into a trust issue. One person earning more than another isn't a problem if there's a reason anyone can follow. It becomes a problem the moment the only available reason is "because we decided so."

Transparency is unforgiving in this specific way. The instant pay data becomes visible, its foundation gets examined too. You can't reveal the numbers and hide the reasoning. If the reasoning was never built, transparency doesn't expose unfair pay so much as it exposes the fact that no one ever really worked out why.

Consistency matters more than perfection

There's a common misread of what job evaluation is for. People imagine its purpose is to produce a single, flawless, scientifically correct score for every role. It isn't, and chasing that is a good way to never finish.

What organizations actually need is more modest and more useful: roles that are evaluated against the same logic, differences that can be explained in plain language, and a structure that holds together when someone looks across it. Internal consistency beats theoretical precision every time, because consistency is what survives a conversation with an employee.

So the test isn't whether your scoring is perfect. The test is whether, when two roles look similar on paper but are paid differently, you can clearly say why. If you can, the difference is defensible. If you can't, no amount of precision elsewhere will save you.

From gut feel to a system

When pay is settled role by role, in isolation, what you end up with is a collection of individual decisions that were each reasonable at the time and incoherent in aggregate. Strong negotiators do well. People who don't push do worse. A manager's instinct in one department doesn't match the instinct of a manager in another. None of it is malicious. It's just subjective, and subjectivity doesn't scale, and it doesn't explain itself.

Job evaluation replaces that instinct with a structured, objective basis for comparison. Not to remove judgment, but to give judgment something to stand on. The point is to be able to trace any pay decision back to a logic that existed before the decision, rather than reaching for a justification after the fact.

Is job evaluation a project or core infrastructure?

For a long time, job evaluation was treated as a one-off exercise. You brought in consultants, ran a project, produced a thick deck, and shelved it until the next reorganization made it obsolete.

That model doesn't fit how organizations work now. Roles change. New functions appear. The org chart you graded eighteen months ago has drifted. External support still helps, but the capability itself has to live inside the company: you need to understand your own job structures, build a compensation strategy on top of them, and keep updating both as the organization evolves. Job evaluation has quietly moved from being a project you complete to being infrastructure you maintain.

So, the real question

All of which means the question worth asking isn't "should we do job evaluation?" That framing is already outdated. It treats fairness as an optional initiative rather than something your people are going to demand answers about whether you've prepared for it or not.

The better question is much simpler, and a little uncomfortable.

If one of your employees came to you tomorrow and asked why they earn what they earn, could you answer clearly, confidently, and in a way that would hold up if they repeated it to the person sitting next to them?

If the answer is yes, you've already done the work. If it's no, that's not a pay problem. It's a foundation problem, and it's worth fixing before someone asks.

Common questions

What is job evaluation?

A structured method for assessing the relative value of every role in an organization — based on the work itself, not the person or the title. It produces a consistent, objective basis for comparing roles, and that basis is the foundation every defensible pay and grading decision is built on.

Isn't that the same as a salary survey or market benchmarking?

No. Market data tells you what a role is paid elsewhere; job evaluation tells you how your own roles relate to each other internally. You need both — benchmarking for external competitiveness, evaluation for internal fairness.

Does pay transparency require job evaluation?

In the EU, pay transparency rules make an objective basis for comparing roles very hard to avoid. The EU Pay Transparency Directive (2023/970) requires pay structures that let you assess whether workers are in a comparable situation in terms of the value of their work, using objective, gender-neutral criteria such as skills, effort, responsibility and working conditions — and those criteria have to be transparent and accessible to employees. In practice that means a structured way to evaluate and classify roles, which is exactly what job evaluation provides. Member states' deadline to transpose the directive into national law was June 2026, with pay-gap reporting obligations following.

Isn't job evaluation subjective?

Not when it's done properly. A structured evaluation applies the same defined factors and the same decision logic to every role, so the outcome rests on a documented comparison rather than personal opinion. Judgment still plays a part — but it is controlled, consistent, and traceable. That is what makes a grade defensible: you can show exactly how it was reached, not who assessed it or who negotiated hardest.

How often should we revisit it?

Treat it as living infrastructure, not a one-off project. Roles change, new functions appear, and the structure drifts — the value comes from keeping it current as the organization evolves.