Writing a promotion case

The short answer

A promotion case has to survive being read by strangers.

That's the one structural difference from asking for a raise, and it changes everything about how you write it. A pay conversation happens between you and someone who knows your work. A promotion is usually decided in a room containing your manager, several managers of people you've never worked with, and somebody from HR holding a leveling framework — and your manager gets a few minutes to present you against candidates they'd also like promoted.

So the case isn't an argument that you're good. Everyone in that room is good. It's an argument that you are already operating at the next level, and the title is catching up with reality.

Which means it's built from scope and evidence, in the organization's own vocabulary, and written so that somebody who has never met you can repeat it accurately.

Promotion and pay are different arguments

They get treated as the same thing because they usually arrive together, but they answer different questions and the evidence isn't interchangeable.

The practical consequence: a promotion case is written for people who aren't in the conversation. Everything in it has to be legible secondhand.

If what you actually want is more money rather than a title, the pay case is the shorter route and the method covers it directly. If your organization attaches bands to titles — most do — then the promotion is the mechanism and this is the document.

Start from the level definition

Before you write anything about yourself, get whatever your organization uses to define levels: a career ladder, competency framework, role profiles, or the job ads it posts for the level above you.

Then read it as a checklist rather than as aspiration, and mark each line honestly as already doing this, doing part of it, or not yet.

This is dull and it is the highest-leverage hour in the process, for three reasons. It tells you whether you have a case at all this cycle. It tells you precisely where the gaps are, which is a work plan for the next six months if the answer is not yet. And it gives you the vocabulary the committee will actually use, which matters more than it should — a case written in the framework's own language is one your manager can defend without translating, and a case that needs translating usually loses something in it.

If your organization has no framework, use job ads for the next level up, at your employer and at two competitors. Same exercise.

Argue scope, not effort

The commonest failure in a promotion case is a list of accomplishments.

Accomplishments argue that you did your current job well, which is an argument for a good performance review. Promotion committees are asking something else: is this person already carrying the responsibility of the next level? Those are different claims, and a list of achievements answers the wrong one.

Scope is what you own. Effort is what you spent. Only one of them is a level.

Scope evidence looks like: decisions you make that used to be escalated, work you set direction for rather than execute, people or functions that depend on you without being assigned to you, problems that arrive at you first because everyone assumes they're yours.

For each, the useful format is what you owned, what you decided, and what happened. "Led the migration" is an assertion. "Owned the migration end to end, made the call to stage it over two quarters against pressure to do it in one, and it shipped without an outage" is scope, a judgment call, and an outcome. That third one is what survives being repeated by someone else.

Three or four of those beat a list of fifteen bullets. The committee will remember one or two things about you regardless — decide which.

How to structure the document

Keep it to a page or two. Nobody reads more, and the discipline improves it.

1. The claim, in one sentence. What level, and the summary of why. If someone read only this line they should be able to repeat your case.
2. The scope you already hold. Three or four items, each with the decision and the outcome. Mapped to the framework's language where you can.
3. Evidence from other people. Who relies on you, who asked for you, what peers or stakeholders have said. Committees weight this heavily because it's the part you can't self-report.
4. What you'd own next. The forward-looking piece, which turns it from a reward into a plan.
5. The gaps, and what you're doing about them. Counterintuitive and worth it: naming the one or two places you're not yet there makes the rest credible, and pre-empts the objection someone in the room will raise anyway.
6. The title and band. Plainly, at the end.

Write it so your manager can paste sections of it into whatever form they have to fill in. Making their job mechanical is a real advantage.

Your manager is the audience before the committee is

Your manager is not deciding this. They're presenting it, usually alongside other people they'd also like to see promoted, in limited time.

So the question to optimize for isn't will they agree — it's what will they be able to say about me in four minutes. Give them the sentence. Ask them directly what the committee responds to, what sank cases last round, and what they'd want strengthened before it goes in. Ask early enough that the answer can change the document.

And ask what the timeline actually is. Promotion rounds have submission deadlines that are often weeks before the decision, and cases fail every cycle for missing them rather than for being weak.

The backfill still applies

The move that separates a proposal from a request works here too, and almost nobody does it in a promotion case.

If you step up, something you currently do needs to go somewhere. Work out who absorbs what, what justifies a hire, and what stops. Then put it in the document.

It removes the objection that promoting you creates a hole, it demonstrates the exact judgment the next level is supposed to require, and it's a piece of evidence rather than a claim — because thinking about team structure rather than your own tasks is, in most frameworks, precisely what the next level is defined as.

Ready to do it properly?

The free course walks you through the same underlying work — the value you add, the scope you'd take on, and how to put it in terms the people deciding will recognize. About fifteen minutes, nothing to buy, and nothing you write ever leaves your browser.

Start the free course →