Nobody hands you a bigger job. It arrives one urgent thing at a time. A project manager picks up the vendor budget for the whole department. An operations specialist starts building the training program every new hire runs through. A senior analyst becomes the person legal calls before anything ships. None of it came with a memo, and the job description you signed quietly turned into a historical document.
Your calendar changed. Your title didn't, and neither did your pay. By the time you notice, you have been doing the bigger job for free for two years.
Most people do one of two things with that gap. They sit on it for another year, or they bring it up badly, in a hallway, at the end of a meeting about something else. Both cost the same thing: a decision made without your evidence in the room. What follows is how to build the evidence, name which conversation you are actually in, and ask for the review by name. For the full arc behind it, the mid-career salary negotiation guide teaches the L.A.T.T.E. system step by step.
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.