Promotion packet examples
Promotion packet examples for the week when your proof needs shape
If your notes sound like a to-do list, your manager still has to do the persuasive work. A strong promotion packet hands them proof blocks they can repeat upward without rewriting your story.
What a strong proof block does
- Names the work clearly.
- Shows why it mattered to the team or business.
- Adds one outcome, signal, or before-and-after detail.
- Makes the scope sound bigger than routine task completion.
Before and after examples
Project ownership
Loose note: I owned the launch checklist for the release.
Packet version: I took over the launch checklist when approvals were split across Slack and docs, pulled design, support, and engineering into one weekly review, and cut launch-day blockers because everyone worked from the same record.
Cross-team leadership
Loose note: I helped other teams move faster.
Packet version: I turned recurring support questions into a short handoff guide for sales and onboarding, which reduced repeat explanations and gave new teammates the same answer path from day one.
Process improvement
Loose note: I improved our review process.
Packet version: I replaced scattered self-review prompts with one template that grouped wins by outcome, so managers could scan evidence faster and teammates stopped rewriting the same context in three places.
Promotion-level scope
Loose note: I took on more responsibility this half.
Packet version: My role expanded from delivering assigned work to shaping how the work got handed off, prioritised, and reviewed, which is why the case for the next level is about scope, not effort alone.
Copy this proof-block pattern
I led [work]. It mattered because [team or business reason]. The result was [clear change, saved time, reduced risk, cleaner handoff, stronger delivery, or customer outcome]. This shows scope at [target level or type of responsibility].
Common promotion packet misses
- Listing effort instead of change.
- Claiming leadership without a concrete example.
- Burying the ask after a long wall of context.
- Using vague words like helped, supported, or assisted when the work actually drove a decision.