Building a written pay case that survives escalation

The points below about written pay cases are ordered by how much difference they make, not by how often they get repeated.

Write for the second audience

The person you speak to rarely holds the budget, and the person who does will receive a summarised version of what you said. Anything that depends on tone, relationship or context is lost in that transmission, and what remains is whatever was written down.

A short document your manager can forward without rewriting is therefore doing the work in the room you will never enter. It also protects the manager, who has to justify the request against competing claims from people they also value. Making it easy to say yes on your behalf is a more useful goal than making a compelling speech.

Argue about the role, not the person

Cases built on effort, loyalty and personal circumstances ask for a favour, and favours are the first thing cut when budgets tighten. Cases built on scope, market rate and risk ask for a correction, which is a category the organisation already funds. Document what the job involves now against what it involved when the salary was set, with specific responsibilities added and removed.

Where it helps most, where the role has absorbed work from a departed colleague or a closed team, say so plainly and name the work. The question you want the reader to ask is what this post should be paid, not whether you deserve more.

Evidence that can be checked

Outcomes with figures attached are stronger than descriptions, and figures the organisation already reports are stronger still. Where you cannot quantify the result, quantify the scale: how many, how often, for whom, over what period. Written feedback from other teams, clients or senior staff carries weight precisely because you did not write it.

Put simply, avoid inventing precision you cannot support, since one unverifiable claim casts doubt across the whole document. Where a number is an estimate, label it as one and say how it was derived; that reads as rigour rather than weakness.

Benchmarks and how to cite them

Name the source of any external comparison, whether an advertised range, a published scale or a professional body survey. Compare like with like on scope, sector and location, because a benchmark that inflates your role is easily dismissed. Internal comparisons are risky, and naming a colleague's pay usually ends the conversation you were trying to have.

Where the organisation publishes its own bands, positioning within the band is a factual argument rather than an opinion. Present a range with a specific ask inside it, since a range without an ask invites the lowest possible interpretation.

Structure and length

One page is usually right: the ask, the role as it stands now, three or four pieces of evidence, and the benchmark. Put the number in the first paragraph, because a document that withholds the ask forces the reader to hunt for it. Use headings and short paragraphs, since this will be read quickly by someone with a list of similar documents.

Attach detail as an appendix rather than embedding it, so the argument stays visible and the evidence stays available. Send it after the conversation rather than before, so the meeting is a discussion and the document is the record.

Anticipate the answers

Prepare for the budget answer with a request for a date and a figure rather than a general commitment to review. Prepare for the banding answer by asking what the criteria for the next band are and which of them you do not yet meet. Prepare for the performance answer by asking for the specific gap and what evidence would close it, in writing.

In practice, each of those turns a refusal into a defined process, which is the only outcome that changes anything by itself. Record what was agreed and send a short summary afterwards, because the record you keep is the one that exists.

Everything above, in order of what to do first

1. Write for the second audience. The person you speak to rarely holds the budget, and the person who does will receive a summarised version of what you said.
2. Argue about the role, not the person. Cases built on effort, loyalty and personal circumstances ask for a favour, and favours are the first thing cut when budgets tighten.
3. Evidence that can be checked. Outcomes with figures attached are stronger than descriptions, and figures the organisation already reports are stronger still.
4. Benchmarks and how to cite them. Name the source of any external comparison, whether an advertised range, a published scale or a professional body survey.
5. Structure and length. One page is usually right: the ask, the role as it stands now, three or four pieces of evidence, and the benchmark.
6. Anticipate the answers. Prepare for the budget answer with a request for a date and a figure rather than a general commitment to review.

The takeaway

Write one page about the role, with the number in the first paragraph, and make it easy to forward.

Pick the one that costs you least, and let the rest wait.