You know your team member deserves a promotion. They have been doing the work, delivering results, and stepping up consistently for months. So you walk into the promotion committee meeting, make your case, and get told no. Not because the person was not good enough, but because your case was not strong enough. This happens far more often than it should. The gap is rarely about the person. It is about how the argument was built, and when you started building it.
A promotion case is not a favour you do for someone. It is a structured argument backed by evidence that you have been collecting over time. Start too late and you will not have enough to work with.
Why Promotion Cases Fail
Most promotion cases fail for one of three reasons. The evidence is too vague, the timing is wrong, or the argument is framed around tenure rather than impact. Saying "they have been here for two years and work really hard" is not a promotion case. It is a statement of loyalty. Promotion committees want to see that someone is already operating at the next level, with specific examples to prove it. Without that evidence, even the strongest candidate gets a "not yet."
Weak promotion case
No evidence. No impact. Easy to reject.
Strong promotion case
Specific. Measurable. Already at the next level.
The other common mistake is waiting until the review cycle to start gathering evidence. By then, you are relying on memory, and memory is unreliable. You will forget the project they rescued in March. You will miss the feedback a stakeholder gave in passing. The best promotion cases are built continuously, not constructed in a rush the week before the deadline. If you are already running regular performance reviews, you will have a head start.
Building Evidence Over Time
The strongest promotion cases are built across months, not weeks. Every catchup, every project milestone, every piece of peer feedback is a potential data point. The trick is capturing it when it happens rather than trying to reconstruct it later. Keep a running log of moments that demonstrate next-level behaviour. When your team member leads a cross-functional initiative, note it. When they receive positive feedback from a stakeholder, record it. When they coach a colleague through a problem, write it down.
A good development plan makes this easier because it gives you a framework. If you have already agreed on what growth looks like for this person, every piece of evidence maps to a specific area. You are not just collecting random positives. You are building a narrative that shows deliberate progression. Use Targets to track development goals alongside the evidence that supports them, so nothing gets lost between conversations.
Evidence timeline
Five months of evidence tells a story. One week of memory does not.
Talk to peers and stakeholders throughout the year, not just at review time. A casual "how did that collaboration go?" after a project wraps up often yields the kind of specific, attributable feedback that promotion committees value. Document it while it is fresh. You are creating a portfolio of evidence, and the richer it is, the harder it is to argue against.
Structuring the Argument
A promotion case needs structure. Dumping a list of achievements on a committee and hoping they connect the dots is not a strategy. Start with the role expectations at the next level. Then map your evidence to each expectation, showing that this person is already performing there. The goal is to make the committee feel like approving the promotion is simply catching up with reality.
- Current vs next levelShow clearly what the next role requires and how your team member is already meeting those expectations. Use the organisation's competency framework if one exists. If it does not, define the gap yourself and show how it has been closed.
- Impact over activityDo not list tasks. Show outcomes. "Led the migration" is activity. "Led the migration, which reduced deployment time by 40% and unblocked two other teams" is impact. Committees remember impact.
- Third-party validationYour opinion matters, but peer and stakeholder feedback carries more weight. Include direct quotes where possible. "Their manager thinks they are great" is expected. "The head of product said they were the most effective partner they worked with this year" is evidence.
- Growth trajectoryShow progression over time, not just a snapshot. Where were they a year ago? What have they taken on since? A clear upward arc is more persuasive than a single impressive project.
Write the case document as if you will not be in the room when it is read. Many promotion decisions happen in calibration sessions where you are not present. The document needs to stand on its own. Be specific, be concise, and make every sentence earn its place. Recognition that is specific and timely builds the foundation for a case that feels genuine rather than manufactured.
Handling Rejection
Sometimes the answer is no. That does not mean the case was bad or the person is not ready. It might mean the budget was not there, the timing was off, or the committee wanted to see one more quarter of evidence. What matters is how you handle it with your team member and what you do next.
After a "not yet"
Be transparent with your team member. Tell them you made the case, share what the feedback was, and work together on what comes next. Nothing erodes trust faster than vague reassurances or silence. If you promised to fight for them, show them you did. If there are genuine gaps to close, be honest about those too.
A rejection is not the end. It is a data point. Use it to make the next case airtight. The best managers treat a "not yet" as a brief pause, not a permanent verdict. Keep collecting evidence, keep having the conversations, and come back stronger.
Frequently asked questions
Track development goals
Use Targets to build promotion evidence over time. Free to start.