
7 Job Evaluation Mistakes That Quietly Skew Your Pay Bands
Date Published
7 Job Evaluation Mistakes That Quietly Skew Your Pay Bands
A bad job evaluation rarely fails loudly. It fails by a few points here and a grade there, until two jobs with similar demands sit in different pay bands and nobody can explain why.
Those small errors compound. A job scored 30 points too high lands one grade above where it belongs. Multiply that across fifty jobs and your structure no longer reflects the value of the work. You pay more than you should for some roles, you underpay others, and you lose the ability to defend either decision.
This guide covers the seven mistakes we see most often in point-factor programs, what each one does to your bands, and the fix. Most take an afternoon to correct once you know where to look.
TL;DR
- Most evaluation errors come from scoring the person or the title instead of the job's requirements.
- Weak factor definitions and unchecked committee dynamics cause the rest.
- Each mistake shifts points, points shift grades, and grades shift pay bands.
- The fixes are cheap: write scales with observable anchors, score independently before you debate, and document every score.
- Audit a sample of 10 to 15 jobs against these seven checks before your next structure review.
Why small scoring errors become big pay problems
In a point-factor system, you score each job against weighted compensable factors. The total points place the job in a grade, and the grade sets the range. That chain is the strength of the method, and also the risk. An error at the first link travels all the way to the paycheck.
Here is the math. Say your grades are 40 points wide and a Payroll Specialist belongs at 318 points. Score it at 352 because the manager is persuasive, and the job moves up a grade. If the range midpoints are 8% apart, you now overpay that role by roughly 8% for every person who holds it, every year.
Mistake 1: Scoring the person instead of the job
This is the most common error. The incumbent is brilliant, so the evaluator gives the job credit for skills the role does not require.
What it does to your bands: the grade follows the incumbent. When that person leaves, you hire into a range built for a star.
The fix: score the role as designed, assuming a fully competent person. Write each rationale in terms of what the job demands ("requires a bachelor's degree equivalent and five years of applied experience"), never what the current holder brings. This is the same discipline that separates job evaluation from performance evaluation.
Mistake 2: Letting titles do the scoring
"Director" sounds senior, so the job scores senior. But titles vary wildly between companies and even between departments.
What it does to your bands: title inflation pushes jobs into grades their content does not support, and it creates internal inequity between similar roles with different labels.
The fix: evaluate duties and requirements only. The EEOC makes the same point in its Equal Pay Act guidance: consideration should be given to the actual job duties, not job titles or classifications. Hide the title from evaluators if your tool allows it. Our guide to job titling conventions shows how to keep titles from distorting grades.
Mistake 3: Vague factor definitions and degree scales
If "Problem Solving, Level 3" means one thing to Finance and another to Operations, your scores are opinions with numbers attached.
What it does to your bands: two evaluators score the same job 40 points apart. Which grade the job lands in depends on who happened to score it.
The fix: write every degree with observable anchors. Instead of "moderate complexity," write "chooses among established procedures; escalates novel problems to a manager." Test the scale by having three people score the same five jobs independently. If they disagree by more than one degree, the definition needs work. Our guide to writing factor degree definitions gives a template.
Mistake 4: Evaluating from stale or thin job data
A job description written in 2019, or a two-line summary pulled from a posting, cannot support a defensible score.
What it does to your bands: you score the job people remember, not the job that exists. Roles that have grown stay under-graded. Roles that shrank stay over-graded.
The fix: collect structured data through a job evaluation questionnaire or a proper job analysis before scoring. Date every input and set a trigger to re-evaluate when the job changes materially.
Mistake 5: Weighting factors by gut feel
Teams often default to equal weights, or they weight the factors the CEO cares about most. Neither reflects what the organization actually values.
What it does to your bands: the weights decide which jobs rise. Overweight "Working Conditions" in a mostly office workforce and you inflate a few operational roles. Underweight "Accountability" and you compress your managers and senior specialists together.
The fix: set weights deliberately, then test them. Run your 20 benchmark jobs through the system and check that the resulting order matches common sense and your market data. If the Controller scores below the Accounts Payable Supervisor, something is off. The full method is in our guide to weighting compensable factors.
Mistake 6: Letting the loudest voice win in committee
A committee should improve accuracy. Without structure, it often just amplifies the most senior or most forceful person.
What it does to your bands: anchoring. The first score spoken aloud becomes the group's answer, and managers advocating for their own teams push grades up.
The fix: have every member score independently and submit before any discussion. Discuss only the factors where scores differ by more than one degree. Rotate a facilitator who does not own the jobs under review. See how to run a job evaluation committee for a full meeting structure.
Mistake 7: Ignoring bias and skipping documentation
Some factor sets quietly undervalue work that is common in female-dominated roles, such as care, coordination, and emotional demands. And when nobody writes down why a job scored what it did, you cannot defend the grade later.
What it does to your bands: you build in pay differences you cannot justify, and you cannot reconstruct your reasoning when an employee, auditor, or regulator asks.
The fix: check that your factors capture the full range of demands in your workforce, not just the ones typical of traditionally male roles. The EU's EIGE toolkit on gender-neutral job evaluation is a good reference even if you operate in the U.S. Then record the rationale, evaluator names, and date for every score. Documentation is what makes an appeal answerable in ten minutes instead of ten days.
A quick audit you can run this week
You do not need to re-score everything. Pull 10 to 15 jobs, including a few that employees have challenged, and run this check:
Check | What to look for | Red flag |
|---|---|---|
Rationale | Is each score tied to job requirements? | Mentions of the person, or "seems senior" |
Consistency | Do similar jobs score within one degree? | Two similar roles 40+ points apart |
Title test | Would the score change if the title changed? | Yes |
Data freshness | Is the job data under 24 months old? | Older, or undated |
Documentation | Can you find who scored it and why? | No record |
Any job that fails two or more checks goes on the re-evaluation list.
FAQ
What is the most common job evaluation mistake?
Scoring the incumbent instead of the role. It feels natural because you know the person, but it ties the grade to an individual instead of the job's requirements.
How do you know if your job evaluation is biased?
Compare scores for jobs with similar demands but different workforce demographics. If female-dominated roles consistently score lower than male-dominated roles with comparable content, review your factor definitions and weights.
How many evaluators should score each job?
Three to five works well. Fewer gives you no check on individual bias. More slows the process without adding accuracy, as long as you score independently first.
How often should you audit your evaluations?
Audit a sample every year and re-evaluate individual jobs when their content changes. A full structure review every two to three years is a reasonable cycle for most organizations.
Can software prevent these mistakes?
It helps with consistency, documentation, and independent scoring. It cannot fix a vague factor definition or a biased weighting. You still need a clear plan, as covered in our guide to designing a job evaluation plan.
Do these mistakes affect legal risk?
Yes. Under the Equal Pay Act, jobs are compared on skill, effort, responsibility, and working conditions, and the EEOC notes that jobs need only be substantially equal, not identical. Grades that follow titles or incumbents are hard to defend.
Put it to work
If you want a structured way to catch these errors, start with the job evaluation process and the point-factor method overview. When you are ready to score jobs consistently without wrestling spreadsheets, see how PointFactors job evaluations work.
Ready to score your jobs with confidence? Start free with PointFactors and we will walk through your own job data.
By Justin Hampton, founder and CEO of PointFactors.