When is the best time to ask for a pay rise?

Three windows work reliably: just after a delivered, visible result; in the weeks before the organisation's budget or pay-review cycle sets (autumn in much of the UK public sector, before year-end in many firms); and at a genuine change of scope, when the role you do stops matching the role you're paid for. The worst times are during a crisis, straight after an error, and in a corridor.

How much should I ask for?

Anchor to evidence rather than appetite: where you sit in your organisation's band, what comparable roles pay in your market and region — the ONS earnings data and any salary survey your employer already uses are hard-to-dismiss sources — and what has changed in your scope. Ask for one specific figure you can defend, not a range, and put the basis beside it in writing.

Should I mention my cost of living or personal circumstances?

As the basis of the case, no — pay is priced against the value and market rate of the work, and a need-based case invites sympathy rather than a decision, which is the polite version of no. Organisation-wide cost pressures belong to organisation-wide processes like annual uplifts and any union negotiation, and your individual case is strongest kept separate from them.

What if my manager agrees I deserve more but says their hands are tied?

Treat it as an alliance, not a refusal: a manager who agrees on merit is a sponsor looking for a mechanism. Ask which mechanism fits — an exception case, a regrade or job re-evaluation, the next review cycle — who decides, and what paper they need from you. Then supply the paper and a follow-up date. 'Hands tied' plus a route and a date is progress; 'hands tied' with neither is your answer.

Is it risky to ask — will it be held against me?

A professionally made, well-timed, evidence-based ask is ordinary management business, and handling one well is literally your manager's job. What creates risk is the delivery, not the request: ultimatums you don't mean, colleague comparisons, or relitigating the answer weekly. If a calm, well-made case is genuinely met with hostility, that tells you something about the organisation worth knowing early.

Grow

Asking for a pay rise: the conversation, worked line by line

Updated 12 August 2026

Most pay conversations are lost before they start, in three familiar ways: asked at the wrong moment (the corridor, the crisis week, the day after a mistake), asked on the wrong grounds (time served, personal costs, a colleague's rumoured salary), or never asked at all — the commonest failure, politely waiting to be noticed. This page works the fourth way: a deliberate conversation, booked properly, argued from the value of the work, with worked lines for the deflections that almost always come back.

Two facts shape everything below. First, your manager can rarely say yes in the room — pay moves through budgets, bands, and someone senior signing off an exception, which means your real audience is a forwarded email and your real product is a case that survives forwarding. Second, 'no' is usually 'not yet, not like this, or not from this budget line' — each of which has a next move. The answers below treat the first no as the middle of the conversation, not the end.

One boundary, held throughout: the case is built on the work — scope that grew, results that landed, the market price of what you now do. Personal financial pressure is real and human, and it is also the weakest possible argument here, because pay is priced against value, not need. The strongest version of you in this conversation sounds less like an appeal and more like a colleague pricing a role — which, precisely, is what you are doing.

Your career — see where this workplace conversation fits in the wider loop.

What the room is weighing

Whether the case is about the role or the person's feelings about the role. 'My scope has grown — here's what I now own that I didn't in January' is a case; 'I feel I deserve more' is a mood. Managers can only forward the first kind.
Whether your evidence survives someone checking. Named work, dates, figures that are yours rather than the team’s, and a market comparison from a source they can open — the case will be re-read sceptically by someone who was not in the room, and it has to hold up without your voice attached.
Timing sense. Asking in the planning window before budgets set, after a delivered win, in a booked meeting with its purpose named — versus ambushing a manager in a bad week. The timing IS part of the case: it shows the judgement the bigger salary is supposed to be buying.
How you take the first no. Composed, curious, converting it into criteria and a date — or deflated and dropping it, or bristling into a threat. Managers remember the third version for years, and the first version is quietly what earns the follow-up meeting where these things actually move.

Opening the meeting: what do you actually say first?

Why it's asked: The first thirty seconds set the register for everything after. The opening has three jobs: name the purpose plainly (no ambush, no apology), anchor to the work rather than to feelings, and put a specific figure or band on the table so the conversation has something to converge on. Vague asks get vague answers; the worked version below is specific without being sharp.

Model answerBooked one-to-one, senior support engineer, software firm

Thanks for making the time — and as I said in the invite, I want to talk about my pay, so let me lay it out properly rather than edge up to it.

When my salary was set in January, the role was second-line support. Since April I've been running the escalations rota, I own the two enterprise accounts' technical relationships since Dana left, and I shipped the diagnostics runbook that cut our average resolution from five days to two. That's a different job, and I'm asking for it to be priced as one.

Specifically: I'm asking for £52,000. That sits mid-band for product-adjacent support roles at our scale — I've used the salary survey the team already subscribes to, and I'll leave you the comparison.

I know this isn't a decision you can make in the room, and I'm not asking you to. What I'm asking today is whether you'll back the case — and if you will, what you need from me to make it travel.

'There's genuinely no budget for rises this year.'

Why it's asked: The commonest deflection, and often true at the level your manager controls — which is exactly why the response moves the conversation to the levels they don't. Budgets are annual, exceptions exist, and several things that change your pay are not called 'a rise': regrades, band moves, role re-evaluations, and the next planning round all live in different drawers. The reply below opens the drawers without calling anyone's bluff.

Model answerMid-year conversation, procurement officer, county council

I believe you on this year's envelope — so let me ask about the mechanisms that sit outside it.

First: regrading. My JD still describes the role before the contracts consolidation; I'm now running frameworks the old grade never touched. Is a job re-evaluation the right route here, and will you sponsor it? That's not a budget ask — it's the role being described accurately.

Second: the next cycle. Budget-setting starts in the autumn. I'd like my case in the pot before it closes rather than after — can we agree that this paper goes in, with your support, by October?

Third, and smallest: if pay truly can't move twelve months, what can? The professional qualification funding, the leadership course cohort — those change what I'm worth in the next conversation, wherever it happens.

And can we put a date on revisiting this properly — not 'later', a month? I'd rather leave today with a route than with a sympathy.

'You're already at the top of the band for this role.'

Why it's asked: Different from 'no budget' — this one says the container is full, and arguing harder inside the container wastes the meeting. The honest responses split by whether the container is right: if the role has genuinely outgrown its band, the ask becomes a regrade or a promotion case; if it hasn't, the ask becomes what would have to be true — and the reply below does the split out loud, which managers respect.

Model answerAnnual conversation, deputy ward manager, private hospital group

That's useful, because it changes what I should be asking for.

If I'm at the top of the band, then the question isn't 'more inside this band' — it's whether I'm still doing this band's job. Since the restructure I've been carrying the rota, the agency-spend sign-off, and the audit prep, three things the band above lists in its role profile. So the real ask is: will you support a banding review, and if the answer is that the extra duties shouldn't sit with me, I'd genuinely rather know that too — either the pay matches the role or the role matches the pay.

If the review isn't something you'd back yet, tell me what's missing. Give me the two things that, done over the next six months, would make it an easy yes — and let's write them down with a date attached.

What I want to avoid is the quiet version of this: top of band, scope creeping up yearly, and the conversation never happening again. This one's on the record either way.

'Now isn't a good time — can we pick this up after the restructure / the busy season / Q4?'

Why it's asked: Sometimes genuine, sometimes a soft shelf where asks go to be forgotten. You cannot tell which from the words — you tell from what happens when you attach a date. The reply agrees to the delay warmly and converts it into a commitment with a diary entry, a scope, and a named owner, which costs a genuine 'later' nothing and quietly dissolves a fake one.

Model answerCorridor-deferred ask, shift supervisor, food manufacturing

Completely fair — the audit fortnight is the wrong moment to price anything, and I'd rather have this conversation when you can give it attention.

So let's make 'after' real: can we book forty-five minutes in the week of the ninth, with pay as the named agenda, and I'll send you the one-pager the Friday before — what's changed in the role, the figures from the line I run, and the band comparison.

One thing I'd ask in the meantime: if any part of this needs someone above you warmed up before that meeting — HR, your ops manager — could that start now rather than after? I've watched asks like this lose a quarter to sequencing, and the busy season is exactly when the next year's budgets quietly get set.

And so there's no ambiguity I'm parking the ask, not withdrawing it. If the ninth moves, I'll rebook it — cheerfully, but I will rebook it.

'What figure are you actually asking for?'

Why it's asked: If you hear this question, the meeting is going well — and it deserves a number, not a shrug. Give one figure with its basis (band data, a survey the organisation respects, the role's market price), not a range that negotiates against itself. 'Whatever you think is fair' hands your pay decision to the person with the least incentive to inflate it, while sounding humble doing it.

'Aren't you just comparing yourself to what Jamie earns?'

Why it's asked: The colleague-comparison reframe, and a trap worth refusing even when a comparison started your thinking. Individual comparisons drag the meeting into personalities and confidentiality; market comparisons keep it about the role. The strong move: 'this isn't about anyone's payslip — it's about what this work costs to replace', then back to your evidence. If pay transparency is genuinely broken where you work, that is a different conversation, raised differently.

'If we do this for you, everyone will want one.'

Why it's asked: The floodgates deflection — notable because it concedes your case ('this is affordable and others may deserve it too') while refusing it. The reply stays on your file: 'you're not being asked to reprice the team — you're being asked whether THIS role, with THIS scope change, is priced right.' Said without heat, it returns the conversation to the only question your manager can actually answer.

'Would you leave if the answer is no?'

Why it's asked: Occasionally asked straight out, more often floating unasked in the room. Never bluff — a called bluff costs the credibility everything else runs on. If you would look elsewhere, the honest version is calm and unthreatening: 'I'd rather build this here, and I also keep an eye on what my work is worth — both things are true.' If you wouldn't, don't pretend otherwise; the case has to stand on the work, not on a hostage.

What goes in the one-page case you leave behind?

Why it's asked: The meeting persuades your manager; the paper persuades everyone your manager forwards it to. One page: the role as priced then versus the role as done now (three scope lines with dates), two results with figures that are verifiably yours, the market anchor with its source named, and the ask as one figure. No adjectives, nothing you'd wince at being read aloud in a calibration meeting — because that is exactly where it will be read.

The answer is a final no. What's the professional close?

Why it's asked: A no held after a fair hearing still pays you twice if you close it well: ask what would have to be true for a yes and get it written down with a review date, and thank the manager for backing the process even where the answer disappointed. Then decide in private what the no tells you about the next year — a no with criteria and a date is a route; a no with a shrug is information of a different kind.

FAQ

When is the best time to ask for a pay rise?: Three windows work reliably: just after a delivered, visible result; in the weeks before the organisation's budget or pay-review cycle sets (autumn in much of the UK public sector, before year-end in many firms); and at a genuine change of scope, when the role you do stops matching the role you're paid for. The worst times are during a crisis, straight after an error, and in a corridor.
How much should I ask for?: Anchor to evidence rather than appetite: where you sit in your organisation's band, what comparable roles pay in your market and region — the ONS earnings data and any salary survey your employer already uses are hard-to-dismiss sources — and what has changed in your scope. Ask for one specific figure you can defend, not a range, and put the basis beside it in writing.
Should I mention my cost of living or personal circumstances?: As the basis of the case, no — pay is priced against the value and market rate of the work, and a need-based case invites sympathy rather than a decision, which is the polite version of no. Organisation-wide cost pressures belong to organisation-wide processes like annual uplifts and any union negotiation, and your individual case is strongest kept separate from them.
What if my manager agrees I deserve more but says their hands are tied?: Treat it as an alliance, not a refusal: a manager who agrees on merit is a sponsor looking for a mechanism. Ask which mechanism fits — an exception case, a regrade or job re-evaluation, the next review cycle — who decides, and what paper they need from you. Then supply the paper and a follow-up date. 'Hands tied' plus a route and a date is progress; 'hands tied' with neither is your answer.
Is it risky to ask — will it be held against me?: A professionally made, well-timed, evidence-based ask is ordinary management business, and handling one well is literally your manager's job. What creates risk is the delivery, not the request: ultimatums you don't mean, colleague comparisons, or relitigating the answer weekly. If a calm, well-made case is genuinely met with hostility, that tells you something about the organisation worth knowing early.