Why a written case helps
When you are considered for promotion, the people deciding often know only part of what you have done. Your manager may speak for you in a meeting you are not part of, and the others in that room may rely on your manager’s summary. A promotion case is a short, organized description of your work that makes your manager’s job easier. It is not a demand, and it does not guarantee an outcome. It simply makes sure the best information is available when decisions are made.
Even if your organization has a formal process, a personal version of this exercise is useful. It forces you to think about your contribution in terms the organization cares about, rather than a list of tasks.
Start with the target level
A case is only persuasive when it answers the question the decision makers are asking: is this person already working at the next level? So begin by finding out what that level requires. Look for written expectations, or ask your manager. Reading how your organization’s levels differ will help you notice whether the jump is mainly about scope, independence, leadership of others, or technical depth.
Then list three to five of the main expectations in your own words. These become the headings for your evidence. If you are unsure, a skills gap analysis can show where you are already strong and where evidence is thin.
Collect evidence that shows impact
For each expectation, gather examples from the past year or so. Good evidence tends to answer a few simple questions:
- What was the situation or problem?
- What did you personally do?
- What changed as a result, and for whom?
- How do you know?
Results can be numbers, but they do not have to be. Time saved, fewer errors, a smoother handoff, a customer who stayed, or a team that could work without you can all be real outcomes. If you do use numbers, make sure you can explain where they come from. A vague or inflated figure can hurt your credibility more than having none.
Feedback adds weight because it comes from someone else. Messages from colleagues, comments from performance reviews, and notes from clients or partners are all useful. If you have kept a record as you went, this step is much easier. Without one, scan your calendar, sent emails, project files, and old notes to rebuild the year.
Show scope and growth, not just activity
Decision makers often care less about how busy you were and more about the size of the problems you handled. For each example, note things like how ambiguous the task was, how many people or teams were involved, and how little direction you needed. Describing how you helped others, such as coaching a new teammate or improving a shared process, shows that your contribution reaches beyond your own tasks.
It also helps to point out growth over time. If a year ago you needed guidance on certain work and now you handle it independently, say so. That trajectory suggests you can keep growing in the next role.
Be honest about gaps
A credible case does not pretend to be perfect. If there is a skill the next level needs and you are still developing, it is better to acknowledge it and describe how you are building it. This shows self-awareness, which is something senior people tend to value. Receiving feedback without getting defensive is part of this: if your manager points out a gap, treat it as information you can act on rather than an attack.
Organize it simply
A one- or two-page summary is usually enough. A workable structure looks like this:
- A short opening that states the role you are aiming for and why you believe you are ready.
- Three to five sections, each tied to an expectation of the next level, with two or three concrete examples.
- Quotes or references to feedback from others.
- A brief note on what you plan to develop next.
Write in plain language and avoid jargon the decision makers may not share. Use verbs that make your own part clear, such as “led,” “designed,” or “resolved,” and credit others where they contributed. Writing it the way you would write resume bullet points, focused on results, is a useful discipline, but a promotion case can include more context than a resume does.
Share it with your manager first
Your manager is usually the person who presents your case, so bring it to them rather than around them. Ask whether it matches what they have seen, whether any important examples are missing, and how the process works. They may tell you which points will resonate and which will not. Treat their reaction as useful information rather than a verdict.
Timing matters too. If you present a case right after budgets are set or when a reorganization is underway, there may be little room to act. Asking when decisions are made lets you prepare ahead of that point.
Plan for different outcomes
Sometimes the answer is yes. Sometimes it is “not yet,” ideally with specific reasons and a rough timeline. And sometimes it is no, with little explanation. In each case, the work you did is not wasted. You now have a clear summary of your accomplishments that supports a raise conversation, an internal move, or a job search. If you are told no, ask for concrete feedback and decide what to do next, as covered in thinking about being passed over.
A case built honestly and early gives you the best chance of being seen accurately, which is all you can reasonably ask a process to do.