How to build a strong case for promotion

Most people write part one and stop. The case is decided on parts two and four.

1 — You already operate at the level. Evidence, not assertion. Three or four specific things at the next level, dated.

2 — The transition is low-risk. You have already done the hard parts of the next job in some form. This is the part that answers the unspoken question.

3 — What the organisation gets that it does not have today. Not what you get. A promotion is a resource allocation, and it competes with other uses of the same budget.

4 — What happens to your current work. Who does it, or what stops. Almost nobody includes this, and it is the most common unspoken objection in the room: if we move them, who covers what they do now?

Part 4 is the one worth writing first, because it is the one you cannot answer with enthusiasm. It also demonstrates the exact quality the next level requires — thinking about the consequences of a decision beyond your own position.

"Operating at the next level" is easy to claim and hard to evidence. These three tests turn a claim into a proof.

Decided, not recommended. Did you make the call, or did you put options in front of someone who made it? A recommendation is good work at your current level. A decision, with your name on the consequence, is next-level evidence.

Owned, not contributed. Were you accountable for the whole of something, or responsible for a part of it? Ownership means it was yours when it went wrong.

Changed, not maintained. Did you alter how something is done, or do it well as it stands? Excellent delivery is why you have your current job. Changing the standard is the evidence for the next one.

Go through your material and mark each item against the three. Anything that fails all three is not case material, however impressive it felt. If nothing survives, that is the finding, and it is more useful than a weak submission: achievements on your CV is the method for finding what you have.

Six questions. Answer yes, partly or no.

Four or more yeses: write it. Two or three: you have a case and it is not ready, and the gaps are named above. Fewer than two: the honest next step is to change what you do for six months and then return, which is a better use of the time than a submission that gets a polite no.

Part 4, and the section that separates a serious case from an enthusiastic one.

You have three honest options, and one of them is not "someone else will pick it up".

Someone specific takes it. Name them, say what they would need, and say whether you have already started handing it over. If you have been developing someone, say so — it is evidence at the next level in its own right.

It splits. Part goes to a named person, part stops, part comes with you. Show the split.

It stops, and here is why that is acceptable. The riskiest of the three and sometimes the most honest. If part of your current work has stopped mattering, saying so is a service to the organisation.

Write two sentences on this and you are ahead of most internal candidates, who arrive at this question in the meeting and improvise.

The example below is written for this page. It is an illustration, not a real person, a real organisation or a real submission.

Subject: Request for review of role — Senior Engineer to Project Manager

What I am asking for. To be considered for the Project Manager role on the utilities package, at grade [X], from the start of the next cycle.

Where I am already operating at that level. Over the past fourteen months I have run the utilities package in practice: I took over the contractor interface in March when [role] was vacant and have held it since, including the two variation negotiations in September. I set the revised inspection sequence that the other two packages have since adopted. And when the cable delivery slipped in June I took the decision to resequence rather than escalate, which cost four days instead of the three weeks a re-tender would have cost.

Why this is a low-risk move. The job is not new to me — I have been doing most of it without the title. The two parts I have not covered are cost reporting to the client and formal contract administration, and I have sat in on both with [colleague] since April.

What the department gets. A package manager who already knows the contractor, the site and the sequencing, instead of three months of handover. It also closes the gap the vacancy has left, which we are currently covering informally.

What happens to my current work. [Colleague] has been shadowing the inspection coordination since May and can take it with two weeks of handover. The drawing register goes back to the document controller where it originally sat. Nothing is left uncovered.

Five short blocks, about 300 words, and every claim is dated and checkable. Note what it does not contain: no mention of how long the writer has been with the organisation, no comparison to a colleague, no adjectives, and nothing about what the promotion would mean to them personally.

• [ ] Every claim is dated, specific and would be confirmed by someone else
• [ ] At least three items pass one of the three proofs
• [ ] The role I am asking for is named as it exists or would exist
• [ ] The organisation's gain is stated before my own, and my own may be absent entirely
• [ ] The succession answer is written, with a name in it where possible
• [ ] The gaps in my readiness are acknowledged, with what I am doing about them
• [ ] No comparison to any named colleague appears anywhere
• [ ] No reference to tenure, loyalty or how hard I work
• [ ] It is under one page
• [ ] My manager has seen it before anyone else does

The last item matters more than the document. A case that reaches a decision-maker without your manager having seen it first creates a problem you then have to solve instead of the promotion.

Give it to your manager first, in a conversation, with the document to keep. They are the person who has to carry it, and ambushing them converts a supporter into a defender.

Time it to the cycle, not to your patience. Compensation and grade decisions usually run on a calendar, and a case submitted two weeks after the numbers were locked is a case for next year. Ask when the window is; it is not a strange question. How to ask for a salary increase covers working backwards from the cycle.

One page, plus the conversation. A twelve-page portfolio signals that you have not worked out what matters.

Tenure. Five years is not an argument. Five years of scope growth is.

Comparing yourself to a named colleague. It converts your case into a dispute about someone else, and it damages both of you.

Listing everything. Three strong items outperform nine, because nine makes the reader choose which to take seriously.

"I am ready for more responsibility." This is the sentence the whole document is supposed to replace.

Any version of "or else". An implied threat converts a promotion decision into a retention decision, and those are decided differently and remembered longer: counter offer after resigning.

Asking for the title without the scope. If you want the grade but not the accountability that goes with it, that will be visible, and it is the fastest way to lose a case that was otherwise sound.

Ask for the specific gap, in writing if you can. "Not quite ready" is not feedback. "You have not demonstrated that you can hold a position when a senior stakeholder pushes back" is.

Ask two questions: what would have to be different, and when is the next realistic window. Vague answers to both are themselves information.

Then write the date in your diary and treat the intervening period as evidence-gathering rather than waiting. Most successful second attempts are built in the six months after the first one failed.

Where a competency framework or grade definition exists, write the case against it, line by line. This is the single highest-return move available, and it is available more often than people check. Larger and public-sector organisations frequently publish or share the criteria: competency-based interviews explains how that assessment thinks.

Know who signs. In structured organisations the approver may sit above your manager or in a committee, and a case written only for your line manager may not survive translation upwards.

Write in the language the process runs in. A case submitted in the wrong language is read by fewer of the people who decide.

Discretion while it is in progress. Peers may be candidates for the same seat, and how you conduct yourself during the process is part of what is being assessed, whether or not anyone says so.

Should the case be written or spoken?

Both. The conversation first, with the document left behind — because the document is what travels to people who were not in the room.

How long should it be?

One page. If it does not fit, the problem is selection rather than length.

What if my organisation has no formal promotion process?

Then the case matters more, not less, because the decision will be made informally and on impressions. A written page is a way of controlling what is remembered.

Should I mention that I have had an approach from elsewhere?

Not in a promotion case. It converts the decision into a retention question and changes who is deciding and on what basis.

I do the work but the title has not followed for two years.

Then the scope case is already made and the question is who has to sign. Focus on parts 4 and 5 of the readiness gate — the succession answer and the approver — because those are usually what is actually missing.

What if there is no role above me?

Then the case cannot succeed, and the decision is a different one: promotion coaching covers diagnosing that, and should I resign or stay covers what follows.

Before you write anything else, answer the question nobody asks out loud: if they move you, who does what you do now? Two sentences. Most people cannot answer it, and it is the reason their case does not move.

Book a discovery call · Message Saad on WhatsApp · See coaching options