Job Evaluation Questionnaire: How to Build One That Scores Cleanly

Job Evaluation Questionnaire: How to Build One That Scores Cleanly

Every point-factor system runs on the same fuel: a written description of what a job actually demands. The job evaluation questionnaire is how you collect it. Get the questionnaire right and scoring goes fast, committee debates stay short, and your grades survive scrutiny. Get it wrong and you spend the next six months arguing about whether "manages complex projects" means a $40,000 vendor renewal or a $12 million platform migration.

Most questionnaires fail for a boring reason. They are written as job description templates — duty lists, reporting lines, nice-to-have skills — when they need to be written as measurement instruments. A questionnaire is not there to describe a job. It is there to produce the specific evidence your factor scales require, in a form a stranger can score consistently.

This guide covers how to structure a job evaluation questionnaire around your factors, what to ask, what to never ask, and how to keep the data honest.

TL;DR

• A job evaluation questionnaire collects the evidence needed to score a job against your compensable factors — nothing more.
• Build it backward from your factor degree scales. Every question should map to a factor; every factor should have at least one question.
• Ask for evidence, not self-ratings. "How many people report to you and at what levels?" beats "Rate your leadership responsibility 1–5."
• Cap it at 25 to 35 questions. Longer forms get skimmed, and skimmed forms produce noise.
• Have the manager review and the analyst verify. Unverified employee self-reports inflate scores by a grade or more.

What a Job Evaluation Questionnaire Actually Does

A job evaluation questionnaire (sometimes called a JEQ, a job analysis questionnaire, or a position description questionnaire) is a structured form completed by the jobholder, the manager, or both. It gathers standardized information about a role so that evaluators can score it against a common set of compensable factors.

That last clause is the whole point. The questionnaire is subordinate to the factor plan. If your plan measures problem-solving complexity across five degrees, the questionnaire's job is to surface enough detail to place the role in one of those five degrees — and to leave a paper trail showing why.

It is worth being precise about the boundaries:

A questionnaire can feed a job description. A job description almost never contains enough to score a job. That gap is why so many evaluation projects stall at the data-gathering stage — teams try to score off existing descriptions, discover half the evidence is missing, and start over.

If you have not yet settled how you are collecting job data at all, work through job analysis methods first. The questionnaire is one method among several, and it works best in combination with interviews for a sample of benchmark roles.

Build It Backward From Your Factor Scales

Do not start with a blank form. Start with your factor plan and write questions that force out the distinctions your degrees depend on.

Take a typical five-degree responsibility-for-results scale. Degree 3 might read "accountable for outcomes within a defined function, with a budget under $2M." Degree 4 might read "accountable for outcomes across multiple functions, with a budget of $2M to $10M." To place a role, you need two facts: functional span and budget magnitude. So the questionnaire asks exactly that:

• What budget do you have direct signing authority over? State the annual amount.
• Which functions or departments depend on your decisions to hit their own targets? List them.

Now compare that to what most forms ask: "Describe your level of responsibility." That question produces a paragraph of prose that three evaluators will read three different ways.

Run this mapping exercise for every factor. The factor degree definitions you have already written are your specification document. If a degree boundary depends on a fact your questionnaire never asks for, you have found a gap. If a question does not feed any degree boundary, cut it.

A practical target: two to four questions per factor. With a typical 8- to 12-factor plan, that lands you at 25 to 35 questions. Longer than that and completion quality drops sharply — people start pasting from their job description.

The Question Types That Work

Countable facts. Headcount by level, budget in dollars, number of direct and indirect reports, geographic scope, years of experience required, revenue influenced. These are the backbone. They are hard to inflate and easy to verify against HRIS data.

Concrete-example prompts. "Describe the most difficult problem you solved in the last twelve months. What made it difficult, what options did you consider, and who approved the decision?" One well-chosen example tells you more about problem-solving complexity than a page of duty statements.

Decision-authority questions. "Which of these can you approve without a second signature?" followed by a checklist — hiring, termination, capital spend above a threshold, contract signature, policy exceptions. Authority boundaries map almost directly onto responsibility degrees.

Constraint questions. "Which policies, standards, or regulations constrain how you do this work, and who sets them?" This separates roles that operate inside tight procedure from roles that write the procedure — often the single cleanest signal of level.

Working-conditions checkboxes. Physical demands, hazard exposure, shift patterns, travel percentage, on-call frequency. Keep these factual and specific. Vague working-conditions questions are where gender bias creeps in most quietly, because the physical demands of traditionally male roles get itemized while the sustained concentration, emotional demands, and interruption load of traditionally female roles get omitted entirely. The UK Equality and Human Rights Commission is blunt about this in its guidance on job grading: the factor set has to capture demands present in both male- and female-dominated jobs, or the scheme reproduces the pay gap it was meant to expose.

What to Leave Out

Self-ratings. Never ask someone to score their own factor level. Self-ratings compress toward the top, they vary by personality rather than by job, and they hand the jobholder a number to argue about later.

Performance content. How well someone does the job is irrelevant to what the job is worth. Job evaluation is not performance evaluation, and any question that invites a performance answer contaminates the data.

Person-specific attributes. Degrees held, certifications earned, tenure, or "special skills I bring." You are evaluating the position, not the incumbent. If the role genuinely requires a CPA, that belongs in the required-qualifications question — phrased as a requirement of the job, not an attribute of the person.

Titles as evidence. Do not ask what the role should be called or what grade the jobholder believes it deserves. The answer is always "higher," and it poisons the committee discussion.

Anything you will not score. Every unscored question is a signal to respondents that this exercise is bureaucratic theater.

Running the Collection Process

Sequence matters more than form design here.

1. Pilot on 8 to 10 benchmark jobs. Pick roles that span your levels and functions. See where respondents misread questions before you send the form to 400 people. Your benchmark jobs selection does double duty as the pilot sample.
1. Give respondents an example. Attach one completed questionnaire for a fictional role. Completion quality roughly doubles when people can see what "good" looks like.
1. Route through the manager. The jobholder drafts, the manager reviews and adds or corrects. Two signatures on the form, with disagreements noted rather than silently overwritten. Those noted disagreements are often the most useful data in the whole exercise.
1. Verify the countable facts. Cross-check headcount, budget, and reporting lines against HRIS and finance data before scoring. This step alone catches most inflation.
1. Hand clean packets to the committee. The job evaluation committee should receive verified questionnaires, not raw submissions. Scoring live from unverified data turns every session into a fact-finding meeting.

US federal classifiers have worked this way for decades. OPM's Classifier's Handbook stresses documenting only the major duties and the aspects that actually affect the final classification, precisely because everything else adds length without adding evidence.

Building your first factor plan and questionnaire from scratch? See how PointFactors structures factor scales and scoring before you commit to a form design.

Keeping the Questionnaire Honest Over Time

Questionnaires rot. Roles change, the business reorganizes, and a form written for a 2023 org chart stops asking the right questions by 2026.

Two habits keep it current. First, review the questionnaire whenever you revise a factor degree scale — the two documents are a matched pair, and changing one without the other creates silent scoring drift. Second, sample-audit completed questionnaires annually: pull twenty at random, re-verify the countable facts, and check whether the assigned degrees still hold. If more than a couple have moved, you have a re-evaluation backlog, not a paperwork problem.

The EHRC's guidance on carrying out job evaluation frames analytical schemes as the mechanism that lets an employer demonstrate its grading system is fair and free of sex bias — and that only works if the underlying evidence is current and consistently gathered. A stale questionnaire quietly undermines that defense.

Frequently Asked Questions

How long should a job evaluation questionnaire be? Twenty-five to thirty-five questions, completable in 45 to 60 minutes. Two to four questions per compensable factor is a reliable rule of thumb. If yours runs to 60 questions, some of them are not feeding a scoring decision.

Who should complete it — the employee or the manager? Both, in sequence. The jobholder drafts because they know the day-to-day reality. The manager reviews because they know how the role fits the wider structure. Record disagreements rather than resolving them silently; they often reveal genuine ambiguity about the role.

Can I use one questionnaire for every job in the organization? Yes, and you should. A single instrument is what makes scores comparable across functions, which is the entire basis of internal equity. Add optional sections for genuinely distinct conditions — plant and field roles usually need a fuller working-conditions block — but keep the core factor questions identical for everyone.

What is the difference between a job evaluation questionnaire and a job analysis questionnaire? In practice the terms overlap heavily. Job analysis questionnaires tend to be broader, gathering data for job descriptions, selection, and training as well as evaluation. A job evaluation questionnaire is narrower and purpose-built: it collects only what your factor scales need to score.

Do I still need interviews if I have questionnaires? For benchmark jobs, yes. Interview the roles that anchor your structure, because errors in those propagate everywhere. For the remaining population, verified questionnaires plus manager sign-off are usually sufficient.

How do I stop people from inflating their answers? Ask for countable facts you can verify, require manager sign-off, and cross-check against HRIS and finance data. Also tell people plainly that the exercise evaluates the job, not the person, and that grades are not being cut. Most inflation is defensive, not dishonest.

Should the questionnaire mention pay or grade? No. Any reference to current grade, salary, or target level anchors the respondent and biases the description. Evaluators should ideally score without seeing the current grade at all.

Get the Instrument Right Before You Score a Single Job

The questionnaire is the cheapest place in a job evaluation project to fix a problem and the most expensive place to leave one. A form that asks for verifiable facts, maps cleanly onto your factor degrees, and gets reviewed by two people will carry a whole evaluation cycle. A form that asks people how responsible they feel will generate months of rework.

Build it backward from your scales, pilot it on benchmarks, verify the numbers, and audit it once a year. See how PointFactors turns structured job data into scored, defensible grades — book a demo.

Justin Hampton is the founder and CEO of PointFactors.