When is the right time to ask for a promotion?

Two clocks matter: yours and the organisation's. Yours: after a run of evidence — a delivered project, absorbed responsibilities, strong review — not in the same week as a stumble. The organisation's: before pay and promotion rounds are locked, which is typically a quarter earlier than people think. Asking two months before the round is planning; asking two weeks after it closed is a year's wait.

What should I say when asking for a promotion?

Name the ambition plainly, evidence it with next-level work you are already doing, then hand the conversation over with the diagnostic question: 'what's the honest distance between me and that role?' The first meeting's goal is criteria, a sense of who decides, and a follow-up date — not a verdict. Asks that demand a yes in the room usually get the safest available no.

What if my manager says I am not ready for promotion?

Ask what the 'not' is — a capability gap, a track-record gap, or no vacancy — because each has a different fix. Convert whatever comes back into named work with a date, ask whether you'd be the backed candidate once it's done, and put the revisit in the diary yourself. A 'not yet' that survives those questions intact was probably honest; one that goes vague under them was a deferral.

Should I ask for a promotion or a pay rise first?

Decide which you actually want, because they are different conversations won with different evidence: the promotion case is about readiness for the next level's work; the pay case is about the market value of the current level's. Bundling them lets a manager answer the cheaper one and feel finished. If both are true, lead with the role — a regraded role usually brings the pay conversation with it.

Is it pushy to ask for a promotion?

Asked the way this page asks it — evidence first, questions instead of ultimatums, timelines instead of threats — it is the opposite of pushy: it is what taking your own development seriously looks like, and most managers privately wish more of their people did it. The pushy version is the demand for a verdict today. The professional version asks for a path, then walks it visibly.

Grow

Asking for a promotion: the case, the timing, the conversation

Updated 12 August 2026

Promotions are decided in conversations most people never start. The waiting strategy — do good work, be patient, assume the system notices — feels virtuous and works about as well as any plan built on being noticed. Managers are busy, promotion rounds have queues, and the colleague who named their ambition out loud eighteen months ago is standing nearer the front of yours. Asking does not gazump anyone; it enters you in a race you were assumed not to be running.

The ask itself is misunderstood in a specific way: people prepare for it as a verdict — am I good enough? — when it actually opens a process. The first conversation's realistic job is not 'yes'; it is to put your ambition on the record, extract the actual criteria the decision will use, and start a clock. Measured that way, almost every version of the conversation succeeds at something, including the ones that end in 'not yet' — provided you know what to do with a 'not yet', which is what half this page is about.

One distinction before the worked lines, because the two conversations get conflated and are won differently: this page is the role conversation — the step up in level, scope, and title. The money conversation in your current role is its own craft with its own page in this family. They overlap at the edges, but bundling them in one meeting usually weakens both: a manager who cannot move a grade this year may still be able to move your scope, and you want to be able to take that yes cleanly.

Your career — see where this workplace conversation fits in the wider loop.

What the room is weighing

Whether your case is evidence or tenure. 'I've been here three years' is a fact about time; 'I've been doing the next level's work for six months, and here are the four examples' is a case. Managers can only carry the second kind up the chain.
Whether you understand what the next level actually is. Candidates who describe the step as more of the same, but better-paid, reveal they haven't studied it — the level above usually differs in kind: broader ownership, other people's output, decisions with fewer safety nets.
How you take the first no. 'Not yet' is where the real assessment happens: pushing back with questions and a timeline reads as the seniority you are asking for; sulking, or dropping the subject forever, reads as the case against it.
Whether anyone else would say it. A promotion case that exists only in your own account is fragile; one your manager has heard echoed — from peers, other teams, the stakeholders you serve — is the kind that survives a calibration meeting where you are not in the room.

Opening the conversation — asking to be considered without demanding a verdict.

Why it's asked: The opener sets the register for everything after it, and the common failures are opposites: so tentative the ambition is deniable, or framed as an ultimatum the manager can only lose. The strong version names the ambition plainly, asks for a path rather than a promotion, and gives the manager a role that is easy to accept: adviser, not judge.

Model answerRequested one-to-one, senior support analyst, software company

"I asked for this half-hour because I want to talk about my next step, and I'd rather do it deliberately than drop hints and hope.

The short version: I want to be a team lead here, and I'd like your help getting there. I'm not asking you to promote me in this meeting — I know it doesn't work like that, and there may not even be a vacancy yet. What I'm asking is that from today, my name is in your head when that conversation happens above you.

Why I think it's a serious ask rather than a hopeful one: for the last six months I've run the escalations rota, which means I'm already doing the triage half of the lead job — and the two new starters both came to me as their unofficial mentor, which is the other half. The September outage, I ran the customer side of, and you saw how that went.

So my actual question is this: from where you sit, what's the honest distance between me and that role? What would you need to see that you haven't seen yet?"

The closing question is the whole design — it converts the meeting from a verdict you might lose into a diagnosis you can act on, and it makes the manager the author of your criteria, which matters enormously eighteen months later.

'What would it take?' — turning warm noises into criteria you can actually meet.

Why it's asked: The most consequential moment in the whole process, and the one most often left vague. 'Keep doing what you're doing' and 'more visibility' are not criteria — they are the sound of a manager who hasn't had to think about it yet. Your job is to leave with specifics: capabilities, evidence, and who else has a vote.

Model answerSame meeting continued, senior support analyst, software company

"That's helpful — can I push on it a bit, because 'more leadership presence' is the kind of thing I'll fail to aim at precisely.

When you picture someone unambiguously ready for the lead role, what are they doing that I'm not doing yet? Is it running projects with other teams' people in them? Handling the vendor relationships? Something about how I show up in the planning meetings?

[The manager names two or three real things.]

Right — so if I take the incident-review overhaul and run it end to end this quarter, with the network team involved, that's the cross-team evidence. And I'll take over the Fenwick vendor calls from next month if you'll hand them to me. On the planning meetings: fair, I do sit quiet in those. That one's just mine to fix.

Two more questions and I'll let this go. Who else has a voice in this decision when it happens — is it yours, or yours plus Rachel's? And can we make this a standing item — ten minutes, once a quarter, where you tell me honestly whether the gap is closing?

I want this to be a plan we're both watching, not a wish I mentioned once."

Notice the mechanics: every vague phrase gets converted to a namable piece of work in the same breath, and the who-else-decides question is asked out loud — because promotion cases are argued in rooms you are not in, by the person you are talking to now.

'You're not ready yet.' — the answer that decides whether the ask was worth making.

Why it's asked: Most first asks land here, so this is really the conversation you were always preparing for. 'Not yet' has three species — a genuine development gap, a diplomatic no-vacancy, and a brush-off — and they are distinguished the same way: by asking for the specifics and the date. How you receive the verdict is itself being marked.

Model answerOne-to-one, assistant category manager, supermarket head office

"Okay. I'd be lying if I said that's the answer I wanted — but I'd rather have it straight than warm, so thank you.

Help me use it, then. When you say not yet — what's the not? Is it a capability you haven't seen, a track record that needs more time, or honestly just that there's no category manager slot to promote into right now? Those are three different problems and I'd work on them differently.

[The manager: partly experience — you've not run a full range review solo — and partly headcount.]

That's genuinely useful, because both halves have answers. The range review: the autumn cycle starts in eight weeks — I'd like to run one of the smaller categories solo, with you as backstop rather than lead. That converts 'hasn't done it' into 'did it' by Christmas. The headcount half I can't control — but I can ask this: if a slot opens next year and the range review has gone well, am I the internal candidate you'd back? Not a promise — just, is that the honest shape of it?

And can we put a date on revisiting this properly — say, first week of February, after the review lands? I'll put it in the diary so it's my job to raise, not yours to remember."

The close is the craft: a named piece of evidence, a named date, and the revisit made your responsibility — which is what stops 'not yet' quietly becoming 'never' by nobody's particular decision.

'There's no vacancy at that level.' — the honest constraint, and what still moves.

Why it's asked: Often perfectly true, and not the end of the conversation people assume. Structure moves slower than scope: a manager with no slot to give can usually still give the next level's work — ownership of a project, deputising in their absence, a stretch assignment with your name on it. The reply that works accepts the constraint and asks for exactly that, because when a slot does open, the argument 'already doing the job' beats every other candidate's 'ready to learn it' — and if the structure never moves, a scope-grown CV is also what the external market pays for.

The already-doing-the-job case — when the step up happened and the title didn't.

Why it's asked: The strongest promotion case there is, and the one that most needs saying out loud — absorbed responsibilities feel obvious to you and are invisible in a structure chart. The conversation names the drift precisely, kindly, and with a deadline-shaped question at the end.

Model answerOne-to-one, project coordinator, civil engineering consultancy

"I want to lay something out plainly, because I think it's become invisible through being gradual.

When Tomasz left in January, his project officer duties were split 'temporarily' — and over eight months, most of them have settled on me. I'm running the Ashford scheme's reporting solo, I chair the subcontractor calls, and the client emails me directly now rather than going through anyone. I've kept a list — it's not a grievance list, it's just accurate — and it maps almost line for line onto the project officer job description on our own intranet.

I want to be clear about my position: I'm not complaining about the work. The work is the job I want — that's rather the point. What's out of alignment is that I'm doing it at coordinator grade, with coordinator authority, which occasionally gets awkward in rooms where I'm the one accountable but not the one with the authority.

So my ask is direct: I'd like the role I'm doing to be the role I hold — title and grade regularised to match the responsibilities. What would it take to make that happen this cycle, and what's the first step you'd need from me?

And if the honest answer is that it can't be regularised — then we should talk about which parts of it go back, because the current arrangement prices the role at the wrong grade for whoever does it, not just for me."

The final paragraph is doing quiet, important work: it is not a threat — it is the logical consequence stated calmly, and it converts 'be patient' from an easy answer into an expensive one.

'Ask me again next year.' — accepting the timeline without losing it.

Why it's asked: Sometimes a real constraint (cycles, budgets, calibration rounds have dates); sometimes a soft archive where ambitions go to be forgotten. The reply distinguishes them by adding machinery: what specifically will be different by then, which criteria from q2 apply, and a named check-in before the year is up. 'Next year, meaning the April round? Then can we agree what my case needs to contain by February, and look at it together in January?' A timeline with contents and checkpoints is a plan; a timeline without them was a deferral, and the question politely finds out which one you were just given.

The sponsorship ask — getting someone senior to say your name in the room.

Why it's asked: Promotion decisions are made in rooms you are not in, which makes the person who speaks for you there more valuable than any document you submit. Sponsorship differs from mentoring — advice helps you; advocacy moves you — and it can be asked for more directly than people think, provided the ask is specific and earnable: not 'will you champion my career?', but 'the lead role in the spring round — knowing my work on X, is that a case you'd feel able to speak for? And if not yet, what would get it there?' Senior people respond to that framing because it lets them be honest, and their honest answer tells you where your case actually stands.

The nod arrives — 'apply in the next round'. What changes now?

Why it's asked: A backed internal application is a different game with different traps, chiefly complacency: internal candidates lose winnable processes by assuming the panel already knows their work. Treat the formal round as its own preparation project — the panel may include people who owe you nothing, and your manager's backing gets you into the room, not through it. The interview itself is a discipline of its own and beyond this page's scope; what belongs here is the conversation with your manager about the round: which evidence to lead with, who sits on the panel, and what the process weighs — asked exactly as directly as everything else on this page.

The answer stays no — the graceful close, and what the pattern is telling you.

Why it's asked: One 'not yet' with criteria and a date is a plan. The same conversation, annually, with moving goalposts and evidence that keeps being absorbed without consequence — that is also an answer, delivered slowly. The graceful close keeps every relationship intact ('understood — I'd rather know where I stand, and I'll keep doing the work well') while you decide privately what to do with the information. No outcome is promised by asking well; what asking well does deliver, every time, is an honest reading of where you actually stand — and that reading is worth having whichever direction it eventually points you.

FAQ

When is the right time to ask for a promotion?: Two clocks matter: yours and the organisation's. Yours: after a run of evidence — a delivered project, absorbed responsibilities, strong review — not in the same week as a stumble. The organisation's: before pay and promotion rounds are locked, which is typically a quarter earlier than people think. Asking two months before the round is planning; asking two weeks after it closed is a year's wait.
What should I say when asking for a promotion?: Name the ambition plainly, evidence it with next-level work you are already doing, then hand the conversation over with the diagnostic question: 'what's the honest distance between me and that role?' The first meeting's goal is criteria, a sense of who decides, and a follow-up date — not a verdict. Asks that demand a yes in the room usually get the safest available no.
What if my manager says I am not ready for promotion?: Ask what the 'not' is — a capability gap, a track-record gap, or no vacancy — because each has a different fix. Convert whatever comes back into named work with a date, ask whether you'd be the backed candidate once it's done, and put the revisit in the diary yourself. A 'not yet' that survives those questions intact was probably honest; one that goes vague under them was a deferral.
Should I ask for a promotion or a pay rise first?: Decide which you actually want, because they are different conversations won with different evidence: the promotion case is about readiness for the next level's work; the pay case is about the market value of the current level's. Bundling them lets a manager answer the cheaper one and feel finished. If both are true, lead with the role — a regraded role usually brings the pay conversation with it.
Is it pushy to ask for a promotion?: Asked the way this page asks it — evidence first, questions instead of ultimatums, timelines instead of threats — it is the opposite of pushy: it is what taking your own development seriously looks like, and most managers privately wish more of their people did it. The pushy version is the demand for a verdict today. The professional version asks for a path, then walks it visibly.