Plenty of people work hard for years and stay exactly where they are, while colleagues who seem no more capable move up twice. That is not always politics. Promotions answer a different question from performance reviews: not "did this person do their job well" but "is this person already operating at the next level, and can we defend that in a room they are not in."

Once you see the question that way, the work becomes clearer. You need scope that looks like the next level, results that other people can describe, at least one senior person willing to argue for you, and a written case that survives a budget conversation. This guide covers each of those, how promotion cycles actually run, and what to do when you are blocked.

What actually gets people promoted?

Three things, in this order. First, evidence that you are already doing work at the next level, because almost no organisation promotes on potential alone. Second, visibility, meaning that people beyond your immediate manager can name what you delivered. Third, a sponsor, which is a senior person who will say your name when decisions are made and who has enough standing for that to matter.

Effort is not on the list, and neither is loyalty. Long hours and years served feel like they should count, and in a fair world they might, but promotion decisions are forward looking: they are a bet that you can hold more responsibility. A performance appraisal measures the job you have. A promotion is an argument about the job you do not have yet, and the argument has to be made with specifics your manager can repeat from memory.

Do the next job before you have the title

Start by finding out what the next level actually means in your company. Many organisations have written levels or competency frameworks, and if yours does, read the one above you carefully; if it does not, ask your manager to describe the difference between your level and the next in terms of decisions rather than tasks. The gap is usually about ownership: who decides, who is accountable when it goes wrong, and how wide the impact reaches.

Then take one piece of that scope deliberately, with your manager's agreement. Volunteer for the project nobody wants that is clearly a level up. Take over a recurring decision your manager currently makes. Start mentoring a junior colleague if the next level involves developing others. Two or three months of doing that work is worth more than a year of doing your current job flawlessly, because it turns the promotion conversation from a request into a description of what is already happening. Be honest with yourself about capacity, though, since taking extra scope while your core work slips is the fastest way to lose the argument.

Make the work visible without self-promotion

Quiet excellence is a real risk. If your manager cannot summarise your last six months in three sentences with numbers, they cannot defend your promotion, and the person deciding will hear a stronger story about someone else. Visibility is not bragging; it is making your work legible to people who were not in the room when you did it.

  • Keep a running record. One line per month: what you did, what changed, and the number attached to it. You will not remember in November what you saved in March.
  • Report outcomes, not activity. "Cut onboarding time from nine days to four" travels further than "worked on onboarding".
  • Present your own work. Take the demo, write the summary, join the review. Let people hear it from you once.
  • Give credit generously. Naming collaborators makes your account more credible, not less, and it buys goodwill you will need later.
  • Be useful to other teams. Cross-team reputation is what turns a manager's opinion into a consensus.

A short monthly note to your manager summarising progress does most of this work for you, and it has a second benefit: at review time you are handing them the material rather than relying on their recall.

How do you build the case for your promotion?

Write it down, in one page, before you have the conversation. State the level you are asking for, then list three or four pieces of evidence that you already work at that level, each with a result and a number. Add what other people would say, such as feedback from a stakeholder or a peer, and finish with what you will own next once the title matches the work.

Then have the conversation early, not at the review. Ask your manager directly: "I want to reach the next level in the next cycle. Based on this, what is missing?" That question does two useful things. It converts a vague hope into a checklist, and it makes your manager a participant rather than a judge. If the answer is a real gap, get it in writing and close it visibly. If the answer is that nothing is missing, ask what the process and timeline look like and who else needs to be convinced.

Keep pay slightly separate. A promotion and a pay rise arrive together in most companies but are decided by different constraints, one about level and one about budget, so prepare both arguments and do not let a salary discussion swallow the level discussion. The mechanics of the money conversation are covered in how to ask for a raise.

Timing: how promotion cycles really work

Most companies decide promotions in cycles, often twice a year, with budgets fixed weeks before anyone is told and cases submitted by managers ahead of a calibration meeting where levels are compared across teams. If you learn your company's dates, you learn when your case has to exist, which is usually about a month earlier than people assume.

Work back from that. Your evidence needs to be visible in the months before submission, your sponsor needs to know your case before the meeting rather than during it, and asking in the week the budget closes is asking to be told to wait. Good moments to make your intention known include just after a delivery that went well, at the start of a planning cycle, or when the team is taking on new scope and somebody has to hold it. A change of manager also resets the clock, so make sure a new manager learns your track record early rather than assuming you are simply competent at your current level.

What if you are blocked?

First work out which kind of block it is. A structural block means the level or budget does not exist right now, which is not about you. A performance block means there is a real gap, which is workable if it is specific. A relationship block means your manager will not champion you, which is the hardest and the most common. And a headcount block means the seat above you is taken and nobody is leaving.

Each has a different move. For a structural block, get a written timeline and a scope increase now, so the title follows when the budget appears. For a performance block, ask for the two things you must demonstrate and a date to review them. For a relationship block, build support beyond your manager: a sponsor elsewhere, a secondment, or an internal move, and remember that a mentor or a senior colleague from another team can vouch for you in rooms your manager does not enter. Widening who knows your work is the same skill as networking for a job, applied inside your own company.

If two cycles pass with promises and no movement, treat that as an answer. Internal transfers are often faster than promotions, and the external market usually reprices you more generously than an internal review will, so start looking without drama and compare properly using how to evaluate a job offer. Should you decide to go, leave in a way that keeps the door open, as described in quitting your job professionally, because the people you worked with are the ones who will hire you next. More guides are in the article library.