TL;DR
- A promotion packet is a summary of a case that was already made — or wasn't — by the work and the visibility that happened months before you write it.
- Writing a strong packet from a blank page, right before the deadline, is trying to win an argument you haven't been building evidence for.
- The strongest packets read like a well-organized record, not a persuasive essay — because the writer had the material, not just the argument.
- Waiting until promotion season to think about scope, ownership, and impact means missing months where you could have been documenting exactly that.
- The fix is unglamorous: note the moments that show scope and impact as they happen, so the packet is assembly, not invention, when the time comes.
The packet is a summary, not a persuasion exercise
A promotion case is decided by what actually happened at the scope and impact level expected of the next title — the packet just has to show it clearly. Writing well can't manufacture scope that wasn't there.
What “starting early” actually means
It doesn't mean campaigning for months. It means noticing and writing down, in the moment, the handful of decisions and outcomes that later become the evidence: the project you owned end to end, the call you made under ambiguity, the thing that wouldn't have happened without you specifically.
Why a blank-page packet reads thin
Reconstructing a year under deadline pressure produces vague, generic language — “drove key initiatives,” “collaborated cross-functionally” — precisely because the specifics were never written down and now can't be recovered. Reviewers can tell the difference between a documented case and a persuasive one.
What a well-documented case actually looks like
Specific, dated, verifiable entries: what the situation was, what you decided, what changed, ideally with a number or a named outcome attached. Assembling five or six of those into a packet is fast. Inventing them from memory isn't.
Frequently asked questions
How far in advance should I start documenting for a promotion?
As early as possible, ideally as an ongoing habit rather than something tied to a specific promotion cycle — you won't always know in advance which projects will end up mattering.
What kind of moments are actually worth writing down?
Anything that shows scope, ownership, or judgment at the next level: a decision you made, a project you drove, a problem only you could have solved the way you did.
My manager writes most of my promotion case for me — does this still matter?
It matters more, not less — a manager writing from your specific, documented examples produces a stronger case than one writing from a vague recollection of your year.
What if the moments I have don't feel impressive enough?
Write them down anyway, in plain language, without editorializing. Whether something counts as promotion-worthy is often easier to judge with a full list in front of you than by guessing in advance.
Related reading: How to build a brag doc with AI.