How to Ask Your Boss for a Raise: Scripts and Examples
How to ask your boss for a raise comes down to three things: timing the conversation, naming a specific number, and backing it with evidence your manager can repeat to their own boss. Most people get the first two wrong and skip the third entirely, which is why the answer so often comes back as a vague "let's revisit this later." Below are word-for-word scripts for the meeting request, the conversation itself, and every response you are likely to get, plus a calculator to work out what to actually ask for.
Free Raise Calculator
What Should You Actually Ask For?
Work out the number before the conversation, not during it. Leave a field at 0 if you do not know it yet.
Disclaimer: This article is general career guidance, not legal, tax, or financial advice. Pay practices, salary ranges, and pay transparency rules vary by employer, state, and locality. If you believe a pay decision involves discrimination, retaliation, or a violation of your employment agreement, speak with an employment attorney licensed in your state, or contact the EEOC, rather than relying on a negotiation script.
Last reviewed: September 2026.
Before You Ask: The Four Things to Have Ready
The conversation is short. The preparation is what decides how it goes.
A number, not a range. Ranges get answered at the bottom. If you want 8%, ask for 8% or for the specific salary figure it produces. Naming a figure also signals you have done the work, which changes how the request is received.
Three to five specific accomplishments, with outcomes attached. Not "I've worked hard this year." Something closer to "I took over the vendor scheduling in March, we've had no missed deliveries since, and it freed up about six hours a week on your side." Numbers are ideal, but a before-and-after works when you do not have them.
Market data for your role. A salary range from a reputable source for your title, region, and experience level. The Bureau of Labor Statistics publishes free occupational wage data by area, which carries more weight in a conversation than a crowd-sourced figure. This is context, not a threat, and it should be delivered as information rather than leverage.
A read on the budget cycle. Find out when compensation decisions are actually made at your company. Asking two weeks after the budget locks means the answer is no regardless of merit, and the single most common reason a good case fails is timing.
Raise Conversation Prep Checklist
- Specific number or percentage decided in advance
- Three to five accomplishments with measurable or observable outcomes
- Market data for your title, location, and experience
- Date of your last raise and what has changed in the role since
- Your company's budget and review cycle timing
- A written summary you can send after the meeting
- Your fallback ask if the answer is no on salary
- A decision made in advance about what you will do if the answer stays no
Script 1: Requesting the Meeting
Never ambush your manager with this in a hallway or at the end of an unrelated one-on-one. Ask for the time, and say what it is about, so they can prepare and can bring anything they need to check first.
Email or message:
"Hi [Name], could we set up 20 minutes sometime this week or next? I'd like to talk through my compensation and where things stand after the last year. Happy to work around your schedule."
That is the whole message. Do not make the case here. You want the discussion live, where you can respond to what they say, and you want them to arrive knowing the topic rather than feeling blindsided by it.
Script 2: The Core Ask
Open with the point. The instinct is to build up to it with context, and it almost always reads as apologizing in advance.
"Thanks for making time. I want to talk about my salary. I've been in this role for [time period], and since [reference point] I've taken on [specific additions]. Based on that and on what I'm seeing for this role in our market, I'd like to discuss moving my salary to [specific number]. I wanted to bring it to you directly and hear how you see it."
Then stop talking. The silence after the number is uncomfortable and it is doing work. Most people fill it by softening the ask, and that gives away the position before the other side has even responded.
Script 3: Backing It With Evidence
When your manager asks for the reasoning, keep it to three items and make each one concrete.
"Three things, mainly. First, I took over [responsibility] in [month], which wasn't part of my role when I started, and [outcome]. Second, [project or improvement] led to [result]. Third, I've been training [person or team] on [process], which has [effect]. My salary hasn't changed since [date], and the market range I'm seeing for this role is [range]. That's what puts me at [number]."
One thing to avoid: personal need. Rent increases, a new baby, and a partner's job loss are all real, and none of them are arguments your manager can take upstairs. The case has to be about the value of the role and your performance in it, because that is the only version that survives being retold to a finance director.
Script 4: When They Say There's No Budget
This is the most common response and it is often true. The goal shifts from getting a yes today to getting a commitment with a date attached.
"I understand budgets are set. Can we look at what's possible at the next cycle? I'd like to agree on what the number would be and what you'd need to see from me between now and then, so we're not starting this conversation over in six months."
Then ask the question that matters: "What would need to be true for this to be approved?" If the answer is specific, you have a path. If the answer stays vague after you have asked twice, that is information too.
Script 5: When They Say It's Not the Right Time
"That's fair. Can we put a date on it? If we revisit in [specific month], I'll put together where things stand between now and then. Does that work?"
Get the date in writing afterward, in a short follow-up email. Not as a gotcha, but because managers change, priorities shift, and a verbal agreement made in March rarely survives to September in anyone's memory.
Script 6: When They Ask What You're Looking For
Sometimes the number question comes back at you before you have made your case. Answer it directly rather than deflecting.
"I'm looking at [specific number]. That's based on [brief reason: market range, scope added, time since last adjustment]. I'd rather give you a real figure than a range so we're working with the same information."
Script 7: When the Answer Is a Smaller Number
A counteroffer is a good outcome, not a rejection. Treat it as the start of the negotiation rather than the end of it.
"I appreciate you coming back with something. It's below where I was hoping to land. Is there flexibility to get closer to [your number], or could we bridge the gap with [specific alternative] and revisit the base at the next review?"
Useful alternatives when the base salary is genuinely capped: a one-time bonus, a title change that moves you into a different band, an additional week of PTO, a schedule change, a professional development budget, or a scheduled review at a fixed date with an agreed figure. Get whatever you agree to in writing.
Script 8: When You Have a Competing Offer
Only raise this if you are prepared to take the other job. Used as a bluff, it works exactly once and costs more than it gains.
"I want to be straightforward with you. I've received an offer at [figure], and I wasn't looking. I'd rather stay, and I'm telling you before I make a decision rather than after. Is there room to close that gap?"
Be ready for a yes that comes with a changed relationship, and for a no that arrives faster than you expected. Both happen.
Script 9: The Follow-Up Email
Send this within a day, whatever the outcome. It creates the record, and the record is what the next conversation starts from.
"Hi [Name], thanks again for the conversation today. To summarize what we discussed: [the ask], [their response], and [the agreed next step and date]. Let me know if I've misstated anything. I appreciate you hearing me out."
Short, neutral, and specific. It is not a negotiating tactic, it is a way of making sure two people remember the same meeting the same way.
Timing: When to Ask
The best moments are shortly after a visible win, during the run-up to the budget cycle rather than after it, after you have absorbed new responsibilities that were not in the original role, or at a formal review when compensation is already on the agenda. Six months to a year in a role is usually the earliest a raise conversation lands well, unless the job itself has materially changed.
The worst moments are predictable: right after layoffs or a bad quarter, in the middle of a crisis your manager is firefighting, immediately following a mistake of yours, or on a Friday afternoon. Also avoid the week your manager is dealing with their own review, since they have limited capital to spend and will not spend it then.
Mistakes That Sink the Ask
- Apologizing for asking. "I hate to bring this up, but..." undercuts everything that follows. It is a normal professional conversation.
- Leading with personal expenses. Real, but not an argument your manager can carry to anyone else.
- Comparing yourself to a coworker. It shifts the conversation to salary confidentiality and away from your value, and it rarely ends well.
- Threatening to leave without meaning it. You only get to do this once, and the aftermath outlasts the raise.
- Accepting a vague "later" without a date. Later is not a commitment, it is a way to end the meeting.
- Not asking what would need to be true. This one question turns a no into a plan more often than anything else you can say.
If the Answer Is No
Ask for specifics: what would need to change, by when, and what the number would be if it did. Get it in writing. Then take the answer seriously in both directions. A manager who gives you a clear path and hits the date has told you the system works. A manager who cannot articulate any path, twice, has told you something equally clear.
Keep a running record either way. Note what you took on, what changed, and what the results were, month by month, while it is fresh. The single most common reason these conversations go badly is that people try to reconstruct a year of work from memory the night before, and end up with three vague claims instead of five specific ones.
For Managers on the Other Side of This
If you are the one receiving the ask, the worst response is a vague deferral, because it produces a quietly disengaged employee who starts interviewing. Even when the answer has to be no, a specific one preserves the relationship: what the constraint is, when it changes, and what would move the number.
The structural fix is making sure these conversations do not arrive as surprises. Where goals, review history, and performance notes are tracked in one place rather than reconstructed annually, both sides come to the meeting with the same facts. In Updoot, goals and review history sit on the employee record, and KPI tracking keeps the results attached to the person who produced them, so a compensation discussion starts from evidence rather than from two different memories of the same year.
Frequently Asked Questions
Open with the topic directly, state a specific number, and give three concrete reasons. A working version: "I want to talk about my salary. Since [date] I've taken on [responsibilities], and based on that and the market range for this role, I'd like to discuss moving to [specific figure]." Then stop and let them respond. Avoid apologizing for asking and avoid personal financial reasons, since neither helps your manager make the case to their own boss.
For a standard merit increase where the role has not changed, 3% to 5% is typical. Where you have taken on significantly more scope or are below market, 8% to 15% is a reasonable ask. If you are moving into a new title or level, the increase can be larger. Anchor the figure to market data for your title, location, and experience rather than to a percentage that feels bold, and name a specific number instead of a range.
Request the meeting by email, then have the conversation live, in person or on video. Email is the right medium for scheduling and for the follow-up summary, but it is a poor place to make the case, because you cannot respond to objections in real time and your manager may need to check budget before answering. Do send a short written recap afterward capturing the ask, the response, and the agreed next step.
Shortly after a visible win, before the budget cycle locks rather than after, once you have absorbed responsibilities beyond your original role, or at a scheduled review where compensation is already on the agenda. Find out when compensation decisions are actually made at your company, because a strong case delivered two weeks late gets deferred for a full cycle regardless of merit.
Shift the goal from a yes today to a commitment with a date. Ask what would need to be true for it to be approved, agree on a specific figure and a revisit date, and confirm both in a short follow-up email. If base salary is genuinely capped, ask about a one-time bonus, a title change into a different band, extra PTO, a schedule change, or a development budget instead.
Only if you are genuinely prepared to accept it. A bluff works once and damages the relationship permanently when called. If the offer is real, be straightforward: say you received it, that you would rather stay, and ask whether there is room to close the gap. Expect either a fast no or a yes that changes how you are viewed, and be ready for both before you raise it.
Final Takeaway
Decide the number before the meeting, ask for it in the first thirty seconds, support it with three specific results rather than effort, and leave with a date attached to whatever you were told. Most raise conversations fail for one of two reasons: the person never named a figure, or they accepted a vague promise and had no record of it six months later. Both are fixable with fifteen minutes of preparation and one follow-up email.