Asking for a Raise: When to Do It, and When Not To

There is an enormous amount written about the best month to ask for a raise. Almost none of it is usable, for one reason: it reasons about a generic calendar, while the decision is made inside a specific one — your company's, your department's, your budget line's.

What follows gives you no month. It gives three conditions to check, a list of genuinely bad windows, and a method for reading, in your own correspondence, the point at which this conversation has the best chance of landing.

In the article that follows, I explore how a pay conversation is prepared and the pressure that comes with it. If you recognise yourself in this theme, the tests on the platform help you take stock.

The calendar is not the moment

A pay request is not an isolated event. It is the visible point of a process that started long before, and most of that process is already settled by the time you walk into the room.

Three things decide it: what you can demonstrate, what the organisation can decide at that instant, and what your counterpart can commit to alone. The month of the year affects none of them directly. It is a crude proxy for the second.

That is why two people asking for the same thing on the same day, in the same company, get different answers. One asked at the right moment of their own file; the other asked at the right moment of somebody else's calendar.

Condition 1: a record of facts you can produce

This is the most neglected condition, and the only one entirely within your control.

What happens: most requests rest on a general impression — "I do more than I used to", "I've been here three years". An impression cannot be discussed, cannot be checked, and enters no arbitration. What it changes: a dated record does enter the arbitration, because it can be handed over. The scope taken on in March. The account picked up in June after someone left. The new stakeholder assigned in September. The onboarding you have been running for new joiners since November. Each of those exists somewhere in your written exchanges, with a date attached.

That is exactly what ScanMyJob puts in sequence: the observable margins inside your correspondence — who proposed what, when, what was accepted, what was left open. The output is not a line to recite; it is a dated record of facts, each line of which you verify yourself. The gallery of examples shows four real cases with their record, which lets you see what a file looks like before building one.

The simple test: if you cannot produce six dated facts in ten minutes, the request is early — not in the year, but in your preparation.

Condition 2: the budget cycle

This is the constraint nobody explains, and it accounts for half of all refusals.

In most organisations, salary envelopes are settled on a date, and the decision concerning you is taken before the meeting where it will be announced to you. A request made after that arbitration meets an answer that has nothing to do with your value: it is an envelope already allocated.

How to find out: ask directly, outside any request context, several months ahead. "When in the year are pay decisions arbitrated here?" is not an awkward question; it is an organisational one, and it is almost always received as such. What it changes: if the arbitration happens in November for a March effective date, the useful conversation takes place in September or October. In February you are no longer negotiating — you are asking for an exception.

Condition 3: a counterpart who has the margin

The third condition is the easiest to check and the most often skipped.

Some managers decide, some propose, some merely relay. Talking to someone who relays is not a mistake — but the conversation changes nature. It no longer targets a decision; it aims to build an advocate who will carry your file into a room you won't be in.

That is prepared differently. What you supply is not an oral argument but reusable material: short, dated facts they can lift straight into a meeting. Writing becomes central, which is the subject of a separate article.

The genuinely unfavourable windows

Some moments are bad for verifiable reasons, not superstitious ones.

The last case deserves a note. Absorbing a departed colleague's work is the most common trigger for a request — and one of the worst-timed, because the organisation is in savings mode, not spending mode. The fact itself is excellent; it is used later, once the handover is stable and documented.

Why "at the annual review" is usually too late

The annual review is presented everywhere as the natural moment. It is natural for the employer, rarely for you.

What happens: in many organisations the review exists to deliver a decision prepared upstream, from material your manager submitted weeks earlier. Arriving that day with fresh arguments means arriving after the meeting where they would have counted. What it changes: the useful conversation happens two to three months earlier, and it isn't called a pay request. It sounds like: "I'd like us to look together at how my scope has changed over the year, so it's clear before the arbitration." You ask for nothing yet; you place the file in the mind of the person who will prepare the decision.

This is a direct application of what Fisher and Ury, in the Harvard negotiation method, call separating the people from the problem: you are not arguing over a number, you are building a shared description of the situation. The number comes afterwards, into a frame that is already favourable.

What your last twelve months of correspondence reveal

This is what separates serious preparation from intuition.

Your work messages contain, without your ever having noticed, a complete chronology: the moments something was handed to you, the commitment phrases ("we'll revisit this at year end", "this will be recognised"), the requests you made and how they were received, the periods when your counterpart replied fast and the periods when they didn't reply at all.

Three things read directly off that record:

• Open commitments. A line like "let's take another look after the summer" is a door left open, with a date on it. It beats a month picked at random.
• Windows of availability. The months when replies are slow and meetings get moved are not the months when decisions get made.
• Unnamed scope expansions. These rarely appear in an official document and almost always in an ordinary message.

Putting those in sequence gives you a factual basis for timing instead of a guess about someone's mood. That is precisely what the ScanMyJob record is for: it doesn't tell you what to say, it shows what was said and when.

If the moment isn't there

Two options, and only one is useful.

Passive waiting — "I'll see later" — lets the file dissolve. In six months, this spring's facts will no longer be datable.

Prepared waiting means doing three things now: build the record while the correspondence is still accessible; set your range before a conversation forces a number out of you (a dedicated article covers that); and ask a neutral question about the arbitration calendar. None of the three requires nerve, and together they change the starting position entirely.

That difference between waiting and preparing tracks what Bandura called self-efficacy: confidence does not produce action, repeated experience of concrete successful actions produces confidence. Building a record is a concrete action. Hoping for a good moment is not.

What this article does not do

It does not give you a date. The three conditions are checked inside your organisation, not in an article. A month that suits one sector says nothing about another. It addresses no question of law. What your employer must or must not do, the form a contractual amendment takes, obligations attached to review meetings: these are legal questions. They go to an employee representative, an official employment information service, or a lawyer — never to a blog post. It promises no outcome. A solid file at the right moment clearly improves your odds; it does not remove an organisation's real constraints. What happens after a refusal is covered separately, and a documented refusal beats a request never made: it opens a review date.