Negotiating Your Salary by Email: The Message That Opens Instead of Closing

Many people write a pay-request email because they dread the conversation. That's a poor reason, and yet it is often the right choice — for reasons that have nothing to do with nerves.

An email does three things speech does not. It puts a number where it stays legible. It produces a document your manager can circulate into a meeting you won't attend. And it gives you time to delete the sentences that would work against you.

The problem lies elsewhere: most emails of this kind are written in a way that closes the discussion before it starts, out of excessive caution.

In the article that follows, I explore how a pay request is worded in writing, and what haste or over-caution cost there. If you recognise yourself in this theme, the tests on the platform help you take stock.

What email does better than speech

It sets the anchor cleanly. A written number carries no hesitation and no embarrassed rounding-down. Tversky and Kahneman's work on anchoring shows that the first number present in a discussion durably steers the other party's estimate; in writing, that number is the one you chose with a cool head, not the one an awkward silence produced. It becomes transmissible. This is the most underrated advantage. Many managers do not decide alone: they carry your case elsewhere. A clear, short, factual email is reusable material; a spoken conversation is not. You are not only preparing your counterpart, you are preparing the meeting you won't be in. It can be reread. Twenty minutes between writing and sending is enough to remove the three phrases that weaken the message. That delay does not exist in speech. It carries a date. A written request exists on a date. If refused, that date becomes the starting point of a review — which matters a great deal for what comes next.

The four-block structure

An effective email fits in fifteen to twenty lines. Beyond that, the person who decides won't read to the end.

Block 1 — Subject and frame (2 lines). An explicit subject line, never cryptic: "My pay — request for a conversation". Then one sentence announcing the intent and proposing a frame. You ambush nobody; you ask for a meeting or a read. Block 2 — Dated facts (5 to 8 lines). This is the core, and the part almost everyone skips. No adjectives, no personal effort, no comparison with a colleague. Facts with dates: the scope taken in March, the account picked up in June, the new stakeholder assigned in September, the onboarding you have run since November. Three to five lines of that beat a page of argument. Block 3 — The request, costed (2 lines). A range, never a single figure, in an explicit unit — gross annual — because ambiguity about the unit is expensive. An uncosted request forces the other side to guess, and they will guess low. Block 4 — The opening (2 lines). A sentence showing you are looking for a solution and not a confrontation: availability to discuss, openness on the terms, acknowledgement of possible constraints. This is what Fisher and Ury call separating the people from the problem — and it is what distinguishes a request from an ultimatum.

The six phrases that close the door

Each is written out of politeness, and each costs something.

The last two deserve a note. An implicit threat sometimes works short-term and reliably damages the relationship afterwards; Pruitt and Rubin's model shows a contending posture produces less durable agreements than a problem-solving one, even when it gets the number. And "I feel I deserve" opens a discussion about your perceived value, when your strong position is the factual description of what you carry.

Dated facts are not recovered from memory

That is the practical difficulty of block 2, and where most emails weaken: you remember "taking on a lot", without being able to say what, or when.

Those elements already exist in written form, in your work correspondence. A scope expansion almost always arrives in an ordinary message — "can you pick that up", "you're their contact now", "just cover it for the moment". So do the commitments made to you: "we'll revisit at year end", "this will be recognised". Those sentences are margins left open, with a date and an author.

That is exactly what ScanMyJob measures: the observable margins in written exchanges — who proposed what, when, what was accepted, what was left open. What you take away is not a line to recite but a dated record of facts, each line of which you verify before pulling three of them into your email. The gallery of examples shows four real cases with their record, which makes the material concrete.

The difference from a downloaded template is sharp. A template gives you sentences; a record gives you your facts — the ones nobody can contest, because they come from your counterpart's own messages.

What email does worse

This has to be said as plainly, otherwise you write when you should have spoken.

It adjusts nothing in real time. In conversation, a reaction informs you and lets you move the discussion — towards the bonus, towards a review date, towards scope. An email is fixed. It cannot hear the unspoken constraint. "The envelope has been closed since November" is rarely written down. Yet it is the information that changes the whole strategy, and it surfaces in conversation. It hardens what could have stayed flexible. A written disagreement is harder to repair than a spoken one, because it remains legible and rereadable. A badly received phrase goes on existing. It may be read at the wrong moment. You control neither the mood nor the context of the reading.

The combination that works

In practice, writing and speaking are not rivals: they occupy two places in one sequence.

A short email to open, requesting a conversation and naming the subject without treating it. It avoids the ambush effect and lets the other side prepare.

The spoken conversation for the substance: that is where real constraints are voiced and trade-offs are found.

A confirmation email afterwards, short, restating what was said: the amount, the unit, the deadline, what remains open. It is the most useful of the three, and the most often skipped.

That third email is not an act of distrust. It is ordinary professional practice, and it does two jobs: it prevents misunderstandings about units or scope, and it fixes a review date when the answer is "not now". In the case of an internal move, where several people are involved, it becomes outright indispensable.

Two formal mistakes that cost a lot

Writing while heated. An email drafted on the evening of a frustration always contains one sentence too many. The rule is simple: never send on the day you write. Copying people in. Adding a senior manager or HR to a first request turns an exchange into a case file and puts your counterpart on the defensive. Copies may be justified later, possibly — never on the first message.

And a note on the channel: this kind of message belongs in work email, not in an instant-messaging thread. The medium is part of how seriously the content reads — and it makes the message easier to find again and to forward.

What this article does not do

It supplies no template to copy. That is deliberate. A generic email is spotted instantly, and it lacks what gives it force: your facts, your dates, your range. It addresses no question of law. The legal weight of written exchanges, the form a contractual amendment takes, whether an employer must answer a pay request, retention of work messages: these are legal questions, varying by country and sometimes by sector. They go to an employee representative, an official employment information service, or a lawyer. It does not guarantee a favourable answer. A well-built email clearly improves the starting position, and when it goes out matters as much as what it says. What it does guarantee is a dated trace of what was asked — and six months later, that trace is often worth more than the answer itself.