Negotiation
The budget calendar decides when a rise is even possible
A well-argued case put at the wrong point in the financial year loses to a weak one put at the right point. The calendar is not a detail.
What follows is the working version of pay review timing: the decisions in the order you actually meet them, with the reasoning attached.
Before you start
- Pay pots are usually fixed months before any rise is announced.
- The decision date matters more than the date the money changes.
- Off-cycle increases exist but need a reason the system recognises.
The money is allocated long before you hear about it
Most organisations set a total pay pot during their planning cycle, months ahead of the reviews in which it is distributed. By the time a manager discusses your pay, the amount available to their team has usually already been decided and cannot be enlarged. This is why an excellent case presented during the review conversation can produce sympathy and no money at all.
The conversation that changes an outcome happens while the manager is still arguing for their team's allocation, which is considerably earlier. Asking a manager when they build their case for the following year is a simple question that reveals the whole timetable.
Finding the actual dates
The financial year end, the planning cycle and the review cycle are three different dates and only one of them is usually published. Colleagues who have been there several years will know when the awkward months are, and managers will usually tell you if asked directly.
On an ordinary week, in larger organisations the sequence typically runs from a central envelope, to divisional splits, to individual decisions, with each stage narrowing the room. Once a figure has been entered in a system and approved upward, reopening it requires an exception rather than a decision. The practical rule is to be early, because everything after the allocation stage is a redistribution rather than an increase.
Off-cycle increases and what triggers them
Most employers have a mechanism for changing pay outside the review, and most of them prefer you not to know about it. The triggers that usually work are a change in the role, a retention risk the organisation recognises, a market correction, or a demonstrable error in banding.
Where it helps most, the triggers that rarely work are personal financial need, length of service alone, and comparison with a specific colleague. Framing a request against one of the recognised triggers gives the manager a category to file it under, which is what escalation requires. Without such a category the request has nowhere to go, and it will be deferred to the next cycle by default.
Joining, promotion and the review you miss
Joining shortly before a review often means a pro-rated increase or none at all, on the basis that your salary was recently set. That can effectively delay your first increase by close to two years, which is worth discovering before you accept rather than afterwards. Asking at offer stage when the next review falls and whether new joiners are eligible costs nothing and occasionally moves the start date.
The useful part is this: the same applies after a promotion, where an uplift granted in one month may exclude you from the general award a few months later.
Where that is the practice, ask for it to be confirmed in writing, since a policy stated verbally has a way of changing.
Preparing during the year, not the week before
The evidence that supports a pay case is generated all year and remembered by nobody, including you, unless it is written down. A running note of what you delivered, what changed in scope and what would have cost the organisation had you not been there takes minutes a month. Feedback from other teams, saved when it arrives, is far more persuasive than a summary you write about yourself afterwards.
For most people, by the time the review arrives, the work is assembling a document rather than reconstructing a year from memory. The same file makes an external application substantially faster, so the effort is not wasted even if the internal answer is no.
Some of this will suit you and some will not, and that is the point.
When the timing is genuinely bad
Hiring freezes, restructures and poor trading periods are real constraints, and pushing hard during one damages the relationship without changing anything. The useful move is to secure agreement on the principle and a specific date for revisiting it, in writing.
A manager who will commit to a figure and a date is worth waiting for; one who will not is telling you something. Meanwhile the market rate for your work does not pause, and the external option remains the honest benchmark. Deciding in advance what you will do if the deferred date passes without action prevents the conversation repeating indefinitely.
The takeaway
Find out when the pot is set, and have the conversation before that date rather than after it.
The version you keep doing is the version that works.
Questions readers ask
When should I raise pay with my manager?
Before their budget is set, not during the review meeting. Ask when they build the case for their team and start the conversation ahead of that.
Do off-cycle rises exist?
In most organisations yes, but they need a recognised trigger such as a role change, a retention risk or a banding error. Personal need is rarely one.
