Talk about growth without promising a promotion
Keep career aspirations, verified criteria and your next information request separate, so a useful 1:1 does not imply a promotion guarantee.

“Will I be promoted if I take this on?”
You want to encourage your direct report. You can offer a useful project, help them understand expectations, and ask the people who make the decision. You may still have no authority to promise the title.
The difficult part is keeping those statements separate while sounding like someone who intends to help. “Let’s get you ready for the next level” can mean preparation to you and a commitment to them. Before you close the conversation, make the next move clear enough that neither person has to guess what was agreed.
Check the process before offering reassurance
Start with what your organisation actually uses: the current role expectations, who can confirm them, and who makes the promotion decision. If you have an approved process, use it. If a criterion is missing or unclear, write down the question you need answered. Do not fill the gap with your own unofficial career ladder.
Then distinguish what you know from what you expect. You may have seen someone handle a complex handover well. That is an observation about their work. It does not establish that a role is available, that a decision maker agrees, or that a promotion has been approved.
GitLab’s public 1:1 guidance recommends focusing on current skill development and opportunities when a career conversation could be understood as a promotion promise. That is a useful prompt for preparation, not a replacement for your employer’s process.
A learning opportunity also needs its own reason to exist. Ask which work the report wants to learn and whether the opportunity is useful to them. Avoid presenting extra responsibility as an exchange for an outcome you cannot authorise.
Say what you can do, and name what remains unknown
Here is a fictional example, not a customer conversation or a promotion policy.
A direct report wants to move into a senior role. Their manager can ask for the current criteria and arrange a discussion about a suitable learning opportunity. The manager cannot approve the promotion.
A response to adapt might be:
I understand that a senior role is what you want to work towards. I can help you understand the current expectations and discuss work that would help you develop. I cannot confirm a promotion or a date today. I will ask who makes that decision and which criteria currently apply, and bring the information back at our next 1:1.
If you already know who decides, name that process rather than acting as if everything is unknown. If the answer is a confirmed no, say so plainly; a request for information must not become a way to keep someone waiting for an outcome you know is unavailable.
The date in that response belongs to the manager’s update. It is not a date for advancement. Choose a return date you can reasonably keep, even if the update turns out to be “I asked, and I do not yet have an answer.”
Write a recap that preserves the distinction
A note reading “Senior promotion — next 1:1” loses the meaning of the conversation. The next reader cannot tell whether that is an ambition, a decision, or a follow-up request.
For the fictional example above, a clearer recap would keep these statements distinct:
- Aspiration: The report wants to explore a senior role.
- Criteria: Current criteria have not yet been verified. The manager will obtain the applicable document or confirmation from the authorised person.
- Learning opportunity: Discuss a suitable opportunity after clarifying the report’s interests and the relevant expectations. No assignment or exchange for a title has been agreed.
- Manager’s next action: Ask who decides and which criteria apply; report back at the next 1:1.
- Decision: No promotion or promotion date has been confirmed.
These are labels for this example, not a new required form. If your process already answers a question, replace the unknown with the verified answer. Keep the note as short as the situation allows, within your organisation’s rules for what should be recorded and who may see it.
Before saving it, read the action back together: “Is this the next step you understood us to agree?” A shared recap is only useful if it preserves the actual conversation.
1on1 presents guided agendas, written session context, tracked actions and recurring follow-up. In this situation, that workflow gives the manager a place to retain the information request and return to it in the next conversation. The value comes from the wording you put there: a tracked item called “Approve promotion” still says the wrong thing if you only agreed to ask about criteria.
Return with the information, even when the answer is incomplete
At the next 1:1, bring what you found and distinguish it from what you still need to check. “I received the current role expectations; the decision owner has not yet confirmed the review process” is more useful than “It’s progressing.”
If the answer is delayed, name the remaining question and your next action. Do not quietly roll the item forward as if silence were approval. Your report can then decide what further questions to ask and whether the proposed learning opportunity still fits their goals.
If your earlier wording implied a guarantee, correct the implication directly. Explain what you can actually commit to and acknowledge the difference from what the report understood. A tidier note alone does not repair a misleading conversation.
The next career 1:1 does not need to end with a promised title. It can end with a clear account of the report’s aspiration, what is known, who will obtain the missing information, and when you will return to it.
Before that meeting, check the real internal process. Afterwards, review the exact recap together. If you are exploring a recurring written workflow for those conversations, read about 1on1 with this specific question in mind: can you keep the information request distinct from the eventual decision?
Sources
- GitLab Handbook — 1:1s: organisational guidance on career-development conversations and promotion expectations.
- 1on1: product workflow described in its authorised product sources. This article makes no claim about current prices, plan access or promotion outcomes.
Next step
Test it with one manager and one direct report
Start free and keep this article context through the registration step.
Start free