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.
Use this page when: you already did the work, the packet is coming together, and you need examples of what "promotion-ready" proof sounds like.
Use the £19 tracker instead if the real problem is missing receipts. Use the £24 prep kit instead if the review or packet deadline is close and you need a cleaner draft fast.
Start with the full promotion packet template if you still need the structure first.
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.
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].