How to Ask for a Raise: The Manager-Approved Framework That Actually Works

The mental shift: you're not asking for a favor

The single biggest reason raise conversations fail is that the employee treats the conversation as a personal request. It isn't. A raise is a business decision — your manager is deciding whether the value you produce is worth the number you're asking for. When you frame the ask as a favor, the manager evaluates it emotionally. When you frame it as a business case, they evaluate it against the same criteria they use for headcount and budget requests, which is what you want.

The evidence file: build it now, not the week before

Start a running document — call it 'Wins' or 'Impact Log' — the day you start any job, and update it once a week. For every completed piece of work, capture four fields: what you did, the scope (team size, budget, users, timeline), the outcome (with a number), and the counterfactual (what would have happened if you hadn't done it). Six months into the job, you have 25–30 entries. When the raise conversation comes, you're not scrambling to remember; you're picking the five strongest wins that align with the level above yours.

Read your company's compensation rhythm

Every company has an unwritten calendar for raises: annual review cycle, mid-year adjustment, promotion cycle, or 'ad hoc when a manager pushes.' You need to know which one your company uses before you ask. If your company only moves salary at annual review, asking in July is asking the manager to fight paperwork they can't win — and even if they say yes, the raise will come in January. If your company allows ad hoc, you have more flexibility, but you still want to time the ask right after a visible win, not right after a bad quarter.

Benchmarking: what to compare yourself to

Bring three data points to the conversation: (1) the market rate for your role and level in your city or remote market — from Levels.fyi, Payscale, Radford, or an industry-specific benchmark; (2) internal parity if you can get any signal on it — colleagues who've shared numbers, offer letters you've fielded, or a recent counter-offer; and (3) your current salary as a percentage of the market midpoint. If you're 15% below midpoint, that's the primary number you name in the conversation. If you're at midpoint or above, the argument shifts to scope and impact rather than parity.

Timing: the day and week that maximize your chances

Ask in a scheduled 1:1, not on a walk, not in Slack, not after a stressful meeting. Give your manager 3–5 business days of warning by putting 'Compensation conversation' on the calendar invite. Pick a week when the team's numbers are up or a big project just shipped. Avoid Mondays (managers are catching up) and Fridays (managers are wrapping up); Tuesday or Wednesday afternoon is the sweet spot. If your company has a fiscal year, ask 4–6 weeks before planning starts, not after budgets are locked.

What to send before the meeting

48 hours before the 1:1, send a short email — three paragraphs, no attachments. First paragraph names the topic ('I'd like to use our 1:1 on Wednesday to talk about my compensation and next-level scope'). Second paragraph shows you've thought about it ('I've been tracking impact against the [next level] rubric for the last two cycles and I'd like to walk through where I think I'm meeting and exceeding it'). Third paragraph closes with respect ('I know comp decisions involve more than just our conversation — I'm not looking for an answer in the meeting itself, just to align on the case'). This email does three things: it removes the surprise, it primes your manager to think in the same frame you'll use in the meeting, and it signals professionalism.

The 15-minute meeting script

Open by thanking your manager for the time, then move immediately to the case. 'I want to walk through the impact I've had this cycle and how it maps to the next level, then talk about compensation.' Spend five minutes on three wins, tied to numbers and scope. Then name the specific ask: 'Based on the impact and the market rate for this level, I'd like to move to $X — that's a Y% increase and it puts me at the midpoint of the band for the level I'm operating at.' Then stop talking. The silence after the ask is where most candidates panic and undercut themselves; don't. Let the manager respond.

What to do with the manager's response

If your manager says yes on the spot, that's great — get the specifics in writing within 24 hours, including the amount, the effective date, and any conditions. If your manager says 'let me think about it,' ask two clarifying questions: 'What would help you make the case upward?' and 'What's a realistic timeline for a decision?' If your manager says 'we can't do that this cycle, but…', get the 'but' in writing: what specifically has to be true for the raise to happen, on what timeline, and with what proof.

Common manager objections and how to answer

• 'It's not the right time' — 'Understood. What would need to be true for it to be the right time?'
• 'You just got a raise' — 'I did — and my scope has grown since. Here's what changed.'
• 'The budget isn't there' — 'I understand. Is there room for a title change or a mid-year adjustment when the budget opens?'
• 'That's above the band' — 'That's helpful to know. What's the top of my band right now, and what's the top of the next band?'
• 'HR would have to approve' — 'Happy to help you build the case for HR. What would that look like?'
• 'Let's revisit at your next review' — 'Great — can we agree on the specific criteria I need to meet by then?'

What a 'no' actually means (and doesn't mean)

Some 'nos' are structural — the company has a real budget freeze, or your role has a firm cap. Some 'nos' are managerial — your manager doesn't want the political friction of pushing for you, which is a much more serious signal about your future. The way to tell them apart is to ask two questions in the follow-up: 'If the freeze ended tomorrow, would you push for the raise?' and 'What would I need to demonstrate in the next two cycles for you to advocate for a promotion?' If the answers are specific and enthusiastic, it's structural. If they're vague, start looking.

How and when to escalate

If your manager blocks you and you have a strong relationship with a skip-level or with HR, you can escalate — carefully. The move is not 'my manager said no, please override them'; it's 'I'd like to make sure my career development is on track. Can we do a career check-in?' A skip-level who thinks your manager is holding you back will find a way to move you; a skip-level who agrees with your manager will tell you what to work on. Either answer is useful.

The outside offer play — when and when not to use it

An outside offer is the single most powerful raise lever, and also the most dangerous. Only use it if you'd actually take the outside job. Managers can sense a bluff and, even when they match, they often mentally reclassify you as a flight risk. If you go this route, present the offer as an unsought data point: 'I wasn't looking, but this came across my desk and it made me realize I might be undermarket here. I'd rather stay — is there room to close the gap?' Give the manager 72 hours to respond and be prepared to actually leave if they can't.

Follow-through: what to do the week after

Whatever the answer, send a summary email within 24 hours: what you discussed, what was agreed, and what the next step is. This creates the paper trail you'll need for the next raise conversation, and it also holds your manager accountable to what they said in the room. If the answer was 'not this cycle,' put a calendar reminder six weeks out to check in on progress against the specific criteria you agreed on. If the answer was 'yes' or a partial yes, thank your manager once, then get back to work — over-celebrating shrinks your leverage next time.

Why this matters

The advice in this guide is drawn from real recruiter conversations and analysis of what actually moves candidates forward. Apply it as a checklist on your next application.

Put it into practice

Don't try to apply everything at once. Pick the one or two changes that feel most relevant to your situation, ship the update, and measure the response over your next 10 applications.

Common mistakes to avoid

• Treating advice as universal — context always matters
• Over-editing until your voice disappears
• Skipping the proofread because you've read it 30 times
• Forgetting that recruiters are people, not algorithms