Practical reference material · Guide

Job Architecture: A Practitioner's Guide

What job architecture actually is, why it underpins every defensible pay decision, and how to build one that holds up to scrutiny.

1 · What it is

Job architecture is the structure beneath your pay

Job architecture is the organised framework that defines how work is grouped, levelled and related across an organisation. It answers three questions that every reward decision depends on: what job families exist, what levels sit within each, and how one role compares to another in scope and contribution.

It is not a list of job titles. Titles are labels; architecture is the logic underneath them. Two people can hold the title "Manager" and sit three levels apart in reality. Job architecture is what makes that difference explicit, consistent and defensible — rather than a matter of history, negotiation or who asked.

When people describe pay as "inconsistent" or "hard to explain," the root cause is almost always architectural. The numbers are only ever as sound as the structure they sit on.

2 · Why it matters

Every defensible pay decision rests on it

A salary range means nothing until you know which roles belong in it. A market benchmark is misleading until you have matched your role to the right comparator level. A promotion is arbitrary until "the next level" is actually defined. In each case, the pay decision inherits its credibility — or its fragility — from the architecture beneath it.

This is why organisations with weak job architecture experience the same recurring symptoms: pay compression, inconsistent offers, uncontrolled exceptions, grade inflation, and decisions leaders cannot explain when challenged. None of these are pay problems in origin. They are architectural problems that surface as pay problems.

Under stronger pay-transparency scrutiny, this matters more than ever. When an employee, a candidate or a regulator asks why two comparable roles sit in different grades, the answer has to come from a structure — not from an individual's memory of a decision made years ago.

3 · The components

The four building blocks

A working job architecture is built from four related components. Each depends on the ones before it.

Job familiesGroupings of roles that share a common type of work — for example, Finance, Engineering, Commercial. Families let you compare like with like and build career paths that make sense.

LevelsThe vertical structure within and across families — the rungs that define increasing scope, complexity and accountability. Levels are what make "senior" mean something specific rather than subjective.

Job evaluationThe method that places a role at the right level using consistent, evidence-based criteria — not job title, incumbent seniority or manager influence. Evaluation is what makes the structure defensible.

Grades & rangesThe pay structure that maps onto the levels — the salary ranges each grade carries. This is where architecture connects to money, and where a sound structure pays off.

4 · How to build it

Building an architecture that holds up

The sequence matters. Organisations that struggle usually tried to price roles before defining them. A structure that lasts is built in this order:

Define the work before you price it. Start with job families and a clear levelling framework — what distinguishes each level in terms of scope, complexity, autonomy and impact. This is the foundation; everything else maps onto it.

Evaluate consistently. Place roles into levels using a documented evaluation method applied the same way every time. Whether you use a recognised methodology or a well-designed internal framework, the discipline is the same: the same evidence produces the same result, regardless of who is in the role or who is doing the evaluating.

Map grades and ranges onto the structure. Only once roles are levelled do salary ranges become meaningful. Ranges attach to grades, grades attach to levels, and market data is interpreted against the right comparator level — not a job title.

Govern the exceptions. No architecture survives contact with reality unchanged. What separates a durable structure from a decaying one is not the absence of exceptions but the governance of them — every deviation recorded, justified, time-bound and reviewed. Ungoverned exceptions are how good architectures quietly collapse.

5 · Common failures

Where architectures break down

Most job architectures do not fail at launch. They erode. The common patterns:

Title-driven levelling. Roles placed by job title or by the seniority of the current holder, rather than by evaluated scope. Over time this inflates grades and destroys internal equity.

Structure without governance. A well-designed architecture with no discipline around exceptions, promotions or off-cycle adjustments. Within two or three cycles, the structure on paper no longer matches the structure in practice.

Evidence you cannot produce. Decisions that felt right at the time but were never documented. When challenged, the organisation cannot show why — and being correct is no defence if you cannot prove it.

The through-line is consistent: a grade that looks right and a grade you can prove is right are not the same thing. Job architecture is the discipline that closes that gap.

Next step

Assess your own structure

If this guide raised questions about your own job architecture, the Reward Governance Diagnostic assesses exactly these areas — job families, levelling, evaluation and the governance around them — and shows you where the gaps are.

Start the diagnostic Describe your challenge