Promotion packet example
A committee that has never seen you work reads your case for a few minutes. The packet, not the work, is what you're judged on — so prioritize scope over volume.
A promotion packet is a structured evidence document showing you already operate at the next level — your projects, their impact and scope, and the people who vouch for you. The thing to understand before you write a word: a committee that has never seen you work will read it for only a few minutes, so the packet, not the work, is what you're actually being judged on.
Understand who reads it, and how
At most companies past a few hundred people, your manager doesn't decide your promotion — a committee does, and the committee has never watched you work. They read a one-page case (written by you or your manager) and often spend on the order of fifteen minutes deciding whether you've shown "sustained next-level performance." This is the uncomfortable truth behind the visibility trap: you are not evaluated on your work, you are evaluated on the evidence of your work that makes it into the packet.
So the packet's job is not to log everything you did. It's to make a committee of busy strangers confident, fast, that you already operate at the next level. Everything that doesn't serve that goal is noise that buries the signal.
What to include — and what to cut
- 3–5 next-level projects: what you did, the impact (with a defined goal), and what made it complex
- Quantified organizational impact ($ saved, % moved, time reclaimed)
- Scope: cross-team, ambiguous, strategic work — the qualitatively different kind
- Mentoring and glue work, and the impact of that glue work
- Advocates and peer support — often weighted more than your self-review
- Honest gaps and how you're addressing them
- Long lists of tasks, tickets, or features
- PR counts and lines of code — output, not impact
- Hidden weaknesses — omitting mistakes tends to backfire
- More of your current level's work, just more of it
- Jargon a cross-functional committee can't parse
- Unsupported claims with no link, metric, or witness
How to prioritize the case
- Scope and complexity first. You get promoted by doing qualitatively different work — more ambiguous, more cross-cutting — not twice as much of your current work.
- Quantified impact second. "Reduced support tickets 20% year on year" or "unblocked four teams" gives the committee something concrete to defend.
- Leadership and leverage third. Who you mentored, the glue work you did, and what it changed for the org.
- Corroboration last but essential. Peer reviews carry real weight — sometimes more than your own words, because people assess others more reliably than themselves.
Write it long before you need it
The best-known guidance, from Will Larson's work on staff engineering, is counterintuitive: write your first packet long before you're nominated, and review the empty version with your manager in a 1:1. Used this way the packet is a compass, not a trophy — it focuses your work toward the criteria over quarters, and it survives the manager changes that would otherwise reset your progress. When it's finally time to submit, you're editing a year of collected evidence into the official template, not excavating it from memory the week before.
What did you do · what was the impact (with a goal) · what made it complex?
The high-leverage ways you improved the org — named, with the result
Who you mentored and toward what · the glue work you do and its impact
Keep each entry short; link out to the design docs and data that back it
How Workfied helps here
A packet is only as good as the evidence behind it, and that evidence is built over quarters, not the night before. Workfied accumulates it for you: each ten-second note becomes a dated, impact-framed entry, sorted toward the scope and complexity a committee rewards. When it's packet time, you're assembling a case from a full record — not staring at a blank template trying to remember a year. Built for you, never reading from your company's systems — only what you send it. Encrypted in transit and at rest.
Evidence
How it's judged
A committee that never saw you work reads a one-page packet for minutes and decides. The packet is the proxy for you.
Source: How to Get Promoted in Tech, 2026
The mechanism
You're evaluated on the evidence of your work that reaches the packet — not the work itself. Doing great work is necessary, not sufficient.
Source: jobsbyculture.com (2026)
Include vs cut
Cut "did 2x the tickets." Keep cross-team, ambiguous, strategic work — scope is the axis that gets you promoted.
Source: Larson, Staff Engineer