Promotion Packet Examples: Weak vs Strong, Side by Side

Most "promotion packet example" results are empty templates with square brackets in them. Those are not examples, they are stationery. What you actually want to see is the difference between a paragraph that gets deferred and a paragraph that gets approved, because the gap is smaller and more specific than people expect.

Below are real patterns, rewritten. The work is identical in each pair. Only the writing changed.

Example 1: The executive summary

This is the only part guaranteed to be read. Committees spend 3 to 5 minutes per candidate, and some of them will read this and skim the rest.

Weak version:

Over the past year I have worked on the payments platform, contributing to several major projects and supporting the team. I have grown a lot and taken on more responsibility, and I believe I am ready for the next level.

Nothing here is false. It is also completely unusable. There is no number, no scope, no named outcome, and "I believe I am ready" asks the committee to take your word for it.

Strong version:

I own the payments reliability workstream, which I proposed after our Q1 outage. Over three quarters I cut payment failure rate from 2.3% to 0.4%, recovering roughly $1.8M in annualised revenue. The idempotency pattern I designed is now used by four teams outside payments. I mentored two engineers through the same period, one of whom now owns the retry service.

Same person, same year. The second version answers the three questions a committee is actually asking: what did they own, what changed because of them, and does their influence extend past their own team.

Example 2: An accomplishment

The shape that works, every time, is: the situation, what you specifically did, the measurable outcome, and who else was affected.

Weak version:

Led the migration of our authentication system to the new provider. Worked with multiple teams to ensure a smooth rollout. The migration was completed successfully with minimal disruption.

This is the single most common paragraph in promotion packets, and it is invisible to a committee. "Multiple teams" and "minimal disruption" are the two phrases that most reliably mean "I did not measure this".

Strong version:

Our auth provider announced end-of-life with 9 months notice, affecting 14 services across 5 teams. I owned the migration end to end: wrote the design, negotiated the sequencing with the Growth and Platform teams, and built the dual-write layer that let us cut over without downtime. We finished 6 weeks early with zero customer-facing incidents and removed $140k of annual licence cost. Platform have since reused the dual-write pattern for their database migration.

Every vague phrase became a number or a name. "Multiple teams" became 5 teams, with two of them named. "Minimal disruption" became zero incidents. And the last sentence does the heavy lifting for a senior or staff case: the work outlived the project.

Example 3: Leadership without a title

The section people find hardest, because most of them are individual contributors and assume they have nothing to write.

Weak version:

I mentor junior engineers on the team and am always happy to help people. I do a lot of code reviews and try to give constructive feedback.

Strong version:

I mentored two engineers this year. Priya joined with no distributed systems background and now owns our event pipeline; she shipped the consumer rewrite solo in Q3. I also rewrote our code review guidelines after noticing review latency was our biggest delivery bottleneck. Median time to first review across the team dropped from 19 hours to 5.

The difference: the weak version describes a disposition, the strong version describes an effect on named people and a number that moved. You do not need a title to write the second one. You need to have noticed what changed.

What should the whole thing contain?

A complete packet is usually 2 to 4 pages and contains, in this order:

1. Executive summary. 3 to 4 sentences. At least one number. Written last.
2. 3 to 5 accomplishments. Each in the situation, action, outcome, scope shape. Not 12. Committees discount long lists.
3. Key metrics. Pulled out so they are skimmable. The committee should be able to find your numbers in 10 seconds.
4. Leadership and influence. Named people, named teams, what changed for them.
5. Scope statement. An explicit sentence about the level you are operating at, in your company's own language.

What to leave out: responsibilities, job description language, anything you cannot evidence, and any accomplishment you would rank sixth. A shorter packet with five strong items beats a longer one with five strong items and four weak ones, because the weak ones become what the committee argues about.

The pattern across all three

Look back at the three strong versions. None of them describe better work than the weak versions. It is the same work. What changed is that every vague phrase was replaced by something checkable: a number, a name, a team, a date, a before and after.

That is the whole craft. Committees cannot evaluate adjectives. Give them something to verify and you have made it easy to say yes.

For the structure behind these examples, read how to write a promotion packet, or see what promotion committees look for.