Almost every pay dispute we're asked to help resolve starts the same way: an employee believes they are paid unfairly relative to a colleague doing similar work. Whether or not they're technically right, the fact that the organization can't immediately produce a clear, structured answer is itself the problem. Job evaluation exists to make that answer possible before the dispute happens.
Job evaluation does not rank people, and it does not rank job titles. It systematically measures the content of a role — the skill it requires, the level of responsibility it carries, the complexity of the decisions it involves, and (where relevant) its working conditions — independent of who currently holds it or what they're currently paid. That distinction is what makes it defensible: the evaluation would produce the same grade for the role regardless of the incumbent.
Breaks each role into weighted factors (skill, responsibility, effort, working conditions) and scores them numerically. The most rigorous and most defensible method, and the one we use most often for organizations that need a structure to hold up under scrutiny.
Simply orders roles from most to least valuable to the organization as a whole. Fast and simple, but subjective and hard to defend at scale — better suited to very small organizations.
Roles are matched against pre-defined grade descriptions (common in public sector and large multinational structures). Efficient once the grade descriptions exist, but the initial design work is significant.
A hybrid approach comparing roles factor-by-factor against a set of benchmark roles. More precise than ranking, less resource-intensive than full point-factor.
A grading structure earns trust when three things are true: the methodology was applied consistently across every role (no exceptions made quietly for specific individuals), the criteria are documented and available to employees who ask, and it is reviewed periodically rather than left untouched for a decade while the organization changes around it.
A job evaluation exercise touches something employees care about directly, which makes a rushed or inconsistent process worse than no process at all — it creates the appearance of favoritism where none may have existed. Getting it right means clear methodology, consistent application, and transparent communication about how grades were determined.
Roles change — responsibilities grow, new positions are created, technology reshapes what a job actually involves day to day. A grading structure built once and never revisited quietly drifts out of alignment with the organization it was designed for. Treat job evaluation as a maintained system with a periodic review cycle, not a project with a finish line.
A salary survey tells you what the market pays for a role. Job evaluation tells you how that role compares internally to every other role in your organization. You need both — evaluation for internal fairness, market data for external competitiveness.
Best practice is transparency about the grade and the criteria used to reach it, even if the underlying numerical scoring detail isn't published — employees should always be able to understand why their role sits where it does.
Every two to three years for a stable organization, or immediately after a merger, major restructuring, or a period of unusually fast growth.
Trinity's Job Evaluation & Grading service has helped organizations across East Africa build pay structures that survive scrutiny — from the boardroom to an individual employee's question about why their grade is what it is.