Promotion Case-Building Checklist
A strong promotion case isn't written in the two weeks before a cycle opens. It's built in the months between, in the projects you take on, the visibility you create, and the evidence you save while it's still fresh. This is the groundwork that makes the eventual ask a formality instead of a surprise.
Key Takeaways
- Start documenting wins the week they happen, not the week before the cycle opens. Evidence written in the moment is specific and defensible. Evidence reconstructed from memory months later is vague and easy to dismiss.
- Visibility isn't self-promotion, it's making sure the people who influence the decision actually know what you did. Most promotion cases fail because the calibration room doesn't know the work, not because the work was weak.
- Take on scope that maps directly to the next level's criteria, not just more work. Extra hours on tasks at your current level don't build a case for the next one.
- Treat the months between cycles as the real work of a promotion case. By the time you formally ask, the evidence and the visibility should already exist, not be something you're scrambling to assemble.
The Checklist
Work through it in order. Tick things off as you go and your progress is saved on this device, so you can come back to it over the days before the conversation rather than doing it all in one sitting.
-
Get the next level's criteria early, not right before you ask
You can't aim at a target you haven't seen. If you don't already have the leveling framework or a clear sense of what the next title requires, get it now, months before you'll need it.
- Find or request the internal leveling guide or career framework for your role.
- If none exists, ask your manager directly what they'd need to see from someone at the next level.
- Translate the criteria into things you can point at: a project type, a scope of ownership, a kind of decision you'd be trusted to make.
-
Log evidence as it happens, not from memory later
The single biggest difference between a strong case and a weak one is whether the evidence was captured close to the event. A win you can describe with specifics and a number beats one you can only describe as "I did well on that project." This is the exact gap Perform Review's Achievement Log is built for: log the win the week it happens and it's already there, specific and dated, when you need it.
- Write down outcomes the week they happen: what you did, the result, who noticed.
- Save specific numbers, timelines, and outcomes rather than general summaries.
- Note who was in the room or affected. Named stakeholders make evidence far more credible than an unnamed "the team."
-
Take on scope that matches the next level, not just more of your current one
More hours on your current type of work doesn't build a promotion case. The work that counts is the kind the next level is actually responsible for, even in a small dose.
- Identify one project or responsibility this quarter that stretches into next-level territory: cross-team ownership, mentoring, a decision with real consequences.
- Ask your manager directly if a specific opportunity would count toward the case, before you take it on, not after.
- Avoid volunteering for more of what you're already good at if it doesn't move the case forward. It feels productive and often isn't.
-
Build visibility with the people who'll actually be in the room
A promotion decision usually gets discussed by people who aren't your manager alone. If they don't know your work, your manager is arguing your case with weaker material than they should have.
- Identify three to five people whose opinion will likely be asked for in that discussion.
- Make sure each of them has seen recent, direct evidence of your work, not secondhand summaries.
- Look for natural ways to create that visibility: presenting your own work, contributing in cross-team settings, writing up outcomes where others will see them.
-
Keep the conversation with your manager ongoing, not seasonal
A promotion ask that only comes up once a year, right before the cycle, reads as a surprise even when the work has been there all along. Naming the goal early gives your manager time to build a case, and time to tell you honestly if you're off track.
- Mention the goal explicitly in a 1:1 well before the formal cycle, not for the first time inside it.
- Ask periodically whether the work you're doing is actually landing as next-level work, or just more of the same.
- If your manager flags a gap, treat it as the most useful information you'll get, not a setback. It tells you exactly what the next few months should close.
-
Check your case against the criteria periodically, not just once
Momentum on a promotion case can quietly stall for months without anyone noticing, especially if the work is good but not mapped to what actually counts.
- Every month or two, hold your running evidence up against the leveling criteria and look for gaps that are still empty.
- If a criterion has been thin for two check-ins in a row, treat that as the priority for the next stretch, not something to hope resolves itself.
- Keep a short running document rather than trying to reconstruct the last six months from memory when the cycle finally opens.
That is the whole checklist
Everything above is general by design, so it holds for most people in most companies. The specifics of your own case are the part it cannot cover.
Work through this against your own situation
The Perform Review AI Career Coach does two things this page cannot, because both are built from your own logged wins and your own reviews.
Guides: When your review is written, your AI Coach can turn it into preparation for the meeting itself: talking points anchored to your strongest evidence, the honest gaps between your case and your ask, the pushback you are likely to get with answers to it, and a script you can say out loud.
Monthly Sessions: A coaching session every month against the goal you set: where it stands, what moved, what is blocking you, and what to focus on next. Reply to any part of it and the AI Coach answers on that specific point.
Both are included with and exclusive to Pro. See Pro.