Irish organisations are about to discover that pay transparency compliance depends on something most of them do not have: a structured, defensible job architecture. Here is why it matters and what good looks like.
When Irish employers think about pay transparency compliance, they tend to think about reporting — disclosing salary ranges, publishing gender pay gap figures, responding to employee information requests. These are visible obligations and they attract attention.
But reporting is the output. The input — the thing that determines whether your reporting is defensible or exposes you to legal challenge — is your job architecture.
Most Irish organisations do not have one. Or rather, they have something they call a grading system or a salary band structure, but it was not designed to withstand the scrutiny the EU Pay Transparency Directive will bring.
What a job architecture actually is
A job architecture is a systematic framework that organises every role in an organisation by:
- Job family — groups of roles with related functions (e.g., Finance, Engineering, Operations)
- Job level — tiers of increasing responsibility, complexity, and seniority within each family
- Job grade — a standardised scale that links levels to compensation bands
The critical feature is that the framework is built on objective, documented evaluation criteria — not tradition, negotiation, or managerial preference.
When someone asks "why is Role A in Grade 5 and Role B in Grade 4?", the answer should be traceable to a set of factors that were applied consistently across the entire organisation. If the answer is "because that is what we offered when we hired them" or "because their manager argued for it", you have a problem that pay transparency legislation will surface.
The Irish mid-market reality
In our work with Irish mid-market organisations — typically 150 to 2,000 employees — we see a consistent pattern:
Titles are inconsistent. The same level of work carries different titles across departments. A "Senior Manager" in one team has responsibilities equivalent to a "Lead" or "Head of" in another. Title inflation is widespread and undocumented.
Grades are informal or missing. Many organisations have salary bands, but the criteria for placement within those bands are not codified. Decisions about where a role sits in the structure are made case by case, often during recruitment, and not revisited.
Historical decisions are baked in. Pay structures reflect a history of individual negotiations, market pressures at the time of hire, and retention adjustments. These are rational decisions in context, but they create structural inconsistencies that are invisible until you look at them systematically.
Role descriptions are outdated. Job descriptions, where they exist, often describe the role as it was conceived at hiring — not as it has evolved. Responsibilities have shifted, but the documentation has not kept pace.
None of this is unusual. It is the normal state of organisations that have grown organically. But it is incompatible with what the Pay Transparency Directive requires.
What the Directive demands
The Directive requires that pay structures be based on "objective, gender-neutral criteria." It specifically mentions job evaluation and classification systems as the mechanism for ensuring equal pay for equal work or work of equal value.
This means:
- You need a defined methodology for evaluating roles
- The methodology must use criteria that are not directly or indirectly gender-biased
- The criteria must be applied consistently across the organisation
- The results must be documented and available for scrutiny
If an employee challenges a pay difference between their role and another role they consider to be of equal value, you need to be able to demonstrate — with documentation — why the roles are graded differently, and that the grading was based on objective factors.
Without a structured job architecture, this defence is not available to you.
What good looks like
A pay-transparency-ready job architecture has several characteristics:
Factor-based evaluation. Each role is assessed against a defined set of factors — typically four to eight — that capture the dimensions of work that determine its value. Common factors include knowledge requirements, problem-solving complexity, accountability scope, and communication demands. The factors themselves must be gender-neutral and tested for indirect bias.
Consistent application. The same factors and scoring methodology are applied to every role, regardless of department or historical context. A finance role and an engineering role at the same grade should demonstrably require comparable levels of complexity, expertise, and accountability.
Clear grade boundaries. The distinction between adjacent grades should be defined in terms of the evaluation factors, not just salary ranges. If you cannot articulate what distinguishes a Grade 4 role from a Grade 5 role in factor terms, the grade structure is cosmetic.
Regular maintenance. Job architectures degrade over time as roles evolve and new positions are created. A sustainable architecture includes a process for evaluating new roles and periodically reviewing existing placements.
Documentation. Every role's evaluation should be recorded — the factor scores, the rationale, and the resulting grade placement. This is your audit trail.
The AI opportunity
Building a job architecture from scratch for a 500-person organisation is a substantial undertaking. Traditional approaches — involving external consultants, structured interviews with role holders and managers, committee-based scoring, and iterative calibration — typically take four to eight months and cost accordingly.
AI-assisted approaches can compress this significantly, primarily by automating the initial analysis of job descriptions, producing draft factor scores, and identifying inconsistencies across the dataset. The human work shifts from doing every evaluation manually to reviewing, calibrating, and validating AI-generated outputs.
This is not about replacing HR expertise. It is about making the underlying analytical work feasible within the timeline Irish employers now face.
The key advantage of AI in this context is consistency. A human evaluator assessing their 150th role description will inevitably apply criteria slightly differently than they did on the 10th. AI does not have this problem. It applies the same framework to every role in the same way, every time. That consistency is exactly what the Directive's "objective criteria" requirement demands.
If your organisation needs to build or formalise a job architecture ahead of the pay transparency deadline, the starting point is a diagnostic assessment of what you currently have and what needs to change. We work with Irish organisations to design practical, evidence-based job architectures that meet regulatory requirements without unnecessary complexity. Contact us to start the conversation.