How to Run a PDQ Project Without Disrupting the Business
Date Published

How to Run a PDQ Project Without Disrupting the Business
A PDQ project asks every employee in scope to stop and describe their job in writing. Done badly, it eats a week of productivity, stirs up rumors about layoffs and pay cuts, and returns a pile of forms you cannot score. Done well, it takes about an hour per employee, spread over a few weeks, and gives your evaluation committee clean evidence.
The difference is planning. You do not need a big consulting engagement. You need a short timeline, a communication plan that answers the fear before it spreads, clear roles, and a pilot before you go wide.
This guide gives you a 10-week job analysis project plan you can adapt, the messages to send at each stage, the time budget for each role, and the traps that derail most rollouts. It assumes you already know what a position description questionnaire is and focuses on running the project around it.
TL;DR
- Run the PDQ project in five phases over about 10 weeks: plan, pilot, launch, supervisor review, and quality check.
- Tell employees early that you are evaluating jobs, not people. Silence breeds rumors.
- Budget about 45 to 60 minutes per incumbent and 20 to 30 minutes per supervisor review. Spread across the organization, the load is small.
- Always pilot with 5 to 10 positions before you send the form to everyone.
- Close the loop. Tell employees what happens next and when.
Start with scope, sponsor, and a steering group
Before you build a timeline, settle three decisions.
Scope. Decide which jobs are in. A full organization-wide study covers every position. A narrower project covers one function, one pay structure, or a set of benchmark jobs. Smaller scope means a shorter project and less disruption. If you only need to anchor a pay structure, starting with benchmark positions is often enough.
Sponsor. Name one executive who owns the "why." This person signs the launch announcement and settles disputes about scope. Without a sponsor, managers treat the PDQ as optional.
Steering group. Form a small group, typically HR, finance, and two or three line leaders. Its job is to approve the plan, clear roadblocks, and keep the project moving. The European Institute for Gender Equality (EIGE) walks through this in a job evaluation case study: a five-member committee formed in month one, with members drawn from each part of the business so every area has a voice.
A 10-week PDQ project timeline
Here is a practical timeline. These durations are planning estimates from practice, not a published standard. Stretch or compress them to fit your size, and adjust after your pilot.

Caption: A 10-week PDQ project timeline showing the five phases from planning through the quality check.
Phase | Weeks | What happens |
|---|---|---|
1. Plan and announce | 1 to 2 | Set scope, name the sponsor, pre-fill identifying data, send the launch message |
2. Pilot | 3 | Test the form with 5 to 10 positions, fix unclear questions |
3. Launch | 4 to 6 | Send the form to all incumbents, hold office hours |
4. Supervisor review | 7 to 8 | Supervisors review, agree or disagree, and sign |
5. Quality check | 9 to 10 | HR audits forms and hands clean data to the committee |
Large public programs follow the same shape. Florida State College at Jacksonville's classification project, for example, starts with initiation and employee orientation sessions, then collects PDQs, then moves to analysis. Planning and communication come first. Data collection comes second.
Phase 1: Plan and announce (weeks 1 to 2)
Pre-fill everything you already know: job title, code, department, location, FLSA status, and reporting line. Every field you complete for the employee is a field they cannot get wrong, and it shortens the form. Build a tracker that lists each position, its incumbent, its supervisor, and its status.
Then send the launch message. The next section covers what it should say.
Phase 2: Pilot (week 3)
Pick 5 to 10 positions that cover different levels and functions. Include at least one supervisor and one hard-to-describe role. Ask pilot participants to time themselves and mark every question they had to reread.
You are testing the form and the instructions, not the people. Look for questions that produce the same useless answer from everyone, sections that take too long, and terms that need a definition. Fix them before launch. A one-week pilot saves you from correcting hundreds of weak forms later.
Phase 3: Launch (weeks 4 to 6)
Send the form with a clear due date, roughly two weeks out. Give people a worked example so they know the level of detail you want. Our guide on how to fill out a position description questionnaire works well as the example pack.
Hold open office hours twice a week for the first two weeks. Track completion daily and send reminders to supervisors, not just employees. Supervisors can clear a stall faster than HR can.
Phase 4: Supervisor review (weeks 7 to 8)
Supervisors review each form, state whether they agree with the duties and percentages, and sign. They should leave the employee's answers unchanged and record disagreements in their own section. Give them a short checklist so the review takes 20 to 30 minutes, not an afternoon.
Phase 5: Quality check (weeks 9 to 10)
HR audits every form for the problems that corrupt data: blank fields, copied job description text, vague duties, and percent of time that does not total what your form requires. Our article on five PDQ mistakes gives you the audit list. Return flawed forms with specific notes, then hand the clean set to your committee for scoring under the point-factor method.
Write a PDQ communication plan
Employees worry when HR starts asking about their jobs. The most common fear is that the project is a layoff exercise or a way to cut pay. Your communication plan exists to replace that fear with facts.
The EIGE case study offers a model. Its first message explained that the process is about evaluating the job, not your individual performance. The company also set up an FAQ page and a feedback channel.
Plan at least four messages.
- Launch announcement (week 1, from the sponsor). Say why you are doing this, what employees will be asked to do, how long it takes, and when it is due. State plainly that the project evaluates jobs, not performance.
- Pre-launch reminder (week 3, from HR). Share the schedule, the worked example, and where to get help.
- Mid-project nudge (week 5, from supervisors). Remind people of the due date and the office hours. Supervisors carry more weight here than HR.
- Close-out message (week 10, from the sponsor). Thank people, say what happens next, and give a date for when they will hear results. Do not skip this one. People who never hear back assume the worst.
Keep an FAQ page live and answer the hard questions directly. "Will this change my pay?" deserves an honest answer, such as "No pay changes happen at the PDQ stage. The committee evaluates jobs first, and we will tell you when results are final."
Know who does what, and how much time it takes
A PDQ project feels disruptive when nobody knows who owns what. Spell out roles at the start.

Caption: Who does what in a PDQ project, with the time each role should plan to spend.
Role | Job in the project | Planned time |
|---|---|---|
Executive sponsor | Announces the why, settles scope disputes | A few hours total |
HR project lead | Owns the schedule, tracker, and quality check | Most of the project |
Supervisor | Releases time, reviews forms | 20 to 30 minutes per form |
Incumbent | Completes the PDQ | 45 to 60 minutes |
The incumbent and supervisor times match the planning estimates in our PDQ guide. South Dakota's Bureau of Human Resources uses the same split: employees complete their own section and supervisors complete a separate review.
The workload math
Here is a fictional example to show how small the load is. Assume 150 positions in scope, one incumbent per position.
- Incumbents: 150 forms × 45 to 60 minutes = 112.5 to 150 hours.
- Supervisors: 150 reviews × 20 to 30 minutes = 50 to 75 hours.
- Total: 162.5 to 225 hours across the organization.
That sounds large until you spread it out. Each incumbent gives up about an hour over two weeks. A supervisor with six direct reports spends 2 to 3 hours on reviews (6 × 20 minutes = 2 hours; 6 × 30 minutes = 3 hours). Neither number disrupts a normal workweek. The disruption comes from poor timing, so avoid launching during payroll close, peak season, or year-end.
Keep the business running
A few scheduling habits keep operations steady.
- Stagger the launch. Send the form to one department at a time if a single deadline would strain a function. Customer service and operations teams often need a wave of their own.
- Offer protected time. Ask supervisors to let people block an hour on their calendar. A due date with no time to do the work guarantees rushed forms.
- Accommodate shift workers. Give hourly and frontline staff paid time and a way to complete the form that does not depend on a desk. Offer a short interview with an HR partner if writing is a barrier.
- Start with the right jobs. If you cannot do everyone at once, begin with benchmark jobs and expand. See our guide to job evaluation implementation for how to sequence a larger rollout.
Common traps that derail a PDQ project
- No pilot. Unclear questions reach everyone and you collect weak data at scale.
- Weak sponsor. Managers ignore deadlines because nobody senior cares.
- Silent supervisors. Supervisors who never read the forms turn review into a rubber stamp.
- No close-out. Employees fill out the form, hear nothing for months, and assume bad news.
- Mixing up purposes. If employees think the PDQ evaluates them, they inflate or hide. Say it again: the form documents the job. For the scoring side, see our job evaluation questionnaire guide.
FAQ
How long does a PDQ project take?
A mid-sized project usually runs about 10 weeks from planning to a clean data set. That is a planning estimate, not a standard. A single-department project can finish in less, and a very large organization needs more.
How much time does the PDQ take each employee?
Plan on about 45 to 60 minutes for the incumbent and 20 to 30 minutes for the supervisor review. These are practical estimates. Confirm them in your pilot and adjust.
Do I need a pilot?
Yes. A pilot with 5 to 10 positions costs about a week and catches unclear questions before they reach everyone. It is the cheapest quality control in the project.
How do I keep employees from panicking about a PDQ?
Tell them early and plainly. Say the project evaluates jobs, not people, explain what happens with the results, and keep an FAQ and a feedback channel open. Silence is what feeds rumors.
Who should own the PDQ project?
HR or compensation should run it day to day, with an executive sponsor who owns the "why" and a small steering group that clears obstacles.
Should I send the PDQ to every employee at once?
Not always. Stagger by department if one deadline would strain operations, or start with benchmark jobs and expand. Avoid peak business periods.
What do I do with the PDQs when they come back?
Audit them for completeness and common errors, return flawed forms with specific notes, and then hand the clean set to your evaluation committee. If you are choosing between instruments first, read PDQ vs PAQ.
Run the project, then use the data
A PDQ project succeeds when people understand why it is happening, know what is asked of them, and see the results. Plan the phases, pilot the form, communicate early and often, and audit what comes back.
PointFactors tracks questionnaire status, flags incomplete forms, and moves approved data straight into point-factor scoring, so your team spends its time on judgment instead of chasing forms. Start free to see a PDQ project run end to end, or review pricing to plan your rollout.
Justin Hampton, founder and CEO of PointFactors, writes about job evaluation, pay structure, and compensation strategy for HR leaders and compensation analysts.
Join the PointFactors newsletter
One email a month on job evaluation, pay equity and pay transparency. No spam; unsubscribe anytime.