A Practical Pay Audit Example for UK Employers

A pay audit example is most useful when it shows more than a headline pay gap. For senior leaders, the real value lies in identifying whether pay differences are explainable, consistently governed and commercially sustainable - before they become an employee relations issue, a retention risk or a board-level concern.

A well-run audit does not start with a spreadsheet and end with a percentage. It starts with a clear question: are people doing work of equal value paid fairly, positioned appropriately against the market and rewarded in line with the organisation’s stated principles? The answer requires sound job architecture, reliable data and careful judgement.

What a pay audit should examine

A pay audit is a structured review of pay outcomes and the decisions behind them. It can be focused narrowly on equal pay risk, or cover the wider reward framework, including salary ranges, progression, incentives, allowances and benefits.

For most UK employers, the scope should distinguish between three related but different issues. Equal pay concerns whether men and women receive equal pay for equal work, work rated as equivalent or work of equal value. Gender pay gap reporting measures the difference in average pay across the workforce, regardless of role. A broader pay equity review may also examine ethnicity, disability or other characteristics where data quality and legal considerations permit.

Market competitiveness matters too. A pay structure can be internally consistent but still fail to attract scarce talent. Equally, paying above market without a clear rationale can create unnecessary cost and distort career progression. The audit should therefore test fairness, competitiveness and governance together.

Pay audit example: a growing technology employer

Consider a fictional UK technology business with 850 employees. It has grown through acquisition, operates hybrid working arrangements and has recently introduced a new career framework. The Chief People Officer commissions a pay audit after seeing a widening gender pay gap and inconsistent starting salaries in technical roles.

The stated objectives are to identify material equal pay risk, assess whether salary decisions align with the new job levelling framework, understand market positioning in key talent groups and provide an action plan for the executive team and RemCo.

1. Build a defensible data set

The review begins with an agreed snapshot date and a clear data dictionary. HR, payroll and finance reconcile core fields including base salary, contractual hours, full-time equivalent pay, bonus outcomes, allowances, job title, department, location, grade, manager, start date and protected-characteristic data where available.

This stage often exposes the first governance issue. In this example, several acquired businesses use legacy job titles, and 11% of employees have no confirmed grade. Bonus data is also recorded differently between business units. Those gaps do not make an audit impossible, but they limit certainty. They must be documented rather than quietly worked around.

The employer then groups roles using the new job architecture. This is critical. Comparing a software engineer with a project manager merely because their salaries are similar produces weak conclusions. The appropriate comparisons are between like work, roles rated as equivalent, or work that has been objectively assessed as being of equal value.

2. Test pay outcomes by comparable group

The analysis reviews base pay first, then variable pay and allowances separately. Looking only at total cash can mask the source of a disparity. For example, a salary gap may be small while bonus eligibility or sales commission arrangements create a significant difference in total reward.

A simplified extract from the technology employer’s audit looks like this:

| Comparable group | Women’s median base pay | Men’s median base pay | Initial finding | | --- | ---: | ---: | --- | | Software Engineer, Level 3 | £54,000 | £57,500 | Difference requires review | | Product Manager, Level 3 | £58,000 | £58,800 | Within expected range | | Customer Success Manager, Level 2 | £42,500 | £42,000 | No material concern identified | | Finance Business Partner, Level 4 | £67,000 | £73,000 | Difference requires review |

The figures are a prompt for investigation, not a finding of unlawful pay discrimination. Median comparisons can be distorted by small populations, individual performance, location premiums or recent recruitment decisions. A credible audit tests whether those explanations are real, evidenced and applied consistently.

In the software engineering group, the employer finds that 14 of the 18 higher-paid employees were hired during a difficult recruitment period. However, recruitment approvals do not consistently record the market evidence used to justify offers above range. Several women in the same grade have stronger performance records but have progressed through smaller annual increases.

The issue is not simply that some new hires were paid more. Paying a market premium can be commercially justified. The risk is that the premium was not governed, was not time-limited and was not followed by adjustments for existing employees performing comparable work.

3. Separate explanation from justification

This distinction is where many internal reviews lose value. An explanation describes what happened. A justification establishes whether the difference can be supported by a genuine, proportionate and non-discriminatory factor.

For the finance business partner group, the company initially attributes the gap to London location premiums. Further testing shows that two men receiving the premium are permanently based outside London and work on the same hybrid pattern as colleagues who do not receive it. The rationale is therefore inconsistent. The audit recommends correction rather than accepting a legacy arrangement as an explanation.

The review also checks performance ratings, relevant experience, specialist skills, working patterns and tenure. Length of service may explain some differences, but it should not be treated as an automatic defence. Leaders need to ask whether it remains proportionate and whether it disadvantages one group in practice.

4. Examine the decisions that created the gap

Pay outcomes are symptoms of decision-making. The technology employer therefore maps the employee lifecycle: recruitment offers, promotion increases, annual pay review, retention awards and bonus allocation.

It finds that starting-salary discretion is high in engineering and sales, while promotion criteria are interpreted differently between functions. Managers have guidance, but no common approval thresholds for offers above range or pay increases outside the annual review cycle. This creates an avoidable dependency on individual judgement.

The audit recommends four immediate controls:

• require documented market evidence and senior approval for offers above the salary range;

• define standard promotion increase parameters, with exceptions reviewed centrally;

• introduce a regular review of pay by grade, gender and key talent population;

• establish a remediation budget for priority cases where disparities cannot be objectively justified.

These measures address the cause as well as the visible pay differences. They also give finance greater confidence over cost forecasting and reduce the likelihood of repeated ad hoc adjustments.

Turning findings into a credible action plan

A pay audit should not promise that every variation will disappear. Some variation is legitimate. The aim is to ensure each material difference has a clear rationale, is supported by evidence and sits within an agreed reward framework.

For the example employer, the executive team agrees to correct three individual pay anomalies immediately, phase adjustments for a further seven employees over two pay cycles and harmonise location-premium rules. It also sets a target to complete levelling for all legacy roles within six months. This matters because unlevelled roles make meaningful pay comparisons difficult and undermine confidence in salary ranges.

The RemCo receives a concise report covering material risks, estimated remediation cost, progress against the job architecture programme and proposed governance changes. It does not receive a long list of unexplained variances. Senior oversight is most effective when reporting focuses on decisions required, exceptions that need challenge and measures of improvement over time.

Communication requires equal care. Employees do not need access to individual salaries, but they should understand how jobs are levelled, how pay ranges are set, what progression looks like and how concerns can be raised. Greater transparency without a coherent framework can create confusion. Transparency supported by consistent principles builds trust.

Common limitations to manage

A pay audit is only as reliable as its data and comparison groups. Small populations can make results volatile, incomplete diversity data can limit analysis, and inconsistent job titles can conceal genuinely comparable work. These are not reasons to postpone the work. They are reasons to state the limitations clearly and improve the underlying reward infrastructure.

There is also a trade-off between speed and depth. A diagnostic review can quickly identify priority risks and establish where deeper investigation is needed. A full equal pay audit, particularly across complex grades, legacy contracts and multiple legal entities, requires more detailed role evaluation and legal input. The proportionate approach depends on workforce size, organisational change, existing evidence and the level of concern.

Indigo Reward supports employers in bringing this work together: rigorous analysis, practical job levelling, market context and governance that leaders can use with confidence. The strongest outcome is not a cleaner report for one year, but a pay framework that makes fair and commercially sound decisions easier every time a manager recruits, promotes or retains talent.