Your manager walks into a room with seven other managers and a spreadsheet of open headcount. Everyone in there has someone to put forward. Your name gets a few minutes at most, and you're not present for any of it.
What most people hand their manager before that meeting is a year's worth of tasks. Accounts managed, reports delivered, launches supported. It's accurate, and it's useless, because none of it answers the question actually being asked in that room: is this person already operating at the higher level, and what does it cost to move them.
Write it for the person who has to repeat you in a room you are not in. That's the whole test, and everything below builds toward passing it.
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.