How to ask for a raise after taking on more responsibility

You said yes when someone left or the project grew, and months later you still own the work. The salary conversation never happened, and you're probably waiting for the annual review to fix it, or hoping your manager brings it up first.

This article covers how to show the job actually changed, and what goes in the one-page case. It also covers when to ask, the exact words for the meeting, and what to do when the answer is "no budget." Start the evidence log now, because most of the case gets built before the conversation.

Most of the advice comes from Ethan Evans, who spent 15 years as an Amazon VP and coached a manager named Kristen through this exact case on a live episode: she grew from individual contributor to running two teams, and her evidence packet, follow-up, and research come up throughout this guide. Adam Goyette, a former VP of Demand Generation at G2, explains what he changed after an intern was promoted over him. Chris Voss negotiated hostages for the FBI.

Show that the job changed

Extra effort during a hard month and a lasting expansion of responsibility call for different conversations. Before you build a compensation case, get clear on what changed:

• Duration: Has the work become recurring, or does it have a clear end date?
• Accountability: Are you now answerable for the result, budget, customer, system, or team?
• Decision authority: Are you making calls that previously belonged to someone more senior?
• Reach: Does the role now span more people, functions, customers, or business units?
• Complexity: Are you handling more ambiguity, more risk, or a longer planning horizon?
• Tradeoffs: What did your manager take off your plate to make room?

If the assignment is still officially temporary, ask for clarity before it quietly becomes permanent:

If the added work is mainly volume, more tasks at the same level of responsibility, use the conversation to reset priorities and workload instead. A heavier task list can burn you out without ever supporting a re-leveling case.

Turn the scope change into a one-page case

In a Level Up live-coaching episode about justifying a raise, Ethan Evans worked through a real case with a manager named Kristen. Her role had expanded from individual contributor to manager, then from one team to two. She had secured outside funding for employee training, developed people into new roles, built cross-team partnerships, and estimated her team's work had saved the company hundreds of thousands of dollars.

Evans summarized her strongest evidence as business and people outcomes: money saved, funding secured, people developed, people promoted. Those are facts her manager could carry to the people who approve compensation.

Kristen knew what a persuasive packet looked like because she had already built raise cases for her own reports, and her manager asked her to build the same thing for herself.

Evans advises drafting broadly first, then asking your manager which items will carry the most weight. Start the log before you write the request, and add an entry whenever the role expands or a result becomes measurable:

1. Name the responsibility. Write what you own now and who owned it before. Note whether it is temporary or recurring.
2. Record the reason. Capture the business problem, vacancy, risk, customer need, or leadership request that led to the change.
3. Show the result. Use revenue, cost, time, quality, adoption, reliability, risk, customer impact, or team development when those measures genuinely fit.
4. Save the proof. Link to a dashboard, launch note, customer message, decision document, performance review, or written feedback.
5. Identify the reach. List the teams, leaders, customers, or systems affected by the work.
6. Compare old and current scope. Make the change easy to see in one sentence.

The Mochary Method's Bill Campbell-style performance review is a useful audit for evidence you might overlook: results against goals, management practices, improvements that make future work easier, and collaboration with peers. Its update template also asks people to report whether promised actions were completed and to state the next action for each priority. Doing that on a regular schedule builds the record before the details get fuzzy.

Make the result attributable

Adam Goyette assumed strong work would be visible through his manager. Then an intern was promoted over him, and he learned that the founders could see the marketing results but could not connect those results to his work.

He began sharing concise experiment updates and translating changes into revenue impact. Making your work visible doesn't have to mean bragging. A short weekly update that names the team, the result, the decision, and the next step gives your manager a reliable record. Credit the people who helped, and include the setbacks when they show what you learned or what you stopped from going wrong.

Anchor the number to the role's pay band

There is no percentage that applies to every role change. Set the target from the pay band for the work you now perform, your position within that band, credible external ranges for comparable scope, and the mix of base salary, bonus, and equity.

Before Kristen ever named a number, she had learned where she sat in the internal range, the company's usual increase, and the largest exceptions compensation had approved. She got that from a friend in HR.

Evans adds two points in the same stretch: companies want to pay people near the middle of a band, because someone at the bottom is easy to poach, and wide bands mean there is often real room to move. The range tells you which job the company thinks you're doing. The exception process tells you whether an off-cycle correction is possible and who has to approve it.

• Internal range: Ask for the band tied to the actual level and scope, plus the company's method for placing someone within it.
• Exception process: Ask what an off-cycle adjustment requires and who approves it.
• External market: Compare several credible sources for similar responsibilities, location, company stage, and compensation mix.
• Your target: Choose a specific request you can explain. Avoid treating one website or a universal percentage as definitive.

Ask while the budget can still move

Ask once the wider scope is clear enough to describe and you have evidence that you can carry it. You don't need to wait a full year if the job changed sooner. But before you ask, learn how compensation decisions happen inside your company. Find out:

• When budgets, salary bands, and annual adjustments are set.
• Whether your manager can approve a raise or has to build a case for someone else.
• Whether a material pay change requires a title or level change.
• Which written evidence the compensation or people team expects.
• Whether an off-cycle adjustment is possible and what would justify one.

Timing also means honoring the timeline you agreed to. Kristen's manager asked for four to six weeks while some organizational changes shook out. She did not chase him every few days.

When the window expired, she checked in and asked what her manager needed to move the case forward. That turned a vague "you're on my list" into a concrete assignment: pull together the packet.

A good moment often follows a visible result, the successful completion of a stretch assignment, or confirmation that temporary coverage has become permanent. Give your manager advance notice instead of dropping the request into the last two minutes of a status meeting.

The raise conversation, word for word

Send your evidence summary before the meeting. Keep it to one page when possible: the old scope, the current scope, three to five outcomes, your request, and the relevant decision timing.

If you do not have enough information to name an amount, ask for the band rather than improvising:

If a title change is part of the case, separate the decisions clearly. State the role, level, compensation, and effective date you want. Your manager may support one part before another, and you need to know which part is moving.

His example is about promotion, and the closing question works the same way when your manager has to advocate for a compensation change. Evans is specific that it should be "we," not "how could I earn that." The request stays clear while the conversation shifts to process and support. If you're negotiating a new offer rather than a raise in your current role, the salary negotiation scripts cover anchors, counters, base, bonus, equity, and written offers.

A delay needs an owner and a date

A written recap prevents two people from leaving the same meeting with different understandings. Send it the same day, while the details are clear.

If your manager cannot commit to the outcome, ask them to commit to the next decision point. "I'll look into it" needs an owner and a date before the meeting ends.

Find out what "no budget" actually covers

Don't argue with a budget you haven't seen. Learn what the answer covers. A fixed budget this quarter, a salary-band limit, and a judgment that the role does not warrant more pay all require different next steps. Ask calmly:

• "Is the constraint the timing of this budget, the range for my current level, or the assessment of the role?"
• "When is the next point at which this can be approved?"
• "Who would need to approve it, and what evidence would they expect?"
• "What target are you willing to advocate for?"
• "If compensation cannot change, which added responsibilities should we reassign or deprioritize?"

After hearing a budget constraint, you can ask, "Would it be unreasonable to put the target and the next decision date in writing?" The wording gives your manager room to reject a bad plan while still engaging with a concrete one.

Then choose the response that matches the constraint:

Reset the role if the pay stays put

A permanent refusal changes the scope conversation. If you keep doing the larger job indefinitely at the same pay, that's a decision too, even if nobody says it out loud.

The scope of your job is part of this negotiation. If the company keeps the pay unchanged, ask it to make an explicit choice about the work.

Set your own decision date

Evaluate the quality of the response as carefully as the amount.

• A workable plan: Your manager names the process, target, missing evidence, decision-maker, and date. Deliver your part and review progress at the agreed cadence.
• A vague delay: Your manager is supportive but will not name criteria or timing. Ask once more for a written decision path, and put the follow-up on the calendar before the conversation ends.
• A durable mismatch: The larger scope is permanent, the company will not adjust pay or title, and nobody will reset the workload. Decide whether the experience is valuable enough to accept for a defined period. Otherwise, start testing internal or external roles that match the work you already perform.

If a promised date passes, refer to the written recap:

The mistakes that weaken the case

• Building the case around effort. Long hours provide context. Lead with the responsibility you own and the result it produced.
• Giving your manager a pile of activities. Select the few examples that best show scope, judgment, business impact, and leverage.
• Using a coworker as the argument. Pay inequity may matter, but a comparison can pull the discussion away from the role you perform. Anchor the main case to scope, evidence, and the relevant range.
• Making the request as a surprise. Give the conversation enough time and send the evidence in advance.
• Threatening to leave before you are prepared to leave. An outside offer changes the relationship. Use one only when it is real and you are willing to accept it.
• Accepting "later" without a date. End with an owner, an action, and the next decision point.
• Taking on even more while the request drifts. Confirm priorities and what will be removed before adding another permanent responsibility.

Frequently asked questions

How long should I wait to ask for a raise after taking on more responsibility?

There is no universal waiting period. Clarify the scope when you accept it. Once the work is recurring and you have credible evidence of results, ask for a dedicated compensation conversation. Also learn when budget and pay decisions are made, so your request reaches your manager while they can still act.

Should I ask for a raise or a promotion?

Ask for the change that matches the role. If you have taken on more work at the same level, compensation may be the main issue. If the work carries higher-level scope, decision authority, or accountability, discuss level and title as well as pay. For the promotion path, see how to ask for a promotion.

What should I say if my manager says there is no budget?

Acknowledge the constraint, ask when the next decision can be made, and request a written plan with the target, required evidence, owner, and decision date. If compensation cannot change, discuss which added responsibilities should be reassigned or deprioritized.

Should I name a salary number?

Name a specific target when you have credible information about the internal range and the external market for the actual scope. If you lack that information, first ask for the approved band and how the company places employees within it. There is no single percentage that fits every role, company, or scope change.

What if the extra responsibilities were supposed to be temporary?

Return to the original agreement. Confirm whether the assignment is ending, becoming permanent, or being extended to a specific date. If it is becoming part of the role, discuss title, level, compensation, and which old responsibilities will be removed.

The raise playbook on one page