How to Make the Case for Your Promotion in Writing
A promotion case isn't a list of accomplishments at your current level. It's the argument that you're already operating at the next one. Five steps for writing it.
You're going up for promotion. Your manager is supportive, calibration is in six weeks, and now there's a document to write — variously called the promo packet, the case, the brag doc, or just 'send me your bullets so I can advocate for you.' You sit down to draft it and reach for the obvious move: list everything you've accomplished in your current role. Strong list, twelve solid bullets, ready to send.
That document loses promotion cases. The mistake isn't that the bullets are weak — they're probably strong. The mistake is that they're describing accomplishments at your current level, which is what the calibration committee already expects from someone at your current level. A promotion case has to argue something different: that you're already operating at the level you're being considered for. The bullets that demonstrate this are usually different from the ones in your standard self-review, and the structural argument that wraps them matters as much as the bullets themselves. The five steps below are how to build that argument deliberately.
Build the case from the role above you, not the role you have
The most common failure of promotion cases is that they're written from the wrong reference point. They list what you did this year and argue you did it well — which is the case for keeping you in your current role. The promotion case has to argue something subtly but importantly different: you're already doing the work of the next level. This requires starting from the next-level role definition and working backward, not starting from your accomplishments and working forward. Pull the role description for the level above you (HR usually has one; if not, your manager can describe what differentiates the levels). Identify the three or four key differentiators — usually scope, autonomy, ambiguity tolerance, and impact — and structure the document around evidence that you're already operating at that bar. Bullets that don't speak to next-level differentiators belong in your performance review, not your promo case.
"What does the role above me actually require — in scope, autonomy, ambiguity, and impact — that's different from my current role? Which of my accomplishments demonstrate I'm already operating at that bar?"
These are the two questions that frame a real promotion case. The first names the differentiators between your current level and the next; the second filters your accomplishments to the ones that speak to those differentiators. Most accomplishments will be solid level-N work and don't belong in the promo case. The two or three that demonstrate level-N+1 operation — work above your scope, decisions made with ambiguity you didn't have authority to resolve, impact across teams you didn't lead — are the spine of the document. Build from those.
Show pattern, not events
Single events are weaker promotion evidence than patterns. 'Led the migration successfully' is one event, which a calibration committee can attribute to circumstance, luck, or an exceptional moment. 'Led three cross-functional initiatives over the past 18 months — migration, customer onboarding redesign, and incident response overhaul — each delivered on time and absorbed by the team' is a pattern. Patterns are much harder to dismiss because they show repeatability and trajectory, which is what 'ready for the next level' actually means. Identify two or three thematic clusters in your work — leadership at scale, technical depth in a critical area, mentorship that produced specific outcomes — and group bullets under each. The themes themselves become the spine of the document, and individual bullets are evidence within them rather than freestanding claims. A promotion case organized by theme reads as 'this person operates at level N+1'; a promotion case organized as a list of accomplishments reads as 'this person had a good year at level N.'
Quantify what changed because of you, not what you participated in
Every senior-level role has the same implicit question behind it: what got materially better at the company because this person was here? Promotion cases that answer that question with specific outcomes win calibrations. Cases that list participation in initiatives without specifying what changed do not. The discipline is to push every bullet from 'was part of' to 'caused this specific outcome' or 'unblocked this specific thing.' Numbers are the proof. The migration didn't just ship — it retired three legacy systems and saved $2.4M annually. The onboarding redesign didn't just complete — it cut activation time by 60% and increased trial-to-paid conversion 12 points. The incident response overhaul didn't just go live — it dropped MTTR from 4 hours to 45 minutes across the next quarter. If you can't say what changed because of you, the calibration committee can't either, and the bullet doesn't carry weight against peers whose bullets do.
Address what gets you to no proactively
Every promotion case has objections that will surface in calibration whether you address them or not. Common ones: scope hasn't grown enough, you're strong technically but haven't demonstrated leadership at the next level, your impact is in your own team but not cross-functional, you've been at the current level less time than peers who got promoted. Identify the two or three objections most likely to come up for you and address them in the document directly. Not defensively — proactively. 'My scope this year was contained to the platform team, but I extended my impact through the architecture review process where I influenced decisions across four other teams.' Naming and refuting objections shows the committee you've thought about the case clearly, and it gives your manager the talking points they need to advocate for you when those objections come up in the room. Cases that ignore the obvious objections leave them unanswered; cases that address them turn potential blockers into demonstrated awareness.
Know when the right move is to ask for a different promotion than the one you thought you wanted
There's a category of promotion case where the document, honestly written, reveals that the promotion path you're on isn't the one that fits your work. Maybe you're a strong individual contributor being told you need to manage to advance; maybe you're a strong manager being asked to demonstrate technical depth that isn't where your value actually is. The first draft of your case may be telling you that the level you're applying for isn't the natural next step. The right response isn't to force the case — it's to consider whether a different track exists or could be argued for. Many companies have parallel IC and management tracks but underuse them; some have specialist tracks that aren't widely advertised. The honest read of your own work sometimes reveals that the standard promotion path isn't the right one, and the conversation worth having is about that mismatch rather than about the standard case. Promotions on the wrong track look like wins and feel like burnout six months later. The harder conversation about path can produce a promotion that actually fits.
Build a promotion case that argues for the next level, not the current one
Brag Sheet Builder takes your accomplishments and uses Strength Radar to score them against role expectations across 6-8 dimensions, surfacing the dimensions where your case is strong and where it has gaps. The Raise mode produces business-value estimates and a meeting script for the conversation, and integrates with Difficult Talk Coach for rehearsing the actual ask.