A quantitative job evaluation technique that assigns numerical points to predefined compensable factors (such as skill, effort, responsibility, and working conditions) to determine the relative worth of each job within an organization's pay structure.
Key Takeaways
The point factor method is the most structured way to answer "how much is this job worth compared to that one?" Instead of ranking jobs based on gut feeling or slotting them into vague grade descriptions, you break each job into specific components, score each component, and let the math produce a result. Here's the basic idea. You define the factors your organization cares about: skill, effort, responsibility, working conditions, complexity, supervisory scope, or whatever else drives value in your context. You create a scoring scale for each factor with defined levels (Level 1 through Level 5, for example). Then, for each job, an evaluation committee reviews the role's requirements and assigns a level for each factor. The total points determine the job's grade and pay range. The power of the method is its transparency. When an employee asks why their role is in Grade 6 while a colleague's is in Grade 7, you can point to the specific factor scores and explain exactly where the difference lies. That's much harder to do with ranking or classification methods. The point factor method gained traction during World War II when the National War Labor Board needed a systematic way to evaluate and compare jobs across industries for wage stabilization. After the war, companies kept using it because it worked. Eighty years later, it's still the gold standard for organizations that want defensible internal equity.
Building a point-factor system requires upfront investment, but once it's in place, it becomes the foundation for every compensation decision.
Choose 4 to 8 factors that represent what your organization values and pays for. The Equal Pay Act's four factors (skill, effort, responsibility, working conditions) are a strong starting point. Many organizations add factors like complexity, supervisory responsibility, communication requirements, and impact on revenue. Don't go beyond 8 factors. Research shows that adding more factors doesn't improve accuracy and slows down the evaluation process significantly (WorldatWork, 2023).
For each factor, create 4 to 6 clearly defined levels with specific behavioral descriptions. For the "Skill" factor, Level 1 might be "follows established procedures with minimal training," while Level 5 might be "applies expert-level specialized knowledge gained through advanced education and 10+ years of progressive experience." Vague descriptions like "high skill" or "moderate skill" defeat the purpose. The level definitions need to be specific enough that two evaluators would assign the same level independently.
Not all factors are equally important. Assign weights that reflect your organization's priorities. A technology company might weight Skill at 40%, Responsibility at 30%, Effort at 20%, and Working Conditions at 10%. Then assign point values to each level within each factor. If the maximum total is 1,000 points and Skill is weighted at 40%, Skill Level 5 would be worth 400 points and Skill Level 1 might be worth 80 points.
Start with 20 to 30 benchmark jobs that span the full range of levels and functions. The evaluation committee scores each benchmark job on every factor. These benchmark evaluations become the reference points for all subsequent evaluations. If the committee scores a Senior Software Engineer at Skill Level 4 and Responsibility Level 3, that becomes the standard for comparing similar roles.
Work through the remaining roles in batches, comparing each one to the benchmarks. The committee discusses each factor and agrees on a level. Total the points and map the score to a grade. A well-functioning committee can evaluate 10 to 15 jobs per day. For a 500-role organization, that's 5 to 6 weeks of evaluation sessions.
Factor weights vary dramatically by industry and organizational values. Here's how typical weightings look across different sectors.
| Factor | Tech Company | Manufacturing | Healthcare | Financial Services | Government |
|---|---|---|---|---|---|
| Skill / Knowledge | 35% | 25% | 35% | 30% | 30% |
| Responsibility / Accountability | 30% | 25% | 20% | 35% | 25% |
| Complexity / Problem Solving | 20% | 15% | 15% | 20% | 20% |
| Supervisory Scope | 10% | 15% | 10% | 10% | 15% |
| Working Conditions | 5% | 20% | 20% | 5% | 10% |
Let's walk through a simplified evaluation comparing two roles using a 1,000-point system with four factors.
| Factor (Weight) | Marketing Manager (Level/Points) | Software Engineer (Level/Points) |
|---|---|---|
| Skill (35%) | Level 4 / 280 pts | Level 4 / 280 pts |
| Responsibility (30%) | Level 3 / 180 pts | Level 3 / 180 pts |
| Complexity (25%) | Level 3 / 150 pts | Level 4 / 200 pts |
| Working Conditions (10%) | Level 2 / 40 pts | Level 2 / 40 pts |
| TOTAL | 650 pts (Grade 7) | 700 pts (Grade 8) |
Understanding both sides helps you decide if the point factor method is right for your organization.
Transparency is the biggest advantage. Every evaluation is documented with specific factor scores, making it easy to explain and defend pay decisions. Courts and regulators view point-factor results favorably in pay equity cases because the methodology is systematic and auditable. It also forces organizations to articulate what they value, since the factor selection and weighting process requires explicit decisions about organizational priorities.
The point factor method is time-consuming. Evaluating 500 roles at 30 minutes each requires 250 hours of committee time. It's also only as good as the factor definitions and the evaluators' consistency. If the committee doesn't calibrate well, the same role might score differently depending on who's in the room. And in fast-moving industries where roles change quarterly, evaluations can become outdated before the project is complete.
Point-factor scores measure internal worth. They don't account for market demand. A niche cybersecurity role and a general IT support role might score similarly on compensable factors, but the market pays the cybersecurity role 60% more due to talent scarcity. Organizations that rely solely on point-factor results without overlaying market data will struggle to attract talent in competitive fields.
You don't need to buy a proprietary system. Many organizations build their own, especially if they have fewer than 2,000 employees.
Key data on usage and effectiveness of point-factor evaluation systems.