Webinar: Implementing job evaluation processes: ensuring long-term success

Making job evaluation work for the long term

A sound methodology is just the starting point. Clear ownership, practical integration and regular review turn job evaluation into a process that keeps supporting the business.

Completing a job evaluation project is a milestone. Keeping the resulting structure useful as roles and business needs change is a separate challenge. A framework can be well designed and still lose relevance if managers apply it inconsistently, new roles have no clear place within it or the results stay disconnected from everyday HR decisions.

In our joint webinar with Merities Consulting, Lisanne Metz (COO, gradar) and Rachel Gibbs (founder, Merities Consulting), moderated by James Mackay, discussed how to turn job evaluation into a lasting process. The central message - plan how it will become part of everyday HR work from the start, rather than treating that as an afterthought.

Watch the webinar recording

Start with the role, not the person

Job evaluation assesses the requirements of a role, not the individual doing it. Both Lisanne and Rachel noted how often this needs reinforcing during implementation, since managers naturally think about their teams. Evaluation results feed into a wider job architecture - grades describe the level of a role, job families group similar work - which can also make career development less dependent on moving into management.

Connect job evaluation to decisions beyond compliance

Connect job evaluation to decisions beyond compliance

Pay transparency is a common trigger, but a maintained job architecture supports more:

• Compensation: Internal pay should be analysed across grades and families before turning to market data - then you can set pay bands and progression criteria from a considered compensation philosophy.
• Development: Role profiles can be linked to competencies, giving talent teams a clearer basis for progression.
• HR systems: A coherent structure of jobs, families and grades gives different HR teams a shared foundation instead of working in silos.

Define ownership before you start

Choosing a methodology does not settle who will operate it. Rachel’s advice was to clarify who owns the methodology, what is expected of HR, managers and leaders, who signs off evaluated roles and which roles and locations are in scope – all before starting the project! Even counting distinct jobs can be hard work, since titles may hide or duplicate roles. There is no single right starting point - beginning with high-volume roles or with senior leadership are both valid, depending on the organisation.

Build the process into everyday work

Rachel highlied the difference between implementing and embaedding job evaluation - and stressed the importance of planning both together. Recruitment is a good example. When a position opens, is it linked to an evaluated role with a clear route for genuinely new roles? In organisations where new types of work have no review process, existing roles are often selected to work around it, which can distort the structure over time. Integration must accommodate change - a system connection alone is not enough.

Communication and review is critical

Different groups need different communication. Managers running evaluations need the method, others need enough context to use results and employees need clear explanations. Rachel encouraged involving employee representatives and planning for questions or appeals early, while understanding the specific concern behind each one.

Keeping evaluations aligned with change was a leading audience concern. Lisanne recommended reviewing the overall architecture at least annually and reassessing roles when their requirements shift - bearing in mind that when responsibility moves into one role, it may move out of another. Rachel suggested the annual pay review as a natural checkpoint to catch changes that haven’t reached HR.

From completed project to ongoing process

Job evaluation creates lasting value when results stay connected to real decisions. That requires clear ownership, informed managers, processes that use the architecture and a way to keep it current. Technology supports this but does not replace the judgement and governance around it.

A useful question is not only “have we evaluated our jobs?” but also “where do those evaluations influence decisions today and who keeps them relevant?”

Watch the recording for the full discussion and practical examples from gradar and Merities Consulting.