Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Grading and pay banding for a German IT and digital services group under works council co-determination

Industry
IT and digital services (within a commerce group)
Region
Germany (two sites)
Size
Multi-site technology workforce
Best for
Co-determined, multi-site technology organisations linking roles, grades and pay under time pressure
3
role groupings with defined career levels
14
job groups across the groupings
~6
months to deliver the first project
2
German sites under co-determination
01 Context

Starting point

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.

Client profile

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.

The problem

  • Unclear roles and inconsistent role definitions across the technology divisions
  • No analytical job evaluation basis underpinning the existing job profiles
  • Salary differences between sites for comparable work that were hard to justify
  • A separate salary system in the consulting division that had to be reconciled
  • No transparent connection between grades and salary bands

Why it mattered at that point

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.

Alternatives considered

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.

02 Approach

How the project was delivered

Guided by the principle “as much equality as possible, as many differences as necessary”.

Building block 1

Job evaluation

gradar evaluation criteria were added to the existing job profiles, from professional knowledge to decision-making framework.

Building block 2

Job architecture

Roles were structured into job families and career levels within three groupings.

Building block 3

Pay banding

Grades were connected to salary bands, so employees could see where they sat within their band.

Building block 4

Performance linkage

Salaries were reviewed based on a manager assessment and a Career Development Committee.

Scope at a glance

  • Initial project (2022 to 2023) for a digital solutions provider entity across two German sites
  • Subsequent project (2025 onward) extending the approach to further IT and data entities, phased through 2026 into 2027
  • Grading, job architecture, pay analysis, salary system and works agreement, and implementation

Three role groupings

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.

Key decisions
  • How to structure career levels within the three role groupings
  • How to reconcile the existing consulting salary system with the new group-wide logic
  • How to handle pay differences between the two sites
  • How to connect grades to salary bands and position roles within them
  • How to link performance assessment to movement within bands
  • How to structure the works agreement so the system was co-determined and durable
Data and inputs

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.

03 Challenges

What made it difficult

Unclear roles

Roles had to be clarified before they could be evaluated and slotted.

An existing consulting salary system

It had to be integrated into the new logic rather than discarded.

Pay differences between sites

Salary differences for comparable work had to be analysed and addressed.

Committed works councils

Their involvement was essential and had to be built into the timeline and design.

A short timeline

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.

Stakeholder involvement

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.

04 Results and lessons

What changed

Before
After
Unclear and inconsistent role definitions
Clearer role definitions and a consistent grading framework
No connection between grades and pay
Transparent salary bands: employees know their job, their band and where they stand
Pay differences between sites hard to justify
Site differences addressed on a documented basis
A separate consulting salary system
Reconciled into one group-wide logic, anchored in a works agreement

What was delivered

  • An analytical job-evaluation framework built onto the existing job profiles
  • A job architecture with three role groupings and defined career levels
  • Salary bands connected to grades
  • A salary system and works agreement on a co-determined basis
  • A performance-linked mechanism for pay reviews within bands
  • An implementation plan and roll-out across the relevant entities

Lessons learned

  • Add analytical evaluation to job profiles early. Profiles alone do not link roles, grades and pay.
  • Involve works councils and managers from the outset. Their engagement is a success factor, not a formality.
  • Address cross-site pay differences explicitly, guided by a clear principle.
  • Plan for reconciling existing local pay systems rather than assuming they can be replaced.
  • Communicate regularly and allow for unpredictability, especially on a short timeline.
  • Connect grades to transparent bands and a performance mechanism so employees can see how to progress.

Relevant for

  • IT, technology and digital services organisations needing a defensible link between roles, grades and pay
  • Organisations operating under works council co-determination
  • Multi-site organisations facing pay differences between locations
  • Companies that have introduced job profiles but lack a grading and pay-banding layer
  • Organisations professionalising rewards governance under time pressure
  • Companies connecting job evaluation with transparent salary bands and performance-based pay reviews

Explore our job architecture features

Through analytical job evaluation, gradar helps organisations design a clear, consistent job architecture that supports fair, transparent pay decisions.
Businesswoman using a stylus on a digital tablet at a bright office desk with pens and papers.

FAQs

How does job evaluation support transparent pay bands?

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.

How does works council co-determination affect a grading project?

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.

How can pay differences between sites be handled fairly?

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.

What is the difference between job evaluation and salary benchmarking?

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.

How long does this kind of project take?

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.

Who should be 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.

Build your job architecture with gradar

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