Money At Work
A raise is a budget decision that happens months before you ask
Understanding when the money is actually allocated explains why the same request succeeds in one month and fails in another.
By Zubin Mistry3 min read
The conversation is not where the decision is made
People prepare for a pay conversation as though it were the moment of decision — rehearsing arguments, assembling evidence, worrying about phrasing. The preparation is useful, but the timing is usually wrong, because by the time most managers have that conversation the answer has already been constrained by decisions made elsewhere.
Money for increases generally arrives as a pot. A budget is set at a level above your manager, expressed as a percentage of the team’s total salary cost, and your manager then divides it among their people. Once that pot is fixed and allocated, a persuasive case does not create new money. It can only move money from one colleague to another, which managers are extremely reluctant to do.
The cycle, and where you need to be in it
Most organisations run this annually, sometimes twice a year, tied to their financial calendar. The sequence tends to be the same: senior finance sets an overall increase percentage, it is distributed down through the hierarchy, managers propose allocations, those proposals are reviewed and compared against other teams, and then the outcomes are communicated.
The useful implication is that the moment to influence anything is when your manager is building their proposal, which is typically weeks or months before you hear anything. Raising the subject then means your manager can put you at the front of their list and go into the review with an argument ready. Raising it after communication has happened means asking someone to reopen a decision that has already been signed off by their own boss, which is a much larger favour.
So the single most useful question you can ask is not "can I have a raise". It is "when does the pay cycle happen here, and when do you put your recommendations in?" Almost every manager will answer that, and it converts a vague hope into a date.
What actually makes a case work
Managers are arguing for you in a room with other managers arguing for their own people, using a fixed pot. What wins there is not effort or loyalty but material that can be repeated: scope that has grown, work that is now unsupervised, responsibilities absorbed from a departing colleague, an outcome with a number attached that somebody senior already cares about.
Two arguments are notoriously weak. Personal need is one — it is sympathetic and it is not something a manager can present in a calibration meeting. Length of service is the other, since time served is already reflected in the annual increase and does not distinguish you from anyone else who also stayed.
The strongest structural argument is usually that you are being paid below where the market or the internal band would put someone doing what you now do. That reframes the request from a reward to a correction, which is a category managers find much easier to defend upward.
Promotion and pay are different processes
It is worth separating these, because they often run on different calendars with different approvers. A pay rise moves you within a band. A promotion moves you to a different band, usually requires evidence that you are already operating at the higher level, and frequently has to clear a separate approval with its own headcount implications.
Confusing them wastes a cycle. If what you actually want is a level change, the conversation to have is about what evidence would be needed and when the promotion process runs, which is a longer game and typically requires demonstrating the next level for a period before it is granted.
When the answer is no, and what it tells you
A refusal is worth interrogating, because the reasons differ enormously in what they imply. "There is no budget this cycle" is a fact about the organisation and may change. "You are at the top of your band" means the only route is a level change, and you now know that. "Your performance does not support it" is a serious statement that should have been said long before a pay conversation, and if it is the first you are hearing of it, that is a management failure worth naming calmly.
The unhelpful answer is a vague one. Push politely for specificity: what would need to be true, and by when. If nobody will tell you what would change the outcome, then the realistic conclusion is that nothing will, and the decision in front of you stops being about this raise and starts being about whether to stay.
Common questions
How much notice should I give before the cycle?
Enough that your manager can shape their proposal rather than react to yours, which in most places means a couple of months rather than a couple of weeks. If you do not know the calendar, ask; it is an ordinary administrative question and nobody treats it as a threat.
Does threatening to leave work?
Sometimes, and it changes the relationship in ways that are hard to reverse. Even when it succeeds, you have signalled that you were looking, and some managers quietly treat that as a retention problem to be solved rather than a colleague to be developed. It is a card with a real cost attached, not a free move.
Is it worth asking for a one-off payment instead?
It is often easier to grant, because bonuses usually come from a different budget and do not raise the recurring salary cost. That also makes them worth less than they look — a one-off does not compound into future increases. Take it if the alternative is nothing, but do not treat it as equivalent to a base rise.
Editor, After the First Job
Zubin covers first months, managing up, money at work and the questions readers actually send in and is happiest when a piece answers the question completely.
