How to Ask for a Pay Rise in the UK (Timing, Evidence, and What to Actually Say)

Asking your manager for more money is a different conversation from negotiating a new job offer, and it's worth treating it as one. There's no recruiter with a budget line waiting to be moved — there's a person you work with every week, a review cycle with its own rhythm, and a decision that usually has to go up at least one more level before it's final. Get the timing and the case wrong and you don't just fail to get the rise, you can make the next attempt harder too.

Timing: work with the review cycle, not against it

Most UK employers run pay decisions through an annual performance review cycle, and asking outside that window doesn't automatically fail, but it does mean your manager has to go and specifically request an off-cycle exception, which is a harder internal sell than "here's my case, right on schedule." If you know when your company's review happens, that's usually your best shot — and it's worth asking your manager or HR directly if you're not sure, rather than guessing.

If you're newer to the role, UK career advice is fairly consistent on this point: give it around six months before raising pay specifically. That's not an arbitrary politeness rule — it's the time it typically takes to actually build a track record your manager can point to, rather than asking on the strength of promise alone. Asking too early doesn't usually get a flat no, but it does often get a vague "let's revisit this later," which wastes the conversation.

Build a case with wins, not comparisons

The single most important shift in how to frame this: talk about what you did, not what someone else earns. "I found out [colleague] makes more than me for the same job" is one of the most common ways this conversation goes wrong in the UK specifically — it puts your manager in a position where they can't really respond honestly (pay details are usually confidential for a reason), and it can tip into equal-pay territory that HR has to handle carefully, which slows everything down and makes the conversation adversarial rather than collaborative.

What works instead is a short, concrete list of things you actually did:

• Targets you hit or beat. Numbers are best — revenue, retention, tickets closed, projects delivered on time, whatever your role actually measures.
• Money you saved or made the company. If you can attribute a number to something you did, even roughly, that's the strongest single line in the conversation.
• Scope you took on beyond your job description. Managing a project that wasn't yours, covering for a departed colleague, onboarding new starters — anything where your actual responsibilities grew without a matching title or pay change.
• External benchmark data, used to support your case rather than as the whole case. Glassdoor and job ads with disclosed salary bands for your title and level (increasingly common in UK listings) tell you what "market rate" looks like, so you're not guessing. Bring this as "here's roughly where similar roles are paid" rather than "I deserve market rate" as a standalone demand — the wins are what make it land.

Write this down before the meeting. Not because you'll read from a script, but because having it in front of you keeps the conversation on specifics instead of drifting into a general "I feel undervalued," which is true but not something your manager can act on directly.

Get a proper meeting, not a hallway ambush

Don't raise this in a 1:1 that's already packed with other topics, and definitely don't do it informally in a corridor or at the end of a long day when your manager is distracted. Ask explicitly for time to discuss your role and compensation — a scheduled slot signals you're taking it seriously and gives your manager time to actually think, rather than reacting on the spot with whatever answer is easiest to give in the moment, which is usually a soft no or a stall.

A simple message works: "Could we grab 30 minutes this week or next — I'd like to talk through my role and pay." That's enough context for them to prepare, without putting the whole case in writing before you've had the conversation.

What to actually say

This is where UK workplace habits can work against you. Understatement serves you well in most workplace situations, but a pay conversation specifically needs more directness than the culture generally rewards — tentative phrasing gets read as tentative asks, and a manager can quite reasonably decline something that wasn't clearly requested.

Compare:

• Weak: "I was sort of wondering if there might be any room to maybe look at my salary at some point?"
• Direct: "I'd like to talk about a pay rise. Over the last six months I [specific wins]. Based on that and where similar roles are benchmarked, I think [specific number or range] is fair. What would it take to get there?"

The second version gives your manager something concrete to respond to, escalate, or push back on — all of which move the conversation forward. The first version gives them nothing to act on, and "let's see" is the easiest possible response to a question that wasn't really a question.

Ending with an open question — "what would it take to get there?" — is worth keeping even if you're nervous, because it turns a yes/no moment into a discussion, and it's the point where you often learn what's actually possible even if the exact number isn't.

What a realistic ask looks like

It's worth knowing the typical range before you walk in, not to cap your ambition but to calibrate it. A standard, well-supported pay rise in the UK tends to land in the 3–5% range in a given cycle. That's the benchmark, not a ceiling — if you're genuinely underpaid relative to the market for your role (which your benchmark data should tell you), asking for more than that is entirely reasonable, and you should say so explicitly: "the market data suggests this role should be paid more than 3–5% would get me to, which is why I'm asking for X."

Knowing the typical range mostly protects you from two failure modes: asking for so little that you leave money on the table you could genuinely have got, or asking so far outside typical practice that the number itself becomes the story instead of your case.

If the answer is no

A no on the spot is common — even a well-built case often needs to go up to your manager's manager or into a formal budget cycle. Ask what would need to be true for the answer to change, and when it's reasonable to revisit it. That turns a flat no into a concrete follow-up point, and it tells you whether the door is actually closed or just closed for now.

Rehearsing before the real conversation

Building the case on paper is the easy part. Sitting across from your actual manager and holding your number when they push back, or staying calm when they go quiet after you ask, is a different skill entirely — and it's hard to practise because you only get to have this specific conversation with this specific person a couple of times a year.

Prepair's negotiation practice feature has an "annual review" mode built for exactly this — you pick how firm you want the AI manager to play it, and run through the real exchange: stating your case, responding to pushback, asking the follow-up question if they say no. It ends with a score on what you asked for, what you got, and where your case held up or didn't, so you find the gaps in your argument before your actual manager does.

If you're earlier in your job search and this is about a new offer rather than your current role, the negotiation looks quite different — you're dealing with a recruiter, a wider package, and a one-time decision rather than an ongoing working relationship. And if you want to practise the interview stage itself, Prepair's free interview practice covers that, three sessions a month with no card required.