Asking for a Cost of Living Pay Rise (Without Cringing)

Your bills going up is not your employer's problem. Harsh? Maybe. But if you walk into a pay review saying "everything costs more," you've already lost the argument - because so has everyone else in the building, and the answer is still no.

The good news: there's a version of this conversation that works. It just requires reframing what you're actually asking for.

Why "cost of living" is the wrong frame

Employers don't price salaries against your rent. They price them against the market rate for your role. That's the number they're worried about - because if it drifts too far below market, you leave, and replacing you costs them more than the raise would have.

So the moment you say "I need more because things are expensive," you've moved the conversation onto personal budgeting, which is territory where your manager can feel sympathetic and still say no. Move it back to market value, and suddenly you're having a different conversation - one about whether the business is paying fairly for the work, not whether it should subsidise your mortgage.

This isn't just a rhetorical trick. It's the honest version of the conversation. Inflation erodes real pay. ONS ASHE data consistently shows that when nominal wages stagnate across a sector, real pay falls - which means the same role, same experience, same output, is worth less in real terms than it was two or three years ago. That's a legitimate business argument. "I've been here three years and my salary hasn't kept pace with the market" lands differently than "things cost more."

What you actually need before the meeting

One number. Your market percentile.

Not a figure from a salary survey someone filled in on LinkedIn. Not what your mate reckons. The official median and distribution for your role, sector and region - the kind that comes from HMRC PAYE records and ONS ASHE, which covers 140,000+ employers and isn't self-reported. If you're sitting at the 30th percentile for your role in your region, that's the conversation. If you're at the 60th, you need a different argument entirely (scope, progression, a title change - but that's another post).

Rung's Salary Analytics gives you exactly this: your pay percentile from official data, not crowdsourced guesses. Pull that before you say a word to your manager.

The structure that actually works

Keep it short. Three parts:

What the market says. "Based on ONS data for [your role] in [your region], the median is X. I'm currently below that." One sentence. Let it sit.

Why you specifically. This is where your recent wins go. Not a CV dump - one or two concrete things from the last twelve months that justify landing at or above median. A project, a number, a responsibility you've absorbed.

What you're asking for. A specific number or percentage. Vague asks get vague answers. "I'd like to get to £X, which brings me in line with the market median" is a request. "I was hoping we could look at my salary" is a wish.

If writing this up helps you think it through - or if you want to rehearse the conversation before it happens - Rung's Step tool can help you draft the case or run a practice negotiation so you're not thinking on your feet in the actual meeting.

Timing isn't everything, but it's a lot

In the UK, most companies run pay reviews in Q1 or tied to the financial year (April for many, January for others). Asking in March when budgets are already set is asking to be deferred. The real conversation happens two to three months before the review cycle closes - when there's still something to approve.

If your company doesn't have a formal cycle, that's not a reason to wait indefinitely. It's a reason to create a natural moment: after a strong project lands, after a promotion discussion, after a restructure puts new responsibilities on your plate.

One more thing worth saying plainly

A lot of people don't ask because they're worried it'll go badly. It almost never does. Managers expect this conversation. What they don't expect - and what actually moves the needle - is someone who comes in with data rather than discomfort. You're not asking for a favour. You're flagging a market gap. That's a completely reasonable thing to do, and the worst likely outcome is a "not this cycle" with a clearer picture of what would change the answer.

That's useful information too.

---

FAQ

Is "cost of living" ever a valid reason to ask for a pay rise? It's a valid context, not a standalone argument. Inflation eroding your real pay is worth mentioning as background - but the core ask should be grounded in market rate, not personal expenses. "My salary hasn't kept up with the market" is stronger than "things cost more."

How do I know if I'm actually underpaid? You need your pay percentile for your specific role and region, from official data - not salary surveys or job ads, which skew high. Rung's Salary Analytics uses ONS ASHE and HMRC PAYE records to show exactly where you sit in the distribution.

What if my manager says the company can't afford it right now? Ask what would need to change for a salary review to be possible, and get a timeline. If the answer is vague, that tells you something. If it's specific ("after Q3," "once the restructure settles"), hold them to it in writing - a follow-up email summarising the conversation is not aggressive, it's just sensible.

Should I mention what I could earn elsewhere? Only if you mean it. Dropping a competing offer you don't have, or wouldn't take, is a bad bluff in a small industry. If you do have an offer, that's genuinely useful leverage - but be prepared for them to let you go, because sometimes they do.

When is the worst time to ask for a pay rise? Mid-review cycle when budgets are locked, immediately after a difficult quarter, or in the first ten minutes of a Monday morning. Wait for a moment when things are going well and the decision-maker has headspace. It sounds obvious, but timing accounts for more than people admit.