Your manager is arguing against an unwritten standard
John Beeson made this point in Harvard Business Review back in 2009: promotion decisions look arbitrary from below because the criteria for moving up mostly live in people's heads rather than in a document you can read [1]. Your manager is arguing against that unwritten standard on your behalf. Give them language that survives being repeated by someone else.
That language is scope. SHRM's guide to job leveling describes how positions get sorted into levels, by duties, responsibilities, and level of authority [2]. Effort doesn't appear on that list. So write in the currency the room already uses: revenue, cost, risk, and speed.
Build the value brief, not a highlight reel
What travels into that room is not your effort. It's a short, secondhand version of you, carried by whoever remembers your work and however well they can argue for it. What you hand your manager has to be built for that trip. It's a value brief, not a highlight reel, and it has five parts.
- Money and time. What you saved, what you earned, what you shipped faster. Delays you prevented count as much as revenue you added, and leaders know it.
- Scale and scope. Teams you built or led, budgets you managed, the size and stakes of what you were trusted with when it was hard.
- Before and after. The state of things when you arrived and the state of things now, with the change named in their terms, not yours.
- Proof. For every claim, a source you could point to on request: a dashboard, a report, a colleague who would confirm it. A claim you cannot back is a claim you should cut.
- The gap you're ready to close. The problem the next level is trying to solve that your work already speaks to. This is the bridge from what you've done to why you're the bet.
Someone should be able to read your top line out loud in a meeting and know what's being requested. If it needs a second sentence to make sense, it isn't done yet.
Name your sponsors
For each part of the value brief, name the person outside your reporting line who saw it happen. That's a shortcut for a committee member who wants to verify one claim without doing an investigation, and it's how you stop your case from resting on one manager's word.
A mentor advises you in private. A sponsor argues for you in the room where your name comes up. If every name in your brief reports to your own manager, you don't have sponsorship yet. You have one advocate.
Write the handover
This is the part almost nobody includes. Leadership hesitates because promoting you leaves a hole where your current work used to be, so answer that before it gets raised. List your current responsibilities. Say which ones move with you, which a named colleague absorbs, which get automated or dropped, and what the first ninety days after the change look like. When your manager can answer who covers your book without pausing, one easy no comes off the table.
Write it for a room you are not in
There is no official format for any of this, and I would distrust anyone who told you there is one. What I believe about the shape of it is narrower. The test is not polish. It's portability. If your manager could not repeat your point to the board without translating it first, it isn't ready. Clear enough to travel is the bar, every time.
Keep the whole thing tight, send it as one file, and put the top line in the body of the email too. The person who has to argue for you may never open the attachment before the meeting.