Promotion case help
Promotion packet template for the person doing bigger work than their title says
A promotion packet should make your manager's job easy. Show the scope, show the change, show the proof, then show the level you are already working at.
Pick the paid next step by timing
If your packet is due soon and the notes are still rough, use the £24 prep kit first. If you still need one place to collect receipts over the next few weeks, start with the £19 tracker. If the packet is likely to turn into a raise talk, keep the £27 salary scripts for after the review or promotion call.
Get the £24 prep kit Start with the £19 trackerIf calibration is close: send a shorter evidence packet first, then use this fuller version for the promotion case. Start with the calibration evidence page.
Use this five-part packet
- Target role. Name the level or scope you are asking for.
- Three to five proof blocks. Each block should show the work, why it mattered, and one proof point.
- Scope lift. Show where your work already looks bigger than your current title.
- Peer or cross-team signal. Add one quote, partner note, or repeated pattern other people can back up.
- Clear ask. End with the level you want discussed, not a vague hope for growth.
Copy this structure
Target role: [role or level]
Why now: Over the last [period], my work has expanded from [current scope] to [larger scope].
Proof block 1: I led [project]. It mattered because [team or business reason]. The result was [metric, saved time, reduced risk, shipped work, or customer outcome].
Proof block 2: I took on [cross-team or leadership work]. It changed [decision speed, team load, quality, revenue, customer trust, or delivery].
Proof block 3: I improved [process or system]. The before and after was [plain contrast].
Ask: Based on that scope, I would like to discuss promotion to [target role or level].
Example proof block
Launch handoff: I took over the weekly launch handoff when updates were split across Slack threads and status docs. I moved owners, blockers, and approval notes into one sheet, then ran the review with design and support from the same record. The handoff meeting dropped from around 45 minutes to around 20, and the next two launches reused the format without extra cleanup.
What weak packets get wrong
- They list tasks instead of change.
- They claim leadership without an example.
- They ask for promotion before showing scope.
- They bury the proof in one long wall of text.
Turn the packet into something you can actually send
If the packet needs to be cleaned up tonight, move into the £24 prep kit now. If the main problem is missing receipts, start with the £19 tracker and come back here once the proof is in one place. When the next meeting turns to compensation, go to the salary script page.
Get the £24 prep kit Get the £19 trackerNeed the raise wording after the packet lands well? Open the salary script page.