How to Ask for a Raise: Build Your Case First
Many employees treat a raise as a test of courage. It isn't. It's a test of calibration, whether you can tell if you're underpaid, what the role is worth now, and what evidence a decision maker needs to approve a change. Get that calibration wrong and even a confident script works against you.
Table of Contents
- Why Most Raise Requests Turn on Preparation
- Checking Whether You Are Underpaid Before You Ask
- How to Build a One-Page Raise Case
- When and Where to Make the Request
- Scripting the Opening and Answering Objections
- Get a Written Answer or a Dated Review Plan
Why Most Raise Requests Turn on Preparation
Asking usually pays. The CNBC report on LendingTree's survey of 2,049 consumers found that in 2024, 82% of full-time U.S. workers who asked for a raise received one. That's a strong reason not to wait, but it doesn't predict your outcome. A survey average can't tell your manager why your pay should change.
What carries weight is narrower. Managers approve requests they can defend to someone else, usually with expanded scope, measurable results, and a credible market range. Effort alone is hard to approve because effort is hard to compare. A result with a number attached isn't.
Two paths reliably end in a missed raise. The first is waiting for recognition. Your manager may notice good work and still reserve the limited budget for people who made a clear case. The second is walking in with a feeling instead of a figure. If you can't say where your pay sits, what changed in the role, and what number you're asking for, you're asking your manager to build your case for you.
If you want supporting context on workplace patterns before you start, the workplace data guides from Statlyst are useful background, but your own evidence matters more. Start now by writing down the last three months of work as outcomes rather than tasks. Don't list meetings attended or projects supported. Write what improved, what you owned, and how you'd prove it. That raw material becomes the brief you'll refine.
Courage gets you into the room. Preparation gives your manager something approvable.
Checking Whether You Are Underpaid Before You Ask
Feeling underpaid is weak evidence, even when the feeling is strong. The Payscale Pay Confidence Gap analysis found that 63% of employees who were paid at market believed they were below market, and 47% of employees paid above market held the same belief. Another analysis in that report found only 32% of people who believed they were paid unfairly were below market. That doesn't mean you aren't underpaid. It means you need better evidence than your gut.
This is what that evidence gathering looks like in practice.
Triangulate Instead of Copying One Number
Start internally. Ask HR or your manager for your level and salary band, and where you sit in that band. That's the evidence your manager can actually act on. Then check published postings and compensation surveys, matching level, location, and scope as closely as you can. A senior title at a small company may carry less scope than a mid-level title somewhere larger, so titles alone mislead.
Compare total rewards, not just base salary. Bonus target, equity, retirement match, and paid time off can close or widen a gap that base pay alone hides. If base is low but bonus and equity are strong, your ask changes. If everything lags, your case is clearer.
| Source | What It Tells You | How Much Weight to Give It |
|---|---|---|
| Internal salary band for your level | Where you sit within the range for your role | High, if you can see it |
| Pay range in a published job posting | Market range for similar roles in your location | Medium, if the role matches your scope |
| Compensation survey for your job family | Median and percentile pay by level and region | Medium to high, check the sample size |
| Online salary estimate | Rough averages from self-reported data | Low, use only to spot large gaps |
| Recruiter or peer conversation | Pay for comparable scope at other companies | Low to medium, verify with a second source |
This walkthrough shows how to sort conflicting numbers into a range you can defend.
Name the Right Diagnosis Before You Choose an Opening
Separate three situations, because each needs a different first line. If you're below market for comparable work, lead with market data. If you're compressed relative to peers doing similar work, or new hires joining at higher pay for the same scope, lead with scope and internal alignment. If the system is unclear and nobody will share a band, lead with a process request. Ask how pay is determined for your level, request the band, document scope changes, and ask for a review date if an adjustment isn't possible now.
That last move matters more than people think. When you don't know how to ask for a raise in an opaque system, asking for the criteria is a legitimate outcome. It also connects to longer term choices. Our career path planning resources can help you judge whether the next level, not just the next raise, is the key lever.
Calibration first. Don't spend your credibility on a precise number built from imprecise evidence.
How to Build a One-Page Raise Case
A one-page brief forces discipline. Your manager can read it in two minutes, forward it, and use it in a calibration meeting you won't attend. Length isn't the point. Every line has to help someone say yes.
The Harvard Program on Negotiation salary report, reviewing 149 professionals, found people who negotiated increased starting pay by an average of $5,000, with competing and collaborating approaches performing best, while compromising and accommodating were not associated with salary gains. For an incumbent raise, borrow the discipline behind that finding. Benchmark first, quantify value second, make a specific request third, then negotiate trade-offs without filling the silence.
The Six Parts of the Brief
Map scope before and after. Put last year's responsibilities next to today's, one line each for ownership, people managed, budget, and customers. Write, for example, "Then, supported regional pricing. Now, own pricing decisions for two regions." That contrast is the backbone of the case, because it shows the role itself changed, not just your workload.
Pick three to five proof points and quantify each. Choose revenue influenced, costs cut, deadlines met, risks removed, or hours saved. Copy this structure and adapt it: "Rebuilt the renewal process and lifted retention on the account book from 88% to 92% over two quarters." If you can't quantify a win exactly, quantify the scale, such as accounts covered, tickets cleared, or cycle time reduced. Vague claims like "improved collaboration" give your manager nothing to repeat upward.
Set the market range. Use the triangulation method you already worked through, matching level, geography, and scope, and count total compensation. State the range plainly, for example, "Comparable roles in this market sit between X and Y, and my current base sits below that range." Don't present a single website estimate as fact. A range built from two or three sources is harder to dismiss.
Write one clear ask. Name a specific salary or percentage tied to that range, with an effective date. For example, "I'm asking for a salary of X, effective next quarter." A clear ask lets your manager respond to something concrete. "I'd like more" invites delay because nobody knows what yes looks like.
List fallback options before the meeting. Decide in advance what else has value, such as a bonus, equity, title change, review in 90 days, or development budget. Fallbacks give your manager something to approve if base salary is frozen. They also stop you improvising under pressure and accepting a vague promise you'll regret later.
Keep it to one page and handle distribution deliberately. Send it ahead only if your manager prefers reading first. Otherwise bring two copies and walk through it. If you're drafting the accomplishments section, our self-evaluation examples can help you turn tasks into outcome language before you compress it.
What to Leave Out
Leave out tenure, inflation, and personal bills. They explain why you need money, not why the role is worth more. Managers don't set pay from your expenses, and leading with them moves the conversation onto ground you can't win. Keep the frame on sustained contribution and expanded scope.
I would cut anything you can't support if challenged. If a number came from a dashboard, know which one. If a scope change happened informally, note when you took it on and who assigned it. One unsupported claim makes a manager doubt the rest.
Your brief should make approval feel like documentation, not persuasion.
When and Where to Make the Request
Frustration is a poor timing trigger. If you ask the week after a painful deadline or a rough review, your manager hears a request about your mood, not the role. Even a fair case lands badly when it sounds like compensation for a bad month. Wait until you can present the same evidence calmly.
Windows That Strengthen Your Case
Timing works when your value is fresh and the money is still movable.
- After a project lands. Results are visible, stakeholders remember your role, and the numbers are close at hand.
- When you take on a new responsibility. The scope change is the reason for the conversation, and it's easier to price a role as it expands than a year later.
- Before the budget closes. Managers allocate finite pools. Once decisions are locked, even supportive managers have little to move.
- When the market visibly moves. A peer hire or a new posting for similar work gives you current, concrete context.
Check the company calendar for when budgets and compensation cycles are set, then plan to ask a few weeks before that closes. Avoid layoffs, hiring freezes, and the days right after a budget cut announcement. In those windows, a no tells you about the company, not your case, but it still spends the conversation.
Set the Meeting Up Properly
Don't catch your manager in a hallway or tack this onto the end of a packed one-to-one. Request a dedicated meeting in writing. Keep the note short: "I'd like 30 minutes next week to talk about my compensation and how my role has grown." That gives your manager time to prepare instead of reacting defensively.
Before the meeting, confirm three facts. Who makes the final decision, when the budget is set, and whether off-cycle adjustments are allowed. Your manager may be your advocate, not the approver, and that changes what they need from you.
If the cycle has already closed, don't force a debate about money that can't move. Ask for the next cycle date and the criteria it will use, then put that date on your calendar before you leave. You've still moved the request from a hope to a scheduled decision.
Scripting the Opening and Answering Objections
Rehearse a 30-second opening that names the purpose, the evidence, and the ask. Say it aloud twice before the meeting, out loud, not in your head. You'll hear where it rambles and where you hedge. Cut it to the one or two points that carry the most weight.
Use this structure and replace the details with yours: "I'd like to talk about my compensation. Over the past year I've taken on the regional pricing work and delivered a 12% margin gain. Based on the market range for this role, I'm asking for a salary of X, effective next quarter."
Then stop talking.
Silence after the ask gives your manager room to think. Filling it with apologies, extra justification, or a lower number teaches them your first figure wasn't serious. Discomfort is not a signal to negotiate against yourself. If you want help tightening a draft before the meeting, you can text Lauren your situation and a draft, and she helps make it specific and fair and preps you for the conversation. Users also text Lauren what they want to say, and she helps them pick the one or two points worth making and say them calmly.
Read Objections as Information
An objection tells you what's blocking approval. Treat "no budget" and "show more impact" as different problems, because they need different responses. Repeating your number louder doesn't solve either one.
If you want broader tactics while you prepare responses, the salary negotiation advice from Mojolin is a practical companion, especially for thinking through trade-offs. Our guide to speaking up at work also helps if your main obstacle is saying the opening line without softening it.
| Objection | What It Usually Means | Response to Prepare |
|---|---|---|
| There is no budget | The timing or approval is the issue, not your case | Ask what would need to be true for a review, then agree on a date |
| Show me more impact | Your case lacks a clear link to business results | Name two outcomes with numbers and ask which metric matters most to them |
| We will revisit this later | The answer is not yes yet | Ask for a specific date and the criteria, and write them down |
| You are already well paid | They see the current salary as enough | Restate the scope change and the market range rather than your personal needs |
Work through what each response sounds like in your voice. For "no budget," try, "I understand the timing. What would need to be true at the next cycle, and can we agree on the criteria and date now?" For "show me more impact," don't list every task you did. Name two quantified outcomes, then ask which metric matters most to them for the next review. That question turns a vague challenge into a target you can hit.
For "we will revisit this later," pin it down. "Later" is where raise requests go to die. Ask, "Can we set a date and agree on what success looks like by then?" For "you are already well paid," return to the brief. Restate the scope change and where the role sits against the range. Don't argue about fairness in the abstract.
Two Lines to Avoid
Don't issue an ultimatum without a credible alternative. If you say you'll leave and you won't, you've damaged trust and gained nothing. Don't demand a percentage without a defensible anchor either. A number needs a range behind it, or it sounds invented.
If the answer is no on salary, negotiate trade-offs from your fallback list rather than repeating the figure. A bonus, a dated review, or a development budget keeps momentum and creates a record that the conversation happened. Knowing how to ask for a raise includes knowing what else a yes can look like.
Answer the objection you've been given, not the rejection you're afraid of.
Get a Written Answer or a Dated Review Plan
Every meeting ends in one of three outcomes, yes, deferred, or no. Each one needs a written follow-up within 48 hours. Memory is unreliable, managers change, and verbal agreements get reinterpreted. The email you send after the meeting is part of the negotiation, not admin.
The Harvard Program on Negotiation guide to negotiating pay reports that 78% of people who negotiated an offer received a better offer, including 51% whose salary request was fully matched and 27% who received a somewhat higher offer. Those figures concern job offers, not incumbent raises, so treat them as behavioral guidance rather than a promised raise rate. Your outcome still depends on performance evidence, pay policy, budget, and manager authority.
Close Each Outcome Properly
- If it's yes. Send an email restating the salary, effective date, and any other changes, and ask your manager to confirm in writing. Check the first payslip after the effective date.
- If it's deferred. Agree on a dated next step, the metrics that will be judged, and who makes the final call. Put the date in both calendars before you leave the room.
- If it's no. Ask what would change the answer, what threshold you'd need to meet, and when you can return with new evidence. Write that down too.
Watch the common pitfalls. Don't accept vague promises like "we'll look after you." Don't compare confidential coworker salaries carelessly, since partial information undermines an otherwise clean case. Above all, don't leave without a next date. A deferred raise with criteria and a date is a plan. A deferred raise without them is a polite no.
If the answer is no and your market evidence shows you're below market, plan your next move ahead of time rather than in the hallway afterward. You can ask for a formal review during the next cycle, record the outcome, and explore opportunities outside your current employer. An external offer is the only real advantage you have, and you should only use it if you're ready to act on it.
Support around the meeting helps you hold the line on these details. You can ask Lauren to check in, or let her offer, and she texts the morning of a big meeting and again afterward to debrief. Lauren also asks a question or two before advising, then gives a plan, a script, a reframe or honest pushback, followed by one small next step rather than a homework list. I would use that structure even on your own. One clear next step, dated, is worth more than a long list of intentions.
Pick the date of your next check-in before you leave the room. That's the difference between asking once and running a process that ends in a decision.
If you're rehearsing your opening, tightening a draft, or deciding what to do after a stalled answer, Acheloa Wellness, Inc. offers Text Lauren, a text-based executive coach you can reach by SMS for in-the-moment help with exactly these compensation conversations. Text your situation and your draft, get a specific script and one clear next step, and walk into the meeting knowing what you'll say and what you'll ask for in writing.
