Job Evaluation Appeals: How to Handle Reclassification Requests

Job Evaluation Appeals: How to Handle Reclassification Requests

Every job evaluation system eventually gets challenged. A manager reads the grade assignment, decides it undervalues their team, and sends you an email that starts "I think there's been a mistake." How you answer matters more than the grade itself. Handle it well and your structure gains credibility. Handle it badly — no process, no timeline, no record — and you teach the organization that grades are negotiable if you push hard enough. This guide covers the appeal process comp teams actually need: what qualifies as an appeal, what does not, who decides, how long it should take, and how to document the outcome so the next challenge is easier.

TL;DR

• An appeal challenges how a job was scored. A reclassification request says the job itself changed. Route them differently — they need different evidence.
• Publish a written appeal policy before you need one. A 30-day filing window and a 30–45 day decision window are common and workable.
• Appeals must be argued on the original job documentation. If the manager rewrites the job description, that is a new evaluation request, not an appeal.
• Performance, tenure, retention risk, and the incumbent's credentials are never valid appeal grounds. Only job content is.
• Expect appeals on 3–5% of evaluated jobs in a first-year rollout. Track them — a cluster in one factor means your degree definitions are unclear.

Appeal or reclassification? Sort this first

These two requests arrive in the same inbox and look identical at a glance. Treating them the same wastes weeks.

An appeal says: you scored this job wrong. The job description is accurate and the duties have not changed, but the committee applied a factor degree incorrectly or overlooked evidence already in the file. The remedy is a re-review of existing documentation.

A reclassification request says: this job is no longer the job you scored. Duties grew, a team was added, a compliance responsibility moved in. The remedy is fresh documentation and a new evaluation.

Ask one question to sort them: has the work changed since the evaluation? If yes, it is a reclassification. If no, it is an appeal. Say this out loud to the requesting manager, because most will happily argue both at once.

A useful reclassification trigger: require a material change of roughly 10–15% of the job's duties or scope before re-evaluating. Below that, you are looking at normal job drift, and re-scoring every small change turns your structure into a treadmill.

Write the policy before the first appeal lands

The worst time to design an appeal process is while a frustrated VP waits on you. Write it into your job evaluation charter at launch. Six elements cover it.

1. Who can file. Typically the incumbent, the manager, or the department head. UC Berkeley requires the appeal to carry the department head's signature, which quietly filters out impulse appeals.

2. The filing window. Thirty calendar days from written notification is the common standard. Some organizations use ten business days. Pick one and enforce it — an open-ended window means an evaluation is never final.

3. What must be in the filing. Require the appellant to name the disputed factors and explain in writing why the assigned degree is wrong. "This grade feels low" is not an appeal. "Under Factor 3, Supervision Exercised, the job directs four staff and two contractors, which meets Degree 4 rather than the Degree 3 assigned" is one you can adjudicate.

4. Who decides. Someone other than the person who made the original call — a senior comp leader, an appeals subcommittee, or the full job evaluation committee if the first score came from one analyst.

5. The decision window. Commit to a date. Federal agencies must act on classification appeals within 60 calendar days or forward the case to the Office of Personnel Management. For most private employers, 30–45 days is achievable and feels responsive.

6. Finality. State whether the decision is final or whether a second level exists. In the federal system, employees may appeal to their agency or directly to OPM, but not both at once. Most corporate structures should stop at one level. Two is defensible. Three is a bureaucracy.

The rule that saves you: appeals run on the original documentation

This is the single most important line in an appeal policy, and the one most often left out.

An appeal is reviewed against the job description as originally submitted and approved — not a revised version. If the manager rewrites the job description to strengthen their case, that is not an appeal. That is a new classification review request, and it goes to the back of the normal queue with fresh documentation.

Without this rule, every appeal becomes an invitation to embellish. Managers learn that the way to a higher grade is a more dramatic second draft, and your job evaluation questionnaire data quality degrades across the whole organization. With the rule, the incentive flips: managers write accurate descriptions the first time, because the first time is the only version that counts.

Berkeley states it plainly — the appeal process "is not intended to consider revisions of the job description directed toward achieving a desired classification." Borrow that sentence.

What is out of scope — and how to say so kindly

Job evaluation scores the job, not the person. Appeals are where that distinction gets tested hardest. These are never valid grounds:

• The incumbent's performance. A top performer in a Grade 8 job is a top performer in a Grade 8 job. Performance belongs in your merit process.
• Tenure in the role. Twenty years of service does not change the work.
• Qualifications the job does not require. A master's degree in a role that requires a bachelor's is a hiring decision, not a scoring input.
• Volume of work. More of the same work does not change factor degrees. Materially different work might — and that is a reclassification.
• Retention or market pressure. A hot market has a real solution: a market premium, a geographic differential, or a range adjustment. Keep market pricing and job evaluation in separate lanes.

Publish these boundaries in the policy, not in the rejection letter. A manager who learns them after their appeal fails feels ambushed. One who read them in advance usually self-selects out.

Running a point-factor system without an audit trail? PointFactors keeps every score, every factor rationale, and every re-evaluation in one record — so an appeal takes an afternoon instead of a week of archaeology. See how it works.

A five-step appeal workflow that fits on one page

Step 1 — Intake and triage (day 0–3). Log the appeal. Confirm it arrived inside the window, names specific factors, and carries the required signature. Sort it: appeal or reclassification. Send a written acknowledgment with the decision date — that costs nothing and eliminates half your follow-up emails.

Step 2 — Assemble the file (day 3–10). Pull the original job description, the completed questionnaire, the org chart as it stood at evaluation, the scoring sheet with factor rationale, and the comparators used. Add nothing new. The reviewer should see exactly what the original panel saw, plus the appellant's argument.

Step 3 — Independent re-review (day 10–25). The reviewer re-scores only the disputed factors against your published factor degree definitions, then sanity-checks the result against two or three benchmark jobs at the proposed grade. If the appealed job would now outrank a job everyone agrees is bigger, the appeal fails on internal logic alone.

Step 4 — Decision and written rationale (day 25–35). Three outcomes: grade confirmed, grade changed, or referred to full re-evaluation because the file revealed the job did change. Write two or three sentences per disputed factor. An undocumented reversal is the fastest way to invite the next twelve appeals.

Step 5 — Communicate and close (day 35–45). Notify the appellant and the manager in writing. If the grade changed, state the effective date and whether pay adjusts retroactively — decide that in advance, not case by case. File everything with the job record.

Track your appeal rate — it is a diagnostic

Most comp teams treat appeals as noise. They are signal.

In a first-year point-factor rollout, an appeal rate of roughly 3–5% of evaluated jobs is normal. Below 2% usually means people do not know the process exists. Above 10% means something structural is wrong. Look at where they cluster:

• One factor — your degree definitions there are ambiguous. Rewrite them with sharper thresholds and worked examples.
• One function — that group writes job descriptions in a different register. Engineering managers who write in scope and impact out-score administrative managers who write in tasks, even for equivalent work.
• Jobs that were slotted rather than scored — job slotting is fast but produces weaker rationale. Score the contested ones fully.
• A reversal rate over 25% — your original panel is moving too fast. Slowing the first pass down is cheaper than a second one.

Log every appeal with the job, the disputed factors, the outcome, and the reviewer. After a year you will have a map of exactly where your compensable factors need work.

Worked example: the Senior Analyst appeal

A finance director appeals the Grade 9 assigned to a Senior Financial Analyst, arguing for Grade 10. The dispute is Factor 2 (Problem Solving) and Factor 5 (Impact). The job description describes building monthly variance reports and supporting the annual budget cycle; the appeal argues the role "drives capital allocation decisions."

On Factor 2, the panel assigned Degree 3 (analyzes within established frameworks); the appeal argues Degree 4 (develops new analytical approaches). The documentation describes recurring reporting against an existing model — Degree 3 stands.

On Factor 5, the panel assigned Degree 3 (department-level impact); the appeal argues Degree 5 (enterprise impact). The job recommends; the CFO decides. Recommendation authority without decision authority is not enterprise impact — Degree 3 stands.

Total: 612 points, unchanged, Grade 9 confirmed. But the reviewer notes something real: the job description is two years old and predates the analyst taking over scenario modeling for two business units. That is a reclassification trigger, not an appeal issue. The decision letter confirms Grade 9 and invites the director to submit updated documentation for a full re-evaluation.

The structure held, the rules were applied consistently, and the manager got a legitimate path forward instead of a door in the face.

FAQ

What is a job evaluation appeal? A formal request to re-review how a job was scored under your evaluation method, based on the documentation that already exists. It challenges the application of factors and degrees — not the job description itself.

How long should employees have to file an appeal? Thirty calendar days from written notification of the evaluation decision is the most common standard. Some organizations use ten business days for internal committee decisions. Whatever you choose, publish it and apply it consistently.

Can the job description be updated during an appeal? No. Appeals are decided on the originally submitted documentation. A revised job description converts the matter into a new evaluation request, which is the right answer when the job genuinely changed.

Who should decide appeals? Someone who was not part of the original decision. A senior comp leader, an appeals subcommittee, or the full evaluation committee if the first score came from an individual analyst. Independence is what makes the decision credible.

What happens to pay if an appeal succeeds? Decide this policy before your first appeal. Common approaches: adjust effective the date of the appeal decision, or effective the date the appeal was filed. Retroactive adjustment to the original evaluation date is generous but expensive and sets a precedent. Write it down and apply it uniformly.

Is there an appeal process in the federal system we can model? Yes. The U.S. Office of Personnel Management publishes both its classification appeal procedures and a searchable archive of decided appeals. The written decisions are a free education in how to reason from job content to grade.

Build the appeal process into the system, not around it

An appeal process is not an admission that your evaluation method is weak. It is the thing that makes the method credible. Managers accept grades they can challenge. They resent grades that arrive by decree.

The practical requirement is documentation. Every appeal you win is won on the strength of the original scoring rationale — the factor-by-factor reasoning that says here is why this job scored Degree 3 and not Degree 4. If that reasoning lives in a spreadsheet someone's predecessor built, appeals become archaeology.

PointFactors stores the full evaluation record for every job — scores, factor rationale, comparators, and the complete history of every re-evaluation and appeal. When a manager challenges a grade, you open one record and have your answer. Book a demo and see what a defensible audit trail looks like.

Justin Hampton is founder and CEO of PointFactors, an AI-powered point-factor job evaluation platform for HR and compensation teams.