Short answer
Tell the employee clearly that the answer is ‘not now’, explain the decision using published next-role requirements and observable evidence, and separate readiness from role availability or process constraints. Acknowledge the aspiration, invite questions, agree one or two development priorities and a bounded work experiment, then set a review date. Never imply that development guarantees promotion.
1. Separate readiness, role availability and selection
Before planning the conversation, identify which decision you are actually communicating. Readiness asks whether the employee currently demonstrates the requirements of the next role. Availability asks whether there is an approved role, scope or budget. Selection asks how eligible candidates will be compared through the organisation’s process. An employee can be ready when no role exists, or developing well without yet meeting the next-role standard. Conflating these questions damages trust: the employee receives development feedback when the real barrier is structural, or hears an apparent promise when a competitive process still lies ahead. Write one sentence for each question and check it with HR or the relevant decision owner when the process is not yours alone. The employee should leave knowing which conclusion is current, which factors may change and which decisions remain outside the manager’s authority.
- Readiness: what next-role work can the employee perform consistently now?
- Availability: does an approved role, scope and budget exist?
- Selection: who decides, against which criteria and through what process?
2. Prepare evidence against the work—not a personality impression
Start with the role description, capability framework or published promotion criteria. Translate broad labels into observable work. Instead of ‘needs more leadership presence’, specify the situation and evidence: for example, framing a cross-functional decision, surfacing disagreement, making a recommendation and closing with owners. Gather more than one example and look across a reasonable period; a single memorable success or failure can distort judgement. Also test whether the standard is being applied consistently. Singapore’s Ministry of Manpower describes fair employment practice in terms of merit, respect, equal development opportunity and fair reward based on ability, performance, contribution and experience. CIPD’s current selection guidance likewise recommends clear, objective, structured and transparent processes. These principles do not decide an individual promotion, but they are a useful quality check for the evidence you use.
- Use requirements that belong to the next role, not a manager’s preferred style.
- Describe behaviour, output and impact in context; avoid labels such as ‘not strategic’ or ‘not mature’ without evidence.
- Check for comparable standards across employees and for reasonable access to opportunities that produce evidence.
- Distinguish sustained demonstration from one-off exposure or visibility to senior leaders.
3. Say ‘not now’ clearly, then explain the decision
Do not make the employee decode the answer from a long preamble. Open with respect and clarity: ‘I know this progression matters to you. The decision is that you are not ready for promotion to the team-lead role at this point. I want to explain the evidence and agree what would help you test readiness.’ Then pause. State the two most important role requirements, share relevant examples and invite the employee’s perspective. Clarity is not cruelty; vague reassurance can be more damaging because it encourages false expectations. Keep the conversation focused on the decision and the work. Do not compare the employee with a named colleague, speculate about motives or present hearsay as fact. If a panel or senior leader made the decision, explain your role honestly and do not hide behind ‘they decided’. Take responsibility for helping the employee understand the process and next steps.
4. Turn each gap into a readiness statement
A useful readiness statement connects a next-role requirement to evidence and a threshold. Use the pattern: ‘In the next role, you would need to [observable work] in [relevant conditions]. I have seen [current evidence]. I have not yet seen enough consistent evidence of [missing behaviour or output]. Readiness would look like [specific standard].’ This makes disagreement discussable. The employee may have evidence you did not see, or may challenge whether the requirement is relevant. Listen and update your view when warranted. Current performance still matters, but excellence in the current role is not automatically evidence of every requirement in a different role. Promotion should not devalue expert contribution or assume management is the only meaningful path. Where specialist pathways exist, discuss them as real options rather than consolation prizes.
5. Design a bounded development experiment
Do not end with ‘keep doing what you are doing’ or a vague instruction to show more leadership. Choose one or two priorities and create a work experiment that resembles the target responsibility without handing over an unsupported acting role. CIPD’s succession-planning guidance highlights practical, tailored work experience, job moves and secondments as development options, while warning that these need planning and support. Define the assignment, decision rights, success evidence, support, time boundary and review point. Access must be fair: if only already-favoured employees receive visible stretch work, the evidence system will reproduce that advantage. A development assignment should create learning and credible evidence—not free labour or an indefinite audition.
- Assignment: one real piece of next-role work with a clear boundary.
- Authority: what the employee may decide, recommend or escalate.
- Evidence: the work product, stakeholder observation or outcome that will be reviewed.
- Support: sponsor access, coaching, feedback, tools and protected time.
- Boundary: a start, end and review date, plus what happens to the extra scope afterwards.
6. A fictional workplace example
Consider Mei, a high-performing regional key-account manager who wants to become a team lead. Her manager recognises her strong client results but explains that the next role also requires coaching peers and making resource trade-offs across accounts. The evidence is mixed: Mei has informally helped colleagues, but has not yet led a difficult account review or coached someone through a sustained performance issue. They agree an eight-week experiment. Mei will facilitate two portfolio reviews, coach one consenting peer on account planning and recommend one resource trade-off. Her manager will observe the first review, hold fortnightly debriefs and gather structured feedback with Mei’s knowledge. At the end, they will review the agreed evidence. The manager is explicit: successful completion strengthens the readiness evidence, but it does not guarantee a vacancy, selection or promotion. This is an illustrative fictional example, not a SEED client outcome.
7. Handle disagreement without turning the meeting into a verdict
The employee may disagree, become quiet or ask why someone else progressed. Acknowledge the response and ask what evidence or interpretation they see differently. Correct factual errors when you can, and write down questions that need checking. You can say, ‘I hear that you see the stakeholder example differently. Let us review the stated requirement and the available evidence, and I will come back by Friday on the process question.’ Do not debate confidential information about another employee. If the employee raises inconsistent criteria, bias, discrimination, retaliation or a formal grievance, pause the developmental discussion and use the appropriate HR or grievance route. This page is management guidance, not legal advice; policies and obligations vary by organisation and jurisdiction.
8. Review evidence without promising the outcome
Set the review meeting before the conversation ends. Record the requirements, experiment, support, evidence and date in language both people understand. At the review, ask what changed in the work, what the employee learned, what evidence now exists and which questions remain. The result may be ready, still developing or unable to assess because the employee did not receive the agreed opportunity. Treat that third outcome as a system issue, not an employee failure. Be precise about what a positive readiness assessment means: it may make the employee eligible or competitive, but it may not create a role or replace a formal process. If the organisation’s plans change, say so early rather than moving the criteria silently.
The SEED Promotion Readiness Path
Move from a decision the employee can understand to development evidence both sides can review. The path supports a conversation; it does not replace your organisation’s promotion policy or a formal selection process.
Role
Clarify the next role, its requirements and the decision process.
Evidence
Compare observable work with those requirements, not personality or visibility.
Answer
Say ‘not now’ clearly and distinguish readiness from role availability.
Development
Choose one or two priorities, support and a bounded work experiment.
Review
Agree what evidence to review, when and with whom—without promising promotion.
Diagnose the real promotion situation before you speak
A promotion conversation becomes misleading when a manager uses ‘not ready’ to describe a vacancy, budget or process problem. Name the real constraint and choose the right response.
| Situation | What to say | Useful next step |
|---|---|---|
| The employee is not yet ready and a role may be available | Explain the specific next-role requirements and the evidence that is not yet consistent. | Agree a bounded work experiment, support, evidence and review date. |
| The employee appears ready but no suitable role or budget exists | Name the organisational constraint. Do not invent a capability gap to soften the message. | Discuss credible lateral scope, projects or future processes without promising a date. |
| The employee is already carrying materially expanded scope | Acknowledge the work and separate recognition, workload and pay questions from a future promotion decision. | Review role design and reward with HR rather than using development language to delay action. |
| Criteria or comparisons are unclear or inconsistent | Do not improvise a definitive explanation you cannot support. | Pause, check the policy and evidence with HR, then return with a consistent answer. |
| The employee raises discrimination, retaliation or a formal grievance | Listen, record the concern accurately and avoid arguing the case in the meeting. | Use the organisation’s formal HR or grievance route promptly. |
Common mistakes
- Using vague labels such as ‘not ready’, ‘not strategic’ or ‘lacks presence’ without role-based evidence.
- Inventing a capability gap when the real constraint is no role, headcount or budget.
- Treating strong current-role performance as automatic proof of every next-role requirement—or discounting that performance entirely.
- Comparing the employee with a named colleague or disclosing another person’s confidential process.
- Making access to stretch work depend on informal visibility, similarity or manager favour.
- Adding next-role responsibilities indefinitely without authority, support, recognition or a boundary.
- Promising that completing a development plan will result in promotion.
- Ending the conversation without a written next step and review date.
Practical checklist
Name the target role and use its current published requirements.
Separate readiness, role availability and selection in writing.
Check the decision owner, policy and process with HR where needed.
Prepare two or more observable examples across a reasonable period.
Test whether the criteria and opportunities have been applied consistently.
State ‘not now’ clearly near the start of the conversation.
Invite the employee’s evidence, questions and different interpretation.
Agree no more than one or two development priorities at a time.
Define the work experiment, authority, evidence, support and boundary.
Set a review date and explain that no promotion is guaranteed.
Promotion-readiness conversation planner
Use this prompt to turn role requirements and work evidence into a fairer conversation plan. Remove names, client information and confidential employee data before using any external AI tool, and review the output against your organisation’s policy with HR.
You are helping me prepare an evidence-based promotion-readiness conversation. Do not infer personality, protected characteristics or motives.
Current role: [role]
Target role: [role]
Published next-role requirements: [requirements]
Decision owner and process: [owner/process]
Role availability or constraints: [facts]
Observable evidence already demonstrated: [examples]
Evidence not yet demonstrated consistently: [examples]
Possible bounded work experiment: [assignment]
Support I can provide: [support]
Review date: [date]
Create: (1) a concise opening that clearly distinguishes ‘not now’ from no vacancy; (2) two readiness statements linking requirements to observable evidence; (3) five open questions that invite the employee’s evidence and perspective; (4) a development experiment with authority, support, evidence and boundary; (5) language that avoids guaranteeing promotion; and (6) fairness, confidentiality or process questions I should check with HR before the meeting.SEED Academy Promotion Readiness Path · https://www.seedacademysoa.com/resources/answers/how-to-tell-employee-not-ready-for-promotion https://www.seedacademysoa.com/resources/answers/how-to-tell-employee-not-ready-for-promotion
Frequently asked questions
01What should I say to an employee who is not ready for promotion?
Acknowledge the aspiration, state the ‘not now’ decision clearly, explain it against the next role’s requirements and observable evidence, and invite the employee’s perspective. Then agree one or two development priorities, a bounded work experiment, support and a review date. Avoid vague personality labels and do not imply that development guarantees promotion.
02What is the difference between not ready and no promotion opportunity?
‘Not ready’ is a judgement about current evidence against next-role requirements. ‘No opportunity’ means there is no approved role, scope, budget or vacancy. An employee can be ready when no opening exists. Managers should name the real constraint instead of creating development feedback to soften an organisational limitation.
03How specific should promotion-readiness feedback be?
Specific enough that the employee can identify the required work, the evidence considered and what consistent demonstration would look like. Use situations, behaviours, outputs and impact. Protect other employees’ confidentiality, and avoid turning one incident or a subjective style preference into a broad judgement.
04Does completing a development plan guarantee promotion?
No. A development plan can build capability and produce readiness evidence, but role availability, business needs and a formal selection process may still affect the outcome. Say this before the assignment begins, while still honouring the learning and contribution involved.
05What if the employee disagrees with the promotion decision?
Listen for missing evidence, a different interpretation or a process concern. Review the stated requirements and facts, correct errors and commit to checking unanswered questions. Do not debate confidential comparisons. Involve HR when criteria are inconsistent, the process is contested or the employee raises discrimination, retaliation or a formal grievance.
06Can a strong performer be unready for a management promotion?
Yes. The next role may require different work, such as allocating resources, coaching others or making cross-team trade-offs. Explain those requirements without devaluing current performance or assuming management is the only worthwhile career path. Where specialist pathways exist, discuss them seriously.
Sources
Build fairer career conversations
Help managers turn promotion decisions into credible development.
SEED Academy designs practical manager-development journeys around the conversations, decisions and workplace behaviours that matter in your organisation.
Discuss a manager programme