How to Write a Job Description That Holds Up in Job Evaluation

How to Write a Job Description That Holds Up in Job Evaluation

Most job descriptions are written for recruiting. They get drafted in a hurry, posted, filled, and then never opened again — until the day you need to evaluate the job, defend a grade, or explain to a manager why their new "Senior Manager, Strategic Operations" lands at grade 11 instead of 13. That's when you discover the description says "manages key initiatives and drives results" and nothing else.

A job description is the raw input to every downstream compensation decision you make. Evaluate a job from a vague description and you get a vague score. Score it wrong and the grade is wrong, the range is wrong, and the pay decision you make three years from now inherits the error.

This guide covers how to write a job description that works as a compensation document: what to capture, what to leave out, and how to structure it so a point-factor evaluation produces the same score no matter who runs it.

TL;DR

• A job description written for recruiting rarely contains enough detail to evaluate the job — you need decision authority, scope figures, and required qualifications, not adjectives.
• Write the job, not the person. Evaluation scores the role as designed, not the incumbent's performance or tenure.
• Capture each compensable factor explicitly: skill, effort, responsibility, and working conditions, plus your sub-factors.
• Quantify scope. "Manages a budget" is unscoreable. "Owns a $4.2M operating budget across three cost centers" is scoreable.
• Mark essential functions clearly — the EEOC treats a written description prepared before hiring as evidence of what the job actually requires.
• Refresh descriptions on a cycle, not after a dispute. A description revised mid-argument looks like it was written to win the argument.

Start with job analysis, not a blank page

Writing comes last. Before anyone types a word, you need facts about the role: what the person does, how often, with what authority, using what knowledge, under what conditions. That's job analysis — the structured process of collecting those facts through interviews, observation, questionnaires, or a combination.

The practical version for most comp teams: send the incumbent and manager a structured job evaluation questionnaire, then hold a 30-minute follow-up to resolve the contradictions. You will find contradictions. Managers routinely describe a role as having budget authority that the incumbent says requires two signatures above them.

If you're standing up a brand-new role with no incumbent, use the U.S. Department of Labor's O*NET OnLine database as a starting library. It publishes task statements and skill requirements for more than 1,000 occupations. Use it as a checklist against your draft — never as the draft itself, because it describes the occupation in general, not your job in your organization.

The eight sections that actually matter

Skip the corporate boilerplate. A description that supports evaluation needs these, in roughly this order.

1. Job title. Use your internal title standard, not whatever the hiring manager wants on a business card. If you don't have one yet, job titling conventions is the place to start. Also record the working title separately if it differs.

2. Job summary. Three to five sentences on why the role exists and what it's accountable for. Test: if you deleted the role tomorrow, what stops happening? That's the summary.

3. Essential functions. The core duties, each as a task statement: action verb, object, purpose. "Reconciles month-end intercompany balances across four entities to close the consolidated ledger within five business days." Add a rough time allocation to each — it forces honesty. If eleven duties add up to 180% of a job, you're looking at two jobs.

4. Decision authority and scope. This is the section most descriptions omit and most evaluations need. Spell out spending authority in dollars, headcount supervised (direct and indirect), revenue or budget influenced, geographies covered, and what decisions the role makes alone versus recommends.

5. Required qualifications. Education, years and type of experience, licenses, certifications. Write the minimum to perform the job competently, not your ideal candidate. Inflated requirements inflate the skill factor score and quietly push the grade up.

6. Knowledge, skills, and abilities. Specific and testable. "Advanced Excel" means nothing. "Builds and audits multi-sheet financial models with nested lookups and scenario toggles" means something.

7. Relationships and influence. Who the role interacts with, how often, and to what end. Explaining a policy to a peer is a different level of contact than negotiating a contract with a Fortune 500 procurement team.

8. Working conditions and physical requirements. Travel percentage, on-call rotation, shift patterns, plant or field exposure, lifting requirements. Most office roles have a short version of this section. Skipping it entirely means your working-conditions factor scores zero for jobs where it shouldn't.

Write for the compensable factors you actually use

Here's the step that separates a comp job description from an HR one. Your evaluation plan scores jobs against weighted compensable factors — typically skill, effort, responsibility, and working conditions, broken into sub-factors. If your description doesn't contain evidence for a factor, the evaluator guesses. Guesses vary. Scores drift.

Before you finalize a description, run this check:

If every row on the right sounds like your current library, that's normal — and it's exactly why two evaluators score the same job three grades apart.

Once your descriptions carry this level of detail, a point-factor evaluation becomes mechanical rather than argumentative. PointFactors reads the description, scores it against your weighted factors, and shows the evidence behind every degree assignment — so the conversation with a manager is about the facts in the description, not about who feels strongly.

Rules that keep descriptions defensible

Describe the job, not the incumbent. Job evaluation scores the role as designed. If the description says "leverages Maria's twelve years of vendor relationships," you've written a performance review, and the job re-levels the moment Maria leaves.

Use present-tense action verbs. "Approves," "reconciles," "designs," "supervises." Avoid "assists with," "participates in," and "is responsible for" — they hide the actual level of authority, which is the thing you're trying to measure.

Mark essential functions explicitly. Under the ADA regulations at 29 CFR 1630.2(n), a written job description prepared before advertising or interviewing is listed as evidence of a job's essential functions. It isn't conclusive on its own — a duty isn't essential just because someone typed it — but a description written before the fact carries weight that one revised during a dispute does not.

Don't let the title carry the classification. The U.S. Department of Labor is explicit in Fact Sheet #17A that job titles do not determine FLSA exempt status; the actual duties and salary do. If your exemption analysis depends on a description that says "manages assigned projects," it depends on nothing. Spell out the exempt duties — the discretion exercised, the matters of significance involved, the supervision performed.

Avoid gendered and coded language. "Strong," "aggressive," "he," and "manpower" have no place in a document used to establish equal value between jobs. This matters more every year as equal-value frameworks spread across jurisdictions.

Date every version. Record the effective date, the last review date, and who approved it. When someone challenges a grade in 2029, you'll want to show which version of the job was evaluated.

Keep them current without boiling the ocean

A library of 400 descriptions nobody has touched in six years is a liability, not an asset. You don't need to rewrite everything at once.

Prioritize in this order: benchmark jobs first, since they anchor your structure to the market; then high-headcount roles, where an error multiplies; then roles with recent turnover or grade disputes; then everything else on a rolling three-year cycle.

Tie updates to events that already happen — a reorg, a new requisition, an annual manager check-in — rather than launching a standalone "job description refresh project" that dies in month four. And when a manager asks for a re-evaluation, make an updated description the price of admission. It's a reasonable ask, and it keeps the library alive for free.

FAQ

How long should a job description be?

One to two pages for most roles. Long enough to cover the eight sections above with real specifics, short enough that managers will actually read and approve it. If you're past three pages, you're probably describing two jobs or listing every task instead of the essential ones.

How many essential functions should a job description list?

Usually five to eight. Group related tasks under a single function rather than listing twenty micro-tasks. A useful test: each essential function should represent at least 5–10% of the role's time. Below that, it's a task, not a function.

What's the difference between job analysis and a job description?

Job analysis is the process of gathering facts about a role; the job description is the document that results from it. We covered the distinction in detail in job analysis vs job description.

Should the job description include the salary range?

Keep the pay range out of the description itself and store it in your structure, where it can be updated independently. Job postings are a different matter — a growing number of jurisdictions require a good-faith range in the advertisement, and posting requirements change far more often than the job does.

Can I use AI to write job descriptions?

For drafting and standardizing language, yes — it's good at turning messy interview notes into clean task statements. What it can't do is invent facts about your organization. AI given a vague input produces a polished, confident, vague output, which is worse than an obviously bad draft because it looks finished. Feed it real job analysis data and review every scope figure.

How often should job descriptions be updated?

Review on a three-year cycle at minimum, and immediately when the role materially changes — new reporting line, added budget authority, a significant shift in duties. Update before a dispute, not during one.

Does a better job description actually change the evaluated grade?

Often, yes — in both directions. Roles get downgraded when a description finally reveals the "manager" title sits over zero reports, and upgraded when it surfaces decision authority nobody had documented. That's the system working. The goal isn't a particular grade; it's a grade you can defend.

Fix the input, and the rest gets easier

Every complaint about job evaluation — it's slow, it's inconsistent, it's subjective — traces back to the same place. Evaluators are asked to score jobs from documents that don't describe them. Tighten the descriptions and the inconsistency largely disappears.

Start with your benchmark jobs. Rewrite ten of them using the eight sections and the factor checklist above, then re-evaluate them and see how much the spread between evaluators narrows. It's the cheapest quality improvement available to a comp team.

Want to see what your current descriptions actually score? Book a PointFactors demo and we'll run a handful of your real job descriptions through the evaluation engine — factor by factor, with the evidence behind every degree — so you can see exactly where the detail runs out.

Justin Hampton is the founder and CEO of PointFactors.