Direct answer
I treat it as a small negotiation with my manager, not a complaint. I go in with a one-page evidence summary that maps my work to the next level's written expectations, one specific ask, a reason the timing works for the manager's own budget cycle, and a ranked list of fallbacks I would accept. If the manager cannot deliver the first ask, I do not argue the ask again. I convert it into a dated, written commitment (criteria, date, owner) that I can hold us both to.
Step 1: Decide which of the four asks you are actually making
Promotion-linked title, a compensation change, a change in scope, and a learning budget are different negotiations with different decision makers. A manager can often approve a learning budget alone, can propose a scope change, but usually needs HR (human resources) and a calibration committee (a group of managers that compares people for fairness) for a title or pay change. Naming which one you want tells you who has to say yes and how long it takes.
Step 2: Build the case (about one page)
| Part | What goes in it | Why a manager needs it |
|---|
| Level evidence | 3 to 5 outcomes from the last 6 to 12 months, each tied to a line in your company's level guide (the written description of what is expected at each job level). A filled-in line looks like: "Expectation (Level 3 to 4): leads a project across more than one team. Evidence: led the billing migration across three teams, finished two weeks early, no customer incidents." | The manager has to defend you to people who were not there |
| Scope delta | Responsibilities you now hold that were not in your original role (on-call rotation, mentoring two newer colleagues, a new system you own) | This is the strongest argument when scope has drifted upward |
| Market or internal data | Only data you can source (a published band for your level, meaning the pay range for that level, for example a posting that says "$95,000 to $120,000", or peer roles on internal postings, cited with where you found it). Label anything uncertain as an estimate | Keeps the talk about a range, not about a feeling |
| The ask | One sentence: "I would like to be considered for the next level at the next cycle, or a title and scope change now" | A vague ask gets a vague answer |
| Cost to the company | What happens if the work stays the same and the role does not | Frames it as retention and clarity, not a threat |
Step 3: Run the conversation
- Book 30 minutes titled "career and scope" a few weeks before the budget or review cycle closes, so the manager can still act.
- Open with the goal, then ask for the gap, not the verdict:
"I want to grow into the next level here. Over the last two quarters I took over the release process and I am the second on-call escalation. Looking at the level guide, where do you think I am already meeting it, and where is the gap?"
- Listen for the real objection: budget, headcount, a missing skill, or visibility. Each has a different remedy.
- State the ask and stop talking:
"Given that, I would like to be put forward for promotion at the next cycle. What would you need to see from me to do that with confidence?"
- Confirm in writing the same day: "To confirm, we agreed X by date Y, and you will take it to the calibration committee in month Z."
Step 4: The fallback ladder (decided before the meeting)
Rank these in advance so a "no" is not a surprise:
- Promotion at the next cycle, with written criteria and a named sponsor (a senior person who backs your case in the promotion discussions).
- Scope and title change now, pay review at the cycle.
- A one-time item the manager controls (a spot bonus, which is a one-off cash award; an extra equity grant, meaning shares or share options; or extra leave) if the budget allows.
- Stretch scope for six months with a documented checkpoint, so the work is on record for the cycle.
- A learning budget or conference place that closes the named skill gap.
If I get nothing concrete and no date after the written follow-up, that is itself information: the role may not grow here, and I should weigh outside options (my walk-away point, meaning the point at which I would take another offer).
Worked example: the training budget version (illustrative numbers)
Suppose I ask for a cloud certification course. Cost to the company: course $3,000 plus 24 hours of work time at an assumed loaded rate of $60 per hour (loaded rate is the full hourly cost of an employee to the company, including benefits and overhead, so it is higher than the pay rate) = $1,440, total $4,440. I propose a project afterwards that cuts a monthly cloud bill by an estimated $2,000 per month. Payback period (time to recover the cost) = $4,440 / $2,000 per month = 2.2 months. I argue it in payback terms because a manager defending a spend to a budget holder is asked how soon it earns itself back, a number I show as an estimate with the assumption written next to it. I also offer a condition: I will give a 30-minute internal talk and write up the saving.
Worked example: scope has shifted
Role description says "build and maintain data pipelines". Over six months I also became owner of the on-call rota and the vendor relationship. I list the two additions, estimate hours per week (say 6 of 40), and ask: "Either we adjust the role and title to include this, or I hand one of these back." Offering both options shows I am not demanding, and the manager picks the cheaper one for them.
Trade-offs and pitfalls
- Never anchor (set the starting number the whole conversation is measured from) on another colleague's pay or on a competing offer you will not take. It ends the trust the ask depends on.
- Asking in the review meeting itself is too late: budgets and calibration are usually set before it.
- A verbal "we will look at it" is not a fallback. Convert it to a dated written step.
- What would change my approach: if the manager is clearly not the decision maker, I ask who is and request a skip-level conversation (a meeting with my manager's manager), politely and openly.
