The Role of the Job Architecture Owner: A Governance Guide

SkillsTrust

• 4 minute read

In this guide

  • What a Job Architecture Owner is and why the role matters.

  • Why governance is essential under the EU Pay Transparency Directive.

  • The six governance decisions every organisation should define.

  • How to keep your job architecture accurate, compliant and up to date.

You've invested time building a job architecture to support compliance with the EU Pay Transparency Directive. While the initial build may be finished, the reality is that it's a living artefact and it needs to keep pace with your business as new roles emerge and existing ones evolve. Without a simple governance process, decisions get made informally, the architecture drifts, and you gradually lose the ability to explain why jobs are grouped the way they are.

Under the EU Pay Transparency Directive, you need to be able to show that employees doing work of equal value are grouped objectively. If your architecture has drifted, you may not be able to do that.

The fix is straightforward: one named person accountable for changes to the architecture, and a clear process for how decisions get made. This is the role of the Job Architecture Owner.

This is a governance guide for that person. It covers the six decisions needed to set the role up for success.

Decision 1: Who is the Job Architecture Owner?

The Job Architecture Owner is the single named person accountable for the integrity of your job architecture. They are typically a senior HR or Reward professional. Their responsibilities are:

  • Evaluating proposed changes using your job evaluation methodology

  • Deciding whether a change is localised (they can approve directly) or large-scale (requires escalation)

  • Ensuring decisions are documented, including rejections

  • Convening an annual review and escalating any trends in exceptions

  • Handling any challenges from job holders to how their job has been evaluated

  • Ensuring that job architecture feeds into recruitment and pay decisions

Without a single accountable person, job evaluations will get made informally, drift may accumulate, and your job architecture loses the explainability that the Directive requires.

In addition to the Job Architecture Owner, you will also need an escalation point, usually the Chief People Officer, and a small job evaluation working group when there are large-scale decisions required.

You should also have a simple appeals process in place so that job holders can raise concerns about how their job has been evaluated. The Owner is the right person to handle these.

Decision 2: When should your Job Architecture Owner make a governance decision?

The key rule here is that governance decisions relate to jobs in your job architecture and not to the people doing those jobs. If someone is being hired or promoted into an existing job that hasn't changed its requirements, then no governance decision is needed.

Governance is triggered when an entirely new job is being created, or when an existing job's scope has shifted enough that it no longer fits its current evaluation.

Decision 3: How will you handle different types of changes?

You will encounter two main types of changes.

Localised decisions

Creating a new job within the existing framework or reviewing the scores of an existing job due to scope change. The Architecture Owner handles these directly, approving the outcome or escalating to the CPO where needed.

Large-scale decisions

Examples of large-scale decisions include:

  • Adding or removing a job family

  • Adding or removing a grade or level

  • Granting framework exceptions

  • Integrating a large set of new jobs after an acquisition

These need escalation to the Chief People Officer and potentially to the working group.

If you're not sure which category a decision falls into, ask: does this change the framework itself and/or impact a substantial portion of the jobs in it, or does the change involve adding incremental content to it? If it's the former, treat it as a large-scale decision.

Decision 4: How will you document your decisions?

Every request should be recorded: what was requested, the rationale, who decided, and the outcome, including rejections. If you use software to manage your job architecture, the change log should be captured automatically and reasoning can be recorded alongside it.

Documenting every decision matters for two reasons. First, when someone asks in two years why two jobs sit at different levels. Second, when a works council or employee asks you to demonstrate that your job groupings are objective. A clear record of decisions made using a consistent methodology is the strongest defence.

Decision 5: How will you handle exceptions?

You may occasionally need to make exceptions. Each one should be documented with explicit reasoning for why this case warranted different treatment. Watch for patterns too. If you're granting several similar exceptions within a year, it may be a signal that the structure is not meeting the needs of the business and may need to change.

Exceptions are worth scrutinising carefully in the context of job evaluation. If an exception feels right but you can't articulate why using the evaluation criteria, that's a reason to pause. All job evaluation scoring decisions should be well supported by documented evidence in the job profile and not based on assumptions about the job.

Decision 6: How will you run your annual review?

It is recommended to carry out an annual review to check your job evaluation system against the reality of the business. A full re-evaluation is only needed if jobs have changed significantly so the purpose of the annual review is to catch the things that may slip through day-to-day: structural gaps that have opened up as the business has grown, drift in evaluations of specific jobs, recurring friction points surfaced by managers during the year.

Read more about quality checking your job architecture for EU Pay Transparency.

Keep it simple

Day-to-day, most of what the Job Architecture Owner does is straightforward: a hiring manager flags a new job, the Owner evaluates it, records the outcome, and moves on. When governance is working, the job architecture stays current, decisions are made quickly and consistently, and you have a clear record of why things are the way they are.

The goal is to make sure that when the EU Pay Transparency Directive obligations require you to stand behind your job categorisation, you can do so confidently.

Read more articles

Michelle Dervan

2 Nov 2026

All About Averages | Pay Analytics 101

The Importance of the Average When talking about pay data, the term average appears time and time again, but what does it actually mean? Put simply, an average salary gives us one figure to help describe pay across a group of employees. It takes all the salary values from that group and calculates a figure that would represent a ‘typical’ employee in that group. This is useful because it allows us to compare pay between different employee groups without having to look at every individual salary. The average can become an even more powerful metric when we begin to understand and analyse the different ways it’s calculated. It might seem counterintuitive that a figure like the average can be calculated in different ways and possibly provide different answers. After all, how can the same set of salaries produce different averages? The key is that each method looks at the data differently, helping us bring a different part of the picture into focus. There are two types of average that are particularly important when it comes to understanding pay: the mean and the median. So, how do they work, and what can each tell us about pay? Let's introduce them using a simple example company, PeopleTech Ltd. The Mean: What would everyone earn if pay were shared equally? The mean is what many people think of when they hear the word average. It shows us what each employee would earn if the company's total pay were shared equally among everyone. In everyday conversation, the terms mean and average are often used interchangeably. However, this isn't technically accurate, as the mean is just one of the ways to calculate an average, as we'll explore later on. To calculate the mean, we simply add together all the salaries and divide the total by the number of employees. Let's look at the example company, PeopleTech Ltd. Imagine the five employees earn the following annual salaries: €30,000 + €40,000 + €40,000 + €50,000 + €100,000 = €260,000 PeopleTech Ltd. has a total annual salary bill of €260,000 across its five employees. To calculate the mean, we divide this total by five: €260,000 ÷ 5 = €52,000 So, the mean salary at PeopleTech Ltd. is €52,000. In other words, if the company's total salary bill were shared equally between all five employees, each person would receive €52,000. The mean is useful because it gives us an overall picture of pay across the company. However, as we'll see, it doesn't always reflect what most employees actually earn, particularly when there are significant differences between the highest and lowest salaries. The Median: What is the salary in the middle? But what happens when one or two employees earn significantly more than everyone else? This is where the median can give us a different perspective. While the mean looks at the total of all salaries, the median looks directly at the middle of the data. Imagine arranging all our employees in a straight line, from the lowest-paid to the highest-paid. The salary of the person standing in the middle would represent our median salary. Let's look at PeopleTech Ltd. again. Using the same salaries as before, we arrange them from lowest to highest: €30,000 | €40,000 | €40,000 | €50,000 | €100,000 The middle salary is €40,000, making this the median salary for PeopleTech Ltd. What makes the median particularly useful is that it is not affected by unusually high or low salaries, often referred to as outliers. In our example, let's assume the €100,000 salary belongs to the CEO, which is double the next highest salary. This unusually high salary pulls the mean upwards, making the average salary appear higher than what most employees actually earn. The median, however, is not affected by this unusually high salary. At €40,000, it gives us a different perspective on what a typical employee earns in PeopleTech Ltd. This is particularly useful for HR professionals because it helps us understand what employees typically earn, without the results being skewed by a small number of particularly high or low salaries. Neither figure is wrong. They simply tell us different things about how pay is distributed across the company. Looking at both together gives us a more complete picture than relying on either one alone. One thing to note: when there is an even number of employees, there won't be one person sitting exactly in the middle. In this case, we take the two middle salaries and calculate their average to find the median. How does this all relate to the EU Pay Transparency Directive? The EU Pay Transparency Directive requires employers to report on both the mean and median gender pay gap. These gaps are calculated by finding the average pay for male employees and the average pay for female employees, and then measuring the difference between them. The difference is expressed as a percentage of men's average pay. For example, a gender pay gap of +10% means that women's average pay is 10% lower than men's average pay. But why does the Directive want to look at both figures? The size of a company's mean gender pay gap and median gender pay gap can tell us different things about how pay is distributed across the organisation. If a company's mean gender pay gap is larger than its median gender pay gap, this could suggest that higher-paid employees are having a greater influence on the overall gap. Think back to our PeopleTech Ltd. example, where the CEO's €100,000 salary pulled the mean upwards. A similar effect could occur in an organisation where the pay gap between most male and female employees is relatively small, but a highly paid position, such as the CEO role, is occupied by a man. Even though the difference in pay across the wider workforce may be relatively modest, this one high salary could pull the mean upwards and result in a much larger overall gender pay gap. On the other hand, if a company's median gender pay gap is larger than its mean gender pay gap, this could suggest that the difference in pay is more evident across the wider workforce, rather than being driven primarily by a small number of highly or lower paid positions. In other words, the gap may be more noticeable among employees around the middle of the pay distribution, rather than being concentrated at the top. This could highlight wider differences in how men and women are paid across the organisation, and may warrant further investigation. It is important to remember that neither the mean nor the median tells us exactly why a gender pay gap exists. They are indicators that help us identify patterns and differences in pay, rather than explanations in themselves. By looking at both measures together, HR professionals can begin to build a clearer picture of pay within their organisation, identify areas that may need further investigation and take a more informed approach to understanding and addressing any gaps.

Read article

Michelle Dervan

2 Nov 2026

All About Averages | Pay Analytics 101

The Importance of the Average When talking about pay data, the term average appears time and time again, but what does it actually mean? Put simply, an average salary gives us one figure to help describe pay across a group of employees. It takes all the salary values from that group and calculates a figure that would represent a ‘typical’ employee in that group. This is useful because it allows us to compare pay between different employee groups without having to look at every individual salary. The average can become an even more powerful metric when we begin to understand and analyse the different ways it’s calculated. It might seem counterintuitive that a figure like the average can be calculated in different ways and possibly provide different answers. After all, how can the same set of salaries produce different averages? The key is that each method looks at the data differently, helping us bring a different part of the picture into focus. There are two types of average that are particularly important when it comes to understanding pay: the mean and the median. So, how do they work, and what can each tell us about pay? Let's introduce them using a simple example company, PeopleTech Ltd. The Mean: What would everyone earn if pay were shared equally? The mean is what many people think of when they hear the word average. It shows us what each employee would earn if the company's total pay were shared equally among everyone. In everyday conversation, the terms mean and average are often used interchangeably. However, this isn't technically accurate, as the mean is just one of the ways to calculate an average, as we'll explore later on. To calculate the mean, we simply add together all the salaries and divide the total by the number of employees. Let's look at the example company, PeopleTech Ltd. Imagine the five employees earn the following annual salaries: €30,000 + €40,000 + €40,000 + €50,000 + €100,000 = €260,000 PeopleTech Ltd. has a total annual salary bill of €260,000 across its five employees. To calculate the mean, we divide this total by five: €260,000 ÷ 5 = €52,000 So, the mean salary at PeopleTech Ltd. is €52,000. In other words, if the company's total salary bill were shared equally between all five employees, each person would receive €52,000. The mean is useful because it gives us an overall picture of pay across the company. However, as we'll see, it doesn't always reflect what most employees actually earn, particularly when there are significant differences between the highest and lowest salaries. The Median: What is the salary in the middle? But what happens when one or two employees earn significantly more than everyone else? This is where the median can give us a different perspective. While the mean looks at the total of all salaries, the median looks directly at the middle of the data. Imagine arranging all our employees in a straight line, from the lowest-paid to the highest-paid. The salary of the person standing in the middle would represent our median salary. Let's look at PeopleTech Ltd. again. Using the same salaries as before, we arrange them from lowest to highest: €30,000 | €40,000 | €40,000 | €50,000 | €100,000 The middle salary is €40,000, making this the median salary for PeopleTech Ltd. What makes the median particularly useful is that it is not affected by unusually high or low salaries, often referred to as outliers. In our example, let's assume the €100,000 salary belongs to the CEO, which is double the next highest salary. This unusually high salary pulls the mean upwards, making the average salary appear higher than what most employees actually earn. The median, however, is not affected by this unusually high salary. At €40,000, it gives us a different perspective on what a typical employee earns in PeopleTech Ltd. This is particularly useful for HR professionals because it helps us understand what employees typically earn, without the results being skewed by a small number of particularly high or low salaries. Neither figure is wrong. They simply tell us different things about how pay is distributed across the company. Looking at both together gives us a more complete picture than relying on either one alone. One thing to note: when there is an even number of employees, there won't be one person sitting exactly in the middle. In this case, we take the two middle salaries and calculate their average to find the median. How does this all relate to the EU Pay Transparency Directive? The EU Pay Transparency Directive requires employers to report on both the mean and median gender pay gap. These gaps are calculated by finding the average pay for male employees and the average pay for female employees, and then measuring the difference between them. The difference is expressed as a percentage of men's average pay. For example, a gender pay gap of +10% means that women's average pay is 10% lower than men's average pay. But why does the Directive want to look at both figures? The size of a company's mean gender pay gap and median gender pay gap can tell us different things about how pay is distributed across the organisation. If a company's mean gender pay gap is larger than its median gender pay gap, this could suggest that higher-paid employees are having a greater influence on the overall gap. Think back to our PeopleTech Ltd. example, where the CEO's €100,000 salary pulled the mean upwards. A similar effect could occur in an organisation where the pay gap between most male and female employees is relatively small, but a highly paid position, such as the CEO role, is occupied by a man. Even though the difference in pay across the wider workforce may be relatively modest, this one high salary could pull the mean upwards and result in a much larger overall gender pay gap. On the other hand, if a company's median gender pay gap is larger than its mean gender pay gap, this could suggest that the difference in pay is more evident across the wider workforce, rather than being driven primarily by a small number of highly or lower paid positions. In other words, the gap may be more noticeable among employees around the middle of the pay distribution, rather than being concentrated at the top. This could highlight wider differences in how men and women are paid across the organisation, and may warrant further investigation. It is important to remember that neither the mean nor the median tells us exactly why a gender pay gap exists. They are indicators that help us identify patterns and differences in pay, rather than explanations in themselves. By looking at both measures together, HR professionals can begin to build a clearer picture of pay within their organisation, identify areas that may need further investigation and take a more informed approach to understanding and addressing any gaps.

Read article

The information on this page is not intended to serve and does not serve as legal advice. All of the content, information, and material on this website are only for general informational use.

Copyright © 2026 SkillsTrust. All Rights Reserved.

The information on this page is not intended to serve and does not serve as legal advice. All of the content, information, and material on this website are only for general informational use.

Copyright © 2026 SkillsTrust. All Rights Reserved.

The information on this page is not intended to serve and does not serve as legal advice. All of the content, information, and material on this website are only for general informational use.

Copyright © 2026 SkillsTrust. All Rights Reserved.

The information on this page is not intended to serve and does not serve as legal advice. All of the content, information, and material on this website are only for general informational use.

Copyright © 2026 SkillsTrust. All Rights Reserved.