Job evaluation vs performance review is a distinction most UK employers never stop to make. The two get folded into one exercise: sit down once a year, talk about the person, nudge the pay. Then an equal pay question lands, or a grading dispute, or a capability case. Suddenly it matters which process produced which decision, and nobody can say. 

Here is the short version. Job evaluation measures the size of a role. A performance review measures how well a person is doing in that role. One looks at the job as if nobody sat in it. The other looks only at the person sitting there. 

Blur the two and you end up with pay decisions you cannot defend and performance evidence you cannot use. This article sets out the difference, why the processes get tangled, the five mistakes that cause real damage, and a way to run both without doubling your admin. 

Job evaluation vs performance review: the difference in plain terms 

Job evaluation grades the role, not the person. It asks what the job demands: the knowledge required, the problems solved, the weight of the decisions carried. The output is a rank order of roles, which anchors your grades and pay structure. Done properly, the same grade comes out whether the role holder is your strongest performer or your weakest. 

A performance review judges the person in the role. It asks how the individual performed against objectives over a set period. The output is feedback, a development plan, and often a rating that feeds bonus or progression decisions. 

Put side by side, the two answer different questions. 

The two also sit at different points in the employment lifecycle. Job evaluation does its work before anyone is hired: it sets what the role is worth, which shapes the advert, the offer and the band. The performance review does its work after hiring, year on year, while the person is in post. Confusing them means using an after-hiring tool to answer a before-hiring question. 

If you have never graded roles formally, start with our step-by-step job evaluation guide for UK employers. It walks through the full process. This article stays on the boundary between the two processes, because the boundary is where employers get hurt. 

Why the two get tangled in smaller businesses 

In a business of 20 or 200 staff there is rarely a reward specialist. The same manager writes the job description, reviews the person, and decides the pay. All three happen in the same meeting, so the paperwork merges into one document. Two years later, that one document is the only record of anything. 

Vocabulary makes it worse. Managers say appraisal, job review, evaluation and assessment interchangeably. Search for the difference between job evaluation and performance appraisal and most answers are written for HR students, not for the owner of a 40-person firm deciding pay on a Tuesday night. 

The deeper cause is that only one of the two has a deadline. Performance reviews have a calendar slot, so they happen. Job evaluation has no natural deadline, so it quietly never happens. Roles end up graded by history and negotiation rather than by any assessment of the work itself. 

A typical version looks like this. A 35-person firm runs annual reviews. Pay rises follow the review scores. Nobody has graded the roles since the founder wrote the first job adverts. Over five years, three people have negotiated their way into pay that no longer matches their duties. Two others do near-identical work on visibly different salaries. No single decision was reckless. The structure that would have caught the drift simply never existed. 

None of this feels like a problem while the business is calm. It becomes one the day someone compares payslips. 

Five mistakes employers make when the two processes blur 

1. Building the pay structure out of appraisal scores 

When appraisal scores decide grades, the pay structure is built on opinions about individuals. Two people can hold identical roles and sit two pay bands apart because one presents better in review meetings. If those two people are of different sexes, that gap is an equal pay question waiting for a trigger. 

Performance appraisal has a legitimate place in pay. It can fairly drive bonus and progression within a grade. It cannot fairly decide what the grade is, because the grade belongs to the role, and the role is the same whoever holds it. 

The test: if your top performer resigned tomorrow, would the role's grade change? If your honest answer is yes, your grades are tracking people, not roles. 

2. Grading the person instead of the role 

When a strong performer holds a role, the role drifts upward. They absorb extra tasks, the job title grows, the salary follows. None of it gets written into the job description. Then they leave. 

Now you are recruiting at an inflated salary for a job that never required it, or offering the real rate and struggling to explain why the last person earned a third more. Either way, the grade stopped describing the work years ago. 

The discipline is simple to state and hard to hold: grade the role as if it were vacant. Reward the person through performance pay, recorded as performance pay, not through quiet regrading. 

3. Answering an equal pay question with a performance answer 

An employee asks why a colleague earns more for what looks like the same work. The instinctive answer is about the people: he has been here longer, she performs better. Under the Equality Act 2010, that answer only carries weight if you can first show the roles are not equal, or show a material factor behind the gap. Section 65 of the Act defines equal work to include work rated as equivalent under a valid job evaluation study. The study is the starting point. Performance is, at best, the second half of the answer. 

Here is the practitioner reality. When a pay dispute turns formal, the first document a claimant's adviser asks for is the job evaluation record. Most SMEs send appraisal forms instead. Appraisal forms are evidence about people, not roles, so they answer a question nobody asked. ACAS guidance on equal pay points employers towards transparent pay systems built on objective criteria, and a consistent evaluation study is exactly that. 

A sound study will not make a pay gap lawful by itself. It defines which roles are equal, which is the question every equal pay conversation starts with. Not having one leaves that question open for someone else to answer. 

4. Regrading the role to engineer a pay rise 

This happens in every growing business. Someone valuable threatens to leave. There is no bonus budget, so the role gets a new title and a higher grade, with no real change in duties. The person stays. The problem arrives later, twice. 

First, everyone in the old grade now has a comparison point for their next negotiation. Second, your structure now contains a grade that cannot be explained by the content of the role. One unexplainable grade undermines the credibility of every other grade the next time you need the structure to hold, whether in a pay review, a restructure, or a dispute. 

If the duties genuinely changed, regrade properly: run a fresh evaluation and record what changed. If they did not, solve the retention problem honestly. A market supplement, labelled as such and reviewable at a set date, is defensible. A fictional grade is not. 

5. Expecting kind appraisals to carry a capability case 

The most expensive appraisal is the kind one. A manager rates a struggling employee as meets expectations for three years to avoid an awkward conversation. In year four, the business decides to act on performance. Capability is a potentially fair reason for dismissal under section 98 of the Employment Rights Act 1996, but fairness turns on evidence of the shortfall and a genuine process. Three years of positive reviews are now the employee's best evidence, and you wrote it. 

This is the reverse side of the confusion. Just as appraisals cannot grade roles, grading paperwork says nothing about how a person performed. Capability cases live or die on honest, contemporaneous performance records. If your review cycle produces polite fiction, fix the cycle first. Our guide to performance management strategy for UK SME leaders covers how to build one managers actually use. 

What each process protects you from 

Job evaluation earns its keep in pay fairness. Because equal work under the Equality Act 2010 includes work rated as equivalent under a job evaluation study, a sound study maps your exposure, and a missing one leaves the map blank. Only analytical schemes, which score each role factor by factor, count as a job evaluation study for equal pay purposes. A felt-fair ranking of job titles carries no weight there at all. The best known analytical approach scores know-how, problem solving and accountability; our Hay method job evaluation guide explains how it works in practice and what it takes to run. 

Performance reviews earn their keep in development, reward and capability. They create the record that supports bonus decisions, promotion decisions and, when it comes to it, a fair capability process. 

Neither document can do the other's job. That is the one sentence worth remembering from this article. And a note on scope: this article covers the law in Great Britain, where the Equality Act 2010 and the Employment Rights Act 1996 apply. Northern Ireland has separate equal pay and unfair dismissal legislation. This is education, not legal advice. If a live pay or capability dispute is already on your desk, take advice on your specific facts before acting. 

How to run both without doubling the admin 

None of this needs an HR department. It needs separation and a trigger list. 

1. Keep two templates. A one-page role grading record, and your existing review form. The grading record scores the role against fixed factors and carries no judgement about the current role holder. 
2. Grade on triggers, review on the calendar. Re-evaluate a role when it is created, when duties materially change, when its pay is challenged, and before you recruit into it. Review people on your normal cycle. 
3. Score roles against the same factors every time. Knowledge, responsibility, decision-making, people managed. Consistency beats sophistication: a simple scheme applied the same way every time is worth more than a clever one applied twice. 
4. Never let one meeting do both jobs. The moment grading or base pay enters a performance conversation, honest feedback stops. The employee defends their salary instead of engaging with their development. 
5. Write conclusions in separate sentences. The role is graded at level three. The person performed above expectations this year. If one sentence mixes the two, the record is contaminated for both purposes. 

Here is what that looks like in practice. An office manager role changes when the firm opens a second site. That is a trigger, so the role gets re-scored, and the new duties move it up a band. The score sheet records the change and the date. Six months later, the role holder has a poor quarter. That belongs in the review file, in the review meeting, against the review objectives. The grade does not move, because the job has not changed. Two files, two decisions, no contamination. 

The total cost is about an hour per role every two or three years, on top of the reviews you already run. That is the entire price of keeping your pay structure and your performance evidence clean, and it is a fraction of the cost of needing either one and finding it missing. 

Where does your business actually stand? 

Most owners find out about a gap like this from the dispute that exposes it. There is a cheaper way to find out. The free HR Health Check takes under one minute and lets you know where your HR is solid and where it is exposed, scored across the areas that surface in real disputes. 

Take the free HR Health Check before the next pay question lands on your desk.