.svg)
The point factor method is a structured job evaluation approach that assigns points to a role across defined compensable factors, then uses the total score to support grade placement. It is useful because the evaluator has to show which job requirements drove the result instead of relying on title, incumbent pay, or an overall impression.
The method is not automatically objective just because it uses numbers. The factor definitions, degree descriptions, weights, job documentation, evaluator judgment, and grade boundaries still have to be designed and applied consistently. A weak factor model can produce a precise-looking score that is still a weak compensation decision.
This article focuses on the methodology itself: what compensable factors are, how point-factor scoring works, a worked example, how it differs from other job evaluation methods, and what compensation teams should review before a score becomes a grade. For the software workflow, see CompBldr job evaluation software.
What Is the Point Factor Method of Job Evaluation?
Point-factor job evaluation breaks a role into predefined evaluation criteria. Each criterion has degree descriptions or scoring levels. The evaluator selects the degree that best matches the documented requirements of the job, the factor scores are totaled, and the result is compared with the organization's configured grade structure.
The method answers an internal-structure question: How demanding is this job relative to other jobs evaluated under the same framework? It does not by itself answer what the external market pays for the role. That is a separate market-pricing question.
What Are Compensable Factors?
Compensable factors are the job-related criteria an organization chooses to evaluate consistently across roles. The exact factor set depends on the methodology and operating model. Common dimensions include knowledge, problem-solving or complexity, accountability, decision scope, communication demands, and working conditions.
A factor is useful only when its degree descriptions distinguish meaningful differences between jobs. “Complexity” is too vague on its own. A usable framework explains what increasing levels of complexity look like, what evidence an evaluator should use, and where one degree ends and the next begins.
The evaluator should score the requirements of the job, not the qualifications or performance of the current employee. That distinction also appears in U.S. Equal Pay Act guidance: the EEOC evaluates job content and the skill, effort, responsibility, and working conditions required by the jobs being compared. A point-factor framework can help document job-related criteria, but it does not create a legal safe harbor or prove pay-equity compliance by itself. See the EEOC's Equal Pay Act guidance. This article is general compensation information, not legal advice.
How the Point Factor Method Works Step by Step
1. Define the factor framework
Select the compensable factors that reflect the work your organization needs to distinguish. The framework should work across the intended job population, not just one function. A factor that matters for engineering but cannot be applied sensibly to operations, finance, or frontline roles may need a broader definition.
2. Write degree definitions before scoring jobs
Each factor needs observable degree descriptions. The goal is to make the difference between adjacent levels reviewable. If two trained evaluators repeatedly interpret the same degree in different ways, the descriptor is probably too broad or too subjective.
3. Set the scoring and weighting logic
Point-factor systems convert selected degrees into points. Some methodologies also weight factors differently. Weighting is a design decision because it changes which job requirements have the greatest effect on the final score. Compensation teams should be able to explain why those weights fit the organization's job architecture rather than treating them as permanent defaults.
4. Evaluate the job from approved role evidence
Use the current job description, documented scope, decision authority, organizational impact, reporting relationships, and other role evidence required by the methodology. Do not increase a score because the incumbent is unusually experienced or reduce it because the current employee is still developing.
5. Review the factor pattern, not only the total
Two jobs can reach similar totals for different reasons. One may require deep technical knowledge with limited organizational scope; another may require broader accountability with less technical depth. Review the factor-level pattern before accepting the total score as a sensible representation of the job.
6. Map the approved score to the grade structure
The final score is compared with the organization's point-to-grade bands. Those grade boundaries are part of the job architecture and should be governed separately from the evaluation itself. If many jobs cluster unexpectedly at a boundary, review the factor model and grade ranges rather than automatically forcing individual jobs into different grades.
Point Factor Method Example
Illustrative example only: assume an organization evaluates a Customer Support Operations Manager using four simplified dimensions. These point values and grade boundaries are fictional and are not the JESAP® scoring table.
| Illustrative factor | Evidence considered | Illustrative points |
|---|---|---|
| Knowledge | Requires operational expertise, people-management knowledge, and familiarity with support systems | 110 |
| Complexity | Balances staffing, service levels, escalations, and process improvement across changing conditions | 80 |
| Accountability | Owns team performance, operating decisions, and material customer-service outcomes | 95 |
| Working conditions | Primarily office or remote work with periodic peak-volume pressure | 25 |
| Total | Sum of the approved factor scores | 310 |
If this fictional organization's grade table defined 300–329 points as Grade 6, the role would provisionally map to Grade 6. The compensation team should still review whether the factor selections are supported by the job evidence and whether the resulting placement is coherent with comparable roles. The lesson is the sequence: factor evidence → degree selection → points → total score → grade review.
Point Factor vs. Other Job Evaluation Methods
| Method | How it works | Main trade-off |
|---|---|---|
| Job ranking | Places jobs in overall order of relative value | Simple, but provides limited factor-level explanation as the job population grows |
| Job classification | Matches jobs to predefined class or grade descriptions | Efficient when classes are clear, but borderline roles can depend heavily on interpretation |
| Factor comparison | Compares benchmark jobs across selected factors, traditionally with monetary values attached to factors | Can be analytically detailed but is harder to maintain and explain than simpler classification approaches |
| Point factor | Scores each job against defined factors and degree levels | Creates a reviewable scoring record, but only if factors, degree definitions, and calibration are maintained |
| Market pricing | Compares a job with external salary survey matches | Answers an external-pay question rather than replacing an internal job-evaluation framework |
Organizations often use more than one method. A role can be evaluated internally with point-factor scoring and then priced externally through market benchmarking. Mixing those two questions too early can cause the external salary number to influence how the job itself is evaluated.
Where Point Factor Evaluation Commonly Breaks Down
Factor definitions are too generic
If descriptors use words such as “high,” “complex,” or “significant” without observable context, evaluators are likely to apply them differently. The fix is not more scoring precision. It is better degree definitions.
Job documentation is inconsistent
A detailed role will appear more demanding than a poorly documented role even when the underlying work is comparable. Standardize job descriptions and role evidence before treating score differences as structural differences.
Evaluators score the incumbent instead of the job
Performance, tenure, individual capability, and current salary can influence judgment if the process does not explicitly separate person data from job requirements. This is one reason a structured job leveling framework and approved role documentation matter before evaluation.
Calibration happens only after a dispute
Calibration should be part of the operating process, not an emergency response. Review adjacent roles, unusual factor patterns, large evaluator differences, and jobs near grade boundaries before the structure is finalized.
Grade boundaries are treated as unquestionable
A point total is only one input into the architecture. If repeated evaluations produce strange clustering or many jobs sit just above and below one boundary, review the grade structure and methodology configuration. Do not change scores simply to make a preferred grade fit.
Point factor is mistaken for market pricing or pay equity analysis
Job evaluation establishes an internal relative-value framework. Job grades, salary ranges, external market data, employee pay, and pay equity review are related but separate decisions. Keeping the evidence streams distinct makes later review easier.
How JESAP® Applies Point-Factor Scoring in CompBldr
CompBldr uses JESAP®, a 15-factor point-factor methodology, in its job evaluation workflow. The current product experience presents factor definitions and degree descriptions during scoring, updates the running score and proposed grade, and compares that total with the configured job-grade score bands.
Saved evaluations preserve factor scores, evaluator identity, timestamps, total points, and resulting grade as versioned records. Teams can compare saved versions and can review algorithm-based evaluation output alongside human evaluations as a calibration aid without replacing evaluator judgment.
That is the operational value of software in a point-factor process: not “automatic objectivity,” but a more reviewable record of the methodology, evidence, score changes, and grade decision. See the JESAP® framework for the methodology and the job evaluation software workflow for the scoring and versioning experience.
A Practical Point-Factor Evaluation Workflow
- Approve the role evidence. Confirm the job description, scope, reporting relationships, and decision authority before scoring.
- Score factor by factor. Require the evaluator to use the degree definitions instead of relying on title or current pay.
- Review unusual selections. Investigate factors that are materially higher or lower than comparable roles.
- Calibrate adjacent jobs. Compare roles within the same job family and across similar levels before accepting the grade pattern.
- Review the grade mapping. Confirm that the total falls into the configured grade band and that the placement is coherent with the broader architecture.
- Preserve the record. Keep the factor scores, evaluator, version, rationale, and effective date available for future review.
- Price the job separately. Once internal placement is approved, connect the role to external market evidence and salary ranges.
Point Factor Works Best When the Reasoning Is Reviewable
The value of point-factor evaluation is not the number itself. It is the ability to trace the number back to defined factors, degree descriptions, job evidence, evaluator decisions, and a governed grade structure.
For compensation teams, that record becomes more useful when it stays connected to job architecture, market benchmarking, and downstream compensation decisions instead of being left in a one-time spreadsheet.
Book a Demo to test the CompBldr job-evaluation workflow with one of your own roles.
.svg)
.svg)
.svg)
