An Equal Pay Risk Case Study for Employers

An equal pay risk case study showing how fragmented data, weak job evaluation and undocumented decisions can turn a pay anomaly into exposure early on.

A board request can expose a problem long before a tribunal does. In this equal pay risk case study, a routine question about salary differences between two teams revealed a pattern of pay decisions that the employer could see, but could not fully explain. The issue was not one unusually high salary. It was the absence of a consistent, evidenced record of how comparable roles had been valued over time.

The following is a fictionalised composite based on the pressures many UK employers face during growth, acquisition and annual pay review cycles. It illustrates how equal pay risk develops, why gender pay gap data alone will not resolve it, and what leaders need to do when an apparent anomaly becomes a governance question.

Equal pay risk case study: the overlooked exception

A UK services group with 1,200 employees had grown quickly through acquisition. Its payroll was managed centrally, while pay decisions remained largely within business units. HR held job descriptions in its HR system, Finance held payroll extracts, and managers used local spreadsheets to track recruitment offers, retention payments and counteroffers.

At year end, the Chief People Officer was preparing a board paper on reward. A director asked why the average base salary for senior client managers in one division was materially higher than for senior client managers in another. The immediate explanation seemed straightforward: the higher-paid division operated in a more competitive market.

The first analysis appeared reassuring. The business had a published salary range for the role family, and most employees sat within it. However, once the data was joined by grade, role history, location, sex, starting salary and subsequent increases, the position became less comfortable. Women in the lower-paid division were more likely to have entered at the bottom of the range, while men in the higher-paid division had received larger recruitment premiums and more frequent off-cycle adjustments.

No single data point proved unlawful unequal pay. But the organisation could no longer treat the question as a reporting variance. It had become a risk requiring investigation, evidence and a defensible response.

A business rationale is not yet a defence

The division leader could point to client demand, a shortage of experienced candidates and historic acquisition terms. Those factors may be relevant. Under the Equality Act 2010, however, an employer facing an equal pay claim must be able to show that any difference in contractual pay for equal work is explained by a genuine material factor that is not sex-discriminatory.

That test is fact-specific. A market premium can be legitimate, but it needs to be real, proportionate and consistently applied. It is harder to defend where there is no clear policy, no approval record, no stated review date and no evidence that the premium related to the role rather than the individual who negotiated hardest.

In this case, managers had used phrases such as “market adjustment” and “retention necessity” in emails, but the business had no shared definition for either term. Some adjustments were permanent additions to base pay. Others were intended to be temporary but had never been revisited. The rationale may have existed at the time, yet the evidence trail did not meet the standard the organisation now needed.

When a pay gap question becomes an equal pay question

The group had produced its statutory gender pay gap report on time. Its median pay gap had improved year on year, largely because representation of women in management had increased. That was positive, but it did not answer the board’s question.

Gender pay gap reporting examines aggregate differences across a workforce. Equal pay concerns whether individuals of different sexes are receiving equal contractual pay and benefits for equal work, work rated as equivalent or work of equal value. A favourable gender pay gap figure does not rule out equal pay exposure. Equally, a gender pay gap does not by itself establish an equal pay breach.

The distinction mattered because the organisation had relied on the gender pay gap report as a broad indicator of fairness. It had not carried out a structured equal pay analysis across comparable roles, nor had it maintained a current job evaluation framework following the acquisition. This left leaders without a clear view of where risk sat or which pay differences had a documented, non-discriminatory explanation.

What made the risk difficult to defend

The central weakness was fragmentation. The organisation could extract salary figures, but it could not readily reconstruct each employee’s compensation journey: their starting point, grade, job scope, changes in responsibility, market adjustments, performance outcomes and approval history.

Its salary bands also lacked operational control. Bands existed in a policy document, but managers could make offers outside them with informal senior approval. The payroll team processed the final figure, yet did not receive the underlying rationale or a trigger to assess whether an exception altered pay compression or created a comparability concern.

Job architecture added a further complication. Similar jobs carried different titles after acquisition, and title matching was used as a substitute for role evaluation. That approach can miss genuine comparators and create false ones. The relevant question is not whether two employees share a title, but whether their work is equal under the legal tests and the organisation’s own role framework.

The review also found that discretionary decisions had accumulated. Recruitment premiums had not been distinguished from core salary. Some employees had progressed through annual review; others had received ad hoc increases after threatening to leave. There was no complete record of who approved each decision, what alternatives were considered or whether a planned review occurred.

For an executive team, this is more than an HR data issue. It affects legal exposure, workforce cost forecasting, employee trust and the credibility of statements made to the board. When evidence is dispersed across inboxes and local files, the time to respond to a challenge is longer and the quality of the response is weaker.

Reconstructing the evidence before deciding the remedy

The organisation began with an evidence-led review rather than an immediate broad pay correction. A blanket increase may appear decisive, but it can introduce new inconsistencies if comparators, role scope and legitimate factors have not been tested properly.

First, it created a controlled population of roles for analysis. This required mapping legacy titles to a common job architecture, checking reporting lines and confirming whether roles had been evaluated or needed fresh evaluation. The review then compared contractual pay elements separately, including base pay, allowances, bonuses and benefits where relevant. Combining everything into one number can conceal the source of a difference.

Next, the team examined individual pay histories. For each material variance, it recorded the date of change, decision-maker, stated rationale, supporting evidence and any planned review. Where a market premium had been applied, the team tested whether contemporaneous market data supported it and whether employees in similar circumstances had been treated consistently.

This work identified three categories. Some differences were explained by documented changes in role scope. Others reflected legitimate but poorly recorded market factors and required a clear review plan. A smaller group could not be adequately evidenced. Those cases were escalated for legal advice and individual remediation planning.

The value of this approach was not that it produced a single risk score. It gave the executive team a traceable basis for action. They could distinguish a data-quality problem from a policy failure, and a policy failure from a potential legal exposure.

Correcting pay without creating another problem

The group made targeted adjustments where the review showed that employees had fallen behind an appropriate comparator group without an evidenced explanation. It also corrected salary band positions where historic progression had been inconsistent. Each action was documented with the reason for change, approval route, effective date and future review point.

Communication required judgement. Employees do not need a running commentary on confidential comparator data, but they do need confidence that pay is assessed fairly. Managers were given clear language for explaining salary bands, progression criteria and the organisation’s process for reviewing concerns. They were not asked to improvise legal explanations.

The business also avoided treating the exercise as a one-off clean-up. Equal pay risk can re-emerge as new hires are recruited, specialist skills become scarce, teams restructure or managers use counteroffers to retain people. Remediation without changed decision controls is simply an expensive pause.

Turning compensation decisions into governance evidence

The lasting change was to bring compensation data, policy and approvals into one operating record. Every pay decision now required the relevant role, salary band, reason code, supporting context and approver. Exceptions triggered a review against comparable employees, budget and band position. Temporary premiums carried an expiry or review date rather than quietly becoming permanent base pay.

For leaders, the most useful view was not a static annual report. It was a live picture of where pay was drifting: employees outside range, recurring exceptions, compressed salary relationships, unexplained differences within comparable groups and decisions awaiting review. Orgress is designed to provide that visibility alongside the documented decision trail needed for pay governance and reporting.

The practical lesson is simple: do not wait for an employee challenge, a due diligence exercise or a board query to discover whether a pay difference can be explained. Make the rationale visible when the decision is made, test it against the role framework, and retain evidence that allows your organisation to stand behind it.