Make a pay rise argument your manager can assess

Updated 14 October 2026 · Published by Look at you go · Editorial policy

Quick answer

To justify a pay rise, connect your contribution to a clear reason for reviewing your pay: sustained results, increased responsibility or a mismatch with comparable roles. Explain what changed, what you personally contributed and what evidence supports it. Then show why that contribution is not adequately reflected in your current salary, without overstating your impact.

Start with why your pay should change

The key to how to justify a pay rise is distinguishing good performance from a reason to change your salary. A list of completed tasks shows that you have been working. A pay rise justification explains why your contribution, responsibilities or position within the pay structure merits a review.

Start with the basis of your request, rather than a chronological tour of your year. Perhaps your role has expanded, your results now support a higher position within your pay band, or comparable roles suggest your salary needs reviewing. Different reasons need different evidence. Combining them is fine, provided each stands up on its own.

For example: “I would like my salary reviewed because I now own the supplier escalation process as an ongoing responsibility, alongside my existing role.” That gives your manager a specific claim to assess. “I have been really busy” gives them a feeling to acknowledge.

This page focuses on the reasoning behind your request. For help bringing the wider preparation together, use the [pay rise case guide](/uk/pay-rise-case).

Choose reasons for a pay rise that fit your situation

Your strongest argument should reflect what has actually changed. Do not squeeze your experience into a more impressive-sounding category. Increased workload, greater responsibility and stronger performance are related, but they are not interchangeable.

Consider which of these reasons describes your situation, then check your employer’s pay policy or ask how salary decisions are made.

Explain the link between your work and business value

A business case for a pay rise needs a bridge between what you did and why it matters. That value might be commercial, operational or service-related. Better quality, clearer decisions, safer delivery and more reliable handovers can all matter. Not every useful contribution arrives carrying a revenue chart.

For each claim, ask: what problem existed, what did I do, what changed, and why was that change important? Then add the pay link. Did the work demonstrate sustained contribution beyond the expectations used to set your salary? Did it introduce ongoing accountability? Does it support a review under your employer’s progression criteria?

For example, “I now attend supplier meetings” describes activity. “I now own supplier escalations, agree corrective actions and brief the service lead on unresolved risks” describes responsibility. The pay argument becomes clearer if that ownership is ongoing and was absent from the role on which your current salary was based.

Separate your contribution from the team’s result. If you coordinated testing while colleagues designed and built a service, say so. Accurate attribution makes your account easier to trust and gives your manager something they can repeat without quietly editing it first.

Also distinguish outcomes from intentions. Introducing a checklist is an action. Demonstrating that it prevented missed steps is an outcome. If the outcome is not yet established, describe the new process and its purpose without treating the expected benefit as a proven result.

Use CAIP to turn a claim into a credible explanation

The [CAIP Framework](/caip-framework) stands for Context, Action, Impact, Proof. It helps you explain an achievement in a way someone else can assess. For a salary discussion, follow that explanation with a separate sentence about why it supports reviewing your pay.

Illustration: an operations coordinator has taken ongoing ownership of a difficult handover between customer support and the delivery team. This is a fictional example of the reasoning, not a claim about a real employee.

Test the evidence before your manager does

Read your justification as if you were being asked to approve it. Can someone verify the claim? Does the evidence cover the period you describe? Is the result attributable to your work, or could another change explain it? Does the example demonstrate your normal contribution or an exceptional event?

Use measurements where they exist and are meaningful. Keep the reporting period, definition and comparison consistent. If you cannot establish the baseline, do not manufacture a tidy improvement figure. A modest claim supported by a reliable record is more useful than an impressive claim that dissolves under a follow-up question.

Qualitative evidence can still be specific. A stakeholder’s written confirmation, an accepted deliverable or a record of changed decision-making responsibility can support a claim. Explain what each item establishes. Praise may support the quality of your work, but it does not automatically prove financial impact or a change in role level.

Look At You Go can help you record work accomplishments through voice or text check-ins and build a private, dated record that is not shared with your employer. That record gives you material to review, but the argument still needs your judgement about relevance and attribution.

For a closer look at supporting material, see [evidence for a pay rise](/resources/pay-rise/evidence-for-a-pay-rise). Keep workplace confidentiality in mind when recording examples, and refer to sensitive records without copying restricted information.

Write the justification so someone can pass it on

Your manager may need to explain your request to someone who does not know your work. Write a short opening that states the basis for the review, followed by your strongest evidence and a clear explanation of its relevance to pay. Put supporting detail underneath rather than making the reader excavate the argument.

For example: “I am requesting a salary review because my role now includes ongoing ownership of supplier escalations. I manage corrective actions and report unresolved risks to the service lead, alongside my original duties. The updated responsibility record and recent escalation reviews show this change. I would like to discuss whether my salary reflects the current scope of the role.”

Where market pay is part of your case, explain how you selected comparable roles. Match responsibilities, seniority, location and sector as closely as possible, and distinguish base salary from the wider package. A matching job title is a starting point, not proof that the jobs are equivalent.

Keep the strength of your case separate from the organisation’s ability to act immediately. Budget, approval routes and pay-review timing may affect the decision. You can acknowledge those constraints without withdrawing the request: ask whether your manager agrees with the substance and what process would be needed to review it.

Remove weak arguments, then make the request clear

Personal costs explain why more pay matters to you, but they do not by themselves explain how your employer should value your role. Long service, effort and loyalty can provide context. They become more persuasive when connected to applied expertise, reliable contribution or responsibilities that your current pay does not reflect.

Avoid turning the case into a complaint about colleagues. Use relevant role criteria and credible comparisons instead of assumptions about someone else’s salary. Equally, do not disguise a permanently larger role as simply working harder. The underlying issue may be job level or role design as well as pay.

End with a request your manager can respond to: review my salary against these responsibilities, assess my position within the pay band, or explain what evidence is missing. If the answer is not now, ask what would need to change and agree when the discussion will be revisited.

You can use the [pay rise evidence builder](/tools/pay-rise-evidence) to organise your material before drafting. Look At You Go can also help you keep a private record of accomplishments between reviews. The aim is not a longer document. It is an argument that remains clear when someone asks, “What supports that?”

Common questions

Can I justify a pay rise without measurable financial results?
Yes. Use evidence appropriate to your work, such as accepted deliverables, improved quality, stakeholder confirmation or documented responsibility. Describe exactly what the evidence supports. Do not convert a useful contribution into estimated savings unless you have a defensible method and the information needed to calculate them.
Is doing my job well enough to justify a pay rise?
It may support a request, depending on your employer’s pay arrangements. Some salary reviews recognise sustained performance within a role; others depend on progression criteria or changed responsibilities. Connect your performance to the relevant criteria rather than assuming either that good work is sufficient or that promotion is required.
How should I justify a pay rise during probation or soon after joining?
Check what was agreed when you joined, including any review point. If the actual role differs materially from the agreed scope, document that difference. Otherwise, build evidence of sustained contribution and ask how salary reviews work. Early enthusiasm is useful, but it is not the same as established impact.
What if my manager agrees with my evidence but says there is no budget?
Ask whether they support the justification in principle and what approval or budget process applies. Request a clear point for revisiting it and record any agreed actions. Separate a timing constraint from disagreement about your contribution, so you know whether to strengthen the evidence or follow up on the process.

You did the work. Keep the evidence.

Look At You Go turns a 90-second weekly check-in into a private, dated record you can use in reviews, promotion cases and CVs.

Start keeping the evidence

Keep reading