How to Get Promoted: Build the Case Before You Ask

A professional building the case for a promotion

To get promoted, you have to do three things in order: do the next job before it is officially yours, make the case visible in writing, and ask at the moment the decision is actually being made. Most people do none of the three. They work hard, wait to be noticed, and raise it at the annual review - which is the one meeting where the budget is already spent and the list is already written.

You have been doing the work. You covered for the person who left, you took the project nobody wanted, you are the one who actually knows how the system works. And the promotion went to someone whose work you would not trade for. That is not a sign you are bad at your job. It is a sign that promotion is not a reward for the work you have done - it is a bet on the work someone believes you can do next, and that bet gets made in rooms you are not in.

Why good work is not the reason people get promoted

If effort were the currency, the hardest worker on every team would be the manager. It is not, and anyone who has watched a promotion cycle knows it. The decision is made by a person who has to defend it to someone else, and that person is answering a different question than you are. You are asking, "have I earned this?" They are asking, "if I put this name forward, what happens if it goes wrong?" A promotion is a small act of risk-taking by your manager, and your job is to make that risk feel small.

The reframe: you are not asking for a reward, you are reducing someone's risk

That one shift changes how you prepare for everything. A reward is argued with feelings and tenure - "I have been here three years and I have never missed a deadline." A risk decision is argued with evidence and precedent - "here are four things I have already delivered at the next level, here is what the team gets if you formalise it, and here is what is at risk if you do not." The second argument is the one that gets approved, because it is the one your manager can repeat upstairs without having to defend you personally.

Step 1: Find out what the next level actually is

You cannot hit a target you have not seen. Most people carry a vague picture of the next role - more money, more respect, a better title - and no idea what the job actually requires on a Tuesday. Before you do anything else, get specific.

Read the real description for the level above you. Not the version in your head - the internal posting or the job description. The responsibilities listed there are the syllabus.
Ask your manager one direct question: "What would I need to be doing consistently for a promotion to be an easy decision for you?" Write the answer down word for word. That sentence is your brief.
Find someone promoted in the last year and ask what changed in their work in the six months before it happened. The pattern is usually the same: they started owning something that used to be escalated.
Check the calendar. When does your company set budgets and make leveling decisions? If the cycle closes in March, a conversation in April is a conversation about next year.

Step 2: Do the next job before it is yours

Promotion is a formalisation of something that is already true. The people who get promoted are rarely the ones who were promised it and then delivered - they are the ones already operating a level up, so the title is just paperwork catching up. That means the work starts months before the ask.

Take one thing off your manager's plate permanently. Not a task you help with - a responsibility you own end to end, including the reporting.
Own an outcome, not a task list. "I ran the campaign" is a task. "I ran the campaign and reply rates moved from here to there" is an outcome.
Be visible in the rooms where the next level lives. Present your own work, write the summary, answer the question in the meeting. If your manager is always the one explaining your work, you are invisible by design.
Bring a solution with the problem. Anyone can escalate. The person who escalates with two options and a recommendation is already doing the next job.

Step 3: Build the case file

This is the part almost everyone skips, and it is the part that decides the outcome. A case file is one page - not a brag sheet, a decision document. It exists so that when your manager walks into the room where promotions are decided, they are carrying your evidence instead of their memory.

Section	What goes in it	Why it works
The scope shift	Two or three things you now own that were not in your original remit.	Shows the job has already changed, so the title is catching up rather than getting ahead.
The results	Each item with a number, a before and an after, and the date.	Turns "I work hard" into a claim someone else can verify.
The next-level proof	One project where you did the work of the level above - led it, decided it, or fixed it.	Answers the only question that matters: can they already do the job?
The cost of waiting	What is at risk if the level stays where it is - a stalled team, a gap you are covering informally.	Gives your manager a reason to act this cycle rather than next.

Step 4: Make your manager's job easy

Your manager is not the obstacle; they are the person who has to sell this upstairs. The more of that work you do for them, the more likely the answer is yes.

Write the summary they will read out. Three sentences they can repeat without editing.
Name the timing. "I would like this considered in the March cycle" is easier to act on than "I would like to grow here."
Ask what would have to be true. If the answer is no, you want the conditions, not the verdict. "What would need to be different by June?" turns a closed door into a checklist.
Never make it a threat. Ultimatums force a defensive decision. Evidence forces a considered one.

Step 5: Time the ask to the calendar, not to your frustration

The worst time to ask is the moment you are fed up, and the second worst is the annual review, when the money is already allocated. The best time is four to eight weeks before the decision cycle closes, in a normal one-to-one, with the case file already sent. Ask early enough that saying yes is still possible, and late enough that your evidence is current.

The ask: a script that does not sound like a demand

Keep it short, factual and forward-looking. Four sentences is enough.

"I want to talk about the next level, and I have brought the case for it."
"Over the last six months I have taken on [scope], delivered [result], and led [project] - which is the work in the [next level] description."
"I would like to be considered in the [month] cycle. What would you need from me between now and then to make that an easy yes?"
"If the timing is wrong, tell me what has to be true and I will work to it."

The one-page case file worksheet

Fill this in before you ask. One page, four rows - it is a decision document, not a brag sheet.

Row	What goes in it	The test it has to pass
Scope shift	Two or three things you now own that were not in your original remit.	Has the job already changed, or are you asking for a title you have not grown into?
Results	Each item with a number, a before and an after, and the date.	Could someone else verify it without taking your word for it?
Next-level proof	One project where you led, decided or fixed something at the level above.	Does it answer the only question that matters - can you already do the job?
Cost of waiting	What is at risk if the level stays where it is.	Does it give your manager a reason to act this cycle rather than next?

What good looks like

You can name the next level's responsibilities without looking them up.
You have asked your manager what an easy yes would require, and written the answer down.
You own at least one responsibility end to end, including the reporting.
Your case file is one page and every result has a number and a date.
You know when the budget and leveling cycle closes.
The ask is scheduled four to eight weeks before that date, not at the review.
You have a written answer for what happens if the answer is not yet.

Where people get stuck

Stuck because you do not know what the next level requires. Read the real description for the level above you and ask your manager one direct question: what would I need to be doing consistently for this to be an easy decision? That sentence is your brief.

Stuck because your work is invisible. Visibility is a habit, not a personality trait. Present your own work, write the summary, answer the question in the meeting. If your manager is always the one explaining what you did, the room never sees you.

Stuck because the answer was not yet. Ask for the conditions in writing and a date to review them, then do exactly those things. A no with conditions is a plan; the same no twice with no change is information about the company.

Common mistakes

Waiting to be noticed. Visibility is not a personality trait; it is the habit of presenting your own work.
Asking at the review. The decision was made weeks earlier, in a budget meeting you were not in.
Arguing with tenure. "I have been here three years" is a fact about you, not a reason for them.
Listing tasks instead of outcomes. Nobody promotes a to-do list.
Making it emotional. Frustration reads as a risk signal, which is the opposite of what you need.
Going around your manager. If they are surprised, they will be defensive - and you need them as an ally.
Stopping after one no. A no with conditions is a plan; a no without one is information about the company.

What to do if the answer is not yet

A "not yet" is the most useful answer you can get, as long as you convert it into specifics. Ask for the conditions in writing, agree a date to review them, and then do exactly those things. If you get the same "not yet" twice with no change in the conditions, you have your answer about the company - and that is when the career plan and the search become the better use of your energy.

The ninety-day version

If you want a starting point: this week, get the next-level description and ask your manager the one question. This month, take one responsibility off their plate and start the case file. Next month, add two results with numbers and send the one-pager before the cycle closes. Ninety days is enough to change the conversation from "someday" to "this cycle" - and if it does not, you will know that too.

Where this fits

If the direction is still unclear, How to Make a Career Plan turns "I feel stuck" into one page with a review date. If the promotion conversation turns into a compensation conversation, the Salary Negotiation Roadmap walks from the first number to a signed offer. And if you decide the next level is somewhere else, the Resume Value Proposition Worksheet is where the case file becomes a resume.

The promotion you want is not a reward waiting at the end of good work. It is a decision someone else makes about risk, and you can lower that risk on purpose - with scope, with evidence, and with a well-timed ask. Build the case first. The ask is the easy part.

Quick answers

Short answers to the questions this piece gets asked most.

How do I get promoted?
Do the next job before it is officially yours, make the case in writing, and ask four to eight weeks before the decision cycle closes. Promotion is a risk decision your manager has to defend upstairs, so evidence beats effort: scope you have taken on, results with numbers, and one project where you already did the work of the level above.

Why do I keep getting passed over?
Usually because the decision is made in a room you are not in, weeks before the review. If your manager is the only person who can explain your work, you are invisible by design. Present your own work, own an outcome rather than a task list, and send a one-page case file before the cycle closes.

How do I ask for a promotion without sounding demanding?
Keep it to four sentences: name the next level, give the evidence, ask to be considered in a specific cycle, and ask what would need to be true. "What would you need from me between now and then to make that an easy yes?" turns the conversation into a plan instead of a verdict.

What if my manager says not yet?
Convert it into specifics. Ask for the conditions in writing, agree a date to review them, and do exactly those things. A no with conditions is a plan; the same no twice with no change in the conditions is information about the company - and that is when the career plan and the search become the better use of your energy.

Read next:I Spent 10 Years in the Wrong Career. Here's How I Fixed It — A first-hand method for figuring out what you actually want to do next.They Offered You More Money to Stay. What Happens Next? — What really happens after you accept a counteroffer, and how to decide.The Experience Paradox Is a Lie. Here's How to Break In — How to break in without years of experience, and what entry level really means.

LaunchPath Careers tool: want to build this with structure instead of guesswork? LaunchPath Careers has a Getting Promoted Roadmap and a Career Planning Roadmap. Start at LaunchPathCareers.com.

LaunchPath Careers by UFO Chaser® helps job seekers build a strategy-first job search. Learn more at LaunchPathCareers.com.

Search This Blog

Cosmo's Career Strategy Blog