What Your Employer Is Actually Deciding
When you ask for more money because your scope grew, you're asking your employer to look again at where your role sits inside its own pay structure. SHRM publishes guidance for employers on running job evaluations and building fair pay structures from them [1]. WorldatWork calls the larger system job architecture, and describes it as the hierarchy of jobs inside an organization: job levels, job titling conventions, grades, career paths, spans of control, and the criteria for moving between them [2].
Two different budgets sit behind that structure, and they behave differently. The annual merit pool is the smaller one. SHRM reported employers projecting an average salary increase budget of 3.5% for 2026, after delivering an average merit increase of 3.2% in 2025 [3]. A level change is a separate decision, made against the structure rather than out of the merit pool.
So the number you get depends on which decision you triggered. Ask for a merit increase when the work moved a level, and you'll get a percentage that has nothing to do with what you're carrying.
Build the Evidence Before You Build the Ask
The step people skip here is Look, the first step of L.A.T.T.E., and Look is not a feeling about how busy the year was. It's a file. When I teach the achievement portfolio I tell people it's a financial brief, not a brag sheet. A brag sheet lists what you did. A financial brief translates what you did into what it was worth. A scope conversation adds one more requirement on top of that: you have to show the work is permanent, not a hard quarter.
Put two documents side by side: the job description you were hired into, and the last three months of your calendar. For every responsibility that isn't in the first document, write three things.
- What you own. The decision, the budget, the relationship, the system. Name the thing that would have to be handed to someone else if you left tomorrow.
- When it moved to you. A date, or the project that carried it over. This is the line that separates a role that changed from a busy stretch.
- What it produced. Not the task, the outcome. Not 'led the vendor migration' but 'led the vendor migration that cut processing costs by 15%.' Cycle time before and after. Contract value. Headcount you onboarded. Errors that stopped happening. Where you don't have the number, write down who does, then go get it before the meeting.
Two more pieces belong in the file. Pull any written feedback that names the expanded work, from a review, a skip-level, a note from a stakeholder. And get one sentence from someone outside your team who depends on that work, in their words, describing what you do for them. A cross-functional partner saying 'she runs our intake' carries weight your own summary can't.
Which Conversation Is This: Raise, Title, or Promotion
Before you decide what to ask for, look. That's step one of L.A.T.T.E., and it's the step people skip on their way to a script. What follows is what looking produces: your evidence on one side, the conversation it supports on the other.
There's a difference between doing more work, doing work at a higher level, and being ready for a different role. Those situations overlap. They aren't the same conversation, and what follows is a preparation tool rather than a formula for what your employer will decide.
- Your role is substantially the same, but your workload expanded for a temporary period. Start with a scope and workload conversation. You're clarifying whether the work is temporary, how it will be prioritized, and what support is available.
- You're consistently performing higher-level responsibilities, but the title stayed the same. Start with a title and level-alignment conversation. You're clarifying which job level best matches the work, what criteria apply, and what evidence is still needed.
- Your level is appropriate, but your compensation no longer reflects the role, the results, or the market. Start with a compensation conversation. You're clarifying how pay decisions get made, what documentation is relevant, and when the next review happens.
- You're targeting a role with broader people, budget, or enterprise accountability. Start with a promotion-readiness conversation. You're clarifying what the next role requires and how your readiness will be evaluated.
- You don't know which of these is true. Start with a fact-finding conversation. You're clarifying what your current level is, what your role is expected to cover, and what a realistic next move would require.
A grounded opening can sound like this: 'Over the last year, my responsibilities have expanded in three ways: scope, decision-making, and business impact. I want to understand how this work maps to my current role and what the right next conversation should be, whether that is title, compensation, promotion readiness, or a development plan.'
That doesn't assume an answer. It gives your manager something concrete to respond to.
Ask for the Meeting, Not for the Raise
Send the request about a week ahead and say what it's for. Your manager needs time to read your documentation and talk to whoever else has to sign off, and a manager who gets ambushed will default to the safest answer available.
Something like: 'Can we put thirty minutes on the calendar next week for a compensation and role conversation? My responsibilities have changed since my job description was written and I'd like to walk you through it. I'll send my notes ahead so you have them.'
In the room, lead with the work. Walk the evidence in the order you built it, own the decisions plainly, and let the artifacts do the arguing. Then say what you're asking for: a compensation review, a level review, or both, by name. Then stop talking. The silence after your ask belongs to your manager.
The objection you're most likely to hear is that your number sits above the range for this role. The answer is not to argue the range. Bring the outcomes that show you're already operating above the role, and ask what it would take to be leveled where you actually work. That question is the whole bridge. It moves the conversation from what you want to how their own structure works.
If the room drifts toward feelings, anchor back: 'I understand your perspective, and my request is based on the value I bring and what the market shows for this work.' You're not arguing. You're returning to the evidence every time.
When the Answer Is Not Now
Budget freeze. Cycle timing. 'Let me take it to HR.' All three are real, and all three are also where a good case goes to die if you accept them as the end of the conversation.
Ask three questions before you leave. What would need to be true in the record for this to be a yes. When the decision actually gets made. Who makes it. Then send the follow-up email the same day, summarizing what you asked for, what your manager said, and the date you agreed to revisit.
That email is the record. If a second review comes and goes with no date and no criteria attached, you have learned something about the structure you're working inside, and you can plan around it.
A documented scope case doesn't guarantee a raise or a title change. Compensation budgets, job architecture rules, and review policy decide the outcome. What the file changes is whether that decision gets made with your evidence in the room or without it.