Pay decisions run in a sequence: a pool is set, split across the business, allocated to individuals, then approved and communicated. Once the split has happened, moving your number means taking it from somebody else, which is why late asks fail. The request that works lands before allocation, and the conversation that makes it work happens a cycle earlier still.
The decision is made before the meeting
Merit budgets are allocated in a planning cycle, then distributed in a meeting where managers argue for their people. By the time you sit down for a review, the number usually exists.
Which means the conversation that matters happens weeks or months earlier, and the useful question is not when to ask but when to give your manager what they need.
When to actually raise it
Six to eight weeks before your organization’s review cycle, so it lands while budgets are being planned rather than after they are fixed.
Ask your manager directly when the cycle runs and when decisions are made. Most will tell you, and knowing it is worth more than any phrasing you could choose.
What to give them
A short written record of what you delivered, with numbers where they exist. That is not for you — it is what they carry into a room you are not in, and a manager arguing from specifics does better than one arguing from impressions.
Keep it to a page. Anything longer will not be read by the people who decide, and the manager will end up summarizing it anyway.
The moments that genuinely help
Just after finishing something visible and successful. When your scope has actually grown — new responsibilities, a bigger team, an area you now own. When a market adjustment is justified by published data.
Each gives the decision a reason attached to a moment, which is easier to act on than a general request at an arbitrary time.
The moments that do not
Immediately after the budget has been set, when there is nothing left to allocate. During a hiring freeze or layoffs, when the answer is structurally no.
Also immediately after a visible failure, and in the same conversation as a complaint about workload — which turns a pay discussion into a grievance discussion.
Off-cycle requests, and when they work
They are possible and they need a reason the annual cycle cannot wait for: a genuine change in scope, a documented market gap, or a competing offer.
Without one of those, an off-cycle request is usually deferred to the cycle anyway, which spends your ask without gaining timing.
The follow-up that does the work
If the answer is no or not yet, ask what would change it and by when. A defined review with written criteria converts an indefinite wait into a date and a standard.
Then diarize it. The most common failure after a deferred raise is that nobody returns to it, and the person with the most reason to remember is you.
The longer game
Ask early in the year what would justify a strong increase at the next cycle, then spend the year doing it and keeping a record. That converts the review from a negotiation into a confirmation.
It also makes the manager’s job easy, which is the thing that actually produces movement in a process where somebody else is doing the arguing.
Find out when the cycle actually runs
Organizations differ enormously — calendar year, fiscal year, or anniversary-based increases tied to your own start date. The last one means your timing is personal rather than organizational.
Ask HR or your manager directly. It is an administrative question with a factual answer, and getting it wrong means arriving after every decision has been made.
The conversation to have first
Before asking for anything, ask what a strong increase would require. That is a low-stakes question, it signals intent without making a demand, and the answer gives you criteria to work against for the rest of the year.
It also tells you whether the constraint is performance or structure. If the honest answer is that the band has no room, no amount of timing helps and the real conversation is about level.
Common questions
When should I ask?
Before allocation, which is usually a quarter or more ahead of when letters go out. Ask when the decisions are made and work back from that.
Why is the answer always 'not this cycle'?
Because after the split, raising your number means lowering someone else's. It is often a genuine constraint rather than a way of saying no.
Does the review meeting matter at all?
For the rating, yes, and the rating drives the allocation. For the number itself it is usually too late.
Can I get a raise outside the annual cycle?
Yes, through retention adjustments, market corrections and reclassifications. They need a trigger and an extra approval, so they are slower and rarer.
How do I find out the cycle?
Ask when increases take effect and when decisions are made. Both are ordinary factual questions and asking them commits you to nothing.
When should I ask for a raise?
Six to eight weeks before your organization's review cycle, so it lands while budgets are being planned rather than after they are fixed.
What should I give my manager?
A one-page written record of what you delivered, with numbers. It is what they carry into a room you are not in.
What if the answer is not yet?
Ask what would change it and by when, get written criteria, and diarize it. The usual failure is that nobody returns to a deferred raise.