Seeing a real promotion packet makes the abstract advice concrete. Below are example sections from strong promotion packets, showing how to map accomplishments to criteria and make the case that you're already operating at the next level.
What makes a promotion packet strong
Before the examples, the principles every strong packet shares:
- Evidence mapped to criteria — each section answers a specific promotion requirement.
- Specific, quantified accomplishments — outcomes and numbers, not adjectives.
- Honest scope — claims that hold up in calibration.
- A clear trajectory — growth over time, not a single good moment.
Example: summary section
Requesting promotion to Senior. Over the past three quarters I've consistently operated at the Senior level — leading the billing migration end to end, setting technical direction for the reporting pipeline, and mentoring two engineers to independence. This packet maps that work to each promotion criterion.
Note how it states the ask, previews the headline evidence, and signals the structure.
Example: criteria-by-criteria evidence
Criterion: Impact
Led the billing-platform migration that reduced checkout errors by 40% and recovered previously lost orders. This was the highest-impact reliability project on the team this year, and I owned it from problem definition through rollout.
Criterion: Cross-functional leadership
Coordinated three teams — engineering, data, and operations — to ship the migration on a compressed timeline. I created the rollout plan that became the single source of truth and ran the syncs that kept everyone aligned.
Criterion: Technical depth / ownership
Set the technical direction for the new reporting pipeline, led the design reviews, and brought the team through implementation. The pipeline is now the source of truth for three teams' weekly planning.
Criterion: Developing others
Mentored two new hires through ramp-up. I set up weekly check-ins, walked them through our systems, and coached them on their first independent projects. Both now operate without oversight.
Example: impact highlights section
- Led billing migration → 40% reduction in checkout errors.
- Built the reporting pipeline now used by three teams.
- Mentored two engineers from onboarding to independence.
Short, scannable, results-forward — the wins you most want remembered.
Example: addressing a gap
One area I've deliberately developed this year is broader organizational influence. I started by leading the cross-team migration working group, and I'm now driving the planning process for our next major initiative.
Naming a gap and showing you're closing it builds credibility rather than undermining it.
What to avoid (from weak packets)
- Listing activity, not impact: "Worked on the migration" instead of "Led the migration, cutting errors 40%."
- Unmapped evidence: accomplishments that don't connect to any stated criterion.
- Vague self-praise: "I'm a strong leader" with nothing behind it.
- Overclaiming scope: taking credit that calibration will challenge.
- Recency bias: only last month's work, with the rest of the year missing.
The bottom line
Every example above shares one foundation: specific, quantified evidence the candidate could actually recall and cite. The strongest packets aren't written from memory at promotion time — they're assembled from a record kept all along. Capturing your wins as they happen turns packet-writing from a stressful reconstruction into simple assembly, which is what [CareerRise](/) is built for.
---
Advance on evidence, not memory.
Start logging your wins free →