How to Bring Up a Raise in a Performance Review | HireFlow

9 min read

Your review is on the calendar and you've decided this is the year you say something. You don't want to sound grabby, you don't want to ruin an otherwise good conversation, and you're not sure whether money even belongs in this meeting.

Here's the part almost nobody tells you. Learning how to bring up a raise in a performance review matters far less than when you first mention it — and by the time you're sitting in the review, the budget has usually already been submitted.

That doesn't mean the meeting is useless. It means you use it differently. And before any of it, make sure your resume reflects the job you actually do now — run it through the free ATS resume checker so you know what your options look like either way.

Why the performance review is the wrong place to start

Most companies run compensation on a planning cycle. Managers get a budget pool, propose increases for their team, send those up for approval, and then deliver the results in review meetings.

So by the time you're in the chair, your manager is often reading out a decision that was made weeks ago by someone else.

That's why a first-time ask in the review so often gets the same reply: warm words, genuine agreement, and no money. Your manager isn't stonewalling you. They just spent their pool in March.

What this is not: a reason to stay quiet. The review is still where you set up the next cycle, and in smaller companies without formal cycles it may genuinely be the decision point. The move is to find out which situation you're in.

What to do weeks before

Step 1: Ask when the cycle runs

One question in a one-to-one, asked neutrally: "When do comp decisions get made here — is it tied to review season or a separate cycle?" Nobody reads that as an ultimatum. It tells you exactly when your ask needs to land.

Step 2: Signal early

A month or two before the cycle closes, say the sentence out loud: "I'd like to talk about my compensation this cycle. What do you need from me to make that case?"

That single line changes your manager's job from defending a number to helping you build one. Most will tell you exactly what evidence their own boss wants.

Step 3: Write the one-page scope summary

Three to five bullets. Each with a number and a month. Send it a few days before the review so it can be pasted into whatever system your manager types into.

Take a customer success manager who first writes this:

"I've had a strong year, taken on extra accounts, and consistently gone above and beyond for the team."

Rewritten so it survives a forward to Finance:

"Since February I've carried 34 accounts, up from 21, after we lost two CSMs. Renewal rate on my book went from 88% to 94%. I've also run onboarding for every new CSM hire since April — four so far."

Same year, same person. The second version is a business case; the first is a feeling. Managers can only escalate the second one.

Edge case: your manager is new

A manager who joined three months ago has no memory of what you absorbed last year. The scope summary matters more here, not less, and it should include the context of what the team looked like before they arrived.

How to bring up a raise in a performance review itself

Let the feedback happen first

Opening with money tells your manager the feedback portion is a formality you're waiting out. Take the review seriously, ask about the development points, then move.

The transition line

Near the end, once performance has been covered, use a clean handoff:

"That all makes sense, thank you. Before we wrap — I sent over the scope summary last week. Given the account load and the onboarding work, I'd like to talk about moving my base to $X. Where does that sit with what's possible this cycle?"

"Where does that sit with what's possible" is deliberately gentle. It invites information rather than forcing a yes or no, and information is what you actually need in this meeting.

Then stop talking

The silence after the number will feel long. Let it. People who fill it usually fill it by lowering their own ask.

Edge case: the review is negative

If the feedback is genuinely critical, don't raise money in the same meeting. Ask what specifically needs to change, agree a checkpoint, and revisit compensation once you've met it. Pushing a number over an unresolved concern reads as not listening.

Edge case: no formal review exists

Plenty of small employers never run one. Book a 30-minute meeting yourself and call it a check-in. The structure above works the same; you just supply the occasion. Our guide to asking for a raise covers that standalone version.

Handling each outcome

• An increase you're happy with. Say thank you and ask when the next review of base happens. Then stop negotiating.
• An increase that's below what you asked. Ask what would move it further next cycle, and whether the gap is band-related or budget-related. Those have different fixes.
• Nothing, with a frozen budget. Ask for a written commitment to revisit at a named date, plus one non-cash item — a title, a course, a conference.
• Nothing, with a band cap. The money is behind a promotion, so the conversation changes entirely. Ask what the criteria for the next level are and get them in writing.

Whichever you get, send the recap email the same day. Two or three sentences: what you asked, what was said, any date agreed. That email is what stops "next cycle" from quietly becoming next year.

Something like this is enough:

{`Hi [Manager],

Thanks for the review today — the feedback on [topic] was useful.

To capture the comp part: I asked about moving base to [number],
and my understanding is [what they said, e.g. "the pool is set
for this cycle, and you'll put it forward in the January
planning round"].

I'll keep the scope summary updated between now and then.

[Your name]`}

Notice it doesn't argue. It just makes the commitment exist somewhere other than one person's memory, which is the entire point.

What your manager is actually working with

It helps to know the shape of the problem on the other side of the table. Most managers are handed three constraints, and your ask has to survive all of them.

A pool, not a per-person budget. Many companies hand a manager a single percentage to distribute across their whole team. Giving you more means giving someone else less, which is why "I'd love to but I can't" is often literally true.

A band with a hard ceiling. Every level has a published range. Once you're near the top of yours, no amount of evidence moves base — the money is behind a promotion instead. Knowing which of these you're hitting changes your entire next step.

A calibration meeting. At larger employers, managers defend their proposed increases to peers. Your scope summary is ammunition for that room, and a manager who likes you but has nothing written down will lose that argument.

So ask directly: "Is this a budget constraint or a band constraint?" Managers almost always answer honestly, and the two answers send you in completely different directions.

A budget constraint is temporary. It means waiting for the next cycle with your evidence already filed, and it usually resolves itself within a year.

A band constraint is structural. The only route to more money is a level change, and no amount of patience fixes that on its own. People burn years waiting out the second one because nobody ever told them which of the two they were in.

A second example: when the job did not grow

Scope arguments only work when scope changed. Plenty of people are doing the same job well and are simply behind the market. That needs different evidence.

Take a warehouse team lead, four years in the same role:

"I've been doing this job a long time and I've never had a proper raise. It feels like I'm falling behind."

The same point, made in a way a manager can carry upward:

"My shift has run at 99% pick accuracy for six straight quarters and we haven't had a recordable safety incident since I took over. Team lead roles in this area are posting between $X and $Y right now. I'm at $Z. I'd like to get into that band."

Consistency is a real argument, but only once it has numbers attached. "Never had a raise" is a complaint. "Six quarters at 99%" is a record.

Edge case: you are remote and your manager is not

Distributed teams lose the incidental visibility that usually builds a case. If your manager doesn't see your day, the written summary is doing all the work. Send it earlier than you would otherwise, and include the things that would have been obvious in an office — the escalations you absorbed, the people who route questions to you.

Edge case: your review is late or keeps slipping

A repeatedly postponed review is worth reading as information. Ask whether comp decisions are moving with it. Sometimes the cycle has already closed and the meeting is a formality, in which case your ask belongs in the next planning window and you should find out when that opens.

Mistakes that derail the review

• Leading with money. It reframes the whole hour and makes the feedback feel like an obstacle you sat through.
• Arguing tenure. "I've been here four years" is not a case. Four years of growing scope is.
• Comparing yourself to a colleague by name. The conversation stops being about you within one sentence.
• Accepting "let's revisit" without a date. A revisit with no month attached is a decline in a softer voice.
• Waiting until the review to say anything at all. The most common and most expensive mistake on this list.

Know what the market says before you sit down

The quiet advantage in this meeting is knowing what your role pays elsewhere. Not to threaten with it. Just so the number you name isn't a guess.

Open a few live postings for your title, then check whether your own resume reflects the scope you're about to describe. Upload it to the free ATS resume checker and look at the experience section specifically. If you've been running onboarding for six months and your resume still describes the job you were hired into, that gap is worth closing whatever the review decides.

If the answer is a no with no date, and you decide to look, the cover letter generator will build the letter around the bigger job rather than the old title.

The short version

• How to bring up a raise in a performance review starts weeks earlier, when the budget is still open.
• Send a one-page scope summary with numbers and dates before the meeting.
• Raise the number near the end, then ask what is possible rather than pushing for a yes.

Do this today: send your manager one line asking when comp decisions get submitted. That answer decides everything else about your timing.

And make sure your file matches the job you're describing. Check your resume for free before the meeting, not after it.

Read more

• How to ask for a raise — the standalone conversation, outside review season.
• Can you get fired for asking for a raise? — what the risk actually is.
• How to ask for a promotion — when the money sits behind a level change.