A promotion packet is much easier to assemble when the underlying evidence already exists. Without that, you end up with vague bullets, missing examples, and a manager who has to translate your work from memory. The hard part of deciding what to include in a promotion case is starting with a record of real work, not just a feeling that you had a strong cycle.
The steps below move in order from raw material to a case another person can repeat clearly. That is the standard to aim for.
Step 1: Name the level you are trying to prove
A promotion case is not a summary of everything you did. It is an argument that your work already matches the next level often enough to be credible.
Write down the few expectations that matter most in your environment. They usually cluster around scope, independence, judgment, cross-functional influence, and durable impact. Once those are visible, you can stop collecting random achievements and start selecting evidence that maps to the case.
Step 2: Choose three to five examples that carry the argument
You do not need every project. You need the examples that best show the pattern.
Pick work that demonstrates different dimensions of readiness. One example might show ownership of an ambiguous problem. Another might show influence across teams without formal authority. A third might show that your decisions improved quality, speed, reliability, or customer outcomes over time.
If all your examples prove the same thing, the case will feel narrow even if each example is good on its own.
Step 3: For each example, define the business or team problem first
Reviewers need context before they can value your contribution. Start each example by explaining what needed to change and why it mattered.
Keep this part brief but concrete. Instead of "worked on reporting improvements," say that the reporting process was too slow for planning decisions, or that recurring confusion between teams was blocking execution. A clear problem statement makes the rest of the story easier to follow.
Step 4: Separate your ownership from group activity
This is one of the most important parts of what to include in a promotion case. Shared work is normal. Blurry ownership is what weakens the case.
Spell out what you specifically drove. That can mean framing the problem, making the key decision, coordinating partners, defining the approach, resolving a blocker, or carrying execution through a risky phase. If the result came from a team effort, say so, then identify the part that would not have happened the same way without you.
A reviewer should be able to answer, in plain language, why your contribution was material.
Step 5: Show the result in a form another person can repeat
Outcomes can be quantitative or qualitative, but they need to be specific. If you have durable metrics you are allowed to reference, use them carefully. If not, describe observable change: fewer escalations, faster decisions, cleaner handoffs, stronger adoption, less rework, or more reliable execution.
Good promotion evidence travels well. When your manager explains your example in a room you are not in, the result should still make sense.
Step 6: Add proof that anchors the claim
Strong cases do not rely on assertion alone. Attach or reference the evidence behind each example in a safe, lightweight way.
That proof may include:
- a launch or project summary you wrote
- notes from partner feedback
- a before and after description of process performance
- written recognition tied to a specific outcome
- a short explanation of a key decision and its effect
Keep private company material and sensitive customer details out of your personal system. Save enough detail to support the claim without copying restricted information.
Step 7: Make the level signal explicit
Do not assume the reviewer will infer the promotion point from a good project story. After each example, state which next-level behavior it demonstrates.
Maybe the example shows broader scope than your current band, stronger independent judgment, or repeated influence beyond your immediate lane. This translation step is where many strong contributors lose clarity. They present impressive work but never connect it to the level decision.
Step 8: Build a short pattern summary across the examples
A promotion case works best when the examples add up to a recognizable pattern. End your packet with a concise synthesis of what the set proves.
For example, you might show that across multiple efforts you consistently took ownership of ambiguous work, aligned partners, made sound tradeoffs, and produced outcomes that lasted beyond a single deliverable. The summary helps the reviewer move from isolated stories to a promotion judgment.
Step 9: Test the case like an interview answer
One useful drill is to hand your examples to a trusted peer and ask them to play reviewer. Can they explain the problem, your ownership, the impact, and the level signal without extra coaching from you?
If they get lost, the case is not ready. Weak promotion packets often have the right ingredients but in the wrong shape. This test shows where context is missing, ownership is muddy, or proof is too thin.
A promotion case is stronger when someone else can retell it accurately without you in the room.
Step 10: Keep capturing while the case is in flight
Promotion decisions rarely depend on one static document. New evidence can appear while the packet is being discussed, revised, or deferred.
That is why a lightweight capture habit matters. ImpactLogr is useful here because one well-structured entry can later become a self-review bullet, a promotion example, or material for an interview loop. The capture work is the same. The reuse is what saves you time.
If you want a cleaner way to organize examples before the next review cycle, try setting up an ImpactLogr workspace for promotion evidence.