The IT and digital services divisions of a large German commerce group added analytical job evaluation to existing job profiles, built a job architecture for technology roles and connected grades to transparent salary bands, under works council co-determination and a tight timeline.
The client comprised the IT and digital services divisions of a large, German-headquartered commerce and retail group, with predominantly technology and knowledge roles: software development, IT security, systems administration, data engineering and data science, consulting and delivery, and internal corporate functions.
The work spanned two principal German sites in a strongly co-determined setting. Job profiles already existed, but there was no consistent grading and pay-banding logic, and a previous attempt to establish a functioning system had failed.
A previous attempt had failed, salary increases had been paused, and the competitive IT labour market created high pressure for a functioning system. The first project had to be delivered in roughly six months.
Continuing with job profiles alone would have left roles, grades and pay disconnected. The chosen route added analytical evaluation criteria to the existing profiles and connected the resulting grades to transparent salary bands, providing a defensible, co-determination-ready basis.
Guided by the principle “as much equality as possible, as many differences as necessary”.
gradar evaluation criteria were added to the existing job profiles, from professional knowledge to decision-making framework.
Roles were structured into job families and career levels within three groupings.
Grades were connected to salary bands, so employees could see where they sat within their band.
Salaries were reviewed based on a manager assessment and a Career Development Committee.
Engineering: 4 groups, career levels E1 to E4, from Software Developer to Senior Software Architect.
Consulting and Delivery: 4 groups, career levels C1 to C4.
Internal roles: 6 groups, career levels I1 to I6, up to Team Lead and Department Lead.
Existing job profiles and general job descriptions for each type of activity, the inventory of roles gathered at kickoff, the existing salary system in the consulting division, and site-level pay data needed to analyse and reconcile differences between locations.
Roles had to be clarified before they could be evaluated and slotted.
It had to be integrated into the new logic rather than discarded.
Salary differences for comparable work had to be analysed and addressed.
Their involvement was essential and had to be built into the timeline and design.
Inherent unpredictabilities in a co-determined, multi-site project put pressure on the schedule.
How these were managed: through the guiding principle “as much equality as possible, as many differences as necessary”, close works council involvement, manager engagement for their respective roles, and regular communication throughout.
Governance combined a steering committee at CEO level with a project lead spanning both sites and HR controlling support. Managers were involved for their respective positions, and works council representatives from both sites were engaged throughout. Consideration of the works council and managers, regular communication and realistic attention to time were the key success factors.

Job evaluation provides a consistent analytical basis for grading roles. Once roles are graded, they can be mapped to salary bands, giving employees a clear answer to what their job is, which band they are in and where they sit within it, and giving the organisation a defensible basis for pay decisions.
In co-determined organisations, works councils are key stakeholders whose involvement shapes both the design and the timeline. Anchoring the framework in a works agreement gives it a durable, jointly owned basis. Early and regular engagement is a recognised success factor.
Site-level pay should be analysed against a consistent grading logic. A guiding principle, “as much equality as possible, as many differences as necessary”, helps decide where differences are justified, for example by local market, and where comparable work should be paid comparably.
Job evaluation assesses the internal value of a role using consistent criteria such as knowledge, problem solving, communication and responsibility. Salary benchmarking compares pay against external market data. Both are complementary.
It depends on scope, number of sites, role complexity, data quality and stakeholder involvement. In this case a first project was delivered in roughly six months, but timelines should be set cautiously, especially where co-determination is involved.
Typically a steering committee at executive level, a project lead, HR controlling, managers for their respective roles, and works council representatives from each site. In IT contexts, technical managers help clarify unclear roles.
Job architecture insights are delivered through the gradar platform - connecting job evaluation, compensation analysis and pay transparency in one consistent framework.
Job evaluation
Compensation
Pay transparency