How to ask for a promotion with evidence, not just confidence

Why "I deserve it" doesn't work

Your manager agrees you're good. That's not the bottleneck. The bottleneck is that they need to convince people who have never worked with you, in a meeting where they're also advocating for other people on their team.

1. 01

   You make the case

   This is the easy part. Your manager sees your work daily. They're probably already on your side. But being on your side and being able to articulate your case are different things.

2. 02

   Manager retells it

   Now your work is being described secondhand. Your manager needs specific examples, numbers, and scope to make this work. Without them, they're stuck with "she's been doing a great job," which sounds like every other pitch in the room.

3. 03

   Committee compares it

   People in this room have a budget and a list of candidates. They're comparing across teams. The candidates with concrete evidence win. The ones described in generalities get pushed to next cycle.

Feelings get filtered out at every step. Specifics survive.

The three things a promotion case needs

Not five. Not ten. Three.

1. 01

   Scope increase

   Evidence that you're already operating at the next level, not just doing your current job well. If you were managing 2 projects a year ago and now you're managing 5 across two teams, that's scope increase. If you were an individual contributor and now junior engineers come to you for technical decisions, that's scope increase. The question is: has the boundary of your role expanded?

2. 02

   Measurable impact

   Numbers. Revenue influenced, costs reduced, time saved, people managed, projects delivered. If your role doesn't have obvious revenue metrics, there are still numbers. Deployment frequency, bug reduction rates, customer satisfaction scores, hours saved per sprint. See how to quantify achievements when you don't have numbers for roles where metrics aren't obvious.
3. 03

   Repeatability

   One big win could be luck. A pattern of impact over 6-12 months shows it's you, not the situation. This is where a timeline of achievements matters. A string of wins across multiple quarters is more convincing than a single hero moment, because it demonstrates consistency.

Scope: then vs now

The most persuasive part of a promotion case is often the simplest. Show what your role looked like 12 months ago next to what it looks like now.

If the gap between the two columns is large, you have a scope argument. If they look the same, you may be doing your current job very well, which is worth recognizing, but it's a different conversation than a promotion.

Building the one-page case

Your promotion case should fit on one page. Not because anyone will literally print it, but because the constraint forces you to prioritize. Here's the structure:

Notice: the achievements are specific, numbered, and tied to outcomes. The next-level plan shows forward thinking, not just a request for a title bump.

The conversation itself

The document does the heavy lifting. The conversation is you walking your manager through it.

Don't open with "I want a promotion." Open with the document. Share it a few days before the meeting so your manager has time to read it and think. In the meeting, walk through the highlights. Then ask:

"What would need to be true for this to happen in the next cycle?"

That question is better than "I want a promotion" for a specific reason: it turns your manager into an ally. Instead of responding to a request (which puts them on the spot), they're telling you what's missing. Maybe nothing is missing and the answer is "I'll push for it." Maybe they tell you the one thing the committee will ask about. Either way, you're working together instead of negotiating.

The documentation shortcut

If you've been keeping a career journal or tracking achievements throughout the year, the promotion document writes itself. You're selecting from existing entries, sorting by impact, and formatting. That's a 30-minute exercise.

The difference between "I improved the process" and "I reduced report generation from 3 days to 4 hours, and the CFO now uses the output in board presentations" is the difference between a case that gets deferred and one that gets approved.

Build the case first. The confidence follows.