PDQ vs PAQ: Which Job Analysis Questionnaire Is Right for You?

PDQ vs PAQ: Which Job Analysis Questionnaire Is Right for You?

PDQ and PAQ sound like the same thing with one letter swapped. They are not. A position description questionnaire (PDQ) is a job-specific form that the employee and supervisor fill out to document what one position does. A position analysis questionnaire (PAQ) is a standardized, research-built instrument that a trained analyst uses to rate any job against the same fixed list of worker behaviors.

Both are job analysis questionnaires. Both feed job evaluation. But they collect different kinds of data, ask different people to do the work, and fit different projects. Pick the wrong one and you either drown your HR team in analyst hours or hand your evaluation committee forms full of vague task lists.

This guide compares PDQ vs PAQ side by side: who completes each, what each measures, how long each takes, and which one fits a point-factor job evaluation. You will finish with a simple rule for choosing, plus the cases where using both makes sense.

TL;DR

• A PDQ documents one position's specific duties, decisions, and conditions. The incumbent completes it, the supervisor reviews it, and HR uses it to classify and evaluate the job.
• A PAQ is a standardized instrument of about 190 generic worker-behavior items, rated by a trained analyst. It produces comparable, quantified profiles across very different jobs.
• For most point-factor job evaluation projects, the PDQ is the better primary tool: it captures the evidence your compensable factors need, and it scales across hundreds of jobs without a team of analysts.
• Use the PAQ when you need statistically comparable job profiles for research, selection, or validation work, and you have trained analysts to run it.
• Many mature programs use a PDQ for every job and reserve structured analyst methods for benchmark jobs or disputes.

What is a PDQ?

A position description questionnaire is a structured form that captures what one position actually requires. It asks for the job's purpose, its major duties with the percent of time each takes, the decisions it makes, the people it works with, the resources it controls, and the conditions it works in. We cover the form in depth in our complete guide to the position description questionnaire.

The PDQ is the workhorse of public-sector and university classification. The Iowa Department of Administrative Services, for example, requires a PDQ for every new position and every classification review, and it asks employees to list tasks with the percentage of an average workweek spent on each, totaling 100%. That 100% rule is a good test of any PDQ: it forces specifics.

Three traits define a PDQ:

• It is job-specific. The questions are open-ended, so the answers describe this job, in the employee's own words.
• Insiders complete it. HR or the supervisor fills the identifying section, the incumbent writes the bulk (usually 45 to 60 minutes), and the supervisor reviews it (about 20 to 30 minutes). All three sign.
• It documents the job, not the person. A PDQ records what the position requires. It never rates how well the current employee performs.

What is a PAQ?

The position analysis questionnaire is a standardized job analysis instrument developed at Purdue University by Ernest McCormick, Paul Jeanneret, and Robert Mecham. Their 1969 report for the Office of Naval Research describes Form B of the PAQ with 194 job elements organized into six divisions. Current published versions list 187 job-activity items plus 8 items on how the job is paid.

The six divisions are:

• Information input: where and how the worker gets the information needed to do the job.
• Mental processes: the reasoning, decision-making, and planning the job involves.
• Work output: the physical activities, tools, and devices the worker uses.
• Relationships with other persons: communication, supervision, and personal contact.
• Job context: the physical and social environment the work happens in.
• Other job characteristics: schedule, pace, responsibility, and other conditions.

An analyst rates each item on a scale such as importance to the job, extent of use, or amount of time, mostly from 1 (very minor) to 5 (extreme), with a "does not apply" option. The result is a numeric profile that you can compare across jobs that share no tasks at all, such as a nurse and a forklift operator.

The key difference from a PDQ: the PAQ is worker-oriented. It describes the human behaviors a job demands, not the job's specific tasks. And its publisher advises that incumbents and supervisors generally should not complete it themselves. A trained job analyst observes the work, interviews the employee, and then rates the items.

PDQ vs PAQ at a glance

Caption: PDQ vs PAQ compared on who completes each questionnaire, what it measures, and the output it produces.

The table hides one important point. A PDQ's open answers are evidence: "approves purchases up to $25,000 without review" tells your committee exactly how to score decision authority. A PAQ rating of "4" on a decision-making item is consistent, but it cannot tell you what the job actually decides.

Download a filled-in PDQ and PAQ example

To make the difference concrete, we filled out both questionnaires for the same fictional job: a Payroll Specialist at an invented company. Open them side by side and compare how each records the same facts. The PDQ states the exact rule: the job corrects pay errors up to $500 on its own. The PAQ-style profile rates "deciding how to correct errors" a 3 out of 5.

• Download the filled-in PDQ example (PDF): all 14 sections, percent of time totaling 100%, and a supervisor review note.
• Download the PAQ-style example (PDF): analyst ratings across the six divisions, with a profile summary.

The PAQ example is an illustration that PointFactors wrote to show the format. It does not reproduce items from the licensed Position Analysis Questionnaire. Both examples are fictional.

How each one fits point-factor job evaluation

The point-factor method scores each job against weighted compensable factors, typically skill, effort, responsibility, and working conditions, plus their sub-factors. To score well, your committee needs facts that map cleanly to the factor levels in your plan.

The PDQ maps directly. A well-designed PDQ is built around your compensable factors:

• Education, knowledge, and problem-solving sections feed skill.
• Physical demands and mental pace feed effort.
• Decision authority, supervision, and resources feed responsibility.
• Environment and hazards feed working conditions.

When an evaluator asks "what level of responsibility does this job hold?", the answer sits in a section with that name.

The PAQ maps indirectly. PAQ items cover similar ground, but they were not written for your plan's factor definitions. To use PAQ data in a point-factor evaluation, you must build a crosswalk from PAQ items to your factors and levels, then validate it. That is real statistical work. It made sense for large research programs; it rarely makes sense for a 400-employee organization that needs its pay grades fixed this year.

There is also a scale issue. Suppose you have 250 unique jobs. With a PDQ, each incumbent spends about an hour, and each supervisor about half an hour, spread across the business. With a PAQ, a trained analyst observes, interviews, and rates every one of those jobs. Even at a modest half day per job, that is roughly 125 analyst days before scoring starts.

Want to see how structured PDQ answers turn into factor scores? Book a short PointFactors demo and we will walk through one job with you.

Strengths and weaknesses

PDQ strengths

• Rich, specific evidence. You get the dollar limits, the headcounts, and the decisions that drive scores.
• Scales cheaply. The people who know the work best do most of the writing.
• Builds buy-in. Employees see their job described in their own words, which helps when you explain results or handle job evaluation appeals.
• Doubles as documentation. The PDQ becomes the source record for your job descriptions.

PDQ weaknesses

• Inflation. Incumbents tend to overstate duties. The supervisor review and the 100% time rule are your main controls.
• Uneven writing quality. A strong writer and a weak writer doing the same job can produce very different forms. Good examples and clear prompts reduce the gap.
• Less statistical comparability. Open answers do not drop neatly into a spreadsheet.

PAQ strengths

• Standardized and quantified. Every job gets rated on the same items, so you can compare unlike jobs on equal terms.
• Research pedigree. The original Purdue work reported whole-job reliability around 0.8 between independent raters.
• Less self-report bias. Trained analysts, not incumbents, do the rating.

PAQ weaknesses

• Expensive per job. It needs trained analysts and, in most cases, a license.
• Generic items. Worker-oriented items miss the specifics that separate two similar jobs, such as a $5,000 versus a $500,000 approval limit.
• High reading level. Researchers have long noted the PAQ's demanding language, one reason it is analyst-administered.
• Indirect fit to your plan. You need a crosswalk before PAQ data can score your compensable factors.

How to choose between a PDQ and a PAQ

Caption: A decision tree for PDQ vs PAQ, based on your project goal and the analyst capacity you have.

Work through three questions.

1. What is the project's goal? If you are classifying positions, building pay grades, or running a point-factor job evaluation, start with a PDQ. If you are building selection tests, validating job requirements statistically, or researching job families across an industry, look at the PAQ.

2. Do you have trained analysts? The PAQ assumes you do. If your comp team is three people covering 2,000 employees, a PAQ program will stall. A PDQ spreads the data-gathering load across the business.

3. How many jobs, and how different are they? For many jobs within one organization, the PDQ wins on cost and on evidence quality. For a small set of very different jobs that you must compare on one statistical scale, the PAQ earns its cost.

Our rule of thumb: use a PDQ as your default for job evaluation, and reach for a PAQ only when you need standardized, research-grade comparison and have the analysts to run it.

Can you use both?

Yes, and some mature programs do. The common pattern looks like this:

• Every job gets a PDQ. It is the record of what the position requires.
• Benchmark jobs get a deeper look. For your benchmark jobs, an analyst adds interviews or a structured instrument to check that the PDQ data holds up.
• Disputes get an analyst. When a supervisor and incumbent disagree, or an appeal arrives, a trained analyst reviews the job directly.

For a wider view of the options, including interviews, observation, and work logs, see our guide to job analysis methods.

Common mistakes when comparing PDQ vs PAQ

• Treating them as interchangeable. They are different tools. One documents a position; the other rates worker behaviors.
• Asking employees to self-complete a PAQ. It was built for trained analysts. Self-completion undermines the standardization you are paying for.
• Using a PDQ without a supervisor review. That removes your main control against inflation.
• Rating performance on either form. Both describe the job. Neither should judge the incumbent. If you need a refresher, read job evaluation vs performance evaluation.
• Skipping the link to scoring. Whichever tool you pick, design it around how you will score. Our job evaluation questionnaire guide covers the scoring side.

FAQ

What is the main difference between a PDQ and a PAQ?

A PDQ is a job-specific form that the incumbent completes and the supervisor reviews, documenting one position's duties and requirements. A PAQ is a standardized instrument of about 190 generic worker-behavior items that a trained analyst rates. The PDQ gives you specific evidence; the PAQ gives you comparable numbers.

Who developed the position analysis questionnaire?

Ernest McCormick, Paul Jeanneret, and Robert Mecham developed the PAQ at Purdue University. Their 1969 report for the Office of Naval Research describes the instrument's development and its six divisions.

Is a PDQ or a PAQ better for point-factor job evaluation?

For most organizations, the PDQ. Its sections map directly to compensable factors such as skill, effort, responsibility, and working conditions. PAQ data needs a validated crosswalk to your factor levels before you can use it for scoring.

Can employees complete a PAQ themselves?

Generally, no. The PAQ is designed for trained job analysts, who observe the job and interview the incumbent before rating each item. Employees complete PDQs, not PAQs.

How long does each questionnaire take?

An incumbent typically spends about 45 to 60 minutes on a PDQ, and the supervisor spends about 20 to 30 minutes reviewing it. A PAQ takes analyst time for observation, interviews, and rating, which adds up quickly across many jobs.

Are PDQs and PAQs types of job analysis questionnaires?

Yes. Both are job analysis questionnaires. The PDQ is job-oriented and open-ended. The PAQ is worker-oriented and standardized. Other types include task inventories and job evaluation questionnaires built around a specific scoring plan.

Does either questionnaire measure employee performance?

No. Both describe the job, not the person doing it. Performance belongs in your performance management process, not your job analysis.

Choose the tool that fits the job

If your goal is fair, defensible pay grades, the PDQ gives your committee the specific evidence it needs, at a cost your team can carry. Keep the PAQ in your toolkit for research-grade comparison, and pair it with analyst capacity when you use it.

PointFactors turns structured job data into consistent point-factor scores, with an audit trail for every decision. Start free to see a job go from questionnaire to pay grade, or review pricing to plan your rollout.

Justin Hampton, founder and CEO of PointFactors