Negotiating Pay on an Internal Move or a Change of Role

The message lands on a Tuesday: your name has been put forward for the role. It is good news, it is deserved, and you say yes within the hour.

Three weeks later, rereading the job description, a thought settles in: the scope has doubled, the team has grown, the level of responsibility bears no relation to the old one — and the pay has not moved. When you raised money, the answer wasn't one: "we'll look at that at the next review."

This sequence is probably the most widespread of all pay situations, and the worst handled. Because it doesn't look like a negotiation. Nobody sits down opposite anybody. There is simply a run of good news, and at the end of it, a heavier job at the same price.

In the article that follows, I explore how hard it is to attach a condition when you are glad to have been thought of. If you recognise yourself in this theme, the tests on the platform help you take stock.

Why the window closes on acceptance

One principle governs the whole subject: you negotiate a situation that does not yet exist, never one already in place.

Until you accept, the company has a problem to solve — a role to fill, with an identified, validated, immediately available candidate. The day you accept, the problem is solved. What you ask for afterwards no longer solves anything: it creates new expenditure on a closed subject.

That is why "we'll look at it later" works so well. It is rarely a deliberate lie. It is a sincere way of deferring an awkward decision — but a decision deferred past your acceptance is one that carries no urgency.

There is a further asymmetry: in six months the role will no longer be "widened", it will be normal. You will no longer be asking for recognition of a change; you will be asking for an ordinary increase, under ordinary constraints — annual pot, calendar, comparison with colleagues.

What changes when you negotiate internally

An internal move is not an external hire in disguise. The balance of power differs, in both directions.

What weakens you: your BATNA — your best alternative, in Fisher and Ury's sense — is weak, and the company knows it. Turning the role down does not take you out of the company; it leaves you in the old job. No external option is visible. What strengthens you, and gets forgotten: the company holds rare information about you — it knows you can do the work — and you hold rare information about the company. You know the service's real hiring timelines, how hard the profile is to find, how loaded the role is, which deadline makes a replacement urgent. An external candidate has none of that. What decides it: the company's fallback cost. If your refusal forces a three-month external search on a hard-to-fill role, there is room. If three internal people want it, there isn't. That question is settled with facts, not impressions — and the facts are often available: how long has the role been open? Has it already been advertised externally?

Widening is documented, not narrated

Here is what separates a request that lands from one that slides off.

Saying "the job is much heavier" puts the discussion on the ground of perception, where the other person always has an answer. Showing, line by line, that six duties were added, that the team supervised goes from three to eleven, and that two further processes now sit with you, puts the discussion on ground where disagreement has to be argued.

That material already exists, in documents you hold:

• The old job description and the new one, side by side. It is the single most demonstrative document on this subject.
• The announcement email or internal posting, which describes the role in the employer's own words.
• Appraisal records, which carry objectives and commitments nobody has reread.
• Exchanges with the incoming manager, containing the lines about resources, team, sometimes pay.
• The messages that, month after month, added a file "in the meantime".

The problem isn't having these things: it's that they are scattered across years of mail, and memory does not restore them in order. That is what ScanMyJob produces: a dated record of facts, drawn from your real exchanges, putting the additions of scope in sequence with their dates. Not lines to recite — a chronology you can put on the table. The examples gallery shows four concrete cases, including a widening spread over eleven months that only became visible once the messages were back in order.

The work also pays if the answer is no: a documented chronology is still valid six months later, and becomes the basis of the next conversation.

The "we'll look at it later" trap

This is not a sentence to refuse; it is one to complete. What separates a genuine deferral from an evasion is three things, and you only have to ask for them:

A date. Not "next year": a month.

Criteria. On what basis will the decision be made, and by whom?

A written trace. An email from you summarising what was said, sent the same day.

The third is the only one that genuinely changes anything, and it is the easiest. A written summary that goes uncontradicted carries weight nothing else does in the months that follow — including when your contact has moved on, which happens constantly.

A neutral wording: "Thanks for the conversation. To make sure I've understood: we'll revisit the positioning in January, on the basis of [criteria discussed]. I'm available in the meantime." This forces nobody, embarrasses nobody, and is worth more than thirty minutes of discussion.

Internal comparison: the most fragile argument

"So-and-so does the same job and earns more." The most instinctive argument, and the riskiest.

Why it appeals: it looks objective, and it touches a real sense of fairness. Why it backfires:

• It exposes how you obtained the information, which can be a problem depending on internal norms.
• It shifts the conversation onto your colleague, whose file the other person knows and you don't.
• It installs a comparison register that, applied to other lines, will not always favour you.
• And legally, equal treatment follows precise rules that are not handled from memory.

What works better: talk about the role, not the people. Level of responsibility, market reference points for this kind of function, resources committed. You can raise internal positioning without naming anyone: "I'd like to understand how this level of responsibility is positioned in the company" is a fair question, and it sometimes gets an answer.

⚠️ If you believe the gap follows a protected characteristic — sex, age, origin, health, union activity — you are no longer in a pay negotiation but in a legal question, handled with a lawyer, a union, or the competent authority in your country. An article can do nothing for you there.

Saying yes to the role without saying yes to the terms

This is the central move, and it fits in one sentence.

The mistake is believing you must choose between accepting enthusiastically and attaching a condition. Both are said together, and that is the only formulation that protects the relationship:

"I really want this role and I want to take it. Before I confirm, I'd like us to settle the positioning, because the scope changes significantly — I'd rather we discussed it now than in six months."

Three things happen there. The commitment is explicit, so the question is not "will they come?". The condition is single. And the last clause legitimises the timing of the request, which is exactly where people feel most at fault.

In negotiation terms this is integrative framing in Pruitt and Rubin's sense: your interest and the service's point the same way — that the move happens, and happens quickly.

What this article does not do

It does not say how much to ask for. The order of magnitude depends on the occupation, the market and the real extent of the widening: that is the subject of setting a range. It settles no legal question. Changes to contract terms, variations, equal treatment, job classification: these fall under the law that applies where you are and are checked with a lawyer, an employee representative or an official source. Never an article. It does not promise the request will succeed. A move can be offered inside a genuinely closed budget. What the method guarantees is that the question was asked at the only moment it carried weight — and what to do with a refusal is a subject in itself.