How to Ask for a Raise
Most raise requests fail for reasons that have nothing to do with the ask itself β wrong timing, no evidence, or asking the person who can't actually approve it. Fix the mechanics first.
In Payscale's 2023 Raise Anxiety survey, 60% of employees who asked for a raise received one, but only 44% of women who asked received the full amount requested, versus 51% of men.
Source: Payscale Raise Anxiety Survey, 2023
Employees who never ask for a raise see their pay grow almost entirely through annual merit increases, which have averaged roughly 3-4% per year in recent WorldatWork salary budget surveys β below cumulative inflation in several of those years.
Source: WorldatWork Salary Budget Survey
Most companies set their annual merit increase budget 2-4 months before the review cycle starts β meaning a raise request made during the review conversation itself usually arrives after the money has already been allocated.
Source: Common corporate compensation planning cycle, documented in WorldatWork compensation planning guidance
How This Actually Works
Your manager almost never has unilateral authority to give you a raise
In most mid-size and large companies, a raise outside the annual cycle requires your manager to build a business case and get approval from their own manager, HR business partner, and sometimes a compensation committee. Your manager is your advocate in that process, not the decision-maker β which means your job isn't just to convince your manager, it's to give your manager ammunition they can use one or two levels up.
This is why a request that sounds reasonable in the room can still get a 'let me look into it' and then silence. The manager agreed with you, took it upstairs, and it got deprioritized by someone who never heard your pitch directly. Asking 'what does this need to look like for you to take it to [their manager]?' puts the real approval chain on the table instead of treating your manager as the final decision-maker.
Raise budgets are set before most raise conversations happen
Annual merit increase pools are usually finalized by finance and HR leadership months before individual review conversations happen, and department budgets are often fixed further ahead of that. If you wait until your annual review to make the case, you're negotiating for a slice of a pie that was already baked β your manager may have zero discretionary budget left regardless of how good your case is.
The fix is timing the ask to land before budget planning closes, not during the performance review itself. If you don't know your company's planning cycle, ask your manager directly: 'When does the budget for next year's raises typically get set, so I can make sure I've made my case before that happens?' This is a completely normal question and most managers will answer it honestly because it helps them help you.
'Market rate' and 'merit' are two different arguments β know which one you're making
A market-rate adjustment argues that your pay has fallen behind what the role is worth externally, independent of your performance β this is usually the stronger argument and the hardest for a manager to refuse, because it's framed as a correction, not a reward. A merit-based raise argues you've outgrown your current pay band through performance or expanded scope β this requires your manager to make a performance case, which is softer and more easily deprioritized.
The strongest asks combine both: 'I've taken on [specific expanded scope], and when I look at market data for someone doing this scope, my current pay is below range.' That gives your manager two independent justifications to bring upstairs instead of one.
Scripts You Can Use
"Hey [Manager], I'd like to set up 20-30 minutes in the next couple weeks to talk through my compensation. I've put together some context I want to walk you through β not looking for an answer on the spot, just want to start the conversation. Does sometime next week work?"
Why it works: Scheduling a dedicated conversation signals this is a planned, serious ask rather than an impulsive complaint, and gives your manager time to prepare rather than being caught flat-footed β a prepared manager is more likely to engage constructively than a defensive one.
"I've been looking at market data for my role β specifically [source, e.g. 'levels.fyi' or 'a recruiter who reached out' or 'Payscale'] β and the range for someone with my scope and tenure is [range]. I'm currently at [your pay], which puts me [below/at the bottom of] that range. I wanted to bring this to you directly so we can figure out a path to close that gap."
Why it works: Naming a specific number range and source makes the ask concrete and verifiable rather than a vague feeling of being underpaid, which is harder for a manager to act on even if they agree with you.
"Over the last [timeframe], I've taken on [specific responsibility #1] and [specific responsibility #2], which weren't part of my role when we set my current pay. I'd like to talk about adjusting my compensation to reflect that expanded scope."
Why it works: Naming specific, dated responsibilities (not 'I've been working really hard') gives your manager concrete evidence they can repeat verbatim to their own manager when making the case upstairs.
"That makes sense β can we set a specific date to follow up, so this doesn't lose momentum? And is there anything specific you'd want me to document or provide that would help you make the case?"
Why it works: This converts a vague 'I'll look into it' into a committed follow-up date and gives you visibility into what evidence actually moves the approval chain, instead of waiting in the dark.
"I appreciate you being direct about that. Can you help me understand what would need to be true for this to be possible in the future β whether that's scope, timing, or budget β so I know what to work toward?"
Why it works: This reframes a closed door into a concrete target rather than an open-ended grievance, and signals you're staying constructive rather than checked out β which matters if you decide to stay and try again later.
Copy-Paste Templates
SECTION 1 β Scope change since last compensation review: [list concrete responsibilities added, with dates] SECTION 2 β Impact/results: [2-3 quantified outcomes tied to the above scope, e.g. "Led migration that reduced [metric] by [amount]"] SECTION 3 β Market data: [range + source(s), noting your current pay relative to that range] SECTION 4 β Specific ask: [target number or range, and whether you're open to a phased increase]
Why Most People Get This Wrong
β Asking during the annual performance review conversation itself.
Budget pools for that cycle are typically already finalized by the time the review conversation happens, so even a manager who agrees with you may have no discretionary budget left to act on it until the next cycle.
Instead: Ask 2-3 months before your company's budget planning window closes, and ask your manager directly when that window is if you don't know it.
β Leading with a competing offer as leverage without being willing to actually take it.
If your company counters and you stay, you've signaled you're a flight risk, which paradoxically can affect how you're prioritized for future opportunities and raises β and if they don't counter, you've burned the leverage with nothing to show for it.
Instead: Use a competing offer as leverage only if you're genuinely prepared to take it if they don't match β otherwise negotiate from your actual value and market data, not a bluff.
β Making the ask entirely about personal financial need (rent went up, had a baby, etc.).
Personal financial need isn't something your manager can take upstairs as a business justification β compensation committees approve raises based on market position and performance, not personal hardship, so this framing gives your manager nothing usable even if they're sympathetic.
Instead: Keep the business case (market rate, scope, performance) as the primary argument. Personal context can be mentioned, but it shouldn't be the reason given to approvers.
β Vague language like "I feel like I deserve more" without a number or range attached.
Managers can't act on a feeling. Without a specific number or range, the most likely outcome is a sympathetic but non-committal response that goes nowhere because there's nothing concrete to evaluate or escalate.
Instead: Always attach a specific number or range, sourced from market data, so there's something concrete on the table to approve, counter, or escalate.
Action Plan
- 1
Find out your company's budget planning cycle (ask your manager directly) and target your ask 2-3 months before that window closes.
- 2
Gather market data for your specific role, level, and location from at least one credible source (levels.fyi, Payscale, a recruiter conversation, Glassdoor salary data for your exact title).
- 3
Write a one-page case document covering scope changes, quantified impact, market data, and a specific ask.
- 4
Schedule a dedicated conversation β don't ambush an existing 1:1 or spring it at the end of an unrelated meeting.
- 5
Make the ask with a specific number or range, not a vague request for 'more.'
- 6
If the answer is deferred, lock in a specific follow-up date and ask what would help build the case.
- 7
If the answer is no, ask what would need to be true for it to be possible later, so you have a concrete target instead of an open-ended grievance.