The Promo Packet Is a Leadership Artifact, Not Paperwork
The best engineering leaders don't write promo docs once a cycle. They use them year-round as the single best tool for growing, and keeping, their strongest engineers.
Most managers I've worked with treat the promotion packet as a tax. It's the thing you scramble to assemble in the two weeks before calibration, hunting through Slack and old PRs for evidence that your engineer is, in fact, as good as you've been saying. You write it, you defend it, you forget about it until next cycle.
That version of the promo doc is paperwork. And managers who treat it as paperwork lose good people: sometimes to other teams, sometimes to other companies, almost always to the slow burn of feeling unseen.
The leaders whose engineers consistently get promoted are doing something completely different. For them, the packet isn't a document they write at the end. It's a tool they run all year, arguably the highest-leverage management tool they have.
What the packet actually is
Strip away the template and a promo packet is one thing: the case for why a person operates at the next level, told as evidence. Which means writing one forces you to answer questions you should be answering anyway:
- What does the next level actually look like for this person, in specifics, not platitudes?
- What's the gap between where they are and that bar, concretely?
- What evidence would close that gap, and are they currently positioned to generate it?
- Who, besides me, would need to believe this, and do they?
If you only ask those questions two weeks before calibration, the honest answer is usually "too late." The evidence takes quarters to build. The advocates take quarters to win. The scope had to be handed out months ago. A packet written at the deadline can only describe a year that already happened. A packet used as a tool shapes the year while there's still time.
A promotion is a case you build over quarters, not a conversation you have once. The manager's job is to start building it before the engineer even knows it's started.
How the best leaders run it year-round
Write the draft a year early, then manage against it
Pick your strongest engineers and write the promo packet you wish you could submit, today. It'll be full of holes: claims you can't yet support. Good. Those holes are now your roadmap. Every hole is a piece of scope to assign, a project to steer their way, a stakeholder to introduce. You've turned a backward-looking document into a forward-looking plan.
Make the bar explicit and shared
Most engineers stall not from lack of effort but from a fuzzy target. Sit down and translate "show staff-level impact" into the three or four concrete things your org actually rewards. When the engineer can see the bar clearly, half your management work is done. They'll aim themselves at it.
Collect evidence continuously, not frantically
Keep a running doc per engineer. Every time they make a strong call, unblock a team, or grow someone, drop a line in with a link. Five minutes a week. Come calibration, you're not reconstructing a year from memory. You're editing a case that's been writing itself. And the quality of advocacy you can offer goes up sharply, because specific evidence is what actually moves a room.
Recruit the advocates early
Promotions are decided by people who aren't your engineer's manager. If the first time a peer leader hears your engineer's name is in the calibration meeting, you've already lost. Use the packet to identify who needs to be a believer, then engineer the visibility (the cross-team project, the design review, the demo) that earns it. Months ahead, not the week of.
Why this is a retention strategy, not just a promotion one
Here's the part managers underrate. Your best engineers don't leave because they didn't get promoted this cycle. They leave because they couldn't tell whether they were progressing at all. Ambiguity is what drives people out: the quiet sense that they're working hard into a void.
When you run the packet as a year-round tool, you eliminate that ambiguity as a side effect. The engineer always knows the bar, always knows where they stand against it, always knows you're actively building their case. That's not just how you get them promoted. It's how you keep them long enough for it to happen.
The promo packet was never paperwork. It's the clearest statement a leader can make of how they see a person and where they're taking them. Treat it that way (early, openly, continuously) and the calibration meeting stops being where you fight for your engineers. It becomes where you collect on work you did all year.