Job Re-Evaluation: When and How Often to Re-Score Your Jobs

Job Re-Evaluation: When and How Often to Re-Score Your Jobs

You scored every job two years ago. The grades held, the ranges were built, and everyone moved on. Then a Data Analyst started owning the forecasting model, a Customer Service Lead picked up vendor contracts, and a Plant Supervisor inherited a second site. The titles never changed. The jobs did.

Job re-evaluation is how you keep your structure honest after the original project ends. Done well, it protects internal equity and cuts down on appeals. Done badly, it turns into a steady stream of grade-inflation requests. This guide covers what triggers a re-evaluation, how often to run one, and a process that scales without burying your team.

TL;DR

• Re-evaluate a job when its content changes significantly, not when its title, headcount, or incumbent changes.
• Use a trigger-based process for individual jobs and a scheduled review for the whole structure, typically every two to three years.
• Always re-score the whole job against all factors, not only the factor that changed.
• Document every outcome so you can answer appeals and audits with evidence.
• A point-factor system makes this cheap because you compare new scores against the original ones.

What job re-evaluation is (and is not)

Job re-evaluation means re-scoring an existing job against your factors because its demands may have changed. It is a job evaluation activity. It is not a performance review, and it is not a pay decision about one person. You evaluate the job, not the person holding it.

It is also different from job evaluation appeals, although the two overlap. An appeal is an employee or manager disputing a result. A re-evaluation is the formal re-scoring that an appeal, a reorganization, or a scheduled review may trigger.

The five triggers that justify a re-evaluation

Not every change deserves a fresh score. Most jobs shift a little every year. The question is whether the change is large enough to move a factor level. These five triggers are worth acting on.

1. A significant, sustained change in duties. The job now includes work of a different scope or complexity, and it has lasted for months, not weeks. One-off projects and temporary coverage do not count.

2. A change in reporting line or span. A role that moves from supervising 3 people to leading 15, or shifts from reporting to a manager to reporting to a director, often changes the Responsibility and Supervision factors.

3. A reorganization or merger. When you consolidate teams or acquire a company, you need to confirm that like jobs are scored the same way. This is also where job slotting can speed up the work for jobs that clearly match an already-scored benchmark.

4. New technology or process changes. Automation can remove effort from some jobs and add judgment to others. A claims processor who used to key data may now review exceptions flagged by software. The job's skill and decision-making demands changed.

5. A new legal or regulatory duty. Compliance obligations can add accountability to a role. If your structure supports pay equity work, a job whose content has quietly drifted is a risk. In the U.S., the Department of Labor is explicit that job titles do not determine exempt status; the actual duties do. The same logic applies to your grade: the work, not the title, decides.

What does not trigger a re-evaluation

Four common requests should not start a re-score on their own:

• A request for a raise or promotion.
• A change in the incumbent's tenure or performance.
• A title change with no change in duties.
• A change in market pay for the role. That is a market pricing question, covered in market pricing vs job evaluation.

How often to re-evaluate

Run two tracks at the same time.

Track one is event-driven. Individual jobs get re-evaluated when one of the triggers above is met and verified. Set a firm window, such as 30 to 45 days from a complete request to a decision. A request with no deadline becomes a morale problem.

Track two is scheduled. Review the structure as a whole every two to three years, and sooner after a major reorganization. This is a rule of thumb, not a regulation. A fast-changing technology company may need a lighter annual check on its highest-change families. A stable manufacturer may be fine at three years.

In the scheduled review, you do not re-score every job. You sample. Pull your benchmark jobs, confirm their descriptions are still accurate, and re-score any with material changes. If the benchmarks hold, the structure likely holds. If several have drifted, widen the review to the affected job family.

A step-by-step re-evaluation process

Here is a process that works for either track.

1. Receive a written request. Require the manager and employee to describe what changed, with an updated job description or a list of specific duties added or removed.
1. Screen the request. A comp analyst checks it against your trigger list. Is the change significant and sustained? If not, close the request with a written explanation.
1. Verify the facts. Interview the manager and the incumbent, and compare against the existing job description. Use the same techniques you used originally; see job analysis methods.
1. Re-score the whole job. Score every factor again, with the original scores beside the new ones. Do not touch only the factor the requester cares about. Isolating one factor invites inconsistency, because changes in one factor often ripple into others.
1. Route to your committee. Your job evaluation committee reviews scores that move a job across a grade boundary. Minor shifts that stay inside the same grade can be approved by the analyst.
1. Communicate the result. Share the new scores and the reasoning. If the job moves to a new grade, route the pay implications through your normal process.
1. Record everything. Save the request, the evidence, both score sets, and the decision.

A worked example

Say a Customer Service Lead is scored in Grade 7 at 412 points. After a reorganization, the role takes on vendor contract management and now supervises 8 people instead of 3.

You re-score the whole job. Knowledge goes from 80 to 95 points because the job now requires contract and negotiation knowledge. Supervision and responsibility go from 70 to 88. Working conditions and effort stay flat. The new total is 445 points.

Your grade table shows Grade 7 runs 380 to 439 points and Grade 8 starts at 440. The job crosses the line by 5 points. Because it is that close, the committee checks that the scoring was consistent with how you scored similar roles in other departments. They confirm it, and the job moves to Grade 8. The documented before-and-after scores make the decision easy to explain. See how to convert job evaluation points into pay grades for how to set those boundaries.

Common mistakes

Re-scoring only the changed factor. Public-sector guidance on changed jobs is direct on this point. The NHS Employers guidance on re-evaluating changed jobs says an evaluation "should assess the whole job" with reference back to the original, because dealing with only some factors "could lead to inconsistencies." NHS Employers, Re-evaluation of Changed Jobs

Letting the incumbent drive the scoring. Employees understandably describe their jobs at their best. Use a structured questionnaire and verify with the manager.

No cap on frequency. If a job can be re-evaluated whenever someone asks, you will be in a perpetual cycle. Limit repeat requests on the same job to once every 12 months unless there is a documented reorganization.

Ignoring downward changes. If duties are removed, the job may be over-graded. Decide upfront how you will handle that, and apply the rule the same way in both directions. Many employers protect the incumbent's pay while moving the job to the right grade, then treat any pay above the new range as a red-circle rate.

Skipping documentation. An undocumented re-evaluation is not defensible in an audit or dispute.

Why point-factor makes this easier

A non-quantitative method gives you words to compare. A point-factor system gives you scores. When a job changes, you compare two sets of factor scores and see exactly where the movement came from. That makes the screening step faster and the committee conversation shorter. It also gives you a clean audit trail if someone challenges the outcome.

FAQ

How often should we re-evaluate all of our jobs? Review the full structure every two to three years, using benchmark jobs as a sample. Re-score only the jobs and families where the content has changed. Event-driven re-evaluations handle the rest.

Does a title change require a re-evaluation? Not by itself. Evaluate the duties. If the title changed because duties changed significantly, re-evaluate. If it changed for branding or consistency, update the record and leave the score alone.

Who should be able to request a re-evaluation? The manager and employee together. Requiring both to sign off filters out requests that are really pay negotiations.

Should a re-evaluation change the person's pay immediately? It changes the job's grade. Pay changes follow your pay policy, typically a promotion or adjustment process. Decide in advance whether a grade change is effective on the date the duties changed or the date of the decision. The NHS Employers guidance backdates a changed band to when the postholder and manager agreed the job had changed; whichever rule you choose, apply it consistently.

What if a job's score goes down? Treat it like any other result. Document it, communicate it, and apply your red-circle policy so the incumbent is not cut abruptly. Applying the process in both directions is what makes it credible.

Can AI help with re-evaluation? Yes, for the first pass. AI can compare an updated job description against the original and flag factors likely to move. A human still decides the final score. We cover this in more detail in AI in job evaluation.

What documents do we need to keep? The request, the updated job description, the interview notes, both score sets, the committee decision, and the date the change takes effect.

If you scored your jobs once and never looked again, your structure is already drifting. A light trigger process and a scheduled benchmark check will catch most of it before it becomes an equity problem.

PointFactors scores every job against weighted compensable factors and keeps the before-and-after history, so re-evaluations take hours, not weeks. Start free or see pricing.

Justin Hampton is founder and CEO of PointFactors.