Building Defensible Pay at the Point of Hire

Where People Start Is Where They Stay

Pay gaps don't only emerge through promotions and pay reviews. Many start with the first offer. Starting salaries tend to stick, which means a decision made at the point of hire can shape someone's pay for years. Where people start is often where they stay. 

That matters more as pay transparency increases. Across Europe and the US, employers face growing expectations to publish ranges and explain how pay is set. Under the EU Pay Transparency Directive, differences in pay between women and men doing equal work or work of equal value need to be capable of objective, gender-neutral justification. 

"That's where they started" isn't a defensible pay principle you want to rely on. 

Across two RoleMapper panels on defensible pay, employment lawyers and pay equity specialists kept returning to the same point: the offer is where fair pay is often won or lost. 

Hiring Is Where Pay Gaps Begin 

Hiring creates a perfect storm. Talent acquisition is measured on filling roles. Hiring managers want the right person in the seat. Candidates may also have competing offers. 

Reward are often asking a different question: how did we decide what this work is worth and can we explain why this person should be paid this amount? 

Without clear controls, starting pay can depend as much on hiring pressure as the work itself. 

At a recent Leapsome and Ravio webinar, Ravio shared data on established (P3) software engineers across Europe showing new hires earning 14% more than existing employees in February 2025, and 12% more a year later. The timing is striking, with the gaps appearing as many companies entered a new compensation cycle. It shows how much the point at which someone joins can shape their starting pay, with that initial advantage potentially lasting long after the hiring pressure has passed. 

Five Hiring Habits That Create Risk 

Basing the offer on previous salary: You import another employer's pay philosophy into your own. Any historic inequalities can come with it. Under the EU Pay Transparency Directive, employers must not ask applicants about their pay history. 

"It's the market": Market data can inform pay, but it doesn't by itself explain why two people doing equal-value work are paid differently. It may also reproduce historic patterns of undervaluation. 

Negotiating base pay: When individual bargaining changes salary without clear guardrails, negotiation skill effectively becomes a pay-setting factor. That can be difficult to defend later. 

Making the above-range hire: It may feel justified when a critical candidate is about to walk away. Two years later, the hiring pressure has been forgotten but the pay difference remains. 

Putting hot-skill premiums into base pay: Skills can be scarce today and commonplace tomorrow. If a premium is needed, define what qualifies and document why it exists. Keeping it separate from base pay also makes it easier to review. 

One Fixed Offer Removes the Haggle 

Leapsome has taken salary negotiation out of its hiring process. It publishes its pay bands and tells candidates early that they will receive one offer. The number is based on the band, assessed experience and how comparable colleagues are paid. 

Importantly, Leapsome addressed existing employees' pay first. If a proposed new-hire salary would put the candidate above an existing team member, the employee's pay is reviewed. A competing offer doesn't automatically move the number. 

Removing negotiation doesn't solve every pay problem. It does remove a variable that has little to do with the value of the work. 

A fixed offer is also only as defensible as the band beneath it. That's why job levelling and evaluation matter. 

Five Controls That Make Starting Pay More Defensible 

Defensible pay doesn't mean identical pay. It means differences can be explained using objective, gender-neutral criteria. 

1. Value the work first. Level and evaluate the role before deciding what an individual should earn. Market data can help calibrate bands, but it shouldn't replace your own assessment of the work's value. 

2. Define the offer rules. Write down the legitimate factors that determine where someone sits within a band. If a factor isn't in the framework, it shouldn't suddenly become important because a candidate asks for more. 

3. Check internal comparators. Before an offer goes out, compare it with people already doing the same or equal-value work. A salary can look reasonable against the external market while creating an internal problem. 

4. Control exceptions. Record out-of-band offers and the reason for them. Include who approved the decision and when it will be reviewed. If an offer exposes an unjustified difference with existing employees, address the difference rather than simply adding another one. 

5. Document and explain. Record the factors behind the offer and train managers to explain them. A manager should be able to give a better answer than "that's the band" or "that's what they asked for." 

Six Questions to Ask Before Every Offer 

• Is the role levelled based on the work, rather than the job title? 

• Which written pay factor places this person in the band? 

• Have we kept previous salary out of the calculation? 

• How does the offer compare with employees doing equal-value work? 

• If it's an exception, is the reason documented and approved, with a review date? 

• Could the hiring manager explain the number to the candidate and an existing employee? 

If those questions are difficult to answer, the problem isn't transparency. It's the pay decision underneath it. 

Defensible Hiring Starts with How You Value the Work 

The hardest question in that checklist is often the first: how do you know the role has been levelled based on the work? 

That's the problem RoleEvaluate is designed to solve. 

RoleEvaluate brings job classification and points-factor job evaluation together in one platform. It creates an audit trail from the evidence in the job description to the final levelling decision. AI surfaces the evidence; people make the decision. 

That gives reward and hiring teams a documented explanation of how the organisation valued the work before they decide what to pay the person doing it. 

If you want starting pay you can defend, you need to be able to defend where the role starts too. 

Watch our Defensible Pay panels on demand, or book a RoleEvaluate demo to see it in action.